Pressure-Test the Initiative Before You Fund It - The Well-Run Company Series/Article 8 of 9

The initiative had everything going for it. Real market demand, a credible champion, an exciting revenue number in the deck. We approved it in under an hour, and it consumed nine months before we admitted it was dead. What we learned afterward was the useful part: nothing that killed it was unknowable on approval day. The department that had to execute was missing a key capability, the process the plan assumed did not exist yet, and the manager carrying it was already the most overloaded person in the building. We had funded an initiative the environment could not yet execute, and nothing stopped us, because nobody in the room asked the questions that would have shown it.

It did not fail in month six, when the problems became visible, or nine months later, when we finally shut it down. It failed at the approval meeting.

Two lenses

Since then, I have never taken a major initiative forward for funding without pressure-testing it through two lenses, and I have run the same test inside other companies' planning cycles as an advisor. It has held up in every planning environment where I have used it, and the exciting ideas usually need it most.

The first lens is readiness: is the environment prepared to execute this? Walk the same territory as the environment audit, but pointed at the specific initiative. Does the structure put one accountable owner on it, with enough room in that person's week to own it? Do the processes the initiative assumes actually exist, or does the plan quietly include inventing them midway? Are the required resources committed, or conditional on a good quarter? Will the people doing the work receive the information and training the plan depends on? Score it honestly, and treat low scores as findings.

The second lens is financial: which of the seven levers does this actually move, and by roughly how much? Skip the deck's headline number and ask about the mechanism. Does it move price, volume, cost of goods, operating expense, receivables, payables, or inventory, and what does the rough arithmetic look like after counting the money, capacity, and management attention it will consume? Some exciting initiatives, worked through honestly, move nothing but activity. And some boring ones, a terms change, a pricing cleanup, a purchasing discipline, score quietly spectacular numbers and never get proposed because nobody would applaud.

What the two lenses produce

Scoring initiatives through both lenses sorts them into four piles, and each pile has its own correct move.

Strong on both readiness and financial impact: prioritize it and go.

Strong financially but weak on readiness: build the foundation first. The honest sequence is a readiness project this quarter and the initiative next, however impatient the room gets. Name the missing capability, process, resource, or owner, assign it, and set the condition that must be met before the original initiative returns for approval.

Ready but financially thin: be careful. These are the pet projects that consume good teams while producing little that can be measured.

Weak on both: stop, say so out loud, and thank whoever proposed it so the next idea still shows up.

The sequencing insight is the one that saves companies real money. Most leadership teams treat every approved initiative as immediately startable, so the portfolio runs everything at once and starves it all. The two-lens view makes sequencing conversations natural: this one goes now, this one waits for the foundation we are building, this one dies. A company that sequences three initiatives well beats a company running nine badly, and it is not close.

Kill it out loud

The pile most companies manage poorly is the stop pile. In most companies a dead initiative gets quietly starved instead of killed, lingering on status reports at five percent effort, consuming a manager's credibility and a line of the meeting agenda for quarters. That slow fade teaches your team that commitments are negotiable and that no decision is ever really final.

Kill it out loud instead. Name the initiative, name what the two lenses showed, thank the champion specifically, and take it off the board in front of everyone. A company that can point to initiatives it evaluated, funded, and later killed on purpose, by name, is usually a healthy one. It means ideas get real evaluation, decisions get made, and the leadership team's attention goes where the evidence points instead of where the applause was loudest.

There is a development payoff hiding in all of this, and over time it becomes the main event. Run the two-lens test in public often enough and your managers internalize it. Proposals start arriving already pressure-tested: here is the owner, here is the process gap and the plan for closing it, and here are the levers it moves and the rough math. When that happens, the leadership team is thinking strategically as a matter of habit, which was the point all along.

The nine-month lesson above was mine. The discipline that came out of it has earned its keep in every company and planning cycle where I have used it since. Before you approve your next major initiative, put two questions on the screen: are we ready to execute this, and which financial levers will it move? The quality of the discussion that follows will tell you whether the initiative is ready for funding. And if you want an outside voice in the room for it, my door is open.