Better product definition with Lean UX and Design Thinking
Conference talk at Lean IT Summit
· 36 min
Requirements-driven product definition is a reliable way to launch 100% of the wrong product. In this talk at the Lean IT Summit 2014, Jeff Gothelf, author of Lean UX, explains that the assumptions behind requirements are usually not accurate enough to determine the exact solution those requirements dictate.
Instead, teams should create a series of hypotheses that define potential solutions to their business problem, then work together to learn which hypotheses are keepers and which ideas to kill. Jeff gives an overview of how to apply the ideas behind Lean UX and Design Thinking to project definition and planning.
What you'll learn
- Why requirements-driven product definition tends to launch the wrong product
- Why the assumptions behind requirements are rarely accurate enough
- How to frame potential solutions as a series of hypotheses
- How teams learn which ideas to keep and which to kill
Watch next
-
Jeff GothelfLean UX: Getting Out of the Deliverables Business
-
Jeff GothelfLean UX in the Enterprise
Free weekly newsletter
Real UI patterns and design psychology in your inbox
Learn how successful products use UI patterns and behavioral design. One email a week from UI-Patterns.com and Learning Loop.
Subscribe






