An alignment diagram maps a user's experience or mental model against the activities, processes, and touchpoints of the organisation delivering it. The fundamental purpose is to reveal where the two sides are in sync — and, more importantly, where they diverge. Misalignment between what users experience and what the organisation thinks users experience is the root cause of a remarkable number of persistent product and service failures.
What It Is
Alignment diagrams are a family of related visualisations — including experience maps, service blueprints, and mental model diagrams — that share a common structure: user experience runs along one axis and organisational activities run along the other. The diagram is read by looking for places where user needs go unaddressed and where organisational effort is being spent on things users do not value. James Kalbach's book 'Mapping Experiences' provides the canonical treatment of this family of methods.
How to Run It
- Gather research data that describes the user's experience: journey maps, interview notes, diary studies.
- Document the organisation's current activities, processes, and touchpoints that relate to the same experience.
- Plot both sides in a shared diagram with the user experience on the top half and organisational activities on the bottom half.
- Draw vertical lines connecting user experience moments to the organisational activities that correspond to them.
- Identify gaps: user experience moments with no organisational support, and organisational activities with no corresponding user value.
- Use identified gaps as the primary input for design prioritisation.
When to Use It
Alignment diagrams are most powerful in service redesign projects where the challenge is systemic rather than interface-level. They are essential for cross-functional alignment workshops where teams from different departments need to see how their work connects to the user experience. Use them when organisational silos are producing a fragmented user experience that no single team can see in its entirety.
Tips for Success
- Include frontline staff in building the organisational side of the diagram — they know the real process, not the documented one.
- Focus the gap analysis on the emotionally lowest points in the user experience: these are where organisational effort is most urgently needed.
- Present the diagram in a large format on a wall rather than as a slide: its value lies in its ability to be read as a whole.
- Update the diagram after every significant research or design phase rather than treating it as a one-time deliverable.
