The engineering strategist journey
summary
Moves from blind execution to concrete engineering strategy using domain-driven design and team topologies plus Wardley mapping; recommends “follow the money,” unit economics, and shorter strategy cycles. Diagnostics, a clear direction and executable actions form the strategy; applied at one company over three months by changing hiring, isolating a 5-person full-stack team, training them and doing a Spring Boot rewrite of a service in one month with no production bugs, which sped delivery but caused some specialists to leave.
AI-written summary · about
chapters (23)
- 0:00Engineering strategy journey
- 1:07Overwhelming strategy to personal journey
- 2:10Early execution mistakes
- 3:34Trend copying without impact
- 4:59Learning from failures
- 5:42Business models and unit economics
- 8:10Strategy as iterative exploration
- 9:59Domain-driven design and strategy
- 10:39Engineering strategy components
- 12:47Aligning engineering and business
- 13:30Strategy as continuous learning
- 14:56Fractal strategies and feedback
- 17:04Strategy principles and adaptation
- 18:08When to invest in strategy
- 19:34Good strategy components
- 20:57Strategy development tools
- 22:40Balancing people, process, tech
- 23:46Case study: strategy in action
- 31:57Strategy impact on culture
- 34:27Changing culture via strategy
- 36:30Modeling strategy ecosystem
- 37:33Sharing strategies openly
- 38:41Q&A
related talks
56mDesign and execute your own engineering strategy
33mMaking the Leap from Execution to Strategy
30mStrategic Technology Leadership
48mCase Study: Tools and Strategies for Tackling Legacy Practices
31mFrom Engineer to Engineering Manager
36mCharting the Strategic Waters: From Pancakes to Clear Paths
28mJourney from Design Afterthought to Design First
26mApplying A Technical Brain To Organizational Design