Most workshops get the planning right and the session wrong. The creator names the specific participant, the specific problem, and what the participant should be able to do at the end — and then builds the session itself as a list of topics to cover. The transformation the planning named doesn't happen in the room.
Turning the planning into a session that actually produces the transformation is the work of the DESIGN phase — the second of five phases in the Workshop Doctor Roadmap. Its job is to lay out what the participant moves through: what they arrive knowing, what they do in the first ten minutes, how each segment builds on the last, what they produce by the end, and what they carry out of the room.
Most workshops break at DESIGN, because most workshops are designed as content to cover instead of an experience to move through. When DESIGN is right, the later phases — DEVELOP, DELIVER, EVALUATE — fall into place. When it isn't, nothing downstream can rescue it.
Why DESIGN Matters
PLAN names the transformation the workshop exists to produce. DESIGN decides the architecture that will produce it. These are different jobs. A workshop with a clean PLAN and a weak DESIGN is a session with a sharp target and no path to it — the participant arrives clear on what "success" means and then spends ninety minutes listening to someone explain the topic. A workshop with a clean DESIGN and a weak PLAN is a session with a beautiful flow aimed at no one in particular — polished, engaging, and still generic.
DESIGN is where the Foundations series principles become structural decisions. Cognitive load becomes "how much can I ask working memory to hold in one segment?" The 80/20 engagement ratio becomes "what is the participant actually doing for the eighty percent?" The forgetting curve becomes "what retrieval practice have I built into the sequence?" Pre-work becomes "what do they need warm before they arrive so the live session can do higher-order work?" These aren't decorative concepts the creator reads and agrees with. They are load-bearing design inputs that determine whether the session actually works.
The reason DESIGN is where most workshops break is that DESIGN is where most creators default back to the model they inherited. PLAN and EVALUATE are newer disciplines for most workshop creators — uncomfortable and deliberate. DESIGN feels familiar, because everyone has built an agenda before. That familiarity is the trap. An agenda is a list of topics in a sequence. A design is an architecture that produces a specific transformation. The two look similar on a page and behave completely differently in the room.
Recognizing DESIGN as architecture rather than agenda is the shift that lets the rest of the build start producing what PLAN committed to.
Experience Architecture, Not Content Delivery
DESIGN-phase work starts with a frame change. You are not deciding what to teach. You are deciding what the participant will do, in what order, with what support, toward what producible result. Content is a byproduct — it's whatever the participant needs in their hands in order to produce the thing the session exists to produce. Pick the content first and the session becomes a container for the content. Pick the experience first and the content becomes whatever the experience requires.
The frame change has a concrete test. Describe your session to someone outside the room. If the description is a list of topics — "we'll cover positioning, then we'll cover pricing, then we'll cover the conversion conversation" — you are still in agenda thinking. If the description is a sequence of what the participant is doing — "they arrive with a draft positioning statement built from pre-work, they pressure-test it in a three-person round in the first twenty minutes, they rewrite against the pillar checks in the next forty, they present the rewrite back to a different trio in the last thirty, and they leave with a statement they've defended twice" — you are in experience-architecture thinking. The first description names topics. The second names behavior.
The work of this phase is not content selection. It is architecture. Every segment has to do a specific job for a specific reason. Every transition has to move the participant a specific step closer to what they will be able to do at the end. The sharper the design, the less the delivery has to carry. The vaguer the design, the more the creator has to improvise, and improvisation on top of a weak design produces sessions that feel high-energy in the room and change nothing after it.
You are a master of your content. The DESIGN-phase work is a different craft. It asks you to set your expertise aside long enough to lay out the participant's route through the session, before deciding what parts of your expertise are going to do which job along that route.
The Core Questions DESIGN Answers
What is the container — one session, or many? Match the container to the transformation. A single-skill shift might fit in one session. A behavior change usually needs several. Forcing a six-session transformation into a ninety-minute workshop is the most common scoping mistake, and it produces the room that nods along and leaves unchanged. Decide the container before deciding the activities, because the container determines what activities are even possible.
What is the flow within each session? A well-designed session flows from simple to complex to mastery. The opening segment activates prior knowledge and sets the participant up to engage with new material; the middle segments stack skills on top of that foundation; the closing segment synthesizes what was built. Flat "lecture → discussion → Q&A" structures aren't flows. They're a sequence of content the creator planned, not an experience the participant is being moved through.
What is the participant actually doing for eighty percent of the time? The 80/20 engagement ratio is the structural decision that separates workshops that transform from workshops that inform. Naming it isn't enough. The design has to answer what specific activities fill the eighty percent — collaborative breakouts, individual application, whole-group synthesis, paired work — and which cognitive function each one serves. If the activities are unnamed at DESIGN time, the delivery will default to the creator talking.
How does each session build on the last? If the workshop is multi-session, the inter-session architecture matters more than any single session's structure. Purposeful retrieval of prior learning at the start of every session. New skills stacked on previously developed ones. Between-session application that becomes the input for the next session's opening activity. Treating each session as standalone is the multi-session failure mode that makes six-week cohorts feel like six disconnected workshops.
What do participants need before the session begins? Pre-work converts cold information to warm information. See Warm vs. Cold Information. The live session is where higher-order work happens — applying, analyzing, evaluating, creating — and that only works if the foundational concepts are already in the participant's head when they arrive. Pre-work is not supplementary material; it is a structural piece of the design. If the live session has to spend its first thirty minutes lecturing the foundational concepts into the room, the pre-work failed or was never designed.
How will readiness and comprehension be assessed in the flow? Assessment is a design input, not a delivery reflex. Where does the first comprehension check sit? What activity produces the signal? What is the plan if the signal says they aren't ready? Designing these in advance is what turns real-time coaching from improvisation into a pre-planned capability.
How to Recognize When DESIGN Was Compressed
Observable signs that the DESIGN phase didn't get the attention it needed:
- The session agenda is a list of topics, not a sequence of participant actions — "intro, positioning, pricing, Q&A" rather than "they arrive with X, they produce Y in the first segment, they revise Y in the second"
- The creator can describe what they plan to cover but cannot describe what the participant will be doing at each specific point in the session
- Engagement is loaded into Q&A segments at the end rather than distributed across the whole session, so the eighty percent of the time is mostly the creator talking and the twenty percent is compressed into whatever survived
- Multi-session workshops treat each session as standalone — no retrieval of prior learning at the start, no scaffolding of new skills on previously developed ones, no between-session work feeding the next session's opening activity
- Pre-work is either missing, or it exists as "read this article" with no connection to the opening activity, so nobody does it and nothing downstream assumes it
- Activities are chosen for variety or energy rather than for a specific cognitive function tied to a specific outcome — "let's do a breakout here to wake them up"
- Transitions between segments are flat, so the session feels like separate lectures rather than a single build, and the participant loses the sense of progression from one segment to the next
- There is no planned readiness or comprehension check — the delivery plans to rely on reading the room, which is a delivery reflex substituting for a design decision
- Time has been allocated to topics but not to the activities that are supposed to produce behavior change, so the session runs out of time for the application work every time
- The session length was set before the scope of the transformation was scoped, so either the content is crammed or the transformation was silently shrunk to fit the time
These aren't style problems. They are architectural problems. A session that leaks at any of these is a session where the design isn't doing enough work, and the delivery has to compensate by improvising in the room.
How to Work the DESIGN Phase
DESIGN-phase work doesn't require a template. It requires the discipline to make the architectural decisions before building anything against them.
Scope the container before the activities. Name the transformation PLAN committed to, and decide honestly how many sessions it takes to produce it. Some transformations are one-session transformations and everything after is practice. Some are six-session transformations that cannot be compressed. Forcing the container to fit calendar convenience rather than the transformation's actual scope is what makes most multi-session workshops feel thin.
Design the session flow as a sequence of participant actions, not a sequence of topics. Write out what the participant is doing in each segment. Opening activity, middle segments, closing synthesis. Name the behavior in each segment — producing, revising, presenting, comparing, deciding. If the sentence describing a segment starts with "the facilitator explains," rewrite it until the sentence starts with "the participant does."
Pick activities because they do specific cognitive work. Collaborative breakouts serve different functions than individual application. Whole-group synthesis serves different functions than paired rehearsal. Each activity slot in the flow should have a reason tied to a specific outcome and a specific cognitive function — not variety, not pacing, not energy. If you can't name why this activity goes in this slot, the slot is still unresolved.
Design pre-work as a structural piece of the session, not a supplement. The pre-work produces the warm information the live session's opening activity depends on. If the live session can run fine without the pre-work, the pre-work wasn't structurally designed. If the live session can only run because the pre-work lands, the pre-work is doing its job. Aim for the second.
Build retrieval into multi-session designs. Every session after the first should open with an activity that requires the participant to pull prior learning out of memory and use it. The spacing effect is the mechanism behind this; spaced repetition and retrieval practice covers it in depth. A multi-session workshop without built-in retrieval is a multi-session workshop whose first-session material is mostly gone by session three.
Plan transitions as intentional moves, not connective tissue. Every transition is an opportunity to either reinforce the architecture or flatten it. Name what the opening hook of each segment does, how the bridge from one segment to the next sets up what follows, and how the closing reflection consolidates the segment's work into something portable into the next one. Flat transitions are the reason sessions feel like disconnected lectures.
Design the comprehension signals into the flow. Decide where the first readiness check lands, what activity produces the signal, and what the plan is when the signal says the room isn't ready. Plan the middle-session checks the same way. Planning these during DESIGN turns real-time adjustment from improvisation into a rehearsed capability.
None of this requires more tools, better slides, or a trendier activity bank. It requires the discipline to make the architectural decisions during DESIGN, so that DEVELOP can build against a stable plan and DELIVER can run a session with a skeleton capable of carrying it.
Where this goes next: DESIGN specifies the experience. DEVELOP builds the specific assets that experience requires — and no more. See DEVELOP — Build Less, Build Right.
Related
Read this next:
- DEVELOP — Build Less, Build Right — the next phase; where the architecture designed here turns into the specific assets the session requires
Foundations of this concept:
- How People Actually Learn — the memory pipeline the DESIGN phase is building against
- The 80/20 Workshop Engagement Ratio — the structural ratio the activity selection in DESIGN has to honor
- Warm vs. Cold Information — the principle Pre-work is built around
- Cognitive Load — the ceiling session pacing has to respect
- Scaffolding and the Zone of Proximal Development — the principle behind scaffolded flow and inter-session progression
- Spaced Repetition & Retrieval Practice — the mechanism behind built-in retrieval across multi-session designs
Where this leads:
- DEVELOP, DELIVER, and EVALUATE all inherit DESIGN's decisions. A weak DESIGN makes every later phase more expensive.
References
Wiggins, G., & McTighe, J. (1998). Understanding by design. Association for Supervision and Curriculum Development.