Workshop brief: a one-page template your sponsor will sign
The sponsor says "just get the team together and see what comes out". Three weeks later the same sponsor asks why nothing came out. Between those two sentences sits a missing brief: one page, eight fields, agreed before the invitation goes out, so the workshop has a decision to serve.
Why the brief comes before the invitation
A workshop without a decision behind it produces ideas, and ideas without a decision end up in a slide deck. The brief forces the sponsor to say what they will decide, by when, and what they already know. Once that is on paper, the agenda almost designs itself. It also protects you: when the sponsor changes the question in the room (it happens), you point at the signed page.
The template
Each field is one to three lines. If a field needs more, the question is not clear enough yet.
1. The question. One sentence in the How might we form, narrow enough to answer in one session. How might we halve the time from order to first invoice for new business customers?
2. The decision this workshop serves. What the sponsor will decide after the workshop, and by when. This field is what makes it a workshop rather than a meeting. Which two process changes we pilot in Q1. Decided by the sponsor on 29 January.
3. What is out of scope. Fixed constraints and topics not up for debate, so nobody spends forty minutes on them. The ERP system stays. Headcount stays. Pricing is not on the table.
4. Who is in the room and why. Roles, not names: the people who do the work, one outsider who does not, and the person who can say yes. Two from the order desk, one from finance, a service lead from another unit as the outsider, the head of operations as the person who decides.
5. What we already know. Three bullets with links to context, so the workshop does not start from zero. Last year's process audit (link). Complaint log, top five causes (link). The automation attempt that was stopped, and why (link).
6. The output. What exists at the end of the day, described as something you can hold: a scored shortlist of five, three concepts with owners, a go or no-go. Not "ideas". A scored shortlist of five changes, each with an owner and a one-line reason for its rank.
7. What happens in the week after. Who reads the record, and the follow-up meeting with a date in the calendar before the workshop starts. The sponsor and the owners read the record by Friday. Follow-up meeting on Tuesday 19 January, 10:00. Once the sponsor has decided, the outcome goes into the team's decision log.
8. Capture and consent. How results are recorded (photos of the wall, a scribe, a transcription, a tool like IdeaHone) and what participants are told in the invitation. A scribe captures ideas and decisions in a shared document. No audio recording. Participants are told this in the invitation.
How to use it
The brief is a conversation with the sponsor, compressed to one page.
- Write it in 20 minutes. Fill the eight fields on your own, best guess where you are unsure. Gaps are fine. They are what the sponsor is for.
- Send it with one question. "Is this the decision you need?" Nothing else. The sponsor corrects field 2 or confirms it, and that is the whole approval.
- Wait for the reply. Do not send the invitation until the sponsor has answered. Otherwise the question gets set by whoever accepts first.
- Paste fields 1, 2 and 6 into the invitation. Participants see the question, the decision and the output before they walk in.
If the sponsor cannot fill field 2, the workshop is premature. Run a 30-minute conversation with the sponsor instead about what they are actually trying to decide.
A brief that lists five questions is five workshops in one afternoon, and none of them gets answered. One workshop, one question. If the sponsor insists, rank them and run the first.
When the brief becomes a formality
- Writing the brief after the invitation. The date is set, people have accepted, and now you work out what it is for. The brief becomes a justification.
- The sponsor who delegates the brief. "You know the topic, write something." You can draft it, but the sponsor has to read field 2 and say yes. Someone who will not give the brief ten minutes will not give the decision an hour.
- Output described as "ideas". Ideas are the raw material, not the output. Write down the thing that will exist at 17:00.
- No date in field 7. "We will follow up" is where workshops go to die. A follow-up meeting without a date in the calendar is a wish.
If customers or suppliers join, read how to run workshops with external guests before you send the invitation.
Run the workshop. IdeaHone keeps the record.
While you facilitate, IdeaHone turns what is said into ideas, questions and decisions on a shared board, with who said it. Nobody writes the minutes afterwards.
What should a workshop brief contain?
Eight fields: the question, the decision it serves, what is out of scope, who is in the room, what you already know, the output, the week after, and how results are captured. One page is enough.
Who writes the workshop brief?
The facilitator drafts it, the sponsor signs it. The sponsor must personally confirm the decision the workshop serves (field 2). That part cannot be delegated.
How long should a workshop brief be?
One page. Each field is one to three lines. If a field needs more, the question is not sharp enough yet, and that is worth knowing before the invitation goes out.
What is a workshop brief?
A one-page agreement between facilitator and sponsor, written before the agenda. It states why the workshop happens, which decision it must produce, who attends and what a successful outcome looks like.
