Innovation gets scored two bad ways more often than it gets scored well: either everyone gets a similar middling score because nobody's sure what "counts," or the loudest, most visible idea-pitcher scores highest regardless of whether any of their ideas actually went anywhere. Measuring innovation fairly requires separating idea generation from idea execution, and rewarding both appropriately rather than conflating them.
Getting this right has real business consequences beyond fairness to any individual employee - companies that fail to genuinely recognise and reward innovation tend to see their most creative people either disengage or leave for somewhere their ideas visibly matter, while the people who remain learn quickly that proposing anything risky isn't worth the effort.
Why Innovation Is Genuinely Hard to Measure
Unlike most performance metrics, innovation doesn't have a natural, agreed-upon unit of measurement. Guidance on measuring performance notes that qualitative competencies like creativity are consistently among the hardest to score consistently across reviewers, precisely because there's no natural equivalent to a sales number or a delivery deadline. This doesn't mean innovation shouldn't be measured - it means it needs a more deliberate framework than most performance dimensions require.
Building Psychological Safety for Innovation to Show Up at All
None of the measurement frameworks in this article matter if employees don't feel safe proposing ideas in the first place. A workplace where a proposed idea that doesn't pan out is quietly held against someone teaches people to stay silent rather than risk it - which means the innovation measurement system will simply have nothing to measure, not because people lack ideas, but because they've learned it's safer not to share them.
Measurement and psychological safety aren't separate concerns; a measurement system that visibly, consistently rewards well-reasoned attempts (not just successes) is itself one of the strongest signals that proposing ideas is genuinely safe.
Separating Idea Generation From Idea Impact
The single most useful distinction in measuring innovation is between generating ideas and actually driving impact from them. Someone who proposes ten ideas a quarter, none of which go anywhere, isn't necessarily more innovative than someone who proposes two, one of which gets implemented and meaningfully improves a process.
Scoring purely on volume of ideas rewards noise; scoring purely on implemented ideas can unfairly penalise someone whose good idea got blocked by factors outside their control (budget, competing priorities, a decision made above their level). A fair system tracks both, explicitly, as separate signals rather than collapsing them into one "innovation score."
A Practical Framework
Rewarding Well-Reasoned Failure, Not Just Successful Ideas
A performance system that only rewards ideas that worked quietly teaches people to only propose safe ideas they're confident will succeed - which defeats much of the point of encouraging innovation in the first place.
It's worth explicitly recognising a well-reasoned idea that was tried in good faith and didn't work, distinguishing it clearly from an idea that failed due to careless execution or poor judgment. "Proposed and tested a reasonable hypothesis that didn't pan out, and documented what was learned" is a genuinely different, and often valuable, outcome from simply failing to deliver.
Innovation Doesn't Always Mean Big, Visible Ideas
Innovation measurement often skews toward large, dramatic initiatives - a new product line, a company-wide process overhaul - while missing the steady stream of small, practical improvements that quietly compound over time: a slightly better way to onboard a new client, a small automation that saves an hour a week.
Building space in the measurement framework for incremental innovation, not just big swings, avoids undervaluing the people whose consistent small improvements add up to more real impact than one splashy idea a year.
Setting Realistic Innovation Expectations by Role
Not every role has the same natural opportunity to innovate, and applying an identical innovation expectation across a whole company tends to unfairly disadvantage roles that are inherently more execution-focused.
A customer support agent handling a high volume of routine tickets has less natural room for process innovation than a product manager whose entire job is finding better solutions - and comparing the two on the same innovation scale, without adjusting for what's realistically available to each role, produces an unfair result.
Calibrating innovation expectations by role, while still leaving genuine room for a support agent's smaller-scale process improvement to count, is fairer than a single universal standard.
It's also worth recognising that some quarters simply offer more opportunity for innovation than others, depending on what the business is going through - a period of rapid, reactive firefighting genuinely leaves less room for exploratory thinking than a calmer, more strategic period. Scoring someone's innovation the same way regardless of the operating context they were working within isn't a fair comparison.
How Innovation Measurement Differs at Small vs Larger Companies
At a very small company, informal, constant innovation is often just how the business survives day to day - everyone is expected to solve problems creatively simply because there isn't a specialised function for everything yet.
Formal innovation measurement becomes more valuable as a company grows and roles become more specialised, because that's exactly when informal, everyone-innovates-constantly culture naturally starts to fade unless it's deliberately protected and recognised through the performance system.
Avoiding Innovation Theatre
A risk worth naming directly: once innovation becomes a formally measured thing, some employees will learn to perform it rather than genuinely practice it - pitching ideas mainly to have something to point to at review time, rather than because the idea is actually worth pursuing.
This is a predictable side effect of measuring almost anything, and the fix isn't to stop measuring innovation but to weight implemented impact more heavily than raw pitch volume in how the final assessment is framed, so that performing enthusiasm without follow-through doesn't score as well as fewer, better-executed ideas.
A related pattern worth watching for is the employee who repeatedly proposes the same idea in slightly different language each cycle without ever taking it further. Distinguishing a genuinely new idea from a recycled one that simply hasn't been pursued is worth doing explicitly when reviewing an innovation record, since the latter reflects more about follow-through than about creative volume.
Innovation Metrics That Can Mislead
Some seemingly objective innovation metrics can produce a misleading picture if used carelessly. Counting the number of ideas submitted to a suggestion box, for instance, rewards whoever submits the most regardless of quality or relevance, and can be gamed simply by submitting more.
Counting only ideas that were formally approved by leadership can undervalue genuinely good ideas that got blocked for reasons unrelated to their merit - budget cycles, competing priorities, a decision-maker who happened to be unavailable.
Being deliberate about which specific metrics feed into an innovation score, and being willing to add qualitative manager judgment alongside the numbers rather than relying on any single count in isolation, avoids optimising for the wrong thing.
Documenting Innovation Evidence Through the Cycle
Innovation is one of the easiest performance dimensions to forget by review time, precisely because it often shows up as a scattered handful of moments across many weeks rather than one obvious, memorable event.
A brief running note - a line added whenever an idea is proposed, tried, or lands - saves a manager from reconstructing an entire quarter's worth of contribution from memory during a rushed review-writing session, and produces a far more accurate, specific score than trying to recall it all at once. This is a small habit with an outsized payoff: five minutes spent logging a contribution in the moment it happens is far cheaper than an hour spent trying to remember it three months later.
Talking About a Low Innovation Score Without Discouraging Future Ideas
A low innovation score carries real risk of backfiring if it's delivered carelessly - an employee who hears "you're not innovative enough" as a flat verdict is likely to respond by proposing fewer ideas, not more, precisely the opposite of the intended effect.
It helps to separate the feedback into two distinct parts: an honest acknowledgment of where the gap actually is (fewer ideas proposed than peers, or ideas proposed but rarely carried through to implementation), and a genuinely specific, low-stakes opportunity to practice differently next cycle.
Framing this as a skill still being built, rather than a fixed trait someone either has or lacks, tends to produce a more constructive response than a blunt low score delivered without that context.
Where Talstack Fits
Talstack's Goals module can hold an explicit innovation-related goal - a target number of ideas tested, a specific process improvement to drive to implementation - alongside an employee's other performance goals, rather than leaving innovation as an unmeasured, informal expectation. Combined with 360 Feedback, peers and cross-functional colleagues can flag ideas and contributions a direct manager might not have full visibility into.
Quick Checklist: Measuring Innovation Fairly
- Track ideas proposed and ideas implemented as separate signals
- Measure the actual impact of implemented ideas, not just that they shipped
- Explicitly recognise well-reasoned attempts that didn't succeed
- Make space for incremental improvements, not just big, visible initiatives
- Gather peer input, since colleagues often see ideas a manager doesn't
- Avoid rewarding volume of ideas pitched over quality or follow-through
Copy-Paste Script: Recognising an Innovative Contribution
Hi [Name],I wanted to specifically call out [specific idea/improvement] - not just that you proposed it, but that you followed through and it actually [specific measurable impact].I want to make sure this kind of contribution is visible in how we think about your performance, not just the day-to-day targets. Are there other ideas you've been sitting on that we haven't talked through yet? I'd like to make space for those too.[Manager name]
Frequently Asked Questions
Why is innovation harder to measure than most performance dimensions?
There's no natural, agreed-upon unit of measurement the way there is for sales or delivery targets, which means it needs a more deliberate framework - typically separating idea generation from implementation and impact.
Should someone be scored highly just for proposing lots of ideas?
Not on its own - volume of ideas without follow-through or impact rewards noise. Tracking ideas proposed, ideas implemented, and measured impact as separate signals gives a fairer picture.
Should a failed idea count against someone in a performance review?
Not automatically - a well-reasoned idea tried in good faith that didn't work out, with lessons documented, is different from careless execution, and treating them the same discourages people from proposing anything risky at all.
How do you measure innovation for someone whose contributions are small and incremental?
Explicitly include space for incremental improvements in the measurement framework, not just large, visible initiatives - steady small improvements often add up to more real impact than one big idea a year.
Who should provide input on someone's innovation contributions?
Peers and cross-functional colleagues often see ideas and contributions a direct manager misses, so gathering their input alongside manager observation produces a fuller picture.
What's a good way to formally track innovation as a goal?
Setting an explicit innovation-related goal - a target number of ideas tested, or a specific improvement to drive to implementation - makes innovation a tracked part of performance rather than an unmeasured, informal expectation.
Should every role be held to the same innovation standard?
No - some roles naturally have more room for innovation than others, and calibrating expectations by role, while still leaving genuine space for smaller-scale improvement to count in execution-heavy roles, produces a fairer comparison.
.webp)
