Map User Need Before You Fund Capability Work
Use a Wardley map to decide whether a capability should be differentiated, standardized, outsourced, or delayed.
Capabilities are not strategic by default. Their strategic role depends on which user need they support and how evolved they already are. Start at the top of the map Wardley mapping begins with user need. If you cannot name the need, you cannot tell whether a component matters because it differentiates the experience or because it merely keeps the lights on. Then add evolution Components move from genesis to custom-built to product to commodity. That matters because the right move changes with evolution: experiment, build, buy, standardize, outsource, or automate. Why planners use the map The map exposes over-investment in…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in