Charting the Strategic Waters: From Pancakes to Clear Paths
summary
Reframes strategy as a design process that starts with challenges not goals, using Rumelt’s kernel: diagnosis, guiding policy, coherent actions; practical steps include investing first to cut maintenance costs, introducing a build/buy/partner decision framework, reviewing domains to commoditize components, and enforcing WIP limits. Outcome: regained engineering capacity and a self‑service platform (database provisioning drops from weeks to minutes). One failed attempt is a uniform ROI standard — it proves not addressable yet.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:54Pancakes as strategy metaphor
- 3:21Strategy layer of pyramid
- 4:03Start with challenges not goals
- 6:092021 awakening to strategy
- 8:16What strategy creation means
- 9:41Tesla’s strategy example
- 11:06Engineering team’s strategic pivot
- 13:34Mixing vision strategy goals
- 14:38Distilling strategy into action
- 16:03Strategy creation problems
- 17:09Rumelt’s good strategy kernel
- 20:23Diagnosis policies coherent actions
- 23:132024 strategy framework insight
- 25:03Addressability challenge in strategy
- 25:47Strategy versus tactics
- 27:11Strategy hierarchies across teams
- 28:35How long should a strategy last
- 30:19Key takeaways and book recommendations
related talks
56mDesign and execute your own engineering strategy
28mJourney from Design Afterthought to Design First
44mThe engineering strategist journey
43mChange Your Focus
48mCase Study: Tools and Strategies for Tackling Legacy Practices
33mMaking the Leap from Execution to Strategy
44mAvoiding the pitfalls of rebuilding software
07mLeading from the Middle