Start with the ideas as they were expressed
After a brainstorm, a wall of notes can feel too crowded to use. Clustering helps a group see patterns and decide what to explore next. The risk is that people tidy the wall too quickly: two notes that use similar words may describe different needs, while two notes that look unrelated may point to the same obstacle. Treat clustering as a way to examine ideas, not as a vote on which ones matter.
Before moving anything, give everyone a few minutes to read the full set. Ask contributors to clarify notes that are hard to understand, using neutral questions such as, “What situation were you thinking of?” Keep the original wording visible, even if someone adds an explanation. A short phrase like “make it welcoming” might refer to the tone of an invitation, access to a venue or the first five minutes of an event. Those details affect where the idea belongs.
Group by a question, not just by resemblance
Choose the question the clusters need to answer. For a team planning a collaborative workshop, that might be, “What would help participants contribute?” A visual identity team might instead ask, “What qualities should the identity communicate?” The same set of notes can form different useful groups depending on the decision ahead. State the question aloud so participants know what kind of connection they are looking for.
Invite people to move notes into tentative groups, then ask them to explain the link between notes in each group. Look for a shared concern, desired outcome or stage of a process rather than matching keywords. “Send examples in advance” and “show a sample response” could sit together under “make the task easier to picture,” even though they propose different actions. Leave space between groups so notes can move; a cluster is a working interpretation, not a permanent container.
Keep the distinctions inside each theme
Once a group begins to take shape, write a theme label that describes its common ground without flattening it. “Help people prepare to participate” is more useful than “communication” because it explains why the notes belong together. Under that label, retain the individual notes and mark any meaningful distinctions: who benefits, when the action happens, or which problem it addresses. A label should help someone navigate the material, not replace it.
For example, notes about sending an agenda early and offering a quiet way to respond may both concern participation. But the first gives people time to prepare, while the second changes how they can contribute. Recording that difference prevents the team from choosing one action and assuming it has addressed the whole theme. If a cluster contains competing proposals, add a brief question beside it: “Do we need both options, or do they serve different people?”
Make room for outliers and disagreement
Do not force every note into a group. Set aside a visible space for ideas that do not yet fit, and call it “questions and outliers” rather than “miscellaneous.” An isolated note may reveal an overlooked need, or it may become clearer when the team knows more about the project. Either way, it remains available for discussion. You can also let a note sit between two clusters when its connection to both matters.
When people disagree about a placement, ask each person what relationship they see. The disagreement may show that a word has two meanings or that the group is mixing causes with solutions. If agreement does not come quickly, record both readings instead of spending the session on a perfect arrangement. For instance, “participants need more confidence” might belong with preparation materials or with facilitation during the workshop. Keeping both interpretations visible gives the team a better question to test later.
Turn the map into a usable next step
Finish by reviewing each theme against the original workshop question. Ask what the cluster tells the team, what it does not yet explain, and which distinctions could change a decision. Then choose a modest next step for each relevant theme: sketch two approaches, ask a participant to react to a draft, or examine a point of friction in the current process. Avoid treating the largest pile as automatically the most important; the number of notes can reflect how an exercise was phrased as much as the value of an issue.
Capture the result in a format someone absent can understand. Photograph the arrangement if useful, but also write down the theme labels, the notes within each theme, unresolved disagreements and the reason for the next step. This makes the clusters easier to revisit when the project changes. A good clustering session does not produce a flawlessly tidy wall. It produces a shared map that makes patterns easier to see while leaving enough detail to make thoughtful choices.
