Form
Expectation Map as structured document with three columns, a list of marked conflicts and gaps, and explicit agreements with owner and review date.
RunsheetFacilitation
Expectation Mapping
ComplexityLow
Time45-90 min
Participants3-12
FormatWorkshop
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Whiteboard or Miro board with three columns (Expectation of outcome, expectation of collaboration, expectation of behavior); stickies per person in individual color; timer; template for final agreement list.
People / roles
A facilitator who holds psychological safety; three to twelve participants from involved functions; one scribe for conflicts and agreements.
Pre-read
Scope and occasion (project kickoff, team formation, stakeholder workshop); list of participants and their roles; known friction points from earlier phases.
Time needed
45-90 min
Setup
Three columns on the board. One sticky color per person to keep expectations traceable. Rule: collect silently, then share, then cluster. No judgment in phases 1-2.
02
Core question
The one question this method answers
Which expectations do participants bring to outcome, collaboration, and behavior, where do they differ, and which agreements resolve the differences?
03
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Clarify scope | 5-10 min | Introduce occasion and scope in 5 min. Make participants and roles visible. Rule: expectations are about this group's collaboration, not the whole world. | If scope is unclear, expectations from different topics mix together. Quick narrowing is worth the time. |
2Phase 2: Collect expectations silently | 15-20 min | Solo writing phase of 10 min per person: at least three expectations per column. Formulate concrete expectations tied to behavior or outcome. Place in own color. | No conversation in solo phase. Dominant participants should write instead of talk. Silence protects quieter voices. |
3Phase 3: Share and cluster | 15-20 min | Each person presents expectations in turn (max 2 min). Others ask only understanding questions, not judgment. Then cluster together. | Understanding questions are fine, judgment is not. "What exactly do you mean by X?" clarifies; "That's unrealistic" closes. |
4Phase 4: Mark conflicts | 10-15 min | Check clusters: where do expectations conflict, where are expectations missing, where are they one-sided (one person expects something, others do not know)? Mark with red dot. | One-sided expectations are the most common conflict source. "I assumed X" is classic. |
5Phase 5: Derive agreements | 10-20 min | For each conflict or gap formulate an agreement: what we do, what we do not do, and when we revisit. Assign owner and review date per agreement. | Agreements are either explicit or absent. "We try" is not enough, "We have a weekly 30-min sync to clarify open points" is. |
04
Artifact
What comes out at the end
Versioning / ownership
Own entry per workshop with date and participants. If conflicts recur, reference the map and reactivate agreements. Quarterly refresh recommended.
Tool alternatives
- Miro with three-column frame
- Notion table per expectation type
- Confluence page with table
- Google Doc with three sections
expectation-mapping-working-template.md
Compact working template for Expectation Mapping with context, input, output artifacts, and next step.
Expectation 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
- Expectation Map:
- Alignment Notes:
- Agreements:
Open questions
- ...
Next step
Owner, date, success signal.
05
Example output
Concrete filled scenario, fictional example
expectation-mapping-beispiel.md
Concrete filled scenario, fictional example
Expectation Mapping — Activate-Team and Customer Success Kickoff (2026-05-22)
Scope: Transfer of Activate Team insights and Sabine persona learnings to Customer Success.
Expectation sample:
- Anna (PM, Activate): Expects CS to return structured onboarding feedback monthly.
- Marcus (CS Lead): Expects Activate Team to involve CS early in roadmap.
- Lisa (UX, Activate): Expects CS calls to be recorded so insights are usable.
- Tobias (CS Member): Expects no additional reporting overhead.
Conflicts (red marked):
- Lisa expects call recordings, Tobias worries about extra workload.
- Anna expects monthly feedback, Marcus expects it quarterly.
Agreements:
- Calls with customers start being recorded from 2026-06-01 with customer consent, Lisa runs analysis. Owner: @marcus (recording), @lisa (analysis). Review after 6 weeks.
- Feedback cadence: every 6 weeks, structured template with 5 questions. Owner: @anna for template by 2026-05-30.
- Roadmap sync every 4 weeks for 30 min. Owner: @anna for scheduling.
06
Pitfalls
Recognize symptoms and steer against them
Trap
Judgment in phase 2 or 3
Symptom
Expectations are commented on or downgraded directly.
What to do
Facilitator interrupts. Phases 2 and 3 are judgment-free. Judgment starts in phase 4.
Trap
Vague expectations
Symptom
Expectations read "communicate transparently" or "work professionally together."
What to do
Make them concrete with behavior or outcome. "I expect X to post an update weekly" instead of "communicate transparently."
Trap
One-sided expectations not named
Symptom
One person has expectations but does not state them.
What to do
Solo phase enforces contribution. If someone writes little, invite directly: "What do you expect?"
Trap
Agreements without owner
Symptom
Agreements are formulated but no one is responsible.
What to do
Assign owner and review date for each agreement. Without owner, agreements fade.
Trap
Workshop without follow-up
Symptom
Map remains in Confluence, agreements are forgotten after two weeks.
What to do
Add review date in 6-8 weeks. For conflicts, reference the map. Map is a living document.
07
Stop criteria
Done signals checkable in under a minute
Participants are absent, expectations remain speculative.
An acute conflict is taking over the method, mediation is needed first.
More than 12 people, discussion becomes too large.
Workshop shorter than 30 min, five phases cannot be completed.
Scope not bounded, expectations from different topics mix together.
No willingness to document agreements, workshop stays discussion.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.