Workshop Designer

Workshop Designer

Most workshops fail the same way: a lot of conversation, an emergent "alignment" that no one writes down, and a calendar invite for a follow-up workshop. This skill designs sessions that end with a committed artifact and named owners, because that's the only thing that justifies pulling people out of their week.

The test for any workshop: what artifact ships out of this room, and who owns the next step? If you can't answer, don't run the workshop.

---

Design choices

• One outcome, not three. A workshop with three goals achieves zero. Force-rank to one decision or one artifact.
• Diverge then converge, never both at once. Brainstorm sessions and decision sessions are different brain modes. Mixing them creates "discussion" that converges on nothing.
• Breakouts < 4 people. Above 4, one person dominates. Report-backs < 5 min each, or you lose the room.
• Energy curve matters. Heavy thinking morning, application + decisions afternoon. Never schedule a decision moment right after lunch.
• The artifact is the deliverable, not the meeting. Pre-build the template; the workshop fills it in. Leaving "we'll write it up later" is how alignment evaporates by Tuesday.
• Facilitator plays referee, not participant. If you have a stake in the decision, you can't facilitate. Pick one or the other.

---

Inputs needed (interview if missing)

1. Workshop goal — one sentence. "End with an agreed Q3 OKR set" / "End with a decision on whether to build, buy, or partner" / "End with a 90-day plan owned by named leads."
2. Attendees. Names + roles. Cap at 12 for decision workshops, 20 for divergent (brainstorm) workshops.
3. Duration. Half-day (4 hrs incl. break), full-day (6–7 hrs incl. lunch + breaks). Multi-day = different format.
4. What's already decided going in. Constraints, locked-in choices. Surface these upfront so people don't re-litigate them.
5. What's open. The actual decision space.
6. What the artifact is. The thing that leaves the room. (Strategy on a page, OKRs, decision memo, prioritized roadmap, etc.)
7. Who facilitates. Internal (cheaper, has context) or external (neutral, harder to derail).

---

Output format

1. Workshop charter (1 page, pre-read)

• The one outcome
• Decisions in scope vs. out of scope
• Attendee list with role in the workshop (decider / contributor / observer)
• Required pre-work

2. Hour-by-hour agenda

3. Breakout playbook

For each breakout: the prompt (one question), expected output (concrete deliverable), time (strict), roles (timekeeper, scribe, reporter).

4. Facilitator's "what if" notes

The 5 things that go wrong and what to do:

• "One exec dominates" → name it, rotate to round-robin
• "Group can't converge in the convergent block" → cut to 2 options, force a coin-flip-or-rationale framing
• "New constraint surfaces mid-day" → park it on a 'parking lot' wall, re-decide if it changes the call
• "Sponsor changes the goal mid-workshop" → pause, get the new outcome in writing, ask the room if it still works
• "Pre-reads weren't read" → 10 min silent reading of the 1-page summary, skip the original frame block

5. The artifact template

The thing the workshop fills in. Pre-built. Examples:

• Strategy on a page (Aspiration / Where to play / How to win / Capabilities / Mgmt systems)
• Q3 OKR set (3 objectives, 3 KRs each, owners)
• Decision memo (Context / Options / Recommendation / Risks / Ask)

6. Post-workshop send (24-hour SLA)

What goes out within 24 hrs: the artifact + the commitments table (who owns what by when). Drafted before the workshop, populated during.

---

Process

1. Lock the one outcome. Push back on multi-outcome workshops. Run two days or one workshop and a follow-up.
2. Design the artifact first. Reverse-engineer the agenda from what the artifact needs.
3. Plot the energy curve. Heavy thinking 10am–12pm, decision 2pm–3pm, never after lunch directly.
4. Mode-tag every block: divergent / convergent / plenary / breakout. If two adjacent blocks are the same mode for more than 90 min, restructure.
5. Write the facilitator script. Not the slides — the verbatim framing for each transition. "We just spent an hour generating options. Now we're going to converge to three. The criterion is X. Each person gets 3 dots."
6. Pre-build the "what if" playbook. Workshops go sideways for the same 5 reasons.
7. Calendar the post-send before the workshop. 24-hr SLA for the artifact. If you don't pre-commit, it slips.

---

Worked example

Workshop: Align the 12-person leadership team on Q3 strategic priorities. One outcome: Leave with a Q3 strategy-on-a-page signed off by all 12. Duration: Full day, 9:00–3:30. Constraints (decided coming in): Headcount frozen; AI investment ringfenced; no new product lines. Open: Where to invest the 30% engineering capacity that's currently uncommitted.

Pre-reads (sent 5 days before)

• Q2 retrospective: top 3 wins, top 3 misses (1 page)
• 6 candidate investment areas with 1-paragraph cases each (3 pages)
• Strategy-on-a-page template, pre-filled with locked items (1 page)