Measuring Innovation Is Not the Same as Measuring Output

Most organisations that take innovation seriously have something to show for it. A dedicated budget line, perhaps, or an internal ideas platform that gets reasonable traffic, an annual innovation day that people genuinely enjoy attending, a percentage of revenue earmarked for new initiatives that leadership can point to in a board presentation. What they often cannot show, when pressed, is whether any of it is actually moving the organisation forward in the ways that matter.

This is rarely a problem of commitment or ambition. The people running these programmes care about them and have invested real effort in building them. It is, more precisely, a problem of measurement, and specifically of reaching for metrics that are easy to produce rather than metrics that are honest about what is actually changing. The instinct is understandable and almost universal: when something is difficult to evaluate, organisations tend to default to counting what is countable. Ideas submitted. Events hosted. Workshops delivered. Percentage of employees who have been through an innovation training. These numbers are real and defensible, and they have the enormous practical advantage of being straightforward to put in a report. What they measure, however, is effort and activity rather than progress, and over time, teams learn to optimise for whatever is being tracked. You end up with more ideas in the pipeline and fewer being seriously interrogated, more sessions on the calendar and less that anyone can point to as having changed how the organisation actually works.

Outputs Versus Outcomes

The distinction that gets quietly lost in all of this is the difference between outputs and outcomes. An output is something your organisation produces as a direct result of innovation activity: a new product, a pilot programme, a redesigned internal process, a cross-functional team that did not exist before. An outcome is what genuinely changes as a result, whether in the market, in the organisation's capability, in how customers or stakeholders experience what you deliver, or in the strategic position you occupy relative to your competitors and peers. Most innovation measurement, even in organisations that are genuinely trying to do this well, stops at the output level and then reports back as though the job is done. The pilot ran. The product launched. The programme was delivered. Whether any of it produced the change it was designed to produce is a question that often never gets formally asked.

Starting from a Different Place

What meaningful innovation measurement actually requires is starting from a different place entirely. Before agreeing on what to track, it is worth spending serious time on what the organisation is genuinely trying to change and over what timeframe, and being honest about whether the current activity is designed to produce that change or simply to demonstrate that innovation is happening. A university building new research partnerships with industry needs fundamentally different indicators than a pharmaceutical company running cross-functional capability programmes, which needs different indicators again from a public body trying to shift how it approaches service design and decision-making. The metrics should follow the strategic ambition, and the strategic ambition needs to be specific enough to make that possible. "We want to be more innovative" is not a strategic ambition. It is a direction of travel that nobody can disagree with and nobody can meaningfully measure.

What Failure Actually Tells You

There is also something important in how organisations treat failure within their innovation measurement frameworks, which is that most of them do not treat it as useful information at all. An initiative that does not deliver what it set out to deliver is typically either not discussed or written off as a learning experience in a way that does not actually produce learning. One of the more valuable things an organisation can do is build the discipline of distinguishing between initiatives that failed because of poor execution and those that failed because the underlying assumption was wrong, because those two things have completely different implications for what you should do next. The first is a delivery problem. The second is a strategic insight, potentially a very valuable one, about where the organisation's theory of change needs to be revised.

Measurement That Means Something

We work with organisations to build approaches to innovation measurement that are genuinely connected to strategic intent rather than to the activity that is easiest to count. It takes longer than agreeing on a set of KPIs, and it requires a willingness to have honest conversations about what is actually working and why. But it is the only version that gives leadership a reliable read on whether the organisation is changing in the ways it needs to change, rather than simply a reassuring picture of how busy everyone has been.