Oops I'm A Manager - Finding your Minimal Viable Process
summary
Claims a working recipe called minimum viable process that replaces guilt-driven checklists with high-level feature ownership, concrete experiments, and retros that target the worst friction points. Implements context pairs (two-person feature leads) to cut eight-person daily drag into subteams, shifts QA to a flexible pull-in model (Karan), and runs small experiments tracked on GitHub and slides. Recommends the Popcorn method (Claudio Peroni) for structured experiments; notes one early startup sold for $20M.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:28Meet Andrew Holz
- 3:48Minimum Viable Process
- 5:16High Viable Process
- 9:57The Doing
- 13:19Delivery
- 17:07More Work
- 18:51Agile Manifesto
- 19:15Recap
related talks
01h 02mMinimal Viable Process - how to find flow in your ways of working
45mHow to bake a change
46mManaging The Process
22mOptimizing Product Development: Balancing Speed, Quality, and Process
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
42mHow Doing the Little Things Well Makes the Big Things Possible
01h 01mPopcornFlow
48mLess Process, more Guidance with a Team Playbook