Employee engagement scores go up when people feel heard. Hardly anyone disputes that. And yet most engagement programmes and most innovation programmes run on parallel tracks, each producing activity metrics, and neither changes much.
The organisations that solve both at once build one idea system, designed from the start so that employees take part in decisions that matter. The store colleague who suggested moving the returns desk sees it moved, and fills in next year’s survey differently.
What’s the connection between employee engagement and innovation?
The relationship runs in both directions. Engaged employees are more likely to contribute ideas, and engagement shows up in the numbers: in Gallup’s 2016 Q12 meta-analysis, business units in the top quartile for engagement were 17% more productive and 21% more profitable than those in the bottom quartile. Our reading is that engaged people notice problems and speak up about them sooner.
The causal arrow runs both ways
The relationship is not one-directional. When employees see their ideas taken seriously, reviewed transparently, and sometimes implemented, their engagement rises. Having your input change a decision is one of the strongest engagement drivers there is, and it costs little and tells the organisation something useful at the same time. In plain terms, the voice of the employee is the starting point for durable engagement, and an always-on voice programme is what turns that signal into repeated decisions. We unpack this listening-to-action dynamic in our guide to employee voice.
Why most organisations leave the loop open
The problem is that most organisations don’t build systems that close this loop. They collect ideas but don’t communicate what happened to them. They run engagement surveys but don’t demonstrate that the results changed anything. The opportunity is in the connection: a well-designed idea programme is simultaneously an engagement intervention.
Why do most engagement programmes fail to move the needle?
Because they treat engagement as a feeling to be managed rather than an outcome to be produced. The typical engagement intervention involves a survey, a town hall where leadership presents the results, some working groups, and a set of initiatives that may or may not get resourced and may or may not get followed up on. A year later, the survey happens again. Scores may have moved slightly. The cycle repeats.
The survey-and-town-hall failure mode
The fundamental problem is that these programmes don’t give employees a concrete experience of their input mattering. Being surveyed isn’t the same as being heard. Attending a town hall where leadership presents engagement data isn’t the same as watching your idea get implemented. Surveys produce aggregate numbers; what employees actually want is evidence that their specific input changed something specific.
Why experiences beat programmes
The most durable engagement improvements come from experiences, not programmes. When an employee submits an idea, sees it reviewed, gets a real answer explaining the decision, and occasionally watches it get built into how the team operates, that experience is more powerful than any engagement initiative. The experience is also memorable in a way that survey results aren’t: people remember the day their idea got approved.
What makes an idea programme feel genuine rather than performative?
Mostly speed of response, quality of feedback and visibility of outcomes.
Speed of response
Speed matters because the gap between submission and response is where trust either builds or erodes. If someone submits an idea and hears nothing for six weeks, by the time a response arrives they’ve already formed a conclusion about whether the programme is real. Committing to a 14-day response window and hitting it consistently is more valuable than a sophisticated evaluation framework that takes three months.
Quality of feedback
Quality of feedback matters because it communicates respect. A form response that says “thank you for your idea, we’ll take it under consideration” communicates nothing and builds nothing. A response that says “we reviewed this, here’s how it maps to our current priorities, and here’s why we’re not moving it forward right now” communicates that the idea was actually read and considered. Even a no is fine if it’s a real no with a real reason.
Visibility of outcomes
Visibility of outcomes matters because it answers the most important question employees have: did any of this actually do anything? Publicising implemented ideas, naming the people who submitted them (with permission), and connecting the implementation back to a business result closes the loop in a way that nothing else can replicate.
How does innovation engagement differ from general engagement initiatives?
General engagement initiatives tend to focus on working conditions, management quality, wellbeing, and organisational culture. These matter, but they’re largely about removing negatives: reducing friction, addressing frustrations, improving the environment.
Adding a positive vs removing a negative
Innovation engagement focuses on adding a positive: the experience of contributing meaningfully to how the organisation evolves. This is a different motivational lever. Some employees are primarily motivated by belonging and stability. Others are motivated by impact and contribution. For the second group, especially in organisations with knowledge workers and skilled frontline staff, an idea programme can produce engagement effects that no amount of wellbeing investment can replicate.
Visible to the whole organisation, not just the people affected
The two approaches also differ in who they’re visible to. A wellbeing programme is noticed by the people it affects directly. An idea programme, when it works well, is visible to the whole organisation every time an idea gets implemented and the story gets told. It creates a collective narrative about what kind of organisation this is.
What types of organisations benefit most from this approach?
The highest-impact cases tend to come from a few specific contexts:
- Manufacturing and industrial organisations where frontline workers have deep operational knowledge but few formal channels to surface it.
- Multi-site retail organisations where store-level insights rarely reach decision-makers at the centre.
- Professional services firms where billable work creates pressure that crowds out improvement thinking unless it’s given explicit structure.
- Public sector and regulated environments where employees often see service-quality issues their managers can’t see, and have legitimate ideas about how to fix them within the regulatory frame.
- Multi-country groups where the gap between where ideas live (locally) and where decisions get made (centrally) is the largest, and where the engagement payoff from connecting the two is correspondingly large.
The common pattern: knowledge gap between frontline and centre
What these contexts share is a wide gap between where the knowledge lives (frontline and operational) and where decisions get made (central and managerial). An idea programme bridges that gap, and the decisions improve because the people making them see information they did not have before.
What this looks like at scale: customer benchmarks
Three customer programmes on Hives show what an engagement-focused idea system produces in different sectors. Hives is idea management software for organisations from about 100 employees to multinational groups. Teams start with one challenge and grow the same setup to more sites, countries and business units.
Halfords (UK retail and automotive services, 400 stores)
Halfords runs a structured idea programme using Hives.co across 1,000+ engaged colleagues and 400 stores. Over six months, the programme collected 515 ideas and turned them into £759,000 in business value. Every colleague who submitted an idea got a response, even when it was “we are not taking this one forward, here is why”, and that is what kept participation up after the first week’s enthusiasm.
VINCI Energies (energy and digital solutions, global)
At VINCI Energies, a couple of thousand people across business units in several countries use Hives for idea challenges. Business units run their own challenges in their own language, while the Innovation Department sees what comes in across units and spots themes that turn up in more than one place. Every idea gets feedback, including the ones that stop, with the reason why.
Linköping Municipality (Swedish public sector, 160,000+ residents)
Linköping Municipality ran a structured employee idea programme that produced 200 ideas in three months and reduced administrative effort in the idea process by 66%. Engagement is harder to measure in a council than in a store chain, but the admin cut matters in its own right: staff who used to chase idea forms got that time back for the work they joined to do.
How do you avoid the programme feeling like another HR initiative?
By making it about real business problems rather than engagement metrics. When you launch an idea campaign, the question should be about a specific operational challenge, not an invitation to improve engagement scores. “What slows down the customer return process at your location?” is a real question with real business value. “Help us improve our culture” is an HR question that most employees will respond to with polite indifference.
Positioning matters
The strongest idea programmes are positioned as part of how the organisation makes decisions, not as an HR programme or an innovation initiative. When the CEO or COO introduces a campaign by saying “we’re facing this challenge and we need your input to make the right call,” the programme has a different weight than when the Innovation Manager launches it in the internal newsletter.
Specific operational questions, not engagement-tied vagueness
Operational questions tied to a specific outcome consistently outperform engagement-tied invitations on every metric: submission rate, idea quality, implementation rate, and (paradoxically) engagement-survey movement. The route to better engagement scores runs through better operational questions, not through more direct engagement framing.
The guide on getting executive buy-in covers how to frame the programme in terms that resonate with operational and financial leadership rather than HR and innovation language.
Common pitfalls and how to avoid them
Treating the programme as an engagement KPI lever
If the programme exists to move engagement scores rather than to produce operational outcomes, the workforce notices the inversion within one cycle. Engagement gains follow operational outcomes, not the other way around.
Closing the loop only on selected ideas
Every submission needs a response, including the declines. The single biggest predictor of repeat participation is whether the previous submission was acknowledged with a real reason. Selected ideas matter; declined ideas matter more for engagement because there are more of them.
Visible recognition for some, silence for others
Recognition mechanisms have to apply consistently. Naming the submitters of implemented ideas while leaving the submitters of declined ideas anonymous produces a two-tier feel that erodes trust. The cleanest pattern is to acknowledge every contributor by name (with permission) and to publicise outcomes both up and down.
Importing engagement-survey vocabulary into the idea programme
Words like “engagement”, “voice of the employee” and “culture” tend to read as HR vocabulary. The strongest idea programmes use the operational vocabulary of the business: customer, defect, cycle time, cost, safety. Importing engagement vocabulary signals that the programme is an HR exercise.
Running it without operational sponsorship
If the programme is owned by HR or by an innovation team without explicit line-of-business sponsorship, it tends to drift toward activity reporting and away from operational outcomes. The cleanest sponsorship is from a chief operating officer or equivalent role who has direct accountability for the operations the ideas will improve.
What does good look like at 12 months?
At 12 months, a well-run idea programme that’s also functioning as an engagement driver should show measurable progress on five fronts:
- Participation breadth: at least 40% of the eligible workforce has submitted at least one idea over the year (not per campaign, across the year).
- Implementation rate: at least 20% of reviewed ideas reach implementation.
- Engagement-survey movement: measurable improvement on the specific items about feeling heard and having input that matters.
- Stories worth telling: at least five concrete examples of ideas that changed how you operate, named submitters and named outcomes.
- Sustained cadence: the programme runs without active management interventions to keep it alive; it has become part of the operating model.
Why year one is the hardest
These are our working targets from programmes we have seen, not research benchmarks. The first year is usually the hardest because you’re building trust from whatever baseline you’re starting from. The second year benefits from demonstrated credibility. By the third year, the programme tends to run with much less active management because the culture has absorbed it.
Where to start if your organisation is starting from zero
The most common mistake is trying to build the whole system before running anything. The better approach is to run one focused, well-designed campaign, demonstrate that it works, and build the system around that proof point.
The first 90 days
- Pick a real business problem that leadership has appetite to act on.
- Design a campaign brief that’s specific enough to produce actionable ideas.
- Commit to reviewing every submission and responding within 14 days.
- Implement at least one idea inside the cycle.
- Tell the whole story publicly: what was asked, who submitted, what was implemented, what changed.
That first cycle is worth more than any platform, process, or policy document you could produce. It’s the evidence that makes the next cycle easier to fill, and the one after that easier still.
If you want a step-by-step framework for running that first campaign, the 10-day idea challenge guide is designed exactly for this situation. And if you want to understand the structural factors that make or break engagement in idea programmes over time, the innovation programme diagnostic gives you a clear-eyed view of where your current setup stands.
Frequently asked questions
How quickly can engagement scores move from a well-run idea programme?
Engagement-survey movement on the specific items about feeling heard usually shows in the second annual cycle, not the first. The first 12 months produce the experiences (submission, feedback, implementation) that the second-year survey reflects. Trying to push engagement scores faster than that usually produces gimmicky activity that does not stick.
Should the idea programme be owned by HR or by operations?
Operations, with HR as a partner. HR sponsorship signals to the workforce that the programme is an engagement exercise; operational sponsorship signals that it is part of how the organisation makes decisions. The engagement effect is larger when the programme is operationally owned, even though HR is often the team most interested in the engagement outcome.
What’s the right balance between recognition and operational outcome?
Operational outcome first, recognition second, in that order. Recognition without operational outcome is theatre, and the workforce notices. Operational outcome with consistent acknowledgement of the submitter (whether the idea was implemented or not) produces both engagement and trust at the same time.
How do we handle anonymous submissions in an engagement-focused programme?
Allow anonymity as an option, especially for sensitive topics (safety, ergonomics, leadership). Anonymous ideas still need responses; the platform should support routing the response back to the anonymous submitter without revealing identity. Mandatory identification reduces submission rates from the parts of the workforce that have the most to contribute on sensitive topics.
How do we make sure the programme doesn’t feel like surveillance?
Be explicit about what data is collected, what it is used for, and how long it is retained. In much of Europe, employee representatives have a legal right to be consulted on systems that can monitor performance or behaviour, and in Germany the works council co-decides under the Works Constitution Act. Engaging works councils early, and publishing the data policy openly, eliminates most of the surveillance concern.
Does this approach work in remote and hybrid teams?
Yes, with adaptation. Remote and hybrid teams have less of the informal hallway visibility that surfaces problems naturally, so the platform has to do more of the work. Submission has to work in the tools the team already uses, such as Microsoft Teams or a phone, evaluation has to be async to respect time-zone differences, and recognition has to be more explicit because there are fewer informal opportunities for it.
Can this work in a unionised environment?
Yes, and it usually works better. Worker representatives generally welcome a structured channel for input that complements rather than replaces formal consultation. The key is to be explicit about scope: the platform is for operational ideas, not for changes to terms of employment, which continue to follow the agreed processes.
Is there a minimum company size below which this doesn’t work?
There is no hard minimum. The test is whether an idea can still reach the person who decides in one conversation. While everyone shares a room and a manager, the engagement effect comes from manager behaviour, and a platform adds little. Once there are shifts, several sites or a head office that never sees the floor, ideas stop travelling by conversation, and a structured system starts to show in the engagement scores.
What if previous engagement or idea programmes have failed?
Acknowledge it explicitly in the relaunch. “We have run idea programmes here before that produced submissions and no follow-through. Here is what we are doing differently this time: a named decider, a 14-day response SLA, and visible quarterly outcomes tied to operational metrics.” Trust is rebuilt by being specific about what changed, not by hoping the previous attempt was forgotten.
Related guides and case studies
- 30 employee engagement ideas people actually notice
- Halfords: 515 employee ideas turned into £759,000 in value
- VINCI Energies: idea management at group scale
- Linköping Municipality: 200 ideas in three months
- Why employee ideas get ignored (and what to do about it)
- Your first idea challenge: from question to decision in 10 days
- How to get executive buy-in for an idea management programme
- How to get frontline workers to share ideas
- Is your innovation programme just innovation theatre? 7 warning signs
- Innovation programme diagnostic
- Employee voice programme guide