Worked Walkthrough: Turn a Capability List Into a Wardley Map
Convert a capability inventory into a Wardley map that implies different strategic moves for different components.
The strategy review has a long capability inventory but no context for which items should be differentiated and which should be simplified. User need -> value chain -> evolution -> strategic move The common shortcut is to rank capabilities by internal importance or technology cost. That keeps the conversation architecture-centric and hides whether the capability is actually visible to the user or already mature in the market. Anchor on user need Write the user need that matters most to the strategy, such as complete purchase with confidence. Without the user anchor, the map collapses back into an internal system diagram.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in