Is Lean UX Agile’s Brain? How Lean UX Fixes Common Agile
summary
Argues that Lean UX fixes agile by changing what gets discussed and measured: it cuts 30–40% of scope by validating hypotheses with real users, restructures work so the unit of conversation equals unit of validation, drives cycle time down (examples move from cycle time ~7 days toward ~2–3 days), and replaces big specs with small deliverable features that ship quickly. Practical moves include put designer on the team, mock or isolate APIs, ship working software in 2–3 weeks, and show stakeholders data not promises.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:36How to Break an Agile Team
- 6:53The Stakeholder Experience Rules
- 12:10Traditional UX and the Tyranny of the Spec
- 16:53User's can't tell you what's high value- you need to watch them experience the software.
- 18:11Lean UX DECREASES IT.
- 24:55the unit of design == the unit of development
- 26:16Alternative? Try to Explain the Process
- 27:50Immutable Teams, Mutable Boundaries
related talks
37mHow They Work Better Together: Lean UX, Agile Development and User-Centered Design
54mAgile UX - How to Combine Agility with Usability
20mLean UX discovery and user research: define and start projects without waste
45mGreat UX, Despite Agile: How to Get the Best Out of Your Design Team in Agile Projects
49mUX and an Agile Development Process
42mLean UX Lessons Learned from One Dozen Projects
36mMixing Lean UX & Agile Development
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt