How to bake a change
summary
Explains a repeatable change recipe: start with an initial assessment of stories behind complaints, pick three fixes from the Rule of 63, run small program-sized experiments (30–100 people), measure throughput lead time WIP and use OKRs, value‑stream maps and Wardley maps. Describes VESPA (visualize, eliminate, simplify, practice, automate), warns to automate tasks not processes, and reports a case where a 400‑person program halved lead time in a year and halved it again, delivering 4× output. Launches a productized service called GoWards.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:54Talk origin and meta approach
- 6:23Bake right versus right cake
- 10:52Listening without answers
- 16:02Rule of 63 and where to start
- 18:32Autonomy through alignment
- 21:41OKRs and delivery speed
- 23:05Horizontal alignment and metrics
- 26:14Deming cycles and change
- 27:36VESPA framework
- 34:12Progress and evidence
- 37:00Kitchen rules and advice
- 39:49Small iterative changes matter
- 41:15GoWards productized service
- 42:20Q&A
related talks
54mEffecting Change—The Art Of Leading Teams
20mMaking the Case for Change
21mOops I'm A Manager - Finding your Minimal Viable Process
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
51mEffecting Change—The Art of Leading Teams
41mWant to make a change? Stop talking and start listening
47mContinuous Deprovement will eat your product for breakfast
31mOperations Reform: Tom Sawyer-ing Your Way to Operational Excellence