Most innovation metrics are vanity metrics. "Total ideas submitted" sounds impressive until leadership asks how many got implemented. "Participation rate" sounds great until someone points out you invited 2,000 people and got 40 submissions. "Number of campaigns run" measures activity, not outcome.
This guide shows how to measure what matters and build a reporting routine that shows real progress.
Why do most innovation programmes measure the wrong things?
You launch the programme, recruit champions, run a couple of campaigns. Then leadership asks "what is the ROI on this?" and you have nothing meaningful to answer with. Hundreds of ideas, dozens of campaign emails, lots of activity, no defensible number.
Most teams count submissions but ignore implementation, track participation but never tie it to outcomes, and cite a rough ROI built on guesses. The point is not a perfect ROI — it is to know which signals predict the programme will keep generating value, and which are noise. You do not need a data scientist. You need to know which seven indicators to track and how to read them.
Which seven metrics actually count?
The table below summarises the seven metrics that matter and the healthy benchmark for each.
| Metric | What it measures | Healthy benchmark | Failure signal |
|---|---|---|---|
| Implementation rate | % of submitted ideas that actually get implemented | 5–15% open campaigns; 20–30% scoped challenges | <5%: ideas not landing or process broken |
| Time to decision | Median days from submission to advance / park / reject | Under 3 weeks; first response under 5 days | >90 days: erodes credibility fast |
| Participation rate | Submissions ÷ invitations | 10–15% broad campaigns; 30%+ targeted | Dropping over time: feedback loop broken |
| Ideas per active participant | Total ideas ÷ unique submitters | 2–3 ideas/year for engaged contributors | One-and-done participation |
| Repeat participation | % of campaign-1 submitters returning for campaign 2 | 25–35% (the trust metric) | Below 20%: feedback loop broken |
| Value generated | Documented £/€/$ from implemented ideas | 5–10x platform cost in year 1 | No documented value |
| Feedback responsiveness | Median days to first acknowledgement | 1 week excellent; 2 weeks acceptable | >2 weeks: trust erodes |
1. Implementation rate. The single most important metric. Of the ideas submitted, how many actually got implemented? Not discussed. Not added to a list. Implemented — a concrete next step assigned, a budget approved, a test run, or a change made. A healthy rate sits between 5–15% for broad open submission; 20–30% for tightly-scoped challenges. If yours is higher, either the challenge was very specific or you are defining "implementation" generously. If lower, your process breaks between evaluation and rollout.
2. Time from submission to decision. How long before a submitter finds out what happened to their idea? Not until implementation — until a real decision (advance, park, reject) and feedback. Anything over 90 days erodes credibility faster than no programme at all.
3. Participation rate. Submissions divided by invitations. A 30% rate on a targeted 50-person campaign and 8% on an open 500-person campaign can both be healthy. Compare campaigns of similar scope. If participation is dropping, check whether the feedback loop is closing.
4. Ideas per active participant. Total ideas divided by unique submitters. Depth of engagement, not just breadth. Engaged employees submit 2–3 ideas a year. If submitters drop in one idea at launch and disappear, the programme is not viable.
5. Repeat participation. What share of people who submitted to one campaign also submit to the next? This is the trust metric. If it is low, the feedback loop is probably broken. Aim for 25 to 35 percent.
6. Value generated. Harder than activity metrics, often approximate, but worth trying. For implemented ideas with clear outcomes (cost savings, time saved, errors reduced, revenue uplift), document the before-and-after. A rough small / medium / large bucket per implemented idea beats activity metrics by a mile. Easiest to value: cost-saving ideas in manufacturing, process automations, error-reduction with measurable defect rates. Hardest: cultural improvements, brand initiatives, anything with a long tail.
7. Feedback responsiveness. How long does a submitter wait for any response, even just acknowledgement? One week is excellent. Two weeks is acceptable. Beyond that, trust erodes regardless of the eventual answer. A "no, and here is why" in five days builds more trust than a "yes" in two months.
Which metrics feel good but tell you nothing?
Total ideas submitted without an implementation rate — rewards noise. Number of campaigns run — frequency is a tactic, not a goal. Employee satisfaction surveys right after a campaign — people feel good immediately; the meaningful score is six weeks after results are announced. Composite "innovation index" scores blended from arbitrary weightings — they obscure where movement is actually happening.
How do you measure employee engagement in an idea programme?
Combine three data sources:
Behavioural data. Login frequency, ideas submitted, comments and votes. Signals someone is engaging, not ticking a box.
Sentiment data. Ask directly. "Do you feel heard?" "Do you believe your organisation acts on suggestions?" Someone can submit several ideas while not believing they will ever be implemented — that group does not stay involved.
Retention data. Are the same people back year-over-year? Have you brought new teams in? A successful programme broadens, not just an initial launch peak.
Pull all three into one dashboard: participation, ideas per active participant, average decision time, value generated. If you cannot see those four on one screen, you cannot diagnose a problem in real time.
How do you calculate ROI for an innovation programme honestly?
The formula is simple:
ROI = (Value generated − Programme cost) ÷ Programme cost × 100
The honesty comes from how you fill in each side. A realistic worked example for a 1,000-employee organisation running a 12-month programme:
- Programme cost: €18,000 platform + €25,000 fully-loaded internal time (programme owner at 30% of a role, plus reviewer time). Total: €43,000.
- Ideas collected: 240 — implementation rate 12% — 29 ideas implemented.
- Value mix: 18 small (€2,000), 9 medium (€10,000), 2 large (€40,000) → €36,000 + €90,000 + €80,000 = €206,000.
ROI = (€206,000 − €43,000) ÷ €43,000 × 100 = 379 percent
That is a defensible number. Three things about how it was built:
First, only implemented ideas counted toward value. Submissions and ideas under review do not produce ROI until they are live. Second, programme cost includes internal time. If a manager spends five hours a week reviewing ideas, that time has a cost — leaving it out inflates the number and gets you caught the first time finance audits it. Third, the value categories are conservative. Resist the temptation to put every implemented idea in the "large" bucket. Credibility depends on how the small bucket is treated.
What should you measure, and when?
The cadence below is the minimum. For larger programmes with continuous intake, add a monthly snapshot comparing this month to the trailing three.
| When | What to measure | Why |
|---|---|---|
| During each campaign | Submission count, participation rate, qualitative notes on emerging themes | Spot momentum problems early |
| At campaign end | Time to result announcement, ideas advancing / rejected / parked | Hold the close-the-loop SLA visible |
| 30 days after | Implementation progress on advancing ideas, first value signals | Catch ideas stalling between evaluation and rollout |
| 90 days after | Implementation rate, rough value estimates, repeat participation | Validate which ideas got implemented vs stalled |
| Annually | Trend lines, total value, participation trends, honest assessment of gaps | Decision basis for next year's investment |
How do you present results to leadership?
Leadership cares about three things: economic impact, employee engagement, and whether the programme is sustainable.
Lead with a story, not a number. "An employee in our distribution centre suggested moving the picking station two metres closer to the conveyor. We tested it for a week. It cut average pick-to-pack time by 18 seconds. Across 4,000 picks a day, that is 20 hours of saved labour. Annualised, around €230,000. We have 28 ideas like that this year." That lands harder than "ROI is 379%."
Use simple visuals. A line chart of ideas submitted, implemented and value generated over 12 months tells the story in five seconds. Avoid composite "innovation index" charts. The one-page innovation report has the canonical layout.
Compare to the alternative. "External consulting on the same questions would have cost us €120,000. We did this for €43,000 by listening to our own people."
Show engagement next to value. Repeat-participation rate sits naturally next to ROI. Engagement reduces attrition and recruitment cost — a second-order ROI on the same programme.
Be honest about gaps. If implementation rate is 8% and your target is 12%, say so, then show the two changes you are making to close it. Leaders respect a clean diagnosis more than an inflated headline.
How do you stay honest about what you do not know?
Two failure modes. First: claiming impact you cannot prove. If an idea was implemented but you do not know what it saved, do not invent a number — say "implemented and live, impact captured next quarter." Second: burying implementation rate in activity metrics. If you ran four campaigns, generated 300 ideas, and implemented two, say so. Use the 20-question diagnostic to find where ideas are stuck.
How do you turn metrics into improvements?
Measuring is half. The other half is acting on the data. If turnaround is too long, change the evaluation process. If participation is dropping, check the feedback loop. If implementation rate is low, the ideas are either too vague at submission (use the submission template) or rollout is blocked. The 2-hour triage method is the operational backbone. A good measurement process does not create metrics for reports — it creates feedback loops that make the programme better.
FAQ
How often should we measure?
At minimum after each campaign. Larger programmes with continuous intake can take monthly snapshots. Trend reports quarterly, full reviews annually.
Should we share metrics with employees?
Yes, but honestly. "Our implementation rate is 7%, our target is 10%, here is what we are changing" builds far more trust than a selective report.
What is a good benchmark for our metrics?
Industry benchmarks are hard to compare because programme structure varies so much. Better: your own historical trends — improvement quarter over quarter means your changes are working. The idea scoring scorecard covers consistent evaluation criteria you can reuse as a comparison point.
Should we measure ROI on every implemented idea?
No. That creates more administrative load than the data is worth. Bucket the value (small / medium / large) at implementation, then deep-dive only on the top quartile to validate the bucketing.
How do I value an idea with no obvious financial impact?
Two options. Either categorise it as "engagement / culture" and report it separately rather than mixing it into the financial ROI, or estimate the cost of the problem it solved (avoided risk, complaint volume, retention). Be explicit about which method you used so leadership can read the number correctly.
.webp)
.jpeg)
