Strategic Thinking in Software Architecture using Wardley Mapping
summary
Shows how Wardley mapping turns messy choices into concrete moves: uses Southwest’s all‑737 fleet versus Delta to illustrate tradeoffs, maps a Hunter Industries golf‑controller adding a cellular IoT module to decide build vs buy, and traces ASR from boutique to commodity to warn of the “war” phase and inertia. Recommends tools—onlinewardlemap.com with a VS Code DSL, Miro templates and Mapke for live collaboration—and cites Simon Wardley’s rule of thumb that mastering mapping takes about 6 years 11 months.
AI-written summary · about
chapters (12)
- 0:00Introduction and strategy basics
- 6:57Defining strategy and Wardley Mapping
- 9:25What is Wardley Mapping?
- 12:58Understanding the map components
- 21:10Using Wardley Maps as thinking tools
- 22:17Climactic patterns in strategy
- 29:47Efficiency and innovation in evolution
- 38:56Components co-evolving in systems
- 42:52Doctrine and team archetypes
- 47:04The map is not the territory
- 48:07How to start mapping today
- 51:17Resources and next steps
related talks
50mX Marks the Spot: Navigating Possible Futures with Wardley Maps
58mFrom here to there and back again
45mWardley Maps for Your Microservices Journey
34mPractical Tools and Strategies for Tackling Legacy Practices
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
48mCase Study: Tools and Strategies for Tackling Legacy Practices
21mCrossing the River by Feeling the Stones