Purpose before platform
Answer three questions before you touch a tool. What outcome are we creating? Who is this actually for? How will we know it worked? Pick two or three indicators and design against them.
The best sessions start with verbs: decide, build, align, imagine. Then pick the simplest technology that supports the verb.
Build the run of show like a storyboard
Think in acts rather than a schedule: opening energy, exploration, resolution. For each segment note the duration, the owner, the assets, the transition out, and the emotional tone you're aiming for. That last column is the one everyone skips and the one that makes the difference.
| Segment | Owner | Tone | Fails if |
|---|---|---|---|
| Arrival, 10 min | Producer | Warm, low stakes | Silence and muted rectangles |
| Framing, 5 min | Lead | Clear, brief | It becomes a presentation |
| Small groups, 25 min | All | Loud, generative | The prompt is vague |
| Synthesis, 15 min | Lead | Focused | Nobody wrote anything down |
| Close, 5 min | Lead | Reflective | It just stops |
In Kolab: the run of show lives inside the space as a timed agenda. Each section points at the board, timer, prompt or breakout it needs, so the plan and the room are the same object.
Build it once, run it twelve times
This is the part that changes the economics of a cohort. The first session of a program is expensive to design. Every session after it shouldn't be.
Across our own programs, a repeat session that used to take an afternoon to prepare now takes under an hour, because the space already exists. You reopen the room, swap the prompts and run it.
NewAgenda templates. Save a whole session as a template, including its timers, prompts, breakouts, card decks and Interactives, then reuse it for every session in the cohort. Build session one properly and the rest of the program inherits it.
Worth saying to your finance team: per-session prep hours are the number that justifies a platform line item. Attendance isn't. If you're writing this into a proposal, count the hours you won't spend rebuilding a board twelve times. Our proposal language page has adaptable text for exactly this.
Don't start from a blank canvas
Most program teams already have material: last year's Miro board, a Mural from a partner, a slide deck with the activities in it. Start from that.
NewPaste from Miro and Mural. Copy stickies, shapes, text and frames from either tool and they arrive as native Kolab elements. Moving an existing session over is now an afternoon, not a rebuild.
NewHave AI draft the room. Kola, the AI co-facilitator, drafts agendas and activities from your objective and can see your board while it works. If your team uses Claude, the Kolab connector lets it build spaces, boards, agendas and Interactives from a plain-language brief. Either way, a person reviews and decides. AI can also be switched off entirely, per space.
Prepare people, not just content
Speakers need coaching in the medium, not the material. Run a tech rehearsal. Assign roles explicitly. Decide in advance who watches chat and who watches the clock. Write down what happens if the host drops, because eventually the host drops.
Participants need preparation too, and one short message does most of the work: the schedule, one technical tip, and one sentence about what will be asked of them. Participants join by link, with no account and nothing to install, so that message can be short.
Two weeks out
- Outcome and two success indicators written down and agreed
- Run of show drafted, tone column filled in
- Roles assigned: lead, producer, chat, timekeeper
- Time zones checked against the actual participant list
- Pre-session message drafted, with the system check link in the calendar invite
- Accessibility pass: captions on, bandwidth plan, dial-in fallback
- Waiting room and opening music set
- Backup plan written for host drop and platform failure
- Full team rehearsal scheduled, not hoped for