Begin before you begin
The first ten minutes set the terms for everything after. Use names. Set the frame. Ask for something tiny and easy first, because someone who has already succeeded once is far more likely to speak later.
Keep everyone looking at the same thing
On an infinite canvas, people wander. That's a feature during exploration and a problem during instructions.
NewFollow the leader. When you need the room with you, turn it on and every participant's view follows yours as you move around the board. Turn it off and they're free again.
Manage energy like a producer
In virtual rooms energy is invisible until it's gone. Read chat volume, camera use, and how long the pause is before someone answers. Then act on it out loud. Naming the energy is usually enough to change it.
Narrate every transition
Clunky transitions cause more fatigue than long sessions do. Say what's happening, how long it will take, and what happens when it ends. Participants forgive almost anything if they trust somebody is driving.
In Kolab: the agenda runs inside the session, so timers and transitions are visible to participants rather than living in a doc only you can see.
Run small groups without a facilitator in every room
Small groups are where cohorts bond, and they're where most virtual programs quietly fall apart. Each room needs a clear prompt, a clock, and a way back. Most programs can't staff a facilitator per room, so the structure has to do that job.
- Write the prompt as a task with an output, not a topic. "Agree on one barrier and put it on the board" beats "discuss barriers."
- Give rooms a visible timer and a two-minute warning.
- Ask each group to leave something behind so the plenary has material.
NewBreakout rooms with their own agendas. Assign people, mix them randomly, or let them choose a room. Each room can carry its own agenda and timer, you can see every room at once from a control view, and you can broadcast audio to all rooms for the two-minute call. For informal small talk, spatial audio zones still work without any formal breakout at all.
Make it accessible as you go
Live captions, colour-coded by speaker, work in breakouts as well as in the main room. Participants on weak connections can cut incoming video without turning off their own camera, and chat translation is available to anyone who opts in. Mention all three at the start. People rarely ask.
Embrace imperfection
Something will break. The goal isn't to prevent it, it's to normalise it. Narrate calmly, use humour, hand off to a co-host, stay human. People remember your response, not the failure.
| What breaks | What you do |
|---|---|
| Audio echo | Mute all, bring mics back one at a time |
| Background noise in a breakout | Ask for headphones by name, or move the person to a quieter zone |
| Speaker drops | Host summarises the last point, move to Q&A |
| Someone needs to show their screen | Participant screen share is off by default and works by request and approve, so turn it on for that person only |
| Bandwidth collapse | Cameras off, data saver on, continue on audio |
| Platform outage | Producer sends the pre-written email with the backup link |
In Kolab: Kola can cluster sticky notes and draft a summary while you keep facilitating. It drafts and suggests; it never takes the mic.