How to Justify an Innovation Center to Your Board

Innovation cases fail in board meetings for a predictable reason: they are presented as investment cases with projected returns, and every experienced board member knows those projections are unreliable. Presenting a five year revenue figure for work whose entire purpose is to answer questions you cannot currently answer signals either optimism or unfamiliarity, and neither helps.

Boards do fund exploratory work. They fund it when the downside is bounded, the strategic question is real, the commitment is staged, and the person asking has been honest about what could go wrong. None of those require a projection.

This guide sets out how to structure the case, what to include, what to leave out, and how to handle the questions that come back.

Lead with the question, not the answer

The strongest opening is a strategic question the company cannot currently answer and needs to. Something specific: whether a category of customers can be served profitably at a tenth of the current cost to serve, whether a capability a competitor has demonstrated is reproducible, whether a technology shift makes part of the current model obsolete.

This works because it is true, because it is verifiable, and because it reframes the request. You are not asking the board to believe a projection. You are asking it to agree that a question matters and that answering it is worth a bounded amount of money.

The test of a good question is that both possible answers are valuable. If the answer is yes, you have found something. If the answer is no, you have avoided committing to something that would not have worked. A question where only one answer has value is usually a proposal in disguise.

Bound the downside explicitly

This is the part boards are actually evaluating, and most innovation cases barely address it. The relevant questions are what the maximum exposure is, how quickly it can be stopped, and what is lost if it is.

A well structured case answers all three before being asked. Annual cost is capped and stated. There are defined decision points at which the programme can be stopped. Exit cost is low, meaning short notice periods, no long leases and no large capital commitment. And the fallback position is unchanged, meaning the company is no worse off than if it had never started.

A small senior team in a market with reasonable notice periods, no facility commitment and no capital expenditure is a genuinely bounded commitment, and saying so plainly is more persuasive than any upside case.

The last row is where most cases are weakest and where the eventual failure usually originates.

Stage the commitment

Asking for a three year commitment invites a three year level of scrutiny, and the case will not survive it because nothing in exploratory work can be forecast at that horizon. Asking for a first stage with a defined decision point invites a much smaller decision.

Staging also aligns with how the work actually proceeds. The first stage establishes the team and answers the first question. The second widens the portfolio if the first produced something. The third institutionalises it. Each stage has an explicit decision, and the board retains the ability to stop at each one.

This is not a technique for slipping a large commitment past a board in pieces, and it should not be presented as one. Be explicit that later stages exist and will require their own approval. Boards respond well to a plan that shows the whole path and asks only for the first step.

State the failure conditions yourself

This is the single most effective technique available and the one most people avoid. Say plainly what would have to be true for this to have been the wrong decision.

Name them specifically: if we cannot hire at the seniority required, if the questions we choose turn out not to matter, if the business has no capacity to adopt what we produce, if the sponsor leaves and nobody replaces them. Each of these is a real risk and each has a mitigation, and presenting them yourself demonstrates that you have thought about the proposal as a decision rather than as a request.

Boards are unusually good at detecting when a risk section has been sanitised. A case with no failure conditions reads as a case that has not been stress tested, and the first question will be the one you left out.

• We cannot hire the seniority the work requires
• The strategic question turns out to be less consequential than we believed
• The business has no capacity to adopt what we produce
• The sponsor leaves and no successor takes it on
• We choose safe questions because we are afraid of visible failure
• The centre gets absorbed into delivery work during a difficult quarter

Name the adoption route

Most innovation centres are not closed because they invented nothing. They are closed because nothing they invented was ever used, and the board reasonably concluded the spending produced no effect.

Address this in the case rather than leaving it as an implementation detail. Name the owner in the core business who will receive successful work, confirm they have agreed, and state that productionisation is funded separately so the centre does not have to choose between exploring and industrialising.

This single element differentiates a case that has been thought through from one that has been assembled. It also makes the eventual outcome far more likely to be positive, which matters more than winning the meeting.

What to leave out

Several standard inclusions actively weaken an innovation case, mostly because they invite scrutiny the underlying work cannot survive.

• Five year revenue projections, which nobody believes and which invite a debate you cannot win
• Comparisons to well known innovation successes at other companies, which read as aspiration rather than analysis
• Technology detail beyond what is needed to understand the question
• A headcount plan for years two and three, which implies a commitment you are not asking for
• Any suggestion that the work will not fail, which signals unfamiliarity with exploratory work
• Vague framing such as exploring emerging technology, which constrains nothing and cannot be assessed

Handling the questions that come back

Three questions come back almost every time, and each has a good answer that most people do not give.

Frequently asked questions