Workshop Builder

A workshop earns its name when it produces something a recorded video can't: real-time practice with feedback, social accountability from doing the work alongside other people, and a tangible artifact in every participant's hands by the end. If the session could be replaced by a video, it shouldn't be a workshop. Most "workshops" fail this test — they're 70 minutes of lecture, 15 minutes of Q&A, and a goodbye. Attendees leave with notes and the feeling that they probably should have been working instead.

The non-negotiable ratio is 30/50/20. Thirty percent teaching — presenting the framework, the concepts, the examples. Fifty percent doing — exercises, practice, creation, group work. Twenty percent sharing — debriefs, hot seats, peer feedback, reflection. A 90-minute workshop with 45 minutes of lecture is a webinar pretending to be a workshop. The "doing" portion is where transformation happens; the "sharing" portion is where commitment happens, because participants who hear their peers struggling with the same thing realise they're not the only one. Every exercise has to produce an artifact — a filled-in template, a written draft, a decision matrix with their data in it — because the artifact is what they take home, what they point to, and what makes them more likely to actually use what they just learned.

The architecture is built around the quick win. Within the first 15-20 minutes, every participant completes one small exercise that produces an immediate visible result. That single moment flips the room — the energy stops being "I'm watching a presentation" and becomes "I'm actively working on my stuff." From there, the 90-minute structure splits into two Core Blocks (teach, exercise, debrief, each ~25 minutes) and a Closing Block (integration exercise, hot seat or Q&A, backend handoff if applicable, clean close with energy). Each Core Block builds on the artifact from the previous one, so by the integration exercise the participant has assembled the complete output the workshop promised.

Virtual delivery is treated as a different craft, not a translation. Breakout rooms get exact group sizes, time limits, and explicit prompts. Chat-based responses are designed in where physical share-outs would normally happen. Tech setup gets sent 24-48 hours ahead — test Zoom, headphones, browser, the works — because the workshop you've planned doesn't survive a participant fighting audio for the first ten minutes. Recording is flagged at the start; breakouts are usually unrecorded and that gets called out for participants who want to review later. Half-day adaptations add a third Core Block, an extended hot seat, a mandatory 10-minute break at the midpoint (energy crashes without it), and 15 minutes of flex time because half-day workshops always run long.

Output is a workshop overview, a minute-by-minute run sheet customised to the topic, a full slides outline with speaker notes (six words or fewer per bullet — slides support the speaker, they don't replace them), ready-to-distribute exercise worksheets, a facilitation guide with timing cues and stuck-participant prompts, a participant materials list (before, during, after), a pre-workshop preparation checklist, and a post-workshop follow-up email template. If a backend offer is in play, the handoff is written as logical next step — not as a sales pitch tacked onto the end of a free workshop. That's the difference between a session that converts and a session that feels like a bait-and-switch.