In an effort to speed up iterations and get prototypes in from of peoples eyes much sooner, I spent significant time this past year trying to convince the team to both pare down their documentation and form a studio approach to collaboration. I hadn’t realized that this strategy fell under the lean UX umbrella. But as I read through Lean UX by Jeff Gothelf it seems like a convenient label.
… the lean start-up method to product design, a strategy that implies fast-paced experimentation and validation. It works like this: Prototypes are turned out as fast as possible to test market assumptions early on. This early testing then generates feedback almost instantly, telling you what works and what doesn’t. This way, inaccurate assumptions and weak ideas can be scrapped with little effect, freeing up the resources for your best ideas to flourish.
… design processes normally involve a design team being briefed by someone else, and subsequently creating a product based on this secondhand information. If the design doesn’t work, it is then sent back for reworking, a process that can go on forever
Lean UX gets around this problem by putting designers to work with other employees right away, allowing the team to fix problems immediately and move the process along. Consider a designer and a developer going back and forth in an informal dialogue to design a dashboard. It takes them a few sketches and adjustments but they soon agree on a design. The designer is then free to iron out the specifics, while the developer writes the infrastructural code.