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
Skeleton, Organs, Circulation, Sinew, Skin An Article by Dorian Taylor I’m concerned with how I witness the work of user experience practitioners getting treated: like it’s just a set of motions toward a product’s all-important implementation, and one that we try to compress, due to its ostensible superfluity. Once the implementation is finished, the UX work appears to usually get discarded. Tracing the answer backThe UX coral reef ux
Tracing the answer back I submit that the materials that form the precursors to a product’s implementation have considerable value on their own. My vision is that I will be able to ask a question as mundane as one about the wording of a single button, and trace the answer all the way back to the overarching business strategy to see that it makes sense. decisions
The UX coral reef It isn’t a site, or a service, or even an identifiable product at all, but rather a system for creating a skin around and connective tissue between things like: Demographic studies Contextual inquiries Stakeholder and user interviews Surveys The business ecosystem Personas Scenarios Sketches, storyboards, wireframes Mockups, models and prototypes Email and IM conversations Meeting notes Content inventories and audits Concept schemes, taxonomies, thesauri A UI style guide A branding and visual identity guide A voice and tone guide A code style guide ...etc The individual elements of such a corpus represent the work of half a dozen specialist sub-disciplines, and are useful for realizing a product’s implementation. But if you hook them all up together, they merge to become a strategic artifact that transcends products and operates as a critical control surface for the business. This is because what such an artifact represents is a coral reef of deeply-considered and hard-fought decisions, and a story of the process that yielded them. connection