User Needs Mapping (UNM) is a practical, visual approach for helping organisations align teams, capabilities, and decisions around real user needs.

It helps teams move beyond inside-out thinking — where work is organised around technology, functions, or internal structures — and instead explore how value actually flows to users.

The outcome is often greater clarity around:

• who the users really are

• what those users are trying to achieve

• which capabilities support those needs

• where friction, duplication, or coordination overhead exists

• how team interactions and boundaries might evolve over time

UNM is especially useful when organisations feel busy but struggle to translate effort into meaningful outcomes.

Customer journey maps and service blueprints are often focused on specific experiences or operational flows. User Needs Mapping takes a broader organisational perspective.

Rather than only examining a journey, UNM explores:

• the needs behind the journey

• the capabilities required to meet those needs

• the dependencies between those capabilities

• the teams and systems involved in delivering them

This makes it particularly useful for conversations about:

• team boundaries

• platform strategy

• organisational alignment

• ownership clarity

• dependency reduction

• flow of change and value

No — but the two approaches are related.

User Needs Mapping builds on the first stages of Simon Wardley’s Wardley Mapping approach:

1. identifying users

2. understanding user needs

3. identifying capabilities required to meet those needs

4. exploring dependencies and value chains

UNM intentionally focuses on these earlier stages because they are often where organisations struggle most.

You can think of UNM as helping organisations build stronger situational awareness before moving into deeper strategic mapping and evolutionary analysis.

No. While UNM is commonly used in digital and technology organisations, the underlying principles apply anywhere people collaborate to meet user needs.

That includes:

• platform teams

• operations teams

• product organisations

• internal services

• leadership teams

• transformation initiatives

• cross-functional programmes

The core question remains the same:

“Who is this work ultimately for, and what are they trying to achieve?”

UNM is particularly good at making hidden organisational friction visible.

Common patterns include:

• unclear ownership

• overlapping responsibilities

• duplicated capabilities

• excessive dependencies

• handoff bottlenecks

• teams stretched across unrelated work

• platform teams disconnected from user outcomes

• delivery that feels slower than it should

• initiatives that create activity but little impact

Many organisations already sense these issues. UNM helps make them discussable.

Not directly. UNM is not a reorganisation framework. It is a sense-making approach that helps people better understand:

• how value currently flows

• where friction exists

• where responsibilities may be unclear

• where boundaries might need to evolve

Sometimes this leads to small interaction changes. Sometimes it leads to capability clarification. Sometimes it reveals opportunities for new platform or stream-aligned teams.

The goal is not “reorg for the sake of reorg,” but helping teams make more informed structural decisions grounded in user needs.

Yes — very much so. UNM is frequently used alongside Team Topologies to help organisations explore team boundaries and interactions from an outside-in perspective.

Many practitioners use UNM to:

• identify potential stream boundaries

• understand platform relationships

• visualise dependencies

• reduce cognitive load

• support more effective team interactions

Rather than starting with team shapes, UNM starts with user needs and lets those needs influence organisational conversations.

Not perfectly. In fact, one of the most common discoveries during a UNM session is that people realise they have very different assumptions about who their users actually are.

The mapping process is designed to help teams build shared understanding collaboratively.

Yes. Platform teams often struggle because they are organised around technology rather than clear internal user needs.

UNM helps platform teams explore:

• who their internal users are

• what those users are trying to achieve

• which platform capabilities genuinely reduce friction

• where platform ownership becomes too broad or fragmented

• where self-service and enablement opportunities exist

This often supports stronger “platform as a product” thinking.

It depends on the scope and goals. Some workshops are short exploratory sessions lasting a few hours. Others evolve into multi-day collaborative mapping engagements.

A lightweight session may help:

• align terminology

• uncover obvious friction

• introduce the concepts

Longer engagements may explore:

• multiple user groups

• organisational capabilities

• team interactions

• dependency hotspots

• team design options

A typical workshop is highly collaborative and visual. Participants usually work together to:

• identify users

• explore needs

• map capabilities and dependencies

• discuss pain points and friction

• surface questions and tensions

• explore possible organisational improvements

The aim is not to “teach a framework” in isolation, but to use mapping as a way to create shared clarity using your own real-world context.

No. UNM can be done physically with sticky notes and whiteboards, or digitally using tools like Miro. The important part is the conversation and shared sense-making, not the tooling.

No. The approach scales surprisingly well. Smaller organisations often use UNM to:

• avoid premature silos

• clarify ownership early

• align product and engineering

• understand emerging platform needs

Larger organisations often use it to:

• reduce coordination overhead

• rethink fragmented capabilities

• support organisational evolution

• improve flow across complex systems

A good starting point is simply asking:

“Who are our users, and what are they actually trying to achieve?”

From there, begin exploring:

• what capabilities support those needs

• where dependencies exist

• which teams are involved

• where friction repeatedly appears

The book User Needs Mapping: Aligning Teams Around What Matters and the resources on this website provide practical walkthroughs, examples, and workshop guidance to help you get started.

Increasingly, yes. Many organisations are discovering that AI amplifies existing organisational dysfunction rather than magically fixing it.

Research from DORA highlights that user-centric focus is one of the key capabilities that helps organisations gain better outcomes from AI adoption.

UNM helps organisations:

• keep user needs visible

• avoid technology-first thinking

• identify where AI genuinely supports user outcomes

• understand how capabilities and team interactions may need to evolve

Without that clarity, teams can end up accelerating work in the wrong direction.

You can:

• explore the resources and articles on this website

• subscribe to the newsletter

• read User Needs Mapping: Aligning Teams Around What Matters

• explore related ideas from Team Topologies

• or get in touch about workshops and advisory support

The goal of the site is not just to explain the technique, but to help practitioners apply it in real organisational contexts.