Lean UX Lessons Learned from One Dozen Projects
summary
Claims lessons from a dozen projects: Lean UX is hard but works when design and development integrate, with rapid validation and continuous delivery. Team size averages about five people, projects run 8–24 weeks with some four-week proofs, and the budgeted split settles to one third UX one third core one third front end. Practice is to do minimal upfront UX, use Google Docs Pivotal Tracker HTML5 mockups and style guides, aim for ~70% clarity and expect code is the final design authority.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:30Definitions
- 3:13User Experience
- 4:14Agile
- 5:57UX Documentation
- 7:20The Solution
- 7:40The waterfall process
- 9:11Rapid entropy
- 10:08Work and validation
- 11:42Lean UX life cycle
- 11:52User experience design
- 16:35Client research
- 16:59Market research
- 18:10User research
- 18:33User hypothesis
- 19:23Lean UX process
- 20:42Lead UX process
- 23:22Agile software development
- 26:15Style Guides
- 26:46UX Document
- 27:45Best Practices
- 28:51Questions
- 29:14Team size
- 31:03Continuous delivery
- 32:42Documentation
- 35:06Design Change
- 36:13Information Saturation
related talks
53mThe UX of UX: Building a Culture of UX
36mMixing Lean UX & Agile Development
45mGreat UX, Despite Agile: How to Get the Best Out of Your Design Team in Agile Projects
20mLean UX discovery and user research: define and start projects without waste
50mLean Design in Practice
41mDesignOps - How I Built UX Teams from Scratch in a Company
33mIs Lean UX Agile’s Brain? How Lean UX Fixes Common Agile
40mHow to make UX & Devs build killer products