Guiding teams, and shaping a portfolio using Wardley maps & DDD
summary
Claims that Wardley Mapping creates situational awareness and Event Storming + DDD reveal and shift value‑stream boundaries, with portfolio management deliberately constraining WIP. Uses Wardley maps, Event Storming, bounded‑context canvas, anti‑corruption layers, example mapping, tests and refactor loops. Gives concrete failures: a three‑founder ticketing startup that custom‑built everything and later failed; a company that bought billing software while developers rebuilt a local subscription model and created friction. Says he trained over 100 managers and targets organizations with 5+ teams, stresses antifragility not invincibility.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:12Situational awareness in orgs
- 7:46Market changes with Wardley Maps
- 11:38DDD for system boundaries
- 16:30Collaborative DDD modeling
- 19:19Portfolio management need
- 23:41Nine allies for adoption
- 25:31Leveraging existing processes
- 28:47Building antifragility
- 33:24Constraining WIP for growth
- 35:10Closing remarks
related talks
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
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
39mX Marks the Spot: Navigating Possible Futures with Wardley Maps
34mPractical Tools and Strategies for Tackling Legacy Practices