Maximim Impact, Minimum Effort
summary
Builds a product called narrowkit ~1M monthly users as evidence that focusing on outcomes can scale, and argues teams must measure leading indicators (cases processed per day, days-to-appointment, patients seen per day) not story points. Shows concrete failures: a £70M BBC video project stopped for no value, and a clinic that switches from nine months of admin screens to a shared calendar that reduces wait time. Prescribes using an impact map linking a single near-term business goal to measurable behavior changes, keeping deliverables in your zone of control and budgeting ~5% for technical cleanup.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 1:18The problem with software
- 4:47Two levels of value
- 8:06Connecting goals and actions
- 10:11Avoiding the agile trap
- 14:55Disciplines of execution
- 18:01The measurement inversion
- 21:06Defining outcomes vs outputs
- 25:23Slicing for maximum impact
- 28:28Visualizing with impact maps
- 34:03Debugging impact maps
- 37:31Closing thoughts
- 43:14Q&A session
related talks
18mFrom developer productivity to engineering impact
47mVisualisation
25mMaking big impacts via visual strategic planning
34mBuilding a Culture For Developer Productivity
42mSlaying the Backlog Beast: A #NoBacklogs Approach to Product Management
12mGamify the Metrics, Amplify the Impact
39mPsyched about Outcomes
29mDriving clarity in ambiguous projects