Wardley Maps Saved The Day - How Stack Overflow Enterprise...
summary
Wardley Maps get used to turn a vague backlog into concrete decisions: a simple map surfaces that the team has 100 hours proposed vs 89 available, that configuration management (≈20 days) touches most services, and that investing in puppet and monitoring yields the largest systemic payoff. The map shows dependencies and evolution stages so priorities shift rightward, moved almost everything out of Genesis, freeing time for experiments and validating that automation choice actually works.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:07Stack Overflow for Enterprise
- 16:30Phases of Evolution - The Horizontal
- 19:38Value Chain - The Vertical
- 21:12My First Map
- 26:12Building a Product is an investment
- 28:08In Summary
related talks
39mX Marks the Spot: Navigating Possible Futures with Wardley Maps
35mGuiding teams, and shaping a portfolio using Wardley maps & DDD
46mHow to Wardley Map your technology strategy
44mDemocratizing Strategy: An Intro to Wardley Maps
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
22m4 Maps of DevOps
47mStrategy Maps - Connect Your Roadmaps to the Bigger Picture
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies