Outcome Not Output
summary
The talk argues that delivering working code and following agile practices (user stories, cross-team collaboration) isn’t enough to guarantee project success; instead it emphasizes Lean UX’s core principle “outcome, not output.” It reviews practical practices the presenter found most effective for managing risks and uncertainties in software projects, focusing on measuring and prioritizing outcomes over merely producing features and on respecting people and interactions across teams.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:13Waterfall to agile methods
- 2:58Classical user story problems
- 7:57UX vs stakeholder
- 10:01User-centered development
- 12:06Zero Sprint approach
- 17:26Cross-functional teams
- 24:12Silos risks and leadership
- 26:43Colocation and collaboration
- 27:03Artifacts and proto-people
- 31:35Wireframes and UX coherence
- 32:57Common language and docs
- 35:05Specifications by example
- 37:53Automated regression tests
- 39:19Feature purpose
- 40:40Outcome vs output
related talks
19mEncounters and Solutions While Facing Outcomes
43mNobody needs an Agile Transformation
26mCustomer Obsession
39mPsyched about Outcomes
40mRegain Benefits from Agile Software Development
42mLean UX Lessons Learned from One Dozen Projects
53mOutcome-based product planning
23mHow a lean and agile mindset can lead to more innovative products