Form
An alignment map with perspectives, open issues, and decision questions that can be turned into follow-up work.
RunsheetFacilitation
Alignment Mapping
ComplexityMedium
Time1-2 h
Participants4-12
FormatWorkshop
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Mapping canvas, sticky notes or digital cards, markers, a timer, and space for open issues and next steps.
People / roles
One facilitator, 4-12 stakeholders or representatives, and optionally a scribe for decisions and follow-ups.
Pre-read
The alignment question, the current context, the decision horizon, and any known constraints or non-negotiables.
Time needed
1-2 h
Setup
Create one column or zone per perspective plus space for conflicts and questions. Keep the alignment question visible at the top.
02
Core question
The one question this method answers
Where do stakeholders align, where do they diverge, and what clarifications are needed before a decision can move forward?
03
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-10 min | 10 min | Define the alignment question and confirm the decision horizon or situation under discussion. | If the question is too broad, the map will become a wish list instead of an alignment tool. |
210-25 min | 15 min | Collect stakeholder perspectives individually before the group starts to compare them. | If only the loudest voices speak first, important differences will disappear. |
325-45 min | 20 min | Map the goals, concerns, and assumptions for each perspective side by side. | If the same statement appears in every column, the map is probably too abstract. |
445-70 min | 25 min | Mark conflicts, missing information, and open questions that prevent alignment. | Do not smooth over disagreement. The value of the map is to make the gap visible. |
570-120 min | 50 min | Turn the map into clarification steps, owners, and a short list of decision questions. | If the next step is not owned, the map becomes a static diagram instead of a working tool. |
04
Artifact
What comes out at the end
Versioning / ownership
Record the date, topic, participants, and decision owner. Update the map whenever key stakeholders, assumptions, or constraints change.
Tool alternatives
- Miro board with perspective lanes
- FigJam board with question and conflict zones
- Notion page with side-by-side columns
- Whiteboard with sticky notes and photographed output
alignment-mapping-working-template.md
Compact working template for Alignment Mapping with context, input, output artifacts, and next step.
Alignment Mapping Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Alignment Map:
- Open Issues:
- Decision Questions:
Open questions
- ...
Next step
Owner, date, success signal.
05
Example output
Concrete filled scenario, fictional example
alignment-mapping-beispiel.md
Concrete filled scenario, fictional example
Alignment Mapping - launch readiness, 2026-07-01
Question: Can we move the feature launch to 2026-07-15 without creating support risk?
Perspective map
- Product: wants the earlier date to match the campaign plan.
- Support: needs clearer help content and escalation paths.
- Engineering: wants one more week for rollback hardening.
- Sales: needs a reliable external promise before customer calls.
Open issues
- Who owns the support content update?
- Which rollback test must pass before release?
- What customer promise can be made safely today?
Next steps
- Confirm rollout owner.
- Run the rollback test.
- Revisit the launch date after support content is updated.
06
Pitfalls
Recognize symptoms and steer against them
Trap
The question is too broad
Symptom
The group starts discussing strategy in general and nothing gets mapped.
What to do
Narrow the alignment question until it fits one decision horizon.
Trap
Only one voice dominates
Symptom
The loudest stakeholder fills most of the map and the rest becomes decoration.
What to do
Collect perspectives individually first and then compare them side by side.
Trap
Conflicts are hidden
Symptom
The map looks tidy but the real disagreement is still unspoken.
What to do
Mark the conflict explicitly and keep it visible until a clarification step is owned.
Trap
The map turns into a poster
Symptom
The team stops after drawing the picture and no follow-up exists.
What to do
End with owned questions, dates, and next actions.
Trap
Stakeholders are treated as answers
Symptom
The map becomes a verdict on people instead of a view of perspectives.
What to do
Keep the focus on the perspective, the concern, and the condition that would change it.
07
Stop criteria
Done signals checkable in under a minute
Only one stakeholder perspective is relevant.
The topic is already fully decided and only needs execution notes.
The participants cannot speak openly enough to surface real differences.
There is no decision horizon or concrete topic to align on.
The group is trying to do task planning instead of stakeholder alignment.
No one is available to own the clarification steps after the session.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.