How to run a workshop that ends in decisions

A workshop ends in decisions when you design it backwards from the decision you need. Write that decision down before you write an agenda, invite the person who can make it, agree how the group will choose before anyone generates ideas, and do not let people leave until each decision has an owner, a first step and a date. Everything else, the energisers, the sticky notes and the canvases, serves those four things or gets cut.

This guide covers the whole job: why workshops drift, how to frame and staff one, how to shape the day so it opens and then closes, how to make the closing stick, and what changes when the room is senior, bilingual or remote.

Why most workshops end without a decision

Most workshops are designed as conversations, not as decisions. The invitation says "let's explore", the agenda lists activities, and the session ends when the time runs out. People enjoyed it. Nothing changed.

Four causes come up again and again:

• Nobody wrote the decision down. "Improve onboarding" is a topic. "Choose the two onboarding changes we will pilot in the first quarter" is a decision.
• The decision-maker isn't in the room, or is in the room but hasn't been told they are expected to decide today.
• The group never agreed how it would choose. So the convergence becomes a debate between the loudest voices, and the facilitator ends it with "let's take this offline".
• The output is captured, not closed. Someone photographs the wall and promises a summary. Two weeks later the summary arrives and no one acts on it. We look at this failure on its own in why your workshop ended in photos of sticky notes.

Each of these is a design problem, which means each can be fixed before the day.

Step 1: Start from the decision, not the agenda

Before you open a slide or book a room, write a one-page workshop brief with five lines:

1. The decision. One sentence, starting with a verb: choose, approve, rank, stop, commit. If you have more than three decisions, you have more than one workshop.
2. The decision owner. The named person who will make or ratify the decision. A committee is not an owner.
3. The decision rule. How the group will decide: the owner decides after hearing everyone; the group votes and the owner can veto; the group must reach consent (no one objects strongly). Pick one and say it out loud at the start.
4. What is already fixed. Budget ceiling, deadlines, regulations, choices already made upstream. Saying these early stops the group reopening them.
5. What "done" looks like at 4pm. For example: "Two pilots chosen, each with an owner, a sponsor and a first test booked."

Then turn the decision into a question the group can work on. A good how might we question sits one level below the decision: narrow enough to act on, open enough to allow more than one answer. If you can't write the question, the problem isn't ready for a workshop, and an hour of stakeholder interviews will do more good than a day in a room.

Step 2: Invite for the decision, not for representation

The guest list is a design choice. Invite three kinds of people:

• The owner, who decides or ratifies.
• People who know things the owner doesn't: front-line staff, customers, the person who runs the system today.
• People who will carry it out, because a decision made without them will be quietly undone.

Leave out people who are there only so their department "has a seat". They dilute the room and slow the closing. For a working session, six to twelve people is the range where everyone can speak and you can still converge in an afternoon. Beyond that, split into tables with a clear way to bring them back together.

Brief the owner separately the week before. Tell them exactly when in the day you will ask them to decide, what they will see first, and that "I need to think about it" is acceptable only if they name the date they will answer. If the owner is very senior, the dynamics change enough to need their own plan; see running a workshop with senior executives.

Step 3: Design the day to open, then close

Sam Kaner and colleagues, in the Facilitator's Guide to Participatory Decision-Making, describe group decisions as a diamond: a divergent zone where options multiply, a messy middle they call the "groan zone" where people struggle to understand each other, and a convergent zone where the group narrows down. The useful lesson is that the messy middle is normal. If you plan for it, it stops feeling like failure.

A practical shape for a one-day workshop:

Two design rules matter more than the choice of methods.

Silent first. Ask people to write ideas alone before anyone speaks. It stops the first or most senior voice from setting the direction, and it doubles the range of ideas you get. The case for it, and how to run it, is in silent first: why the best ideas come before the discussion.

Protect the closing. Over-running exercises steal time from the end, and the end is where the decision happens. Put the close on the agenda as the fixed block and let earlier blocks shrink if they must. Never the other way round.

Step 4: Agree the criteria before you see the ideas

The most common reason convergence collapses is that people judge options against different, unspoken criteria. The finance lead is thinking about cost, the service lead about customer pain, the IT lead about risk. Everyone is right and no one agrees.

Fix this before the diverge block, while no one is attached to an idea yet:

1. Propose three to five criteria tied to the decision (for example: customer impact, effort to pilot, fit with this year's plan, risk).
2. Let the group adjust the wording, not the number.
3. If some criteria matter more, weight them now.
4. Write them where everyone can see them for the rest of the day.

Then choose the convergence method to match the stakes. An impact–effort matrix is fast and good for a first cut. A weighted decision matrix is slower but defensible when the owner must explain the choice upward. Dot voting is useful for showing where energy sits, but treat it as input to the owner, not as the decision; it rewards familiar ideas and is easy to game, as why dot voting lies to you explains. For a side-by-side of the options, see how to prioritise ideas.

Step 5: Close the decision in the room

The close is where workshops are won or lost. Run it in this order:

1. Restate the decision and the rule. "We are choosing two pilots. Amina decides after hearing the group."
2. Show the shortlist with its scores against the agreed criteria.
3. Test agreement honestly. A simple scale helps: ask each person to say whether they fully support, support with reservations, can live with it, or cannot support it. Kaner's "gradients of agreement" scale is a fuller version of this. Reservations spoken now are cheaper than resistance later.
4. The owner decides out loud. If they can't, they name the date and what they still need.
5. Run a ten-minute premortem. "It is a year from now and this pilot failed. Why?" The premortem, developed by psychologist Gary Klein, gives people permission to raise risks without seeming disloyal. Turn the top two risks into tasks.
6. Fill the decision record together, on screen or on the wall, before anyone leaves:

If roles beyond the owner are unclear, a quick RACI on the top decision takes ten minutes and saves weeks.

Step 6: The 48 hours after

A decision made at 4pm is fragile by 9am the next day. Within 24 hours, send the decision record, not the full write-up, to everyone in the room and to the people in the "who needs to know" column. Within 48 hours, check that the first step of each decision has started. The full write-up, with the reasoning and the options you rejected, can follow within a week.

The facilitator's checklist covers this in detail, from the day before the session to the day after.

Illustrative example: a regional library service

Illustrative. A regional library service in the north of England wanted to "rethink opening hours". The head of service first asked for a two-day "visioning" workshop with twenty-five people.

The facilitator rewrote the brief. The decision became: "Choose which two branches trial extended evening hours from April, and how we staff them." The owner was the head of service. The rule: she would decide after hearing the group. Fixed: no extra staffing budget this year.

The guest list shrank to eleven: four branch managers, two front-line librarians, a union representative, the facilities lead, a volunteer coordinator, a data analyst and the head of service. Before the session, the analyst prepared footfall by hour for each branch, and two librarians collected comments from users about evening access.

On the day, criteria were agreed in the first hour: user demand, staffing feasibility, building security and travel access. Options were written silently, grouped, then scored. Two branches came out clearly ahead; a third split the room. The head of service chose the two leaders and asked for the third to be reconsidered in June with three months of data. The premortem raised volunteer burnout as the main risk, so the volunteer coordinator took an action to design a rota cap. The decision record went out the next morning. The workshop finished at 3.30pm, not on day two.

Do's and don'ts

Do

• Write the decision, owner and rule on one page before anything else.
• Brief the decision owner privately before the day.
• Agree criteria before ideas.
• Make the closing block fixed and protect it.
• Send the decision record within 24 hours.

Don't

• Run a workshop to "get buy-in" for a decision already taken. People notice, and you spend trust you will need later.
• Invite people for representation rather than contribution.
• Let a show of hands stand in for the owner's decision when the rule said otherwise.
• End with "we'll take this offline" without a named person and date.
• Wait until the full write-up is ready before telling people what was decided.

The most frequent of these traps, and a few less obvious ones, are in 7 workshop mistakes that kill good ideas.

Special situations

Senior rooms. Executives have less time and more at stake. Shorter sessions, pre-reads that are actually read, and a decision designed around their calendar. See running a workshop with senior executives.

Mixed-language teams. When half the room thinks in Arabic and half in English, decisions can be agreed in one language and understood differently in the other. See facilitating mixed Arabic and English teams.

Remote and hybrid. Online, convergence is harder and silence is easier to misread as agreement. Shorter blocks, explicit check-ins and a shared board matter more. See remote and hybrid workshops people stay awake in.

Questions people ask

How long should a decision workshop be? As short as the decision allows. One focused decision can be closed in two to three hours if the evidence is ready. A day suits two or three related decisions. If you think you need two days, check whether you are really running two workshops, or whether the problem needs research first.

What if the decision-maker can't attend? Move the date. If that is impossible, get their decision rule and limits in writing beforehand, and book thirty minutes with them the next day to ratify. Do not run the workshop and hope.

What do I do when the group can't agree? Go back to the criteria. Most deadlocks are disagreements about what matters, not about the options. If criteria are agreed and the group is still split, that is exactly what the decision rule is for: the owner decides, and records the minority view.

Where to go next

Start with the methods that do the heavy lifting: how might we to frame the question, brainwriting to diverge without the loudest voice taking over, the weighted decision matrix to converge, and the premortem to stress-test the choice. The full set is in the method guides.