Most workshops are broken in ways their creators can't see. The reviews come back strong, the room feels engaged, the creator walks out believing the session worked — and a month later, almost nothing has changed in what the participants actually do. The break isn't in the facilitator. It's in the methodology the workshop was built with.
The Workshop Doctor Roadmap is the replacement. Five phases, made in order: PLAN, DESIGN, DEVELOP, DELIVER, EVALUATE. Each phase is a specific set of decisions. Each phase's decisions sharpen what the next phase can actually do — and skipping or compressing any phase collapses the chain.
This series walks each phase at phase level: what it decides, how to think about it, the questions its work resolves, the signs it got skipped, and the core moves that make up disciplined work in the phase. By the end, you should be able to look at your own workshop, see which phases are sharp and which are leaking, and know exactly where to start sharpening.
Why the Roadmap Exists
The standard way workshops get built is a pattern inherited from how most creators were taught to teach in the first place: start from the content you know, build a deck, run the session, collect a feedback form, iterate on whichever participant spoke the loudest. That approach produces sessions that feel good in the room and score well on the feedback form. It doesn't reliably produce sessions that change what the participant does afterward.
The pattern isn't a character flaw or a motivation problem. It's a structural gap — the traditional model doesn't name the decisions that actually determine whether a workshop changes behavior, so most of those decisions get made implicitly, under time pressure, with the creator's intuition substituting for a methodology. The Roadmap names them explicitly, in the order they need to be made, with the specific work each phase resolves.
The Five Phases
Each phase inherits the decisions of the phase before it. None can be done in isolation, and none can be skipped without collapsing the phases that follow.
- PLAN — Decide Who You're Building For and What You're Building Toward. Who the workshop is for, what problem it solves, what the participant should be able to do at the end, and where the workshop sits in a broader business. Every later phase inherits these decisions.
- DESIGN — Architect the Experience the Participant Will Move Through. Turns the target into a session structure that produces it — session flow, activity architecture, pre-work, how sessions connect across a multi-session cohort.
- DEVELOP — Build Less, Build Right. Builds only the specific tools the design requires — pre-work assets, breakout materials, comprehension checks, debrief structures, participant templates.
- DELIVER — Facilitate Like a Coach. Runs the session in coaching mode — circulating, observing, running the comprehension checks DEVELOP built, adjusting in real time.
- EVALUATE — Measure Learning, Not Happiness. Produces the evidence — whether the transformation happened, where the gaps were, and what to sharpen for the next cohort.
PLAN's sharpening unlocks what DESIGN can specify. DESIGN's sharpening unlocks what DEVELOP can build. DEVELOP's sharpening unlocks what DELIVER can run. DELIVER's sharpening produces what EVALUATE can actually read. And EVALUATE's evidence becomes the input for the next build's PLAN. The methodology is self-correcting — once it runs.
How Each Phase Page Is Structured
Each phase page follows the same shape:
- What the phase is and why it matters — the stakes the phase carries, framed for a cold reader arriving via search.
- The phase's perspective — the mindset the phase operates from and the shift the phase asks the reader to hold.
- The core questions the phase's work resolves — four to six questions that, answered cleanly, mean the phase's work is done.
- How to recognize when the phase got skipped or compressed — observable signs a reader can check their current workshop against.
- How to work the phase — six to eight specific moves that make up disciplined work in the phase.
- Where this goes next — the handoff to the next phase.
Read in sequence, the phase pages walk the full methodology. Read individually, each works standalone for a reader arriving from a search result or a direct link.
The Running Case Study
Theory reads flat until you see it in use. So this series includes one worked case — the rebuild of a fictional cohort program called Launch Lab, run by a fictional workshop creator named Mark.
Before applying the Roadmap, Launch Lab was a textbook example of a broken workshop hiding behind great reviews: 9.1 out of 10 on satisfaction, 94% of participants said they'd recommend it, and 8 to 12% actually implemented what they'd learned in the months after each cohort ended. The case study walks Mark's rebuild across all five phases — and tracks how implementation moved from the 8-to-12% baseline to 72% after the first iteration, then 88% after the second. Launch Lab is fictional, but it's built from patterns typical of cohort programs in the creator economy today.
See Mark's Launch Lab, Before and After after walking the phase pages, for the compounding effect in one continuous narrative.
Related
Start here:
- PLAN — Decide Who You're Building For and What You're Building Toward — the first phase, and where every later phase's work starts.
Foundations of the methodology:
- Foundations — The Learning Science Every Workshop Rests On — the learning-science context the Roadmap assumes. Foundations teaches the terrain; the Roadmap teaches the route.
- How People Actually Learn — the memory pipeline every phase of the Roadmap respects.
- From Learner-Centered to Transformation-Centered — the design paradigm the Roadmap operates in.
The worked case:
- Mark's Launch Lab, Before and After — the full rebuild walked across all five phases as one continuous story. Read after the phase pages.