The business case is dead. Long live the opportunity canvas. Every PMO lead and traditional project manager just felt a disturbance in the force — but here’s the truth: business cases, as most organisations use them, are relics. Outdated, slow, and political. In most cases, written to justify a decision someone already made.

Listen on Spotify — The Better Business Analyst Podcast

Why the Traditional Business Case Is Broken

The classic business case has been a staple of project governance for decades. It promises rigour — a structured argument for investment, backed by ROI calculations, risk registers, and options analysis. In theory, it forces decision-makers to think clearly before committing resources.

In practice? It’s usually a political document dressed up as analysis.

Here’s what actually happens in most organisations:

1. A senior leader or sponsor decides they want something.
2. A BA or PM is asked to “write the business case.”
3. The numbers are worked backwards to justify the predetermined answer.
4. Governance approves it — because nobody wants to be the person who killed the exec’s project.
5. The project starts with false confidence and manufactured consensus.

The business case didn’t create clarity. It created the illusion of clarity. And that’s worse.

The Three Real Problems with Business Cases

1. They’re Built for Approval, Not for Decision-Making

A business case is designed to pass through a governance gate. That gate is the audience. So the document is optimised to satisfy the gate — not to surface what’s actually true about the opportunity, the risks, or the alternatives.

Real decisions require honest trade-offs. Business cases written to win approval bury trade-offs in appendices, round numbers favourably, and hedge language where specificity would cause friction.

2. They’re Too Slow for Modern Delivery

A traditional business case takes weeks to months to produce. By the time it’s approved, the market context that justified the investment may have shifted. Competitors may have moved. The customer problem may have evolved.

Agile delivery was supposed to fix this — but many organisations just layered Agile sprints on top of waterfall governance. You still need a 40-page business case to start the work, then you run in two-week sprints once approved. That’s not agility. That’s a slow start to a fast run.

3. They Create False Certainty

A five-year NPV calculation in a business case is not analysis. It’s fiction presented with Excel precision. When you see “projected ROI: 340%,” someone picked a number that would get the project approved, then worked the formula backwards.

False certainty is more dangerous than acknowledged uncertainty. It stops teams from asking the questions they should be asking throughout delivery: Is this still the right thing to build? Are the assumptions holding? Should we pivot?

Enter the Opportunity Canvas

The opportunity canvas is a lean, honest alternative to the business case. Instead of a lengthy document built to survive governance, it’s a single-page (or single-screen) artefact built to drive conversation.

Where a business case asks “can we justify this investment?”, the opportunity canvas asks “should we pursue this opportunity, and what do we need to learn to be sure?”

The key difference is epistemic honesty. An opportunity canvas explicitly separates what we know from what we assume, and what we need to validate before committing fully.

What an Opportunity Canvas Covers

A well-structured opportunity canvas addresses six things on one page:

1. The problem or opportunity — stated in customer or business terms, not solution terms. What’s broken, missing, or possible?
2. Who it affects — specific customer segments, internal stakeholders, or market groups. Not “the business.” Actual people with actual needs.
3. The current impact — what is this costing us, or what are we failing to capture? Revenue, time, risk, experience.
4. The proposed response — a broad direction, not a fixed solution. Room for the team to discover the right answer.
5. Key assumptions and risks — explicit, not buried. What has to be true for this to work? What could kill it?
6. The next learning step — not “approve the project.” What’s the smallest thing we can do to test the most critical assumption?

That last point is the most important. The opportunity canvas doesn’t end with approval — it ends with a validated next step. It treats investment as iterative, not binary.

The BA’s Role in Shifting from Business Case to Opportunity Canvas

This shift isn’t just a document swap. It’s a mindset change — and BAs are well-placed to lead it.

Here’s how to start introducing opportunity canvas thinking in your organisation without declaring the business case dead overnight:

Start with the Discovery Phase

Before anyone writes a business case, run a structured discovery sprint. Use the opportunity canvas format to explore the problem space. Then decide whether a formal business case is even necessary — or whether the canvas itself is sufficient to get started.

Separate Problem from Solution

The most common business case failure is jumping to a solution before the problem is fully understood. An opportunity canvas forces the problem statement first. No solution language until the problem is agreed and evidence is presented.

Make Assumptions Visible

Every business case has hidden assumptions. An opportunity canvas surfaces them explicitly — and assigns ownership. “We assume customers will pay $X. Here’s how we’ll validate that in the next sprint.” That’s BA work at its best.

Replace Five-Year Projections with Nearest Learning Steps

Instead of a five-year NPV, define what you need to learn in the next 30 days to justify the next phase of investment. This aligns with how good product teams work — staged funding tied to validated learning, not upfront approval tied to fictional forecasts.

When the Business Case Still Makes Sense

To be fair: there are contexts where a formal business case is appropriate and necessary.

• Regulatory or compliance-driven investments — where governance requires documented justification regardless of strategic clarity.
• Large capital expenditures — infrastructure, plant, or major system replacements where the decision is genuinely binary and irreversible.
• External funding applications — grants, board approval, or investor decks that require a structured document format.
• Mergers, acquisitions, and strategic partnerships — where due diligence genuinely requires structured financial analysis.

The problem isn’t the business case format — it’s using that format as a default for every initiative, regardless of size, uncertainty, or strategic context.

Key Takeaways from This Episode

• Most business cases are written to justify decisions already made — not to create genuine clarity
• They’re too slow for modern delivery, optimised for approval rather than decision-making, and create false certainty
• The opportunity canvas is a lean alternative: one page, honest about assumptions, ends with a learning step not a budget approval
• BAs can introduce canvas thinking gradually — starting in discovery, before the business case is written
• The business case still has a place — but it shouldn’t be the default for every initiative

Free Templates to Support This Approach

If you’re ready to move beyond the traditional business case, our free template library has resources to support the shift:

• Business Case Template — for when you do need a formal document
• Gap Analysis Template — for mapping current vs. desired state before committing to a solution
• Requirements Traceability Matrix — for tracking assumptions through to delivery

Subscribe to the Better Business Analyst Podcast

New episodes weekly — covering requirements, stakeholder management, Agile BA practice, and building a better BA career. Subscribe on Spotify or watch on YouTube. Browse all episodes on our podcast page.

Also worth reading: What Is Business Analysis? | 15 Essential BA Techniques | Stakeholder Management Guide