Workshop Designer Skill
Workshops fail pleasantly: good discussion, full whiteboards, warm feelings — and nothing anyone can use on Monday. The fix is designing backwards from the artifact: name the thing the room must produce (a prioritized list, a draft charter, three concept sketches, an agreed map), then choose activities that manufacture it — and open discussion is almost never that activity, because it's dominated by the confident and produces talk, not output. Silent writing, structured rounds, and forced ranking exist precisely because they extract from everyone and converge on paper.
What This Skill Produces
- The artifact spec — what the workshop produces, concretely, and who uses it afterward
- The activity sequence — timeboxed blocks, each transforming the previous block's output toward the artifact
- The facilitation notes — per block: instructions verbatim, the timekeeping, the dominance-management moves
- The capture plan — how outputs leave the room usable (photographed, transcribed, owned) — the step every fun workshop skips
Required Inputs
Ask for these if not provided:
- The artifact — pushed to concrete: "alignment on strategy" becomes "a one-page strategy statement the leads will sign" (outline-before-prose claim-discipline applies to workshop goals too)
- The cast — headcount, seniority mix, the known dominators and the known silents (the design manages both), remote/hybrid reality
- The time box and the room — 90 minutes designs differently than a day; hybrid needs its own mechanics (boards everyone can touch)
- The pre-work tolerance — what the group will actually do beforehand (honest answer: little — design for it)
Framework: The Design Rules
- Backwards from the artifact: write the artifact spec first, then ask "what's the last activity that produces it?" and chain backwards — every block's output is the next block's input, and any block whose output feeds nothing gets cut. Agendas built forward accumulate activities; backwards they earn them.
- Silent writing beats brainstorming: individual writing first (everyone produces, nobody anchors), then share-and-cluster — this one substitution fixes the dominance problem, the anchoring problem, and the quiet-expert problem simultaneously. Structured rounds (each person, 60 seconds, no responses) do the same for discussion.
- Converge with mechanisms, not debate: dot votes, forced ranking, 2×2 placement — convergence tools that produce a visible ordered result in minutes. Debate converges at the speed of stamina; mechanisms converge at the speed of the timebox — debate then happens richly on the top-3, where it's worth its cost.
- Design the energy arc: hard divergence early (fresh minds), mechanical convergence mid, decisions before the last block (never in it — tired rooms decide badly), and breaks before the room needs them. After-lunch blocks are active or they're naps with agendas.
- Capture is a role, not an afterthought: one named person photographs boards, transcribes clusters, and records decisions as they happen — and the workshop's last ten minutes assign every output an owner and a date in front of the room. The artifact spec is met when the usable version exists outside the room, same day.
Output Format
Workshop: [artifact] — [duration], [N] people
The Artifact Spec
[What exists at the end · who uses it Monday · the sign-of-success]
The Sequence
| Time |
Block |
Format |
Output → feeds |
| [Diverge (silent-first) → cluster → converge (mechanism) → decide (pre-fatigue) → assign] |
|
|
|
Facilitation Notes
[Per block: verbatim instructions · the dominance moves (rounds, parking lot) · hybrid mechanics if needed]
Capture Plan
[The capture role (named) · boards → digital same-day · the last-10-minutes owner-and-date assignment]
Quality Checks
Anti-Patterns
1---2name: workshop-designer3description: Design working sessions that produce artifacts, not vibes — the outcome-backwards agenda, the activity formats that beat open discussion (silent writing, dot voting, structured rounds), the energy arc, and the output-capture that survives the room. Use when asked design a workshop for X, plan our planning session, facilitate a half-day working session, or our workshops are fun but nothing comes out. Produces the workshop design: the artifact goal, the activity sequence with timings, the facilitation notes, and the capture plan.4---5
6# Workshop Designer Skill
7
8Workshops fail pleasantly: good discussion, full whiteboards, warm feelings — and nothing anyone can use on Monday. The fix is designing *backwards from the artifact*: name the thing the room must produce (a prioritized list, a draft charter, three concept sketches, an agreed map), then choose activities that manufacture it — and open discussion is almost never that activity, because it's dominated by the confident and produces talk, not output. Silent writing, structured rounds, and forced ranking exist precisely because they extract from everyone and converge on paper.
9
10## What This Skill Produces
11
12- **The artifact spec** — what the workshop produces, concretely, and who uses it afterward
13- **The activity sequence** — timeboxed blocks, each transforming the previous block's output toward the artifact
14- **The facilitation notes** — per block: instructions verbatim, the timekeeping, the dominance-management moves
15- **The capture plan** — how outputs leave the room usable (photographed, transcribed, owned) — the step every fun workshop skips
16
17## Required Inputs
18
19Ask for these if not provided:
20- **The artifact** — pushed to concrete: "alignment on strategy" becomes "a one-page strategy statement the leads will sign" ([outline-before-prose](../outline-before-prose/SKILL.md) claim-discipline applies to workshop goals too)
21- **The cast** — headcount, seniority mix, the known dominators and the known silents (the design manages both), remote/hybrid reality
22- **The time box and the room** — 90 minutes designs differently than a day; hybrid needs its own mechanics (boards everyone can touch)
23- **The pre-work tolerance** — what the group will actually do beforehand (honest answer: little — design for it)
24
25## Framework: The Design Rules
26
271. **Backwards from the artifact:** write the artifact spec first, then ask "what's the last activity that produces it?" and chain backwards — every block's output is the next block's input, and any block whose output feeds nothing gets cut. Agendas built forward accumulate activities; backwards they earn them.
282. **Silent writing beats brainstorming:** individual writing first (everyone produces, nobody anchors), then share-and-cluster — this one substitution fixes the dominance problem, the anchoring problem, and the quiet-expert problem simultaneously. Structured rounds (each person, 60 seconds, no responses) do the same for discussion.
293. **Converge with mechanisms, not debate:** dot votes, forced ranking, 2×2 placement — convergence tools that produce a *visible ordered result* in minutes. Debate converges at the speed of stamina; mechanisms converge at the speed of the timebox — debate then happens richly on the top-3, where it's worth its cost.
304. **Design the energy arc:** hard divergence early (fresh minds), mechanical convergence mid, decisions before the last block (never in it — tired rooms decide badly), and breaks *before* the room needs them. After-lunch blocks are active or they're naps with agendas.
315. **Capture is a role, not an afterthought:** one named person photographs boards, transcribes clusters, and records decisions *as they happen* — and the workshop's last ten minutes assign every output an owner and a date in front of the room. The artifact spec is met when the usable version exists *outside* the room, same day.
32
33## Output Format
34
35# Workshop: [artifact] — [duration], [N] people
36
37## The Artifact Spec
38[What exists at the end · who uses it Monday · the sign-of-success]
39
40## The Sequence
41| Time | Block | Format | Output → feeds |
42|---|---|---|---|
43[Diverge (silent-first) → cluster → converge (mechanism) → decide (pre-fatigue) → assign]
44
45## Facilitation Notes
46[Per block: verbatim instructions · the dominance moves (rounds, parking lot) · hybrid mechanics if needed]
47
48## Capture Plan
49[The capture role (named) · boards → digital same-day · the last-10-minutes owner-and-date assignment]
50
51## Quality Checks
52
53- [ ] The artifact is concrete and its Monday user is named
54- [ ] Every block's output feeds the next; orphan activities were cut
55- [ ] Divergence starts silent; convergence uses mechanisms
56- [ ] Decisions land before the final-hour fatigue
57- [ ] Capture has a named owner and outputs leave the room same-day
58
59## Anti-Patterns
60
61- [ ] Do not design forward from fun activities — backwards from the artifact or it's team-building in disguise (which is fine, but name it)
62- [ ] Do not open with group brainstorming — silent writing first, always
63- [ ] Do not converge by discussion — mechanisms converge; discussion enriches the converged
64- [ ] Do not schedule deciding last — tired rooms defer or decide badly
65- [ ] Do not let the boards die in the room — un-captured workshops happened only emotionally
Mohit Aggarwal