From here to there and back again
summary
Explains how Wardley Maps turn system graphs into actionable maps by anchoring users, listing user needs, mapping component evolution, then applying economic and doctrinal patterns to pick where to invest or stop. Shows concrete outcomes: a robotics rollout is canceled when custom racks causing robotics spend cancelled is spotted, a government project saved 425 million by remapping, and Canonical’s play (starting from 3% market share) took 70% of cloud by finding the right attack points. Describes pitfalls: AI hallucinations in vibe coding and where to keep humans in the loop.
AI-written summary · about
chapters (25)
- 0:00Introduction and talk setup
- 1:11AI-generated talk synopsis
- 2:39Origin of mapping journey
- 6:29What is a map vs graph
- 9:17Creating meaningful maps
- 13:56Problem with organizational stories
- 14:17Case study insurance bottleneck
- 17:30Mapping patterns and principles
- 20:20Evolution of practices in HS2
- 23:31Contract flaws and Elvish example
- 25:00Climactic patterns in technology
- 26:02Everything evolves principle
- 27:53Past success and inertia
- 28:59Efficiency enables innovation
- 30:24Canonical's strategic mapping
- 33:41Strategy is iterative
- 36:08Introduction to AI and mapping
- 37:53Conversational programming
- 39:19Tools languages and medium
- 42:09Control of reasoning systems
- 44:36Handing decisions to AI
- 45:41Code is the real architecture
- 47:10Vibe wrangling and risks
- 49:38Future of software engineering
- 50:27Q&A session
related talks
50mX Marks the Spot: Navigating Possible Futures with Wardley Maps
01h 02mFrom here to there and back again
55mStrategic Thinking in Software Architecture using Wardley Mapping
21mCrossing the River by Feeling the Stones
45mWardley Maps for Your Microservices Journey
48mAgile is a cult
42mA different take on (context) mapping -
44mSituation Normal, Everything Must Change