Many a corner office I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome. Dorian Taylor, Agile as Trauma surpriseplanning
In ways you didn't anticipate A Quote by Patrick Hebron www.noemamag.com I always have a hard time wrapping my mind around some of the classic user questions: What is this thing for, is it for novices or professionals, etc? I do my best to avoid these questions, because the best thing you can possibly accomplish as the maker of a tool is to build something that gets used in ways you didn’t anticipate. If you’re building a tool that gets used in exactly the ways that you wrote out on paper, you shot very low. You did something literal and obvious. All sorts of ways to use the machineHacking is the opposite of marketingStretching the productThis tactile form of doodling toolssurpriseux
Two kinds of usability An Article by Ryan Singer world.hey.com I divide usability problems into two kinds: Perceptual: "They couldn't figure out what to do next", "they couldn't find the feature", "they didn't know they could click that button..." etc. Domain-specific: "We need a way to jump back here because in their workflow this happens..." In general, usability testing only catches type 1 perceptual problems. Because in those tests you take people out of the real world and assign them tasks. Usability testing doesn't catch domain-specific problems because they only come up in real life use. uxethnography