The Decisions Workshop Is Convergence, Not Competition

The decision workshop is the third and final stop in the alignment sprint — the session where teams return with their developed proposals and the organization decides what goes forward. It is a moment with significant stakes: resources will be allocated, directions will be set, some proposals will advance and others will not.

The temptation is to frame this as a competition. Teams prepare their "pitches." The room evaluates and votes. The best solution wins.

This framing is wrong, and it produces the wrong session dynamics.

Why "Pitch Contest" Is the Wrong Model

When teams experience the decision workshop as a competition, several predictable things happen.

Protectiveness replaces openness. Teams who believe they are competing for resources present the strongest version of their proposal and conceal its weaknesses. The result is that leadership makes decisions based on the best possible representation of each option rather than an accurate one.

Overlap remains hidden. Teams whose solutions address similar problems from different angles have an incentive to present their approach as distinct and superior rather than potentially complementary. The organization ends up investing in two parallel efforts rather than combining them into a more resilient whole.

Synthesis does not happen. The most valuable output of the decision workshop is often not the selection of the best proposal but the recognition that two proposals could be merged into a single, stronger solution. This synthesis requires participants to be looking for patterns and commonalities rather than defending their territory.

"This workshop is not a pitch contest. It is a convergence moment — a place where teams compare notes, test assumptions, and look for synergies rather than winners. The mindset is simple: we are not competing for resources — we are learning how to combine them."

The Facilitation That Makes Convergence Possible

The service designer's role in this session is to create the conditions for synthesis rather than competition. This begins before the session itself.

In the preparation phase, review all the proposals that will be presented and identify the overlaps in advance. Which proposals address similar customer pains? Which share technical dependencies? Which teams have been working on adjacent problems without knowing it? Bring these observations into the session explicitly rather than waiting for teams to discover them during the presentations.

During presentations, the room should hold the same posture: constructive curiosity, not evaluation. After each presentation, the discussion question is not "is this a good idea?" but "where does this connect to what we already heard?" This keeps the conversation synthetic rather than competitive.

Management's Role in the Closing Round

Management closes the workshop by clarifying how each proposal fits the organization's current reality. This is not a vote or a ranking — it is a structured set of decisions:

• What can go forward now, with existing resources
• What needs more refinement or financial modeling before a commitment can be made
• What requires board or executive discussion
• What must wait for the next planning cycle
• What receives a clear yes or no based on current information

These decisions should be made in the room, not deferred to a follow-up meeting that may take weeks to schedule. The decision workshop's value comes precisely from its convergence function — the moment when diverse exploration becomes aligned direction. Deferring that alignment means losing the momentum that the alignment and creation phases have built.

The output is not a winner. It is a portfolio of selected directions, each with clear ownership, a defined test plan, and a documented next step. That portfolio is the foundation of the Journey Management phase that follows.