Session Brief: Expectation Mapping

Goal

Artifact: Expectation Map

Working Question

Which expectations do participants bring to outcome, collaboration, and behavior, where do they differ, and which agreements resolve the differences?

Context

Scope and occasion (project kickoff, team formation, stakeholder workshop); list of participants and their roles; known friction points from earlier phases.

Setup

• Format: Method session
• Duration: 45-90 min
• Mode: Workshop
• Participants: A facilitator who holds psychological safety; three to twelve participants from involved functions; one scribe for conflicts and agreements.
• Owner: A facilitator who holds psychological safety
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Expectation Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

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.

Preparation

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.

Agenda

1. Phase 1: Clarify scope (5-10 min) Owner: Facilitator Action: Introduce occasion and scope in 5 min. Make participants and roles visible. Rule: expectations are about this group's collaboration, not the whole world. Hint: If scope is unclear, expectations from different topics mix together. Quick narrowing is worth the time. Output: Expectation Map

2. Phase 2: Collect expectations silently (15-20 min) Owner: Facilitator Action: 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. Hint: No conversation in solo phase. Dominant participants should write instead of talk. Silence protects quieter voices. Output: Alignment Notes

3. Phase 3: Share and cluster (15-20 min) Owner: Facilitator Action: Each person presents expectations in turn (max 2 min). Others ask only understanding questions, not judgment. Then cluster together. Hint: Understanding questions are fine, judgment is not. "What exactly do you mean by X?" clarifies; "That's unrealistic" closes. Output: Agreements

4. Phase 4: Mark conflicts (10-15 min) Owner: Facilitator Action: 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. Hint: One-sided expectations are the most common conflict source. "I assumed X" is classic. Output: Expectation Map

5. Phase 5: Derive agreements (10-20 min) Owner: Owner Action: 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. Hint: Agreements are either explicit or absent. "We try" is not enough, "We have a weekly 30-min sync to clarify open points" is. Output: Alignment Notes

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Expectation Map

Closeout

• Update result artifact: Expectation Map
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Expectation Map: Expectation Mapping

Working Question

Which expectations do participants bring to outcome, collaboration, and behavior, where do they differ, and which agreements resolve the differences?

Context

Scope and occasion (project kickoff, team formation, stakeholder workshop); list of participants and their roles; known friction points from earlier phases.

Participants

• Owner: A facilitator who holds psychological safety
• Participants: A facilitator who holds psychological safety; three to twelve participants from involved functions; one scribe for conflicts and agreements.

Input

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.

Template

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.

Completion Check

• Expectation Map is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision