Build the workshop output before the agenda

The output is the starting design constraint

Our workshop design begins with a draft of the output the organisation needs to use afterward. It might be a problem definition, an options comparison or a decision placemat. We leave the unresolved fields visible. They tell us what evidence to gather, whose judgement is required and which activities deserve time in the room.

This connects facilitation to the rest of the Studio method. A diagnostic workshop should improve the account of the operating problem. A working session should build or resolve a defined part of the response. A pilot review should compare evidence with the agreed decision rules. A workshop is useful because of the work it enables next.

We distinguish an empty field from a disagreement. A missing fact needs investigation. Different priorities need an accountable choice. A disputed assumption may need a test. Giving each a route forward is more useful than designing every exercise to end in consensus. The sequence below is one adaptable example rather than a standard agenda for every engagement.

Specify the work the session must do

A workshop can investigate a problem, develop options, test assumptions or support a decision. Those purposes require different designs. A broad invitation to align on strategy often conceals disagreement about what the meeting is supposed to achieve.

Write the intended output before the agenda. It might be an agreed problem definition, a shortlist of options or a decision to fund a bounded test. State what is outside the session's authority and what must happen afterward.

Confirm that the people attending can contribute the relevant evidence and that the decision owner is involved at the appropriate point. A productive discussion cannot substitute for authority. If approval must happen elsewhere, design the output for that process.

Prepare evidence rather than a long presentation

Send a concise brief covering the problem, current evidence, constraints, decision and open questions. Separate established facts from reported experiences and assumptions. Give participants a way to flag missing information before the session.

Include the people who experience and operate the process, not only those who sponsor it. A leader may understand the objective while a frontline colleague knows where the work actually stalls. Where stakeholders cannot attend, gather their input in advance and identify its source.

Check access requirements and confidentiality. Decide what can be recorded, where material will be stored and what attribution is appropriate. Do not promise confidentiality arrangements that the organisation cannot honour.

Use a sequence that separates investigation from choice

The sequence below is an illustrative two-hour design for a bounded operating problem. Adjust it for complexity, access needs and the evidence available. A timebox controls the session, not the validity of the decision. If essential evidence is missing, agree how to obtain it rather than forcing a choice.

Give different views a fair hearing

Invite participants to note observations independently before open discussion. This gives people time to formulate a view and creates material beyond the first confident contribution. Then ask for evidence and examples, not just agreement.

Make disagreement visible. Is the group disputing a fact, an assumption, a priority or an acceptable level of exposure? Each needs a different response. More discussion does not resolve a missing fact. A sponsor's preference does not turn an assumption into evidence.

Use voting as an input when appropriate, not as a substitute for accountable judgement. A popular option may be infeasible or outside authority. Explain how the final decision will be made and how dissent or unresolved conditions will be recorded.

Compare options without false precision

Agree criteria before selecting a preferred option. Consider usefulness, feasibility, cost, implementation effort, exposure and reversibility. Define what each criterion means in this context.

A weighted score can structure discussion, but its result depends on chosen weights and ratings. It is not objective proof that one option is best. Examine whether a plausible change in the assumptions would change the recommendation.

Where the evidence is weak, the right output may be a test plan. Record which uncertainty the test will resolve and what result would change the decision. That is more useful than a confident roadmap built on unexamined assumptions.

Close with an operating record

Before people leave, read back the decision, rationale, conditions, owners and dates. Confirm what remains unresolved. Assign one person to maintain the record and circulate it promptly through the agreed channel.

At the review point, check whether the agreed actions happened and whether the decision is still supported by the evidence. Attendance and participant satisfaction are useful feedback, but they do not establish that the workshop improved the operation.

The quality of facilitation is visible in what the organisation can do afterward. A clear decision, a responsible next test or an explicit unresolved issue is a worthwhile output. A wall of ideas without ownership is incomplete work.