How to prove the ROI of innovation

Innovation leaders are judged on results, yet they rarely have adequate tools to demonstrate them. The budget has to be defended every year, and every year the board's question is the same: what return did we get?

Why the ROI of innovation is so hard to demonstrate

The ROI of a traditional investment is calculated by comparing costs and returns over the same time horizon. Innovation breaks this scheme in at least three places. Timing, first of all: a PoC may last a few months, but the value it generates often materialises years later, when the solution goes into production. Then the nature of the value, which is rarely just direct revenue: it can be cost avoided, risk reduced, capability acquired, time saved. Finally, attribution: when an innovative project improves a process, the credit is shared between those who brought the solution and those who use it every day, and the innovation function struggles to claim its part.

The consequence is familiar. In the absence of a method, reporting slides towards the metrics that are easiest to count: number of ideas collected, events organised, startups met. Real numbers, but they describe activity, not impact. And a board that only sees activity will, sooner or later, cut.

Step one: no initiative without an objective

The foundation of the method is simple to state and demanding to practise: every initiative must be born tied to an explicit business objective. Reducing the cost of a process, opening a new segment, decreasing dependence on a supplier, preparing for upcoming regulation. The objective must be written down before starting, together with the question the initiative is meant to answer.

This step has an immediate effect on portfolio quality. Initiatives that cannot state a credible objective surface right away, and the discussion about what to fund stops being a contest of enthusiasm. It also has an effect on future reporting: if the objective is clear from the start, the impact will have a benchmark to be measured against.

Step two: define leading and lagging metrics

A frequent mistake is measuring innovation with a single type of indicator. You need two families of metrics, with different roles:

• Leading metrics: they signal whether the process is working, before the impact becomes visible. Average time from proposal to decision, progression rate between funnel stages, quality of formulated needs, scouting coverage against declared needs.
• Lagging metrics: they measure realised impact. Solutions taken into production, savings verified with the functions involved, revenue generated by new offerings, risks mitigated in a documentable way.

The first family is for managing, the second for accounting. Presenting only leading metrics to the board sounds like making excuses; presenting only lagging metrics means staying silent for the months, sometimes years, that results need to mature. The credible narrative uses both: here is the impact already realised, and here are the indicators showing the pipeline is preparing more.

Step three: track progress and impact over time

Defining metrics is not enough if the data then lives in spreadsheets updated the night before a meeting. Tracking must be continuous and embedded in the process: every stage transition of a PoC, every committee decision, every validated result should be recorded when it happens, not reconstructed from memory three months later.

There is a practical reason: after-the-fact reconstruction is where credibility cracks. Approximate dates, savings estimated by feel, decisions whose rationale nobody remembers. A CFO notices quickly. If instead the history of every initiative is traced from its birth, the figure presented to the board is an extract from the system, with its rationale documented, and the conversation changes tone.

This is one of the reasons tracking sits inside the workflow in blendX: modules such as PoC Management and Innovation Governance record stages, decisions and results as the process moves forward, and reporting becomes a view over data already collected rather than a construction site that reopens every quarter.

Step four: report to the board in its own language

The last step is one of translation. The board does not want the detail of activities: it wants to understand whether the investment in innovation is producing value and where it is heading. The structure that works is the portfolio view: which business objectives we are serving, how many initiatives are active for each, what stage they are at, what impact has already been realised and what is expected.

The discipline of closing

This reporting should also include what was stopped. It may seem counterintuitive, but declaring closed initiatives, with the reason for closure and what they taught, strengthens the overall case: it shows that the process selects, that budget is not dispersed across zombie projects, and that every PoC produces knowledge even when the answer is no. A portfolio where nothing ever gets closed describes a process that does not decide.

With these four elements, explicit objectives, metrics from both families, continuous tracking and a portfolio-based narrative, the question "what return did we get?" stops being a dreaded moment. It becomes the occasion where the innovation function shows it is managed with the same rigour as every other business function.