Those of us who have been playing this game for a while know that a large proportion of business cases aren’t really designed to help an organization decide; they’re designed to help someone get a “yes.”
When approval becomes the primary objective, the business case understandably starts behaving like a sales document. Benefits are emphasized, risks are softened, assumptions are presented as settled facts, and alternatives are mentioned briefly, if at all, while the preferred option is made to look inevitable and uncertainty is treated as a weakness that needs to be edited out.
The result may well be a polished document and a successful approval meeting, but there’s a very real chance that the underlying decision could still be poor.
This is what approval theater looks like: the reassuring template and financial model are in place, the required meeting takes place, and the relevant names appear in the approval record, yet the formal process does more to confirm an established direction than to examine whether it's the right one.
A better approach starts with a different question: instead of asking, “How do we make this case convincing?” organizations would be much better off asking, “What would help us make this decision well?”
Don’t get me wrong, the business case still has a role to play. It just stops being the be-all and end-all, instead becoming one output of a stronger decision process.
Approval theater often begins before the case is written
In theory, a business case should help an organization define the problem, consider its options, examine the evidence, and decide whether to proceed. In practice, it’s often requested only once a preferred solution has already been selected.
An initiative may already have a sponsor, a preferred vendor, and an internal launch date before anyone's asked to document its expected value or risks. At that point, the case mainly exists just to justify momentum that already exists.
That changes the behavior of everyone involved. The author is encouraged to strengthen the preferred option because a neutral assessment could delay the work, while reviewers are placed in the awkward position of effectively going through the motions of challenging a proposal that's already gathered (likely unstoppable) support.
None of this necessarily happens because of bad intentions, but people are products of their environment, so when an organization asks for evidence only after a commitment has already been made, that evidence naturally becomes cheerleading rather than a genuine test.
A stronger process begins earlier, when there’s still room to change direction. It starts with the outcome the organization is trying to achieve, then considers the available options, the evidence behind them, and the conditions that would make each one successful. The business case can still communicate this work, but it shouldn’t be the first point at which the organization pauses to think seriously.
Persuasive cases tend to smooth away uncertainty
In the real world, meaningful decisions are rarely as precise as their financial models make them appear. Costs may be reasonably well understood, but expected benefits often depend on adoption, behavior change, market conditions, implementation quality, or capacity that hasn’t yet been secured.
A persuasive case tends to make these uncertainties less visible because confidence is easier to approve than ambiguity. Ranges become single figures, assumptions are absorbed into the narrative, and risks are mentioned in passing to tick a few boxes but aren’t explored deeply enough to influence the headline return. A benefit estimate that depends on several uncertain conditions can eventually appear in the executive summary as one clean annual number.
The problem isn’t the use of estimates, since decisions have to be made before every fact is known and uncertainty is therefore unavoidable. The issue arises when the presentation gives those estimates more certainty than the underlying evidence supports.
Suppose a proposal is expected to generate $2 million in annual value. Before that number can support a decision, reviewers need to understand how it was built: how much depends on adoption, whether productivity gains can genuinely be converted into capacity or cost reduction, what happens if implementation is delayed, and which assumptions have been validated rather than simply agreed by the project team.
Off-the-shelf AI lacking sufficient guardrails can make weak foundations easier to overlook because it will happily (and with an unnerving level of sometimes misplaced confidence) produce fluent financial rationales, benefit descriptions, and risk summaries very quickly, all of which can seem sensible enough on the surface. That’s useful during drafting, but the quality of the prose says little about the quality of the evidence. Unless the process distinguishes clearly between user-provided information, imported material, calculated outputs, and AI inference, polished language can give weak claims an authority they absolutely have not earned.
Good decision support should make uncertainty easier to see and discuss, showing where confidence is high, where assumptions remain untested, and which variables are most likely to change the result.
A useful case may create more debate
Many organizations judge a business case by how smoothly it moves through approval, so questions, delays, and disagreement can be interpreted as signs that the case was poorly prepared. Sometimes that is actually true, but additional debate can also be an extremely positive sign because it shows that the process is actually examining the decision rather than merely blindly endorsing it.
Once a proposal is tested properly, the preferred option may become less attractive. A cheaper alternative may perform better under a conservative scenario, the proposed solution may prove premature, or a limited pilot may offer more useful evidence than a full commitment.
These outcomes may well frustrate the sponsor, but changing scope before delivery, identifying a critical dependency, or avoiding a weak investment can save far more in the long run than the short-term cost of a slower approval.
A decision-quality approach should help people understand the outcome they’re trying to achieve, the options that could credibly produce it, the evidence supporting the expected benefits and costs, and the assumptions most likely to affect the result. It should also make clear who's responsible for delivery and who will be accountable for the outcomes after approval.
The depth of analysis should reflect the significance of the decision. A small operational request may need only a lightweight justification, while a major investment may require detailed scenarios, risk modeling, governance, and an approval package. The discipline lies in asking the right questions with an appropriate level of rigor, rather than just producing the longest possible document.
The decision should come before the document
Organizations often treat the completed business case as proof that the decision has been properly examined, even though the document can only reflect the quality of the thinking and evidence behind it.
A more useful approach treats the decision as the primary object. The organization captures the intended outcome, available options, supporting evidence, assumptions, financial logic, risks, responsibilities, approval requirements, and tracking approach in a structured form. From that information, it can produce whatever output is needed, whether that’s a business case, decision brief, approval package, approval record, or tracking plan.
This changes the role of the business case. Rather than becoming a fixed document that’s polished for a meeting and then politely described as “stored” when it has, in reality, simply been forgotten about, it becomes one view of a living decision record. Reviewers can challenge a particular assumption or calculation without losing the surrounding context, and the underlying information can be updated as new evidence emerges.
It also creates continuity after approval because the original assumptions, expected outcomes, and named owners remain visible when results are reviewed.
This is the reasoning behind KangaROI’s Decision-first approach. The intention is to improve the underlying decision by helping users develop the case, identify gaps, compare options, examine uncertainty, and connect approval to subsequent tracking.
kAI supports that work by refining content and highlighting missing evidence, assumptions, or areas requiring validation, while preserving the distinction between evidence, judgment, calculation, and inference.
The problem becomes harder to manage at portfolio level
The limitations of approval-focused business cases become more serious when leaders need to oversee dozens or hundreds of decisions across an organization.
If every team prepares cases differently, senior stakeholders can’t compare proposals consistently. Similar initiatives may be approved in separate departments without anyone recognizing the duplication, expected benefits may overlap (effectively cannibalising each other), and several projects may assume access to the same scarce pool of people or budget.
A folder of individually persuasive documents does little to solve this because the information inside them remains difficult to aggregate or compare. Structured decision data allows leaders to see what’s being proposed, approved, delivered, delayed, or underperforming across teams and portfolios, while comparing expected value, risk, confidence, resource demand, ownership, and progress.
Over time, leaders can compare forecasts with actual results, identify recurring weaknesses in benefit estimates, and recognize delivery risks that regularly pop up across different initiatives. Consistently structured information across many decisions also supports prioritization, resource allocation, governance, and helps to avoid corporate amnesia by fostering organizational learning.
Change the questions around the business case
Organizations don’t need to abandon business cases or make every approval process more complicated. But they do need to become clearer about what the process is intended to achieve, because approval theater takes hold when completing the document and securing sign-off become more important than examining the quality of the decision.
Before a proposal is approved, reviewers should ask whether they’re considering a real choice or validating a direction that's effectively already been agreed upon. They should test whether credible alternatives were assessed fairly, which claims are supported by evidence, which remain assumptions, and what would need to be true for the expected value to materialize.
They should also look beyond the approval meeting by asking who will own the outcomes, how progress and value will be measured, what happens if the assumptions change, and how the proposal interacts with other commitments across the portfolio. These questions help connect the decision being made today with the results the organization expects to see later.
Moving beyond approval theater doesn’t mean making every decision slower or more bureaucratic. It means ensuring that the formal process still has the power to test the preferred answer, expose uncertainty, and change the organization’s direction when the evidence justifies it. That may make approval less comfortable, but comfort isn’t the purpose of governance. The purpose is to help the organization make a sound choice while uncertainty still exists and while there’s still time to respond to what the evidence reveals.
A polished business case can be useful, but polish should never be mistaken for decision quality. The strongest cases make the reasoning visible, expose the trade-offs, preserve uncertainty where it matters, and create a clear connection between what was approved and what the organization later expects to achieve.
That may lead to a proposal being changed, delayed, tested, reduced, or rejected, while in other cases it will give decision-makers much greater confidence that approval is justified. Either way, the organization gains something more valuable than a convincing document: a better understanding of the decision it is making.
