Reading the post-it wall

The post-it wall is a visual synthesis of every idea that surfaced across all groups during your workshop. It is generated automatically after the session — no manual sorting required.

What it shows

Ideas from all groups are clustered into themes. Each cluster represents a topic or concern that recurred across the room. Within a cluster, individual sticky notes show specific statements contributed by participants at different tables.

You can see which group each note came from. This tells you whether a theme is broadly shared or concentrated in one corner of the room — a distinction that matters when you are drawing conclusions.

How to read it

Start at the cluster level: look at which themes exist and roughly how large they are. Larger clusters indicate more discussion volume, but volume is not the same as importance. A small cluster with a sharp, specific claim may carry more weight than a larger one with loose, general statements.

Then go inside each cluster. Look for:

• Convergence — multiple groups naming the same thing in different words. This is strong signal.
• Outliers — one group raising something no one else touched. Worth investigating before dismissing.
• Tension — notes within the same cluster that point in opposite directions. These are often where the real strategic question lives.

Check which groups are missing from a theme you care about. Absence has meaning: it may mean the topic did not come up at that table, or it may mean the group discussed it but did not produce a clear statement.

Using it in a debrief

The post-it wall is good for rapid orientation. In a ten-minute opening of a debrief, you can walk the room through the clusters and ask: does this map match what you experienced?

It is not suitable as a final deliverable on its own. The clusters are labeled by the AI based on content similarity, not by your facilitation intent. Some clusters will need renaming or merging. Others may need to be split.

Treat the post-it wall as a fast first draft of the synthesis, not the synthesis itself.

Common misreadings

Assuming clusters are equal in quality. A cluster is formed because statements were topically similar — not because they were analytically clear. Review the notes inside each cluster before citing it as a finding.

Reading too fast. The wall can look finished. Scan all clusters before forming conclusions. The note that changes your interpretation often sits in a small cluster you nearly skipped.

Ignoring source diversity. A theme supported by one very active group is weaker than a theme supported by four independent groups. Always check the group tags on each note.

Troubleshooting

"A cluster contains unrelated notes"

The clustering algorithm uses semantic similarity, which is good but imperfect. Notes that share vocabulary may land in the same cluster even when they discuss different things. Rename clusters that are misleading, or note the discrepancy in your debrief.

"An important theme I remember from the session is missing"

Check whether the relevant discussion produced clear transcript output. Unclear audio or a dropped capture window can result in a theme being under-represented. Cross-reference with the group transcripts directly.

"The wall shows ideas I expected to see, but the insight report says something different"

The post-it wall reflects idea volume and variety. The insight report weighs evidence and draws narrative conclusions. Disagreement between them is normal — and useful. The tension usually points to something worth calling out explicitly.

Related guides

• [Understand and generate your workshop analysis](/guides/analysis/understanding-workshop-analysis)
• [Reading the insight report](/guides/analysis/reading-the-insight-report)
• [How RoomRadar group summaries work](/guides/analysis/understanding-group-summaries)
• [What to do when summaries feel wrong](/guides/analysis/what-to-do-when-summaries-feel-wrong)
• [Capture decisions during discussion, not after](/guides/workflows/capturing-decisions-during-discussion)