We've walked all five phases of the Workshop Doctor Roadmap — PLAN, DESIGN, DEVELOP, DELIVER, EVALUATE — at phase level: what each phase is for, how to think about it, and the specific work the phase resolves. To make the methodology practical, this case study applies it to a specific workshop — contrasting how most coaches and creators build their workshops today with what applying the Roadmap produces.
This case study follows Mark, a fictional workshop creator built from patterns typical of coaches and creators running early-stage group programs. Mark runs Launch Lab — a six-week cohort for creators building their first group program. Like most cohort programs on the market, he had been running it this way:
- Format: six-week cohort, twenty-five seats per round, $2,500 per seat
- Audience description: "coaches and consultants who want to scale"
- Weekly topics: positioning, pricing, the conversion conversation, email funnels, launches, client delivery
- Pre-work: "read this article before next session"
- Session shape: teaching segment → small-group discussion → Q&A at the end
- Session assets: seventy-five to eighty slides per session, plus a thirty-page workbook participants took home
- Comprehension checks: "any questions?" at the end of each teaching segment
- Evaluation: five-question satisfaction survey at the end of the cohort
Here's what that produced:
- Satisfaction: 9.1 out of 10
- Recommendation rate: 94%
- Implementation rate, three months after each cohort: 8 to 12%
That pattern — strong ratings and near-zero behavior change — is what workshops typically produce when they're built the way most coaches were taught to build them. It isn't a motivation problem on the participant's side; it's a methodology gap the Roadmap is designed to close.
Mark could see the gap between the ratings and the implementation. He didn't know what was producing it. What follows is his same workshop walked through all five phases of the Roadmap, one phase at a time. Each phase sharpened what the phase before it had decided, and each sharpening unlocked what the next phase could actually do. The implementation numbers landed differently on the other side: 72% after the first iteration, 88% after the second.
PLAN — Who Launch Lab Was Actually For
The first thing that changed was the audience description — and with it, the problem statement, the outcome, and the active learning method the cohort would run on. Those four decisions anchor every decision that follows. Mark's original three (audience, problem, outcome) were broad enough that any content aimed at them had to work for everyone simultaneously, which meant it couldn't go deep for anyone; his fourth (method) wasn't a decision at all — it was the unexamined default of delivering content through slides.
|
|
Before |
After |
|---|---|---|
|
Audience |
"Coaches and consultants who want to scale" — broad enough to describe almost anyone running service-based work, which meant Launch Lab was trying to serve two distinct groups (service-based coaches running 1:1 practices and B2B consultants operating on different sales cycles and client models) with the same content. |
"Service-based coaches — health, business, or life — with two to five years of experience and $100K to $300K in annual revenue, whose 1:1 practice is maxed and who want to launch a first group program that actually converts and delivers." One specific participant profile the six-week cohort could actually build for. |
|
Problem |
"They want to scale." Expert-framed, abstract, and generic enough that every participant interpreted it differently. |
"My 1:1 coaching is capped and every attempt to scale — raising prices, launching a group offer, building a funnel — has either stalled at launch or produced a program I can't sustain." The problem stated in the participant's own words and scoped across the six-week arc rather than to a single session. |
|
Outcome |
"Learn the Launch Lab framework." Knowledge-tier — not observable, not measurable, not producible. |
"Produce a complete launch plan — positioning statement, pricing framework, conversion script, email sequence, launch calendar, delivery cadence — and defend each artifact against a live audit before Week 6 ends." Transformation-tier — six specific artifacts the participant builds, each testable by live defense against an evidence-based audit. |
|
Method |
No active learning method intentionally selected. Launch Lab ran on a content-delivery default — slides on this week's topic, Q&A, workbook to take home — with "active learning" treated as an occasional technique Mark reached for when a session felt flat, not as a structural framework he'd chosen. |
Project-based learning. The six-week cohort is structured as one sustained project: each participant builds their own group-program launch, weekly topics serve as stages of that project, and each session produces an artifact that stacks toward the final launch plan. The method fits because the outcome is itself a produced artifact — the cohort's structure now mirrors the shape of the work. |
None of these were cosmetic changes. Mark was nervous about narrowing the gate — excluding consultants entirely and trimming coaches down to one specific stage meant risking enrollment. Enrollment held. The participants who self-selected in were the ones the workshop could actually help, and the downstream effects of PLAN's sharpening were larger than any of the later phases' individual sharpenings.
DESIGN — What Each Session Would Produce
With the audience, problem, outcome, and method locked, DESIGN could build a session shape that actually produced the outcome — not just covered the topic. The changes were structural: session flow, pre-work, and how the weeks connected into one continuous cohort-wide build.
|
|
Before |
After |
|---|---|---|
|
Session flow |
Each 2-hour session opened with introductions or a recap, then Mark worked through the week's slide deck (sixty to seventy minutes of presentation), broke participants into small-group discussion (fifteen to twenty minutes), and closed with Q&A. The session was a topic presentation with discussion wrapped around it; nothing in the room was required to produce anything. |
Each 2-hour session scaffolded around producing that week's artifact. 5-min opening: Mark pulls prior weeks' artifacts back into active memory — Week 3 opens with Week 1 positioning and Week 2 pricing already refreshed on screen. 60-min deep application: participants work on this week's specific artifact — positioning statement (Week 1), pricing framework (Week 2), conversion script (Week 3), email sequence (Week 4), launch calendar (Week 5), delivery cadence + audit prep (Week 6) — filling in the week's one-page template as they go, while Mark circulates. 30-min structured debrief: rotating pairs review each other's artifact against rubric criteria while Mark coaches against specific gaps. 5-min takeaway: each participant names the specific revision they'll make before next week. Participants leave the session with a draft-level artifact in hand, not a set of notes about the topic. |
|
Pre-work / between-session work |
"Read this article before next session." Optional supplementary reading. Almost nobody did it, and the live session didn't assume they had. |
Each week's pre-work is a load-bearing draft of that week's artifact. Week 1 = a positioning-statement draft against three prompts Mark sends. Week 2 = refined positioning + a pricing draft at current rates. Week 3 = refined pricing + last-three-sales-call transcripts. Week 4 = conversion script + current subscriber list. Week 5 = email-sequence drafts + intended launch window. Week 6 = launch-calendar draft + delivery-cadence plan. The opening activity operates on the draft; a participant who didn't produce it can't start the 60-min block cleanly. Between sessions, participants revise the week's artifact against debrief feedback — the revision lands in the shared project folder before the next session starts. |
|
Cohort architecture |
Each week was a standalone topic presentation. Week 1's material wasn't pulled forward into Week 2; Week 3 didn't assume anything from Weeks 1 or 2. The six weeks read as six disconnected workshops taught by the same facilitator. |
The cohort reads as one continuous build, not six disconnected sessions. Week 2's pricing has to hold up against Week 1's positioning. Week 3's conversion script has to be coherent with both. Week 4's email sequence references Week 2's pricing and Week 3's script. Week 5's launch calendar sequences Week 4's sends. Week 6's delivery cadence anchors to what Week 5 launches. By Week 6, the live audit tests all six artifacts as one coherent launch plan — each artifact's quality depends on the prior artifacts' quality, and a weak Week 1 positioning limits what every subsequent artifact can do. |
By Week 6, participants had produced a stacked body of their own work — not Mark's. The cohort shape had shifted from six weeks listening to Mark to six weeks producing alongside him.
DEVELOP — What the Session Actually Needed
Once DESIGN specified the activities, DEVELOP's job narrowed: produce only the specific tools the session actually needed, and cut everything else.
|
|
Before |
After |
|---|---|---|
|
In-session visuals (slide anchors) |
Seventy-five to eighty slides per session, dense with text, bullet points, examples, frameworks, and edge cases. Years of craft had gone into them. Most of each session's time was spent reading through the slides or talking around them. |
Eight to ten slides per session, each one a visual anchor for that week's 60-min application block — Week 1 slides anchor the positioning frame, Week 2 slides anchor the pricing-tier structure, Week 3 slides anchor the conversion-script arc, Week 4 slides anchor the email-sequence timing, Week 5 slides anchor the launch-calendar structure, Week 6 slides anchor the delivery-cadence + audit criteria. Content that had lived on the seventy-plus slides moved into pre-work (higher-order material that needs to arrive warm) or the facilitator cue sheet (context Mark needed but the participant didn't). |
|
Participant artifact templates |
A 30-page reference document participants took home. Most of it was never opened between sessions — it was content to have, not content to use. |
Six one-page templates, one per week, each scoped to that week's artifact — positioning template (Week 1), pricing-tier template (Week 2), conversion-script template (Week 3), email-sequence template (Week 4), launch-calendar template (Week 5), delivery-cadence + audit-prep template (Week 6). Participants fill them in during the live 60-min block; by the end of six weeks, the completed stack is the participant's own launch plan, not Mark's workbook. The templates also seed the pre-work — each week's draft lands on the template before the session starts. |
|
Facilitator assets |
No dedicated facilitator assets. The slide deck doubled as Mark's script, reference, and pacing guide. Breakout instructions were verbal ("break into threes and discuss"). No audit rubric existed because no audit existed. |
A per-week facilitator cue sheet (what to watch for in the template, which prior-week artifacts to pull forward, which misapplications to catch early), printed breakout-prompt cards (prompt + role structure + deliverable + debrief question for every breakout in the session), and a Week 6 audit rubric naming what counts as a pass across all six artifacts. These assets run parallel to the slides — participants don't see them, but they're what lets Mark operate in coach mode. |
|
Tech stack |
Five platforms, some with overlapping functions — a slide tool, a polling tool, a second slide platform, a breakout platform, a survey tool. Each one was one more thing that could fail, confuse a participant, or slow the session down. |
One integrated platform for the entire session, rehearsed deeply, with a backup plan for the most failure-prone pieces. Fewer tools tested thoroughly beats more tools tested lightly. The shared project folder — where pre-work drafts and between-session revisions land — is the only addition; it's load-bearing for the cohort architecture. |
Mark had spent years building those seventy-plus slide decks. They were good decks — and the cut to ten wasn't about quality. It was about what the package was for. Once the participant was producing in the session, the package had to serve that production rather than substitute for it.
DELIVER — Running It as Coaching
DEVELOP produced the tools; DELIVER runs them. The shift from broadcast mode to coach mode shows up in where Mark stands, how he reads the room, how the breakouts actually run, and what governs the session's pace.
|
|
Before |
After |
|---|---|---|
|
Facilitator position |
At the front of the room. Mark walked through the deck, explained the concepts, and managed the session from a single fixed location. |
During each week's 60-min application block, Mark circulates through breakouts, reads the week's specific template as participants fill it in, and catches misapplication at minute ten — not at the share-out. Week 1 he's reading for positioning-statement clarity; Week 4 he's reading for email-sequence specificity; Week 6 he's reading against the audit rubric. His physical location tracks the session's current producing activity, not the front of the slide deck. |
|
Reading the room |
"Any questions?" at the end of each teaching segment. Silence was read as understanding, and the next segment began. If someone did speak up, Mark answered the question and moved on. |
Specific comprehension checks at every transition, tied to the week's artifact. Week 1: "write your positioning statement in the chat before we move to the tier check." Week 2: "poll — which pricing tier does your draft anchor to?" Week 3: "read your conversion-script opener out loud to your pair." Each check produces a specific signal about whether the concept landed for the week's artifact. If the signal is weak, Mark pauses and revisits — often pulling a prior week's artifact back in (a Week 3 conversion-script check failing across the cohort means pulling Week 2's pricing back into active memory, because conversion scripts that don't align with pricing collapse at the live call). The agenda serves the room's readiness, not the other way around. |
|
Breakout design and in-breakout coaching |
"Break into threes and discuss." No specified prompt, role structure, deliverable, or debrief question. Mark set the breakouts up and returned when time was called. Breakouts produced energy but rarely produced outcome-aligned work. |
Every breakout runs against DEVELOP's breakout-prompt cards — specific prompt (tied to the week's artifact), role structure (rotating speaker, fixed scribe), deliverable (the draft or revision of the week's artifact), and debrief question (tied to the participant's own business context). Mark is inside the breakouts during breakout time, listening to conversations and reading deliverables as they form. When he spots misapplication — a Week 1 positioning statement that reads as generic, a Week 3 conversion-script opener that doesn't match Week 2's pricing — he coaches in the moment, before the confusion compounds through the rest of the activity. |
|
Pacing |
The agenda clock governed the session. Mark ran over on multiple weeks — Week 3 especially, the conversion-conversation week — and cut content reactively when the clock caught up with him. The buffer didn't exist because the session was full of slides. |
The room's readiness on the week's artifact governs the session, not the clock. The ten-minute buffer DESIGN built gets spent on the concept the room isn't ready to leave — if Week 2's pricing check fails mid-session, Mark spends the buffer there rather than on unplanned depth. Strategic breaks every sixty minutes. High-focus application followed by synthesis, not stacked high-focus blocks. When sessions ran long in the old cohorts, it meant the deck was too big. When the session now uses the buffer, it means a specific concept earned it. |
That real-time catch — inside the breakout, against the participant's specific week's draft, before the confusion compounds — is where coach mode earns its value. Broadcast delivery can't produce it, because broadcast delivery isn't inside the work.
EVALUATE — Reading Work, Not Reviews
DELIVER produces raw signal; EVALUATE reads it. With actual work samples coming out of the sessions and real follow-up data on what participants did afterward, EVALUATE could close the loop and let each cohort sharpen the next.
|
|
Before |
After |
|---|---|---|
|
Before baselines |
None collected. Mark didn't know what each participant could already do at Week 1 — no baseline of current positioning quality, current pricing clarity, current sales-call close rate. He had self-reported intake forms about "where participants were stuck" but nothing measurable against a common rubric. |
Week 1 pre-work — the rough positioning draft against three prompts — doubles as baseline data, scored against the same rubric that the Week 6 audit uses. This gives Mark each participant's starting quality per dimension before the cohort begins, and lets him see which weeks moved the needle most for which participants. |
|
During signals |
None collected beyond chat activity and the occasional "everyone's nodding" read. No artifact-quality captures, no comprehension-check responses recorded, no work-sample records from the sessions. |
Two signal streams captured every session. Artifact-quality captures at the end of each week's 60-min block — positioning draft quality end of Week 1, pricing draft quality end of Week 2, conversion-script quality end of Week 3, and so on — each scored against the rubric. Comprehension-check responses at each transition (polls, short-answers, live-chat captures) logged as evidence for where the concept landed and where it didn't. Both streams feed the iteration loop. |
|
After outcomes |
A 5-question satisfaction survey at the end of the six-week cohort, asking about experience, facilitator, and likelihood to recommend. Nothing after that — Mark didn't know what happened in participants' businesses. |
Structured check-ins at one week, one month, and one quarter, keyed to specific artifacts. "Have you had a pricing conversation using your Week 2 framework? What happened?" "Did you ship the Week 4 email sequence? What responses came back?" "Did you run the Week 5 launch? Is anyone paying yet?" The questions track behavior, not feelings; the answers tell Mark which artifacts translated into real-world use. |
|
Iteration loop |
Mark iterated on "it felt like the energy dropped there" and on the loudest comments in the satisfaction survey. Same cohort, same result, four times. |
Patterns across the cohort's per-artifact evidence drive the next build — specifically, which weeks had high artifact quality but low real-world application. The first-iteration review surfaced exactly that: Week 2 pricing draft quality was strong, but real-world pricing conversations weren't translating; Week 3 conversion scripts were being written well but falling apart at the live call. Mark added a pricing deep-dive role-play to DESIGN (using each participant's actual recent deal, run in the session with Mark circulating and coaching), and implementation moved 8–12% → 72%. A second iteration review surfaced a second friction point between artifact quality and real-world application; a second targeted DESIGN activity moved implementation 72% → 88%. |
The loop isn't between cohorts as a whole — it's between specific artifacts and their real-world use. What moved implementation from 8–12% to 88% wasn't bigger surveys or deeper reflection. It was honest reading of which week's artifact didn't translate, followed by a targeted DESIGN change aimed at exactly that gap. Same creator, same format, better evidence — better design, better outcomes.
The Compounding Effect
The individual phase changes were each modest. Audience specificity. Session scaffolding. Asset count. Coach mode. Evidence-based evaluation. Any one of them alone would have been a meaningful improvement. Together, they produced a different workshop.
What made the whole larger than the sum of the parts was how each phase's sharpening unlocked what the next phase could actually do. PLAN's narrower audience and project-based method let DESIGN build activities that were both specific and structurally coherent — the old generic audience had forced generic activities, and without a selected method, each session's shape had been improvised around whatever slides Mark had on hand. DESIGN's scaffolded structure let DEVELOP cut seventy-five slides down to ten — the old flat structure had required every slide, because there was nothing else structural holding the session up. DEVELOP's one-page templates let DELIVER coach against actual work in the breakouts — the old thirty-page workbook was too big for Mark to see what anyone was actually producing in real time. DELIVER's coaching let EVALUATE read work samples instead of just satisfaction scores — the old broadcast delivery produced nothing for EVALUATE to read except the rating form.
Each step made the next step possible. Skipping any of them would have collapsed the chain.
What Didn't Have to Change
Mark didn't change his personality. He's still warm, direct, and occasionally too fast in his delivery. None of this required him to become a different kind of facilitator — or to acquire a new credential, a new platform, or a new brand.
He didn't change his content mastery either. The pricing framework he teaches is the same pricing framework he taught before. The positioning work is the same. His expertise on the subject didn't improve; what changed was how his expertise got translated into a session the participant could actually do something with.
He didn't change the price, the cohort length, or the seat count. Launch Lab still runs six weeks, twenty-five seats, $2,500 per seat. The shift was structural — five phases of decisions Mark had been making intuitively and is now making deliberately. Same creator, same subject, same container. Different outcomes.
Where this goes next: The five phases of the Roadmap run the same way on any workshop, not just Mark's. To work them on your own session, start at PLAN — Decide Who You're Building For and What You're Building Toward.
Related
Read this next:
- PLAN — Decide Who You're Building For and What You're Building Toward — the first phase of the Roadmap; where Mark's work actually started, and where the compounding sharpening began
The other four phases:
- DESIGN — Architect the Experience the Participant Will Move Through — where the target PLAN set becomes a session structure that produces it
- DEVELOP — Build Less, Build Right — where the structure DESIGN specified becomes the specific tools the session actually needs
- DELIVER — Facilitate Like a Coach — where PLAN, DESIGN, and DEVELOP's work meets a real room
- EVALUATE — Measure Learning, Not Happiness — where the live room's signal becomes evidence for the next build