Capture decisions during discussion, not after

This guide helps you capture decisions while discussion is live, not in a cleanup pass at the end. Use it when groups produce many ideas but ownership stays vague. In a hurry: define one decision format, run a short decision check every 10-15 minutes, and resolve conflicts by assigning an owner instead of forcing instant agreement.

Fast path (2-6 steps)

1. Set one decision format before breakout starts: decision, owner, date, confidence.
2. Monitor live transcript streams and stop when commitment language appears.
3. Read the decision back to the table in one sentence.
4. Confirm owner and date out loud.
5. Mark open questions separately so they do not pollute the decision list.
6. If tables conflict, assign one resolver and move on.

Before you start

Use this workflow when you are running parallel tables and need outputs people can execute next week.

Use another workflow if your goal is exploration only. In that case, capture hypotheses and evidence, then move to [Combine results from many tables without flattening nuance](/guides/workflows/combining-results-from-many-tables) later.

Prepare three things before round one:

• a visible decision standard in your intro slide or spoken brief
• one place where you track decisions table by table
• one fallback plan if a table phone drops (see [Reconnecting a device without losing the discussion](/guides/setup/reconnecting-a-disconnected-device))

Step-by-step during live discussion

1. Define what counts as a decision

Say this before people split:

"A decision today needs four parts: what we will do, who owns it, by when, and how confident we are."

If one part is missing, keep it as an open question.

2. Listen for commitment language, then pause briefly

Typical trigger phrases:

• "we will"
• "let's do"
• "we choose"
• "I can own that"

Do a short interruption, not a long facilitation detour:

1. draft one clean sentence
2. read it back
3. ask for owner and date
4. confirm confidence (high/medium/low)

This takes 20-40 seconds and prevents vague summary text later.

3. Keep decisions and unresolved questions separate

A common failure is mixing "we decided" with "we need to discuss this later" in one list. When that happens, summaries look complete but teams leave without clear commitments.

Use two buckets while listening:

• decisions: actionable now
• open questions: needs more input

When you generate the final host summary, this separation improves trust because stakeholders can see what is fixed versus pending.

4. Handle conflicts without freezing the room

With many tables, two groups will sometimes choose incompatible actions. Do not burn 15 minutes forcing immediate consensus.

Instead:

1. record both decisions with table context
2. assign one person to resolve conflict after the session
3. set a resolution date

If conflicts are frequent, tighten question wording in your next round or run a short alignment check using [Aligning tables on shared definitions](/guides/facilitation/aligning-tables-on-definitions).

5. Run one final decision check before close

Before people leave, ask each table:

• "Which decision here has an owner and date?"
• "Which point is still open?"

This check takes 5-10 minutes and makes [Review session results before people leave the room](/guides/workflows/reviewing-session-results) much faster.

Common pitfalls and fixes

Pitfall: waiting until the end to capture

When you postpone capture, participants forget wording and ownership becomes "the team".

Fix: run a mini decision check every 10-15 minutes.

Pitfall: over-facilitating every sentence

If you stop too often, discussion momentum dies.

Fix: only interrupt on commitment language or conflicting choices.

Pitfall: decision text is too abstract

"Improve handoffs" is not a decision. It is a direction.

Fix: force a verb + owner + date: "Run weekly handoff review, owner Sara, starts April 15."

Pitfall: technical issue at a key moment

If transcript pauses during decision locking, facilitators often restart the whole table conversation.

Fix: keep talking, recover device quickly, and capture one restatement after reconnect. Use [Replacing a participant phone during a session](/guides/setup/replacing-a-phone-mid-session) if recovery takes longer than a minute.

This guide is for...

Use this guide when your biggest risk is weak accountability after the workshop.

If your bigger risk is weak synthesis across many tables, start with [Combine results from many tables without flattening nuance](/guides/workflows/combining-results-from-many-tables).

Related guides

• [Review session results before people leave the room](/guides/workflows/reviewing-session-results)
• [Combine results from many tables without flattening nuance](/guides/workflows/combining-results-from-many-tables)
• [Capture breakout results participants can actually use](/guides/workflows/capturing-breakout-results)
• [Turning discussion into priorities](/guides/analysis/turning-discussion-into-priorities)
• [Reconnecting a device without losing the discussion](/guides/setup/reconnecting-a-disconnected-device)