top of page

Why Your Business Case Isn’t Changing Minds (and What to Do About It)

You’ve built the model. You’ve hit your margin targets. You’ve shown the ROI. So why is your business case still not convincing decision-makers?

Here’s the truth: It’s not the financials that fail—it’s the process, the people, and the biases behind them. Numbers alone don’t persuade—narratives and dynamics do.


The Big Flaws in Business Cases


  1. Anchored optimism & overconfidence

    • The RAND & PIMS studies show that project estimates are routinely overly optimistic—major cost overruns and inflated benefits are the norm, not the exception.

    • Harvard Business Review research confirms that cognitive biases—like anchoring—undermine accuracy, with nearly 75% of large-scale projects failing to meet expected outcomes .

  2. Misaligned stakeholder narratives

    • Gartner estimates that 85% of AI/digital transformation projects don’t scale—not for lack of value, but due to insufficient executive alignment and multi-stakeholder buy-in.

    • Pavilion data highlights that only 56% of GTM leaders hit Q1 revenue targets, showing a gap between financial expectations and execution .

  3. Lack of behavioral insight

    • Behavioral science identifies top biases in project decision-making: overconfidence, planning fallacy, base-rate neglect—critical value drivers that sales reps often overlook.

    • HBR emphasizes that large business transformation failures aren’t just technical—they're cognitive and political.


Where Most Business Cases Fall Short

Pain Point

What’s Missing

Why It Matters

One-size-fits-all ROI model

Persona-specific framing (CFO, IT, procurement)

Stakeholders across functions care about different value types and risk levers.

Static snapshot, not dynamic

Real-time data nudges and evolving assumptions

As circumstances shift, stale numbers break trust.

Rational-only logic

Behavioral and political context

Neglecting fear, status, risk, and power kills deals.

No calibration

Peer benchmarks and base rates

Anchored optimism leads to unrealistic ROI or cost estimates.

How to Make Business Cases That Actually Convince


  1. Ground in real-world baselinesDefault to trusted industry benchmarks (like PIMS) and correct for bias before you even build your deck.

  2. Map the political landscape—earlyWho else will see this? CFO? IT director? Procurement? Frame value points in their language and concerns.

  3. Build scenarios—not just one outcomeShow base-case, likely case, and upside case. Invite stakeholders to explore the range, not just your high-side forecast.

  4. Make it alive: iterate along the dealAs scope or risk changes, update the model in real time. This builds confidence and shows you're in control.

  5. Surface their behavioral biasesCombat optimism bias by playing devil’s advocate. Highlight uncertainties and show how your model handles them.

  6. Normalize the unexpectedCite case studies—like Gartner’s AI failure rates or HBR’s project overrun stats—to make your assumptions more relatable and realistic.


Why It Works


  • Builds credibility – Using industry benchmarks and assuming the middle ground shows you're grounded in reality—not just selling hope.

  • Speaks everyone's language – Finance hears cost efficiency. IT hears risk reduction. Procurement hears vendor flexibility. Execs hear growth probabilities.

  • Transforms the case from artifact to decision tool – It moves from a set-and-forget deck to a live, shared asset that stakeholders own and trust.


The Bottom Line


If your business case isn’t hitting home, it’s not a numbers problem—it’s a credibility, narrative, and cognitive alignment problem.

To change minds, your business case must be:

  • Grounded in realistic assumptions and external benchmarks

  • Adaptive to deal evolution and changing context

  • Multi-threaded for all decision-makers

  • Cognitively calibrated to counter biases and build trust

Spotlight helps you deliver business cases that not only show ROI—but earn it.


Why Your Business Case Isn’t Changing Minds

Comments


bottom of page