How to Present a Big Solution to Leadership

The Decisions Workshop is the moment when journey management converts months of discovery, mapping, and creation work into organizational commitment. Leadership closes the workshop by determining which Big Solutions move forward, which need more development, which require board discussion, and which receive a clear yes or no. The quality of that decision depends heavily on how the solutions are presented.

Most presentation failures in organizational settings are not failures of ideas — they are failures of framing. The idea may be sound, the evidence substantial, and the customer need genuinely urgent. But if the presentation buries the insight in background, leads with features rather than outcomes, or fails to address the constraints that actually govern the decision-maker's choices, the meeting ends without the commitment the work deserved.

The Six-Element Structure

A presentation that produces clean decisions contains six elements, in roughly this order.

The Big Opportunity. Begin with the customer evidence: the cluster of needs, pains, pressures, and gains that justify this initiative. The room needs to understand what the customer is experiencing before they can evaluate what the organization proposes to do about it. This is not a summary of the discovery process — it is the distilled finding that the Big Solution addresses.

The Proposed Big Solution. The overarching direction: how the initiative synthesizes the emerging solutions teams have been developing into a coherent approach. Not a feature list — a strategic direction that explains how the pieces connect and why the combination is more powerful than the parts would be separately.

The Main Features. What brings the idea to life: the specific capabilities, interactions, or services that will constitute the solution. These should be traceable to the insights that motivated them — each feature connected to a customer need or pain rather than floating on its own.

Expected Experience Impact. Where the experience score is expected to lift and why. This is the forecast: the specific journey stages that will be affected, the magnitude of the expected improvement, and the evidence basis for the forecast. This section is what distinguishes a Big Solution presentation from a feature pitch.

Feasibility Notes. Risks, dependencies, and "gotchas" already identified. This is not a risk register — it is a short, honest accounting of what could prevent success. Teams that surface their own risks earn more credibility than teams whose risks surface for the first time in leadership's questions.

The Test Plan and OKRs. A lightweight experiment that can confirm or challenge the core hypothesis before full investment, paired with the objectives and key results that will govern the Big Solution's development. The OKRs should be tied directly to the experience scores the solution is designed to move.

"When clarity is missing, slides multiply. A presentation that can hold its core argument in six structured elements is a presentation that decision-makers can actually decide on."

What Leadership Needs to Close

Leadership's decision round at the end of the workshop is not about enthusiasm for individual ideas — it is about fit between solutions and the organization's strategic capacity.

What can go forward now depends on available resources, existing dependencies, and whether the Now-horizon test plan is realistic given current constraints. What needs more refinement is usually a solution where the experience impact is unclear or the feasibility notes surfaced questions that weren't answered in the presentation. What requires board discussion typically involves investment at a scale that exceeds the meeting's decision authority.

The presenter's job is to make these assessments possible, not to prevent them. A team that has prepared honest feasibility notes is helping leadership make a better decision — even if that decision involves delay or additional scrutiny. The Decisions Workshop is not a sales pitch. It is a convergence: a moment where the organization looks at what it knows about its customers and decides, transparently, what to do next.