Writing up a workshop or brainstorm: fast and done right

What belongs in a report?

A report is not minutes. You do not need to write down who said what, but you do need what the conversation produced. Use a fixed structure so readers know where to look.

• Goal and central question of the session, plus who attended.
• The three to five most important insights, in plain sentences.
• Where people agreed and where opinions differed.
• Choices made or priorities set.
• Next steps with owner and date.
• An appendix with the raw output for those who want more depth.

Capturing during the session

The better you capture during the session, the less you have to reconstruct afterwards.

Step-by-step: from session to report

1. Collect all material the same day: notes, photos, sheets.
2. Group the input into themes and count how often something recurs.
3. Write the insights and commitments first, then the explanation.
4. Ask a participant to check whether the report is recognisable.
5. Share the report within three working days.

Common mistakes

Too long: a ten-page report does not get read. Too late: after two weeks the energy is gone. Too biased: the note-taker writes what they personally found important. And too vague: sentences like 'communication was discussed' say nothing. Write down what was actually said about communication instead.

A fixed structure for your report

A fixed structure makes writing faster and reading easier. Start with a five-line summary for people who will not read further. Then the insights per theme, with two or three sentences per theme and possibly a striking quote from a participant. Explicitly state where the group disagreed; that is often the most valuable information for decision-makers. Close with the next steps in a table with action, owner and date. The raw output, such as flip chart photos or transcripts, goes in an appendix. Use the same structure for every session so reports become comparable and you can follow developments over a series of sessions.

Reporting on multiple tables or groups

With a session of ten or twenty tables the challenge is not the writing but the overview. Work in two layers. First write a short summary of a few lines per table. Then put the tables side by side and look for patterns: which themes come back at most tables, and where does a table clearly differ? Those differences are often interesting because they show where groups see a question differently. If you work in rounds, also compare round 1 with round 3: has the conversation become more concrete, or broader? Note for each insight how many tables mentioned it, so the reader can judge how widely it is shared.

Sharing and using the report

A report is only finished when it gets used. Do not just send it as an attachment; write the three most important points and the next steps in the email itself. Share it with all participants, including those who attended only part of the session, and with the people who make decisions based on it. Explicitly ask participants to respond within a few days if they miss something or experienced it differently. Then use the report actively: open the next meeting with the commitments from the report. A presentation with the key points often works better than a document, especially for people who were not there.

Faster with AI transcription

With a multi-table session, capturing everything by hand is almost impossible. EchoSphere records each table's conversation with one phone, produces live transcripts and summaries per table and per round, and prepares a summary and presentation at the end. Your report then starts not from a blank page and flip chart photos, but from a complete overview you only need to check and sharpen.

Frequently asked questions