Running workshops that end in decisions

Plenty of workshops end with a wall of sticky notes, a good mood and no decision. A week later, people remember the session differently, and the same discussion starts again. The usual cause is the design: no clear decision to make, no agreed way of making it, and no follow-up.

This guide covers how to plan and run a workshop that ends with a decision people will act on. It walks through purpose, pre-work, agenda design, facilitation techniques such as 1-2-4-All and dot voting, decision rules, and follow-up.

Start with the decision, not the agenda

Before booking a room, write down the decision the workshop must produce, framed as a question. “Which two of our five product ideas do we fund next quarter?” is a decision. “Discuss product strategy” is not.

Then answer three questions:

• Who owns the decision? Bain’s RAPID decision-making guidance says each decision should ideally have one person with the “D”, who makes the final call and is accountable for the outcome.
• Who needs to give input, and who will carry out the result? Invite those people. Leave out people who only need to be told afterwards.
• What happens if the room cannot agree? Decide this now, not at four o’clock on the day.

If the honest answer is that no decision is needed, you may need a briefing or a document rather than a workshop.

Pre-work that saves the room’s time

A workshop is the most expensive way to share information, because everyone’s time runs at once. Send facts out beforehand so the session can focus on judgement.

• A short brief of one or two pages: the decision, the background, the options so far and the criteria you will use to judge them.
• Data or analysis people need to read, sent early enough to read.
• One or two questions for participants to think about, so they arrive with views.

Atlassian’s DACI play follows the same pattern. It recommends a shared document titled as the question the team is trying to answer, with background, data, decision factors and options with pros, cons and costs.

Designing the agenda

Roger Schwarz’s Harvard Business Review article on meeting agendas gives several tips that suit decision workshops:

• Phrase each topic as a question. “Under what conditions should we reallocate office space?” gives the group a clear task; “office space” does not.
• State the purpose of each item: to share information, to seek input, or to make a decision.
• Include only topics that need this group.
• Name a lead for each item so they can prepare.

A useful shape for a decision workshop moves from wide to narrow: confirm the question and criteria, generate or review options, discuss and test them, decide, then plan actions. Put the decision before the last half hour so it does not get squeezed out.

Facilitation techniques that help groups converge

1-2-4-All

1-2-4-All is one of the Liberating Structures created by Henri Lipmanowicz and Keith McCandless. It gets every person’s thinking into the room, whatever the group size, and reduces the effect of rank. The published timings run to about 16 minutes:

1. Introduce the question (1 minute).
2. Everyone reflects silently and writes ideas (1 minute).
3. Pairs share and build on ideas (2 minutes).
4. Pairs join into fours and refine ideas, noting where they differ (5 minutes).
5. The whole group hears the ideas that stood out (7 minutes).

Liberating Structures advises keeping to precise timings and not over-controlling the conversation.

Dot voting

Dot voting gives each person a fixed number of dots to place on the options they prefer. It shows quickly where the group leans. Treat the result as a signal to guide discussion, not as the decision itself. Ask people to choose privately before placing dots, so early votes do not sway later ones, and talk about options that drew strong but split support.

Parking lot

A parking lot is a visible list for important points that are off the current question. It lets you move on without dismissing someone. Review it at the end and give each item an owner or close it.

Agree the decision rule before you need it

Most workshop arguments about “what we agreed” are really arguments about how the group was meant to decide. Pick a rule in advance and say it at the start.

Bain’s guidance is that if a group must share the decide role, it should agree up front how it will reach a final decision without consensus, for example by majority vote or giving the chair the final say. Atlassian’s DACI uses a single Approver for the same reason.

Close and follow up

Spend the last 20 minutes making the decision stick.

1. Read the decision back in one or two sentences and check the room agrees that is what was decided.
2. List actions with an owner and a date for each.
3. Clear the parking lot.
4. Agree who will tell people who were not there.

Send a short written record within a day: the decision, the reasons, the actions and any open questions. Bain also recommends that the decider share both the decision and the reasoning behind it.

An example (illustration only)

An eight-person leadership team at a software reseller must choose which two of five growth ideas to fund. The managing director holds the decision, and the rule is decider after input.

The dots favour two ideas, but the finance lead raises a cash-flow risk on one. The managing director funds the uncontested idea and a smaller pilot of the second, explains why, and the notes go out that afternoon.

Common mistakes

• Running a workshop with no decision to make.
• Presenting information in the room that people could have read beforehand.
• Leaving the decision rule unstated, so a vote later feels like a betrayal.
• Treating dot voting as final when the group has not discussed trade-offs.
• Letting the decision slip to the last five minutes.
• Ending without owners and dates, then not sending notes.