Form
Cluster photo and Markdown clean copy with focus question, all clusters with titles and included stickies, prioritization result, top clusters with follow-up actions, owner and date, plus participant list and author notes.
RunsheetFacilitation
Consensus Workshop
ComplexityMedium
Time1-3 h
Participants5-30
FormatWorkshop
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Large wall or Miro board with areas for individual collection, pair sharing, cluster wall, and title formation; sticky notes; pens; timer; focus question as a visible header; refreshments for half-day or full-day workshops.
People / roles
A facilitator with ICA-ToP experience or comparable training; 5-30 participants; for larger groups a co-facilitator and 2-4 cluster helpers; a documentation team for photos and clean-up.
Pre-read
Clear focus question, open and pointing toward one concrete answer direction; pre-material on the question in 1-2 pages; purpose of the workshop, such as clarification, prioritization, or shared picture; participant list with roles; previous decisions touching the topic.
Time needed
1-3 h
Setup
Wall in three areas: individual collection area, pair-sharing area, cluster wall. Focus question visible in large type. Rule: solo work first, pair sharing second, cluster together, titles last.
02
Core question
The one question this method answers
Which shared themes emerge from the variety of individual contributions to the focus question?
03
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Focus question and individual brainstorming | 15-20 min | Read the focus question aloud and make sure everyone understands it. Silent work: each person collects 5-12 ideas on their own sticky notes. | The focus question must be open but directed. "What do we do in 2027?" is too open; "Which three priorities do we pursue in 2027 in sales?" is directed. |
2Phase 2: Pair sharing | 15 min | Exchange ideas in pairs or groups of three and select the top 5-8 sticky notes per pair. | Pair sharing lowers the barrier for quiet voices. Do not skip it, even under time pressure. |
3Phase 3: Wall contribution and clustering | 30-45 min | Pairs place selected sticky notes on the cluster wall. Cluster together: similar items together, differences visible. At least 4-8 clusters, maximum 12. | Clustering is consensus work, not sorting. In case of conflict over a cluster, discuss it and, if needed, duplicate the sticky note with a marker on the original cluster. |
4Phase 4: Title formation | 30-45 min | Form a shared title per cluster: 3-7 words, verb plus object, summarizing the common thread. Read titles aloud and check whether the group carries them. | The title is the consensus test. Anyone who cannot support the title signals a cluster difference. Split the cluster or change the title until consensus exists. |
5Phase 5: Prioritization and derivation | 20-30 min | Vote or discuss the cluster ranking. Define one concrete follow-up action or responsibility per top cluster. Documentation team takes photos and rewrites cleanly. | The workshop ends only with follow-up actions. Cluster consensus without action stays theoretical. |
04
Artifact
What comes out at the end
Versioning / ownership
Create one entry per workshop with date and focus question in the title. Link follow-up workshops on the same question so the theme evolution stays visible.
Tool alternatives
- Miro or FigJam with a consensus workshop template
- ToP original method with physical wall and photo export
- Mural with clustering function
- Notion with a database per cluster
consensus-workshop-working-template.md
Compact working template for Consensus Workshop with shared ideas, clusters, and priority areas.
Consensus Workshop Working Template
Goal
Bring individual input into a shared shortlist and turn it into consensus themes.
Context
What question should the group answer, and what decision follows?
Input
- Focus question:
- Group members:
- Constraints:
- Source material:
Working area
- Individual ideas:
- Shared ideas:
- Clusters:
- Consensus themes:
- Priority areas:
Output artifacts
- Consensus clusters:
- Theme titles:
- Priority areas:
Open questions
- ...
Decision / next step
Owner, date, and success signal.
05
Example output
Concrete filled scenario, fictional example
consensus-workshop-beispiel.md
Concrete filled scenario, fictional example
Consensus Workshop — Department Priorities 2027 Customer Support (24.05.2026, 2 h, 18 people from 6 teams)
Focus question: Which five priorities do we pursue in 2027 to raise the first-contact resolution rate from 64% to 78%?
Clusters with titles:
- "Maintain the Tier 1 knowledge base consistently" (12 stickies)
- "Clarify and make escalation paths visible" (10 stickies)
- "Shorten onboarding for new agents" (8 stickies)
- "Involve product engineering earlier in recurring issues" (7 stickies)
- "Serve the premium segment with dedicated senior agents" (6 stickies)
- "Integrate tools: one tool instead of three" (5 stickies)
Prioritization (dot voting, 5 dots per person): Cluster 1 (38), Cluster 4 (32), Cluster 2 (29), Cluster 6 (22), Cluster 3 (18).
Follow-up actions for top 5:
- Knowledge base audit plus maintenance cadence (Owner: @anna, by 30.06.).
- Engineering sync format for recurring issues (Owner: @ben, start 01.07.).
- Escalation map with image and Slack channels (Owner: @lisa, by 14.06.).
- Tool integration spike (Owner: @marcus, by 30.07.).
- Onboarding program revision (Owner: @julia, by 15.07.).
06
Pitfalls
Recognize symptoms and steer against them
Trap
Focus question is too open
Symptom
Sticky notes cover everything possible, no cluster forms, and titles become generic.
What to do
Sharpen the focus question before the workshop. Test: does it lead to a concrete answer direction? If not, rephrase it.
Trap
Cluster without consensus
Symptom
The facilitator sorts, the group nods passively, and nobody really supports the cluster.
What to do
Clustering is group work. Make conflicts over assignment visible instead of hiding them. Better 10 real clusters than 6 neat ones.
Trap
Titles become slogans
Symptom
Cluster titles sound like marketing slogans, and nobody can describe concretely what they mean.
What to do
Require titles with verb plus object. Test: an outsider must understand the title without reading the sticky notes.
Trap
Pair sharing is skipped
Symptom
The group moves directly from solo work to the wall, and quiet voices disappear.
What to do
Pair sharing is the core of the method. Do not skip it, even under time pressure. Shorten pair sharing rather than removing it.
Trap
No follow-up action
Symptom
The workshop ends with nice clusters, but without an owner or a date.
What to do
Reserve the last 20-30 min strictly for follow-up actions. One action, owner, and date per top cluster. Otherwise there is no commitment.
07
Stop criteria
Done signals checkable in under a minute
The focus question cannot be clarified and the workshop drifts without direction.
The facilitator has no experience with consensus methods and the phases are not kept.
The group has fewer than 5 people, so a discussion is sufficient.
The group has more than 30 people, so the format becomes unmanageable; Open Space Technology is more suitable.
The conflicts are deep and personal, so mediation is the priority.
A single person must make the decision because of hierarchy, so DACI or RAPID is more suitable.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.