How to make better modernization decisions
summary
Uses Wardley Mapping to place capabilities on an evolution axis and decide what to build versus buy, uses Service Blueprints to map a home‑delivery subscription user journey down to the APIs and temporal couplings, and uses an Architecture/Product Decision Tracking Framework to record options, tradeoffs and status. Works on a decades-old system supporting commerce and subscriptions, aligns over 60 people across teams, surfaces where complexity bleeds to users, and produces concrete, defeasible modernization choices.
AI-written summary · about
chapters (6)
- 0:00Modernizing legacy systems
- 2:32App modernization challenges
- 7:53Wardley Mapping for strategy
- 16:19Mapping user needs
- 25:48Aligning teams on solutions
- 29:20Q&A
related talks
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
01h 12mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization with DDD
53mEnabling aligned decentralised architecture decisions through user needs mapping
34mPractical Tools and Strategies for Tackling Legacy Practices
39mX Marks the Spot: Navigating Possible Futures with Wardley Maps
