Run a multi-table workshop with RoomRadar

Running one table is mostly about group dynamics. Running eight tables is operations.

This guide is written for the moment when you are responsible for both: people in the room and reliable capture in RoomRadar.

Where this workflow fits

Use this when you have several tables working in parallel and you need to:

• keep discussions moving without hovering over each table
• capture enough conversation for meaningful summaries
• leave with outputs you can defend in a report later

Do not use this as-is for a tiny session with one table. In that setting, a lighter facilitation flow is faster.

A realistic prep timeline

45 minutes before start

• Open the session and create one group per physical table.
• Name groups by table markers participants can see (Table A, Table B, Window 1, etc.).
• Confirm one phone per table is available and charged.
• Place one backup phone near you, already tested on the same network.

Why this matters: most first-session mistakes are group mapping mistakes. If the room says "Table 3" and RoomRadar says "Group 7", you will lose time every time you intervene.

20 minutes before start

Run a live test at each table:

1. Ask someone to say one sentence in a normal voice.
2. Check that text appears in the correct group.
3. Move the phone if speech is weak or dominated by nearby tables.

Use the same test phrase at all tables so you can compare quality quickly.

"Table B test. We are checking capture and transcript clarity."

5 minutes before start

Give a short operating brief:

• phones stay flat on the table, not in pockets
• one person speaks at a time when possible
• if a table goes quiet due to confusion, raise a hand

Keep this brief practical. Participants do not need a product demo.

Live facilitation sequence

Phase 1: Launch (first 10 minutes)

• Set the task clearly and display the exact output format.
• Start table work.
• Watch RoomRadar for two things only: active speech and correct group mapping.

Do not correct wording or content at this stage. Your job is to verify every table is actually running.

Phase 2: Guided divergence (main discussion block)

Use a rotation:

1. Scan all groups in RoomRadar.
2. Visit one table physically.
3. Give one intervention question if needed.
4. Move on.

A good intervention is specific:

• "What example from your last project supports this point?"

A weak intervention is generic:

• "Keep discussing this."

Phase 3: Convergence (last 15-20 minutes)

Shift from open exploration to capture-ready outputs:

• ask each table for top 2-3 points only
• convert vague statements into clear sentences
• confirm owners and dates for action items

Scenario: Table D has strong talk but no decisions. Ask: "If you could only commit to one action this month, what is it and who owns it?"

Common pitfalls in first large sessions

Pitfall: You spend too long at one table

Symptom: one table gets high-quality coaching; others drift.

Fix:

• time-box table visits to 2-3 minutes
• leave a clear micro-task before moving
• return on your next rotation

Pitfall: Transcript exists, but outputs are weak

Symptom: lots of words, little usable outcome.

Fix:

• require an output template: insight, evidence, next step
• remind tables in the final third, not only at kickoff

Pitfall: Cross-table noise lowers transcript quality

Fix:

• move phones toward primary speakers, away from room edges
• run shorter rounds with mini-resets
• prioritize capturing conclusions, not every sentence

Troubleshooting under pressure

A table suddenly drops out

1. Do not stop the room.
2. Rejoin with backup phone assigned to that same group.
3. Ask for a 10-second recap from that table so summaries recover context.

Text appears in the wrong group

1. Stop only that table for 20 seconds.
2. Reconnect phone to the correct group.
3. Repeat test phrase.

One table is silent for too long

Treat silence as a facilitation signal, not just a technical signal.

• Ask what they are stuck on.
• Offer a narrower prompt.
• Give them three minutes and revisit.

Facilitator notes after the session

Before participants leave, do a rapid validation pass:

• "Is this summary accurate?"
• "What is missing?"
• "Which point is most important to carry forward?"

This five-minute pass prevents most reporting errors later.

Once participants have left, open the analysis workspace to generate the full output suite: post-it wall, insight report, presentation deck, sketchnote, and participation overview. These are generated automatically from the captured conversations and are usually ready within a few minutes.

If you run this flow two or three times, your main workload shifts from firefighting to pattern spotting. That is when RoomRadar becomes most useful: not as an autopilot, but as reliable infrastructure for your facilitation decisions.

If you are troubleshooting a related case, start with [Manage multiple conversations at one table](/guides/workflows/managing-multiple-conversations-at-one-table).

Related guides

• [Understand and generate your workshop analysis](/guides/analysis/understanding-workshop-analysis)
• [Manage multiple conversations at one table](/guides/workflows/managing-multiple-conversations-at-one-table)
• [Capture breakout results participants can actually use](/guides/workflows/capturing-breakout-results)
• [Capture decisions during discussion, not after](/guides/workflows/capturing-decisions-during-discussion)
• [Review session results before people leave the room](/guides/workflows/reviewing-session-results)