The Decision Was Made Long Before the Approval

Decisions are shaped early. Approvals happen late.

Somewhere in your organization there is a meeting where a large investment gets approved. A deck, a business case, a recommendation, a discussion, a signature. It looks like the moment of decision.

It usually isn't.

By the time a proposal reaches an approval forum, the real choice — what problem are we solving, and what range of answers are we willing to consider — was settled months earlier. It was settled by a small number of people, in conversations that were never called decisions, and it was rarely written down. The approval meeting then does a careful job of testing the case for one option. It almost never tests whether that option should have been the one on the page.

I have sat on both sides of that table, on capital portfolios with total exposure above $18 billion. The pattern holds at every size. It is not about the quality of the people in the room. It is about when the room gets involved.

How the funnel closes early

Three things happen, and none of them look like a mistake at the time.

The problem gets defined as a solution. "We need a second facility" instead of "we cannot meet delivery commitments in the east." "We need a new system" instead of "we cannot see inventory across three sites." Once the problem is stated as a solution, every hour of work that follows is about how, not whether. The framing is invisible because it sounds like a goal.

Developing options costs money. Generating them costs nothing — and belongs to no one. Someone owns the engineering study. Someone owns the cost estimate. Nobody owns the question of whether the right three options are on the list. It is the cheapest work in the whole process and the only step with no name, no budget, and no accountable owner.

Commitment accumulates quietly. A vendor conversation. Engineering hours. A number in next year's plan. An expectation set with a customer, a lender, or a board. None of these is a decision. Together they mean that by the time the formal gate arrives, changing course is no longer a choice — it is an admission. People are rarely willing to make one in a meeting.

What the investment gate actually tests

A good approval process checks that the numbers are sound, the risks are identified, the assumptions are stated, and the returns clear the hurdle. That is real work and it is worth doing.

But all of it can be true of a well-executed answer to the wrong question.

Rigorous scrutiny of the analysis lends the conclusion credibility it hasn't earned. The case survives hard questions, so everyone reasonably concludes the decision is sound. What survived was the arithmetic, not the framing.

While the underlying framing should test the bias along the way.

How to tell if this is happening to you

You don't need an audit. Four signals do most of the work.

• The alternatives aren't real. The case presents the recommendation, an option nobody would seriously choose, and "do nothing." Strawmen are a symptom of a decision already made.

• Nobody can say when the option was chosen. Ask directly: who decided this was the approach, and when? If you get a vague answer about consensus emerging, the decision was made outside any forum designed to make it.

• The scope grew but the justification didn't. The number moved 40 percent and the rationale is still the sentence from the original memo. The proposal and the reason for it have quietly separated.

• The estimate drifted toward the money available. Not always deliberate. Almost always a sign that the answer was fixed and the analysis was fitted to it.

The fix is earlier, not harder

The instinct is to strengthen the gate: more review, more scrutiny, more documentation. That adds cost and delay to a step that isn't where the problem lives. Three changes are cheaper and structural.

1. Put a decision point before the business case. A short forum — half a day, well before serious money is spent — that approves two things only: the problem statement and the option set. Not the solution. The output is a page, not a deck. It is the highest-leverage half day in the entire process, because it is the last point at which changing direction is free.

2. Separate who frames from who develops. The team building the case should not be the team that decided which case to build. This is not distrust; it is basic accountability design. A team that has spent six months on an option cannot be expected to be neutral about it, and shouldn't have to be.

3. Write the problem statement without naming a solution. One sentence, no proposed answer in it. If you cannot write that sentence, you do not yet have a problem statement — you have a preference. That is worth knowing before you spend anything.

Why this matters more as you grow

Small organizations get away with it. The framing conversations happen among people who all have the full picture, and course correction is quick because the commitments are small.

That protection disappears faster than most leadership teams expect. Once the framing happens in one part of the business and the money is approved in another, the gap between the two is where value quietly leaks — not through bad decisions, but through decisions that were never really made anywhere.

None of this is a governance failure in the formal sense. The structure works. It does exactly what it was designed to do. It was just designed to start too late.

---

Breakthrough Edge works with leadership teams facing material investment decisions (capital, expansion, scaling, or implementation) on the structure behind how those decisions get made. If the pattern above sounds familiar, get in touch.