How to run a roundtable discussion at a paid conference

To run a roundtable discussion at a paid conference, give a small group one worthwhile question, appoint a moderator who can manage the conversation, and leave time to turn what people say into a useful conclusion. Choose participants for relevant experience, prepare them before the event, and explain exactly what they can share outside the room.

So you've put a roundtable on the programme. The chairs are arranged, the topic sounds interesting, and a respected speaker has agreed to join. Then someone asks, "What does everyone think?" One delegate talks for most of the session. Another never speaks. Everyone leaves with the same question they arrived with.

You can fix that before anyone sits down. This guide covers the question, participants, moderator, preparation, room, discussion script and follow-up. We'll use a fictional roundtable about improving speaker preparation at a professional conference. Its headcounts and timings are planning examples, not research findings or customer results.

Give the roundtable one question worth answering

The first thing you want to do is finish this sentence. "People should leave this discussion able to decide..." If you can't finish it, the session needs more work. A subject such as conference content is too broad. It gives you no sensible way to choose participants, prepare prompts or recognise a useful ending.

For our example, the question is, "How can conference organisers help speakers deliver practical sessions when rehearsal time is limited?" Delegates can compare preparation methods, understand where those methods break down, and leave with something to try. They aren't expected to agree on a universal speaker policy.

Notice how much that question excludes. It isn't about finding famous speakers, negotiating fees, designing stage lighting or selling sponsorship packages. Those subjects might come up, but they don't become the session just because someone has an interesting story. The moderator needs that boundary as much as the delegates do.

Ask prospective participants whether the question describes a problem they actually face. Someone who runs an annual industry conference may recognise it immediately. Someone producing entertainment events might have little to contribute. That doesn't make one person more important. It means the invitation should match the work being discussed.

Write the intended outcome beside the question in your programme brief. Here, participants will compare preparation approaches and identify conditions that make each useful. That belongs inside your wider paid conference plan. You're spending programme time on a specific learning opportunity, so make its contribution clear before promising access to buyers.

Choose a discussion format you can actually deliver

A roundtable gives participants room to examine each other's experience. Everyone joining should understand whether they can contribute, how the moderator manages turns, and whether there are observers. Putting a panel behind a circular table doesn't give the audience a different experience if only the invited speakers talk.

For our fictional session, choose eight delegate participants, one moderator and one note taker. The moderator guides the conversation rather than bringing another prepared talk. The note taker captures the useful distinctions and checks wording with the group. Those are ten people in the room before you count any access support.

Eight delegates is our planning choice, not a rule that fits every conference. Work backwards from the time available and the depth you want. If each delegate needs to explain a case and respond to others, adding more people makes that harder. A larger audience may need a different session format or clearly described observer places.

We'd keep this example closed to observers because the delegates will examine mistakes in speaker preparation. They should know who hears them. If you want an audience, say how audience questions enter the discussion and what participation means. Don't sell a contribution opportunity and deliver a seat behind other people's conversation.

Keep the same people together for the full session. The value here comes from following one question far enough to test the answers. Repeated introductions and rotating tables serve a different purpose. For this roundtable, let people settle into the subject and hear how earlier contributions change as others challenge them.

Invite people who can move the question forward

Start with experience of the problem. Our speaker preparation roundtable needs people who have briefed speakers, reviewed talks, managed rehearsals or received those instructions as speakers themselves. A prestigious job title doesn't tell you whether someone has done any of that. Ask about a relevant situation rather than assuming seniority equals insight.

Use a short invitation or application question. "What have you tried to improve speaker preparation, and what would you like to understand better?" A brief answer is enough to judge fit. Explain whether places are selected, reserved in order of booking, or allocated through another stated process. People paying for the conference deserve a clear answer.

Look for useful differences within the shared problem. A programme director who works with first time speakers might challenge the assumptions of an organiser using experienced presenters. A speaker can explain why a preparation request was hard to follow. That variety helps when the participants can still understand and examine the same question.

Avoid building the whole group around friends of the moderator. Familiarity may make conversation easy, but it can also leave other delegates wondering whether they have entered someone else's private meeting. Give every participant the same preparation information and the same chance to bring a relevant case.

Confirm the invitation without exposing another person's application. Tell delegates the kinds of experience represented, the question and their expected role. Ask permission before sharing names or affiliations. If someone cannot attend, select a replacement against the same criteria and give them the preparation brief. Don't fill a chair with whoever happens to be nearby.

Be honest about access and commercial terms

Decide what the conference ticket buys before you open bookings. A limited roundtable can sit within general admission, require a separate reservation, or carry an additional charge. Each option needs clear conditions. A buyer should understand whether purchasing the ticket also confirms a roundtable place or only makes them eligible to request one.

In our example, the eight places are included with conference admission and allocated through a short application. The sales page says that plainly. Other delegates still receive the main programme they bought. Nobody should discover that the event's most prominently advertised session was available only to a handful of invitees after they have paid.

Cost the moderator's preparation, the note taker, room time and any required equipment. Include access arrangements in the delivery budget. If your headline speaker moderates, confirm that this work belongs in their agreement. A promise made by the sales team doesn't create another hour of availability in someone's schedule.

Sponsorship needs the same clarity. A sponsor can support the session without directing its conclusion. If a representative joins, they contribute under the stated rules. If the session includes a commercial presentation, describe it before booking. Delegates shouldn't have to work out halfway through whether the discussion exists to solve their problem or pitch a product.

Agree the boundaries with the sponsor contact and programme team together. Don't promise the sponsor participant details or attributed quotes that the session's sharing rules prohibit. Keep the moderator free to interrupt a sales pitch. Their authority becomes useless if another team member has quietly sold an exemption from the discussion rules.

Pick a moderator who will interrupt well

Subject knowledge helps, but the moderator's main job is to make the discussion useful. They need to follow an argument, notice who hasn't entered it, ask for a concrete example and stop a contribution that has gone off course. Being an entertaining speaker doesn't automatically prepare someone to do that work.

Ask candidates how they would handle a dominant participant, a long silence and two people disagreeing. Look for specific responses. "I'd keep it engaging" tells you little. "I'd summarise their disagreement, ask each person which conditions their approach depends on, and invite another case" tells you how they think.

UC San Diego's discussion facilitation guidance distinguishes guiding the process from directing the group towards a preferred outcome. It also recommends checking interpretations with the people speaking. For this conference roundtable, brief the moderator to test the answers without deciding in advance which participant should win the argument.

Give them authority to manage time and conduct. They should be able to pause a contribution, change the order of speakers and involve the organiser when behaviour needs attention. Explain where their authority ends, too. They shouldn't improvise a new booking arrangement or promise access to another session because someone is unhappy.

Run a rehearsal with the actual question. Let a colleague give an overlong answer or vague recommendation, then have the moderator respond. This isn't about memorising a performance. It shows whether the prompts work and whether the moderator can get back to the question without making a participant feel publicly dismissed.

Send a preparation brief people will read

Keep the brief short enough that a busy delegate can use it. Include the question, intended outcome, start and finish times, room, participant role, sharing rules and contact for access requests. Say whether anything needs reading in advance. Don't hide essential instructions in a long general conference email.

For our example, ask participants to bring one speaker preparation request that worked or failed, with names and identifying details removed. They should be ready to explain what they asked for, how the speaker responded, and what they would change. No slides are required. That gives the conversation evidence without turning preparation into unpaid homework.

If you supply a reading, explain why it matters and what to notice. A short anonymised example brief might be enough. Don't send a stack of reports and hope delegates find the same point. The moderator needs a fallback summary for anyone who arrives without having read the material.

Tufts' guidance on effective discussions recommends planning questions, considering advance contributions, establishing expectations and protecting the wrap-up. That guidance concerns teaching. For your conference, use those habits to brief participants, prepare follow-up questions and leave time for everyone to check the conclusion together.

Ask for questions before the event so the moderator can spot misunderstandings. If most applicants expect a session about recruiting speakers, clarify the advertised scope before confirming them. A preparation email should help people decide whether the session suits them. It shouldn't be the first place they learn what you really meant by the title.

Here's a participant invitation you can adapt for the example. "We're running a discussion on helping conference speakers deliver practical sessions when rehearsal time is limited. We'd like you to join because you have experience briefing speakers. Please bring an anonymised example of a preparation request that worked or failed. You'll compare approaches with other delegates, contribute when you wish, and help us check an unattributed summary before it is shared. A confirmed conference ticket is required. Applying does not guarantee a place."

Keep the practical details directly underneath that invitation. Name the room, timing, application deadline and access contact. Include the sharing agreement where someone can read it before applying. Have a colleague unfamiliar with the session read the invitation and explain what they expect to happen. If they expect a presentation by your headline speaker, the wording still needs work. Better to find that misunderstanding before the delegate books travel.

Agree what stays in the room

Choose sharing rules that suit the subject and the output you plan to produce. An open discussion with attributable notes works differently from a discussion where ideas may circulate without identifying participants. Explain the choice before people agree to attend, then repeat it at the start. "Be respectful" doesn't answer whether someone may quote a delegate online.

The Chatham House Rule allows people to use information received while protecting participants' identities and affiliations. It therefore does not mean everything said must remain secret. If you use it, read the official explanation and make sure your invitations, notes and publicity follow the same rule.

For our example, use a plain agreement that participants may share general learning but may not identify contributors or their organisations. No photographs, recordings or public participant list will be produced for this session. The group reviews the unattributed summary before distribution. Tell the note taker and conference photographer these instructions, too.

Don't ask people to reveal information they lack permission to share. A delegate can explain that a rehearsal request arrived too late without naming the speaker or showing their messages. When the example needs sensitive detail to make sense, the participant can pass or discuss a different case. Keep that option available throughout.

Plan how an access requirement might affect the arrangement. Someone may need a support professional or a particular way to retain information. Discuss it privately in advance, agree a workable approach with them, and communicate only what the group needs to understand. A blanket recording ban announced at the door leaves little room to solve anything.

Set up the room for the actual conversation

Check the room with the moderator and venue team. Everyone needs to see and hear one another, reach their place, and leave when necessary. A round table is one possible arrangement. Chairs around an open space may work better. Choose the layout for the participants and approved room conditions, rather than the name of the format.

Keep the room away from noise where possible. A small group beside the exhibition floor can still struggle to hear. Test the sound with people in the seats you will use. Give the note taker a position where they can follow contributions without becoming a barrier between participants or blocking the route into the room.

W3C's accessible events checklist covers accessible materials, microphones, clear speech and time to process information. It notes that some people need amplified audio even in a small room. Ask about requirements beforehand and confirm the equipment and support you will actually provide, rather than assuming proximity solves access.

Make the question and prompts available in an accessible written format, and read them aloud. If the group refers to notes displayed in the room, say what has been recorded. Someone shouldn't have to see a board to understand the conclusion being tested. Keep paper or another agreed contribution method available for anyone who prefers it.

Protect arrival and departure time in the conference agenda. Delegates need a chance to reach the room without missing the opening agreement. If an earlier talk overruns, use the response your programme team has agreed. Don't make the moderator invent a shortened session while participants are still trying to find their chairs.

Build a timetable that protects the ending

Our fictional roundtable runs for sixty minutes. Give the first five minutes to the purpose, roles and sharing agreement. Spend the next ten on brief introductions and relevant cases. Use twenty minutes to examine those cases, fifteen to test possible approaches, and ten to check the summary and individual next steps.

The note taker should receive these checkpoints too so their records follow the discussion as it develops.

Those allocations total sixty minutes. They're a working plan for this group, not recommended minimums for every roundtable. The introduction block gives eight delegates roughly a minute each, with time left for transitions. Ask for their role and one relevant difficulty. Full biographies would consume time you need for the actual question.

Put checkpoints in the moderator's notes. At fifteen minutes, the group should have enough cases to begin examining them. At thirty five, move towards testing approaches. At fifty, start the conclusion even if another interesting example is waiting. A useful unfinished question can appear in the summary; a missing summary gives people nothing to check.

Don't try to give every case equal airtime. Choose cases that reveal different conditions, explain the choice, and let participants add missing circumstances. The moderator should still offer everyone an opportunity to contribute. Equal opportunities do not require an identical number of minutes for every story.

Keep a shorter version ready. If the session begins late, preserve the sharing agreement and conclusion, reduce the number of cases, and tell participants what changed. If you can no longer deliver the advertised experience, involve the programme coordinator. Squeezing the full plan into a rushed conversation won't recover the time or honour the offer.

Use prompts that make people explain their answers

Start by giving people a moment to think. Stanford's small group activity guidance describes individual reflection before discussion and explains why skipping that step can disadvantage people who need quiet processing time. For this roundtable, let delegates note an answer before opening contributions. You don't need to add a separate activity.

The opening prompt can be simple. "Think of a speaker preparation request that produced a useful change in the session. What did you ask for, and how did you know it helped?" Invite a participant to share, then ask another whether their experience supports or challenges that example.

Move beyond preference with follow-up questions. "What made that request manageable for the speaker?" "What information did the organiser have at that point?" "Would it still work if the speaker joined late?" Each question reveals a condition. That's more useful than collecting recommendations that sound sensible until someone tries to apply them.

For a vague answer, ask for the action. If someone says, "We improved communication," the moderator can ask, "What did you send, who sent it, and what happened next?" Don't let a phrase stand in for a process. The point is to help delegates understand what they could do differently after the conference.

Test the favourite idea before closing. "Suppose a speaker cannot attend a rehearsal. Which part of your approach still helps, and which part needs replacing?" The group may discover that a short outline review matters more than another meeting. That's a useful conclusion if they can explain when it applies and what remains uncertain.

You can also prepare a short fictional case for the rehearsal. A speaker receives a request for finished slides before they have agreed the audience's starting knowledge. They send polished slides, but the organiser later discovers the session assumes experience many delegates don't have. Ask the moderator to work through that sequence without prescribing the answer. Where could the organiser have checked the assumption? What would the speaker have needed to provide?

Now change the circumstances. Suppose the speaker is experienced, the audience is familiar to them, and the session uses a practical demonstration instead of slides. A slide deadline may tell you very little. Ask which preparation request would help in that case. Testing a recommendation against a different situation gives participants a reason to explain their judgement. It also helps your moderator recognise the difference between a useful principle and a process someone follows because their team has always done it that way.

Have a script for the awkward moments

At the opening, the moderator might say, "We're examining how to prepare speakers when rehearsal time is limited. You can pass on any question. Please describe cases without identifying people, and help us hear the different circumstances behind each approach." Then they confirm the sharing agreement and explain the note taker's role.

When someone talks too long, interrupt while the point is still clear. "I'm going to pause you there. We've heard how the outline review worked. I'd like to hear a case where it didn't." That acknowledges the contribution and opens a specific comparison. Waiting until people visibly lose patience makes the intervention harder for everyone.

When the room goes quiet, make the question smaller. "Which part of the speaker brief usually needs clarification?" Give people time to think, then invite an answer without requiring it. You can offer a written contribution route. Silence doesn't necessarily mean nobody has anything useful to say, and naming the quietest delegate can make matters worse.

When advice conflicts, ask about circumstances. "One approach uses a rehearsal; the other reviews an outline. What risk is each trying to catch?" Have the note taker record the distinction. Don't force agreement merely to create a neat ending. Different circumstances can support different decisions, and delegates need those conditions in the summary.

When the subject drifts, name the connection and the limit. "Recruitment affects preparation, but selecting speakers is outside today's question. Let's record it as a follow-up topic and return to what happens after confirmation." If behaviour becomes personal or inappropriate, pause the exchange and use the conference's agreed conduct response. A discussion rule needs someone willing to apply it.

Turn the discussion into something delegates can use

Ask the note taker to capture the approach, circumstances, reported experience and unresolved question separately. "Review an outline" isn't enough. "Review an outline before slide production when a speaker is unfamiliar with the audience" tells the delegate when to consider it. Record the group's recommendation as advice, not as a proven result.

At the end, read back the main distinctions and ask participants what you have misunderstood. Give them room to correct the wording, remove an identifying detail or keep a disagreement visible. The moderator should resist writing a cleaner story than the discussion supports. An honest conclusion can include a question the group could not answer.

For our fictional session, the summary might distinguish outline review, an audience briefing and a rehearsal, with the conditions under which participants would choose each. These are possible outputs for the example, not findings from an actual event. The real summary must come from what the people in your room said and agreed could be shared.

Ask each delegate privately to note one action they might test. They don't have to promise a public change or report back to the organiser. A participant may decide their existing process is appropriate, or that they need another conversation with their team. That can still be a useful outcome if the discussion clarified the decision.

Name the person responsible for circulating the checked summary and the route for corrections. Share relevant resources only after checking they match the conversation. Don't attach every speaker presentation because it's available. The follow-up should make the roundtable easier to use, rather than giving delegates another pile of material to sort through.

A checked summary can stay short. "Participants considered an early outline review useful when the organiser needs to confirm the session's practical outcome before slides are built. They discussed rehearsal as a way to examine delivery, while noting that scheduling one can be difficult. The group did not resolve how to review a demonstration that cannot be reproduced before the event. Participants suggested taking that question to the relevant production team."

That fictional wording shows the standard to aim for. It names the circumstances, preserves a limitation and gives the unresolved question somewhere sensible to go. It doesn't claim everyone agreed that rehearsals are essential, or that an outline review caused better delegate feedback. Your note taker needs to keep those distinctions visible when turning a lively discussion into readable notes for participants afterwards.

Follow up and decide whether to run it again

Loopyah's attendee email tools let you send event updates and create segments based on what people bought. Use the appropriate audience for conference updates, and check the recipients before sending anything intended for this roundtable. A roundtable place still needs its own confirmed participant record and sharing agreement.

Send the checked summary through the agreed channel. Ask whether the discussion helped people understand a decision, whether they had a workable chance to contribute, and what was missing. Keep these questions separate from whether they enjoyed the whole conference. An excellent keynote can otherwise hide a roundtable that delivered very little.

Review the moderator's notes with the programme team. Did the group get beyond introductions? Which prompt produced concrete cases? Was preparation useful? Did the final summary reflect different circumstances? Look at the time and cost as well. A session can receive warm feedback while requiring more staff work than your next edition can afford.

Don't turn a small group's responses into a claim about all delegates. Read them alongside your own delivery record and make a specific change. You might narrow the question, improve the participant brief or allow more time for testing approaches. If the subject required a specialist explanation before anyone could discuss it, choose a workshop next time.

A paid conference roundtable earns its place when the right people examine a question they care about and leave understanding what to do with the answers. Start there. Make the promise clear, prepare the moderator and participants, and protect the conclusion. The chairs are the easy part.