Enabling aligned decentralised architecture decisions through user needs mapping
summary
Teams create user needs maps (the value‑chain layer of a Wardley map) through collaborative workshops (typically 1.5–2.5 hour sessions, two to three per team) that trace activities to owning systems and teams. The maps expose surprises: unowned legacy components, cross‑team ping‑pong, and missing SLAs, and enable concrete follow ups—SLOs and team interaction changes—so reliance on a central architect falls as teams update maps every 4–8 weeks and make aligned decentralized architecture decisions.
AI-written summary · about
chapters (12)
- 0:00The architecture challenge
- 1:36Lack of organizational maps
- 4:37Empowering stream-aligned teams
- 7:25Architectural decision making
- 10:15Cognitive load and flow
- 12:54Conflict and shared modeling
- 15:46Introducing Wardley mapping
- 19:40User needs mapping in practice
- 30:26Analyzing the mapped landscape
- 36:36Standardizing visual communication
- 43:44Collaborative modeling methods
- 47:21From enablement to platform
related talks
35mGuiding teams, and shaping a portfolio using Wardley maps & DDD
39mX Marks the Spot: Navigating Possible Futures with Wardley Maps
40mAdaptive Socio-Technical Systems with Architecture for Flow
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
30mHow to make better modernization decisions
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
24mBusiness Value Over Architecture?