Field note
How do you write a business case when you don't know the answer yet?
The spreadsheet wants a number. Innovation can't give you one.
Every innovation leader knows this meeting.
You have an idea that could matter. The steering group asks for a business case. Revenue in year three, payback time, a cost estimate with two decimals. And you sit there knowing that every number you write down is a guess dressed up as a fact.
The problem is not that leaders ask for a business case. They should. The problem is that we use a tool built for known outcomes on work where the outcome is unknown. A classic business case answers "how much will we earn?". In early innovation, the honest answer is "we don't know yet, and here is how we will find out".
Fund the next answer, not the whole journey
The most useful shift I have seen is to stop asking for money for the whole idea and start asking for money for the next question.
Instead of "give us 4 million for a new service", you ask "give us 300,000 and eight weeks to find out if customers will pay for it". The decision gets smaller. The risk gets smaller. And the steering group gets something they can actually judge.
In the figure eight, this is what happens in the explore loop. You prioritize, conceptualize and pilot in small steps, and each step has its own small business case.
Write down what has to be true
A good early business case is a list of assumptions, not a list of numbers. Ask the team: what has to be true for this to be worth doing?
- Customers have this problem often enough to care.
- They will change how they work to use our solution.
- We can deliver it at a cost that leaves a margin.
- Someone in our own line organization wants to own it.
Then rank them. Which assumption, if it turns out to be wrong, kills the whole thing? Test that one first. Most teams test the easy ones first, because it feels like progress.
Use ranges and say how sure you are
If you need numbers, and sometimes you do, give a range and say how confident you are. "Between 2 and 9 million in year three, low confidence, we will know more after the pilot" is more honest than "6.4 million". It also invites a better conversation. Leaders can relate to uncertainty when you name it. What makes them nervous is false precision that falls apart later.
Prove value before you prove scale
In my own work I often replace the word "concept" with proof of value. It is not enough that something works technically. The question is whether it creates value for someone who will pay for it, internally or externally. A small pilot that proves value is worth more than a big plan that promises it.
Agree on when to stop, before you start
The bravest line in a business case is the one that says when you will stop. Set a decision date and the criteria up front. If we don't see X by week eight, we stop or pivot. It sounds negative. It is the opposite. It makes it safe to start, because everyone knows the downside is limited.
What to bring to your next steering group
- The question you want to answer next, not the whole idea.
- The three assumptions that matter most, ranked by risk.
- The cost and time to test the riskiest one.
- The decision date and what will make you stop.
That is a business case a CEO can say yes to. And it is honest.
How do you handle the "give me the number" question in your organization? I would love to hear what has worked for you.
Curious where your organization stands? Take the free Innovation Eight check and get a brief you can bring to your leadership.
Take the Innovation Eight check