Designing a Workshop Backwards From the Decision

Most workshop agendas get built the same way, more or less by habit. Open with introductions, review the context, discuss the topic, wrap up with next steps. It reads perfectly reasonably on the invite. It very rarely produces an actual decision, and the reason is visible right there in the wording: it is built around a topic, not a verdict.

The one-sentence test

The single most useful habit in workshop design is writing the decision as a sentence before the invite goes out, and treating anything that cannot survive that test as not yet ready to be a workshop. "Discuss the loyalty program" is a topic. It can absorb an entire afternoon and still not be closed, because nothing about it defines what closing it would even look like. "Decide whether point-transfer ships in this release or the next one" is a decision. It has exactly two acceptable outcomes, and a room either reaches one of them or it does not.

This sounds like a small wording difference. It changes almost everything downstream. A topic invites exploration, which is genuinely valuable at the right stage, but exploration has no natural stopping point, so a workshop built around one can run past its scheduled end with the room still, quite legitimately, discussing. A decision has a stopping point built into its own definition, which is the entire reason it belongs in a room with the right people rather than an open-ended document.

Working backwards from the sentence

Once the decision sentence exists, the rest of the agenda gets built by asking a single repeated question: what has to be true, known, or agreed before this room can honestly answer that sentence? For the point-transfer decision, that might mean the room needs to know the rough engineering cost of each option, needs to know whether marketing has a launch date it is already committed to publicly, and needs at least one person with actual authority to accept a delay if the more thorough option is chosen. Each of those becomes a short block on the agenda, not because it fills time well, but because the decision cannot be honestly reached without it.

Everything that does not serve answering the sentence gets cut, even if it is interesting, even if someone will ask about it, and even if it feels a little impolite to leave off. A status update on an unrelated workstream, a general discussion of the loyalty program's long-term vision, a round of open questions with no bearing on this specific decision: all of it belongs somewhere else, on a document, in a different meeting, in a Slack thread, anywhere but inside the narrow window where the room's full attention is the scarce resource actually being spent.

What this looks like next to the old version

• Old agenda: Introductions (5 min), context review (15 min), discuss loyalty program options (40 min), open questions (15 min), next steps (5 min).
• Backwards-built agenda: State the decision sentence and the two acceptable outcomes (5 min), engineering cost of each option presented in two minutes flat, no discussion yet (10 min), the marketing launch-date constraint stated plainly by the one person who owns it (5 min), open discussion bounded to exactly the tradeoff between cost and date (20 min), explicit decision made and read back to the room (10 min), owner and next action named out loud (5 min).

Notice the second version has less open-ended discussion time, not more, and that is deliberate rather than a flaw. Unstructured discussion time is where a workshop quietly turns back into a topic-shaped conversation, however tightly the invite was worded. Bounding the discussion to the specific tradeoff that actually determines the decision is what keeps thirty people's worth of opinions from expanding to fill however much time is available.

When the sentence will not come

Sometimes trying to write the decision sentence in advance reveals that it genuinely cannot be written yet, and that is useful information rather than a failure of the exercise. If a room cannot decide between two loyalty program options because nobody actually knows what either one costs to build, the correct workshop is not "discuss the loyalty program." It is a much shorter, much more targeted session to decide who is responsible for getting each cost estimate by a specific date, with the real decision-making workshop scheduled for after that information exists. Running the big discussion anyway, hoping the room will somehow reach a decision it does not have the information to reach, is exactly how you end up back in yesterday's story, with everyone nodding at something that was never actually decidable in that room on that day.

Writing the decision sentence in advance means you have to commit, in writing, to what a good outcome looks like before you have heard the room's opinions. That feels presumptuous the first few times, as though you are pre-judging a conversation that has not happened yet. In practice, it does the opposite. It does not decide the answer in advance; it decides the question in advance, which is what actually lets the room's disagreement be productive instead of directionless. A room arguing about which of two clearly stated options to pick reaches a verdict. A room exploring a topic in the abstract, however smart everyone in it is, very often does not, and tomorrow's article picks up from exactly that point: what to actually do once the disagreement starts happening live in the room.

Go out and be successful.

Oluwatosin Ogunkoya ·  Flotog BA Insights  ·  1:1 mentoring and coaching for BAs at every career stage  ·  www.flotogbainsights.com

TOMORROW

Reading and Managing the Room - What is actually happening when a workshop goes quiet, or when one voice quietly starts running the whole session.