Reading the insight report

The insight report is a narrative account of what happened across all groups in your workshop. It identifies cross-table themes, patterns in participant responses, and findings that emerged from the full session — not just one table.

It is generated automatically as part of your workshop analysis. You do not write it; you read it and apply judgment to it.

What the report contains

The report is organized around findings. Each finding names a theme, describes the evidence behind it (which groups, how many voices), and surfaces any tensions or contradictions within the theme.

You will typically see:

• Shared themes — ideas raised by multiple groups independently
• Divergent views — areas where groups described the same topic differently or reached opposing conclusions
• Strong minorities — a position held clearly by one group that differs from the broader pattern
• Weak signal items — observations that appeared but lacked supporting evidence

The report is written to be readable by someone who was not in the room. It provides enough context to understand the finding without needing to read every transcript.

How to read it critically

The report is a first-pass interpretation built on transcripts. It reflects what participants said in the discussion, filtered through how well the discussion was captured. Treat it as a well-informed draft.

Read the whole report once before forming conclusions. Then go back through the findings and ask, for each one:

• Does this match my observation of what happened in the room?
• What is the evidence quality? Is it a strong claim supported by multiple groups, or a thin claim from one session?
• Is there something I know from facilitation experience that the text could not have captured?

The report does not know what was in your head as facilitator — the design intent, the interventions you made, the group dynamics you observed. Your job is to layer that knowledge onto the text.

Using it for follow-up

The insight report is designed to be shared with stakeholders who were not present. It gives them a structured picture of the session without requiring them to review transcripts.

When sharing, consider whether any findings need context the reader will not have. A one-paragraph framing note explaining the workshop goal and participant composition often makes the report significantly more useful.

If you need to edit findings before sharing — for accuracy, emphasis, or sensitivity — you can do that in the report view before generating a share link.

What the report is not

The insight report synthesizes discussion. It does not evaluate whether the discussion was strategically correct or whether the conclusions are right. That judgment belongs to you and your stakeholders.

It also does not replace the group-level summaries. The insight report aggregates across tables; the summaries give you the table-by-table detail. Both are available in the analysis workspace.

Troubleshooting

"The report describes a finding I believe is wrong"

Re-open the relevant section and check the transcript evidence it links to. If the transcript accurately reflects what was said but participants misspoke or were joking, note that. If the report has drawn a wrong inference from accurate text, use the edit view to correct the finding before sharing.

"An important theme is missing from the report"

Check whether the relevant discussion produced enough transcript content to be picked up. Thin coverage at a table — poor audio, very short discussion, a group that did not speak clearly into the microphone — results in underrepresentation. If you know the finding from facilitation experience, add it manually using the edit view.

"The report is too long to share directly"

Use the presentation deck instead. It extracts key findings into a slide format that is easier to review in a meeting. For a one-page visual, the sketchnote is an option.

Related guides

• [Understand and generate your workshop analysis](/guides/analysis/understanding-workshop-analysis)
• [Reading the post-it wall](/guides/analysis/reading-the-post-it-wall)
• [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)
• [Turning discussion into priorities](/guides/analysis/turning-discussion-into-priorities)