Global employee engagement fell to 20 percent, according to Gallup's State of the Global Workplace: 2026 report. Employee engagement is the emotional and cognitive commitment employees bring to their work, and in innovation, it directly determines whether good proposals move forward or stall. Four out of five employees worldwide are not engaged at work, a pattern that holds across regions and industries.Innovation leaders, managers, R&D leaders, strategy officers, and other organizational leaders at large and mid-sized enterprises feel this number directly. It shapes how many ideas from their people ever reach a decision, making engagement a practical innovation issue.
Most leaders misread the problem as a mindset gap that inspiration or a town hall can fix. The real cause often sits deeper in the system itself: processes are unclear, incentives are weak, and proposals have no route to action.
This article examines how employee engagement shapes innovation, why resistance persists, the benefits of getting engagement right, and four conditions that remove it: clear evaluation, trust, recognition, and change readiness. It also gives organizational leaders a way to diagnose engagement barriers and embed workforce input into a repeatable innovation process that improves outcomes, captures more ideas, and supports growth.

Exhibit 1: The four conditions that remove innovation resistance and the sixteen actions that build them.
The real barriers to employee-driven innovation
Leaders see silence in innovation campaigns and read it as negativity. That reading is skewed, and the importance of fixing these barriers is that innovation results depend on it. Most pushback is a rational response to how the organization has treated employees' ideas before, and when resistance spreads, it often includes actively disengaged workers who have stopped expecting follow-through.
An employee who submitted a proposal last year and never heard back has learned a lesson. Trying again is not worth the effort. Resistance here reflects a memory of a broken process.
McKinsey found that only 11 percent of companies with high-fear cultures are leading innovators, against 58 percent of companies with low-fear cultures. The same workforce produces different results depending on the conditions around it.
The pushback is symptomatic. It means the route from concept to action is slow, opaque, or unrewarded. Most companies respond with surface-level solutions: better communication, innovation campaigns, engagement strategies, and creativity workshops. Yet these fail to address the underlying issues.
These four structural barriers show up repeatedly.
No clear structure for evaluating ideas. Proposals vanish into a black box: no feedback, no visible decision, no path to implementation, no reason to submit again.
No trust. Without psychological safety, people hold back unfinished concepts. They fear that a wrong call will cost them.
No recognition. Effort and contribution go unrewarded, so innovation feels like unpaid extra work.
No change capability. Even strong proposals stall because the organization cannot absorb change. It lacks the ability to turn approval into action.
Left unaddressed, the barriers compound: a clear process without trust still stalls, since employees are unlikely to use it. Trust without recognition fades over time, and recognition without change capability starts to ring hollow. A culture that ignores proposals teaches silence fast in companies across every industry.
That's the cost of inaction. What follows is the case for getting it right, starting with what strong engagement actually delivers for innovation.

Exhibit 2: Four structural barriers stop employee ideas from becoming decisions: no clear process, no trust, no recognition, and no change capability.
What high employee engagement contributes to innovation
Engagement functions as a leading indicator of whether a company's culture actually supports innovation and strengthens business performance: it predicts whether proposals flow and where innovation comes from.
What follows covers what strong engagement actually delivers, why real engagement means ownership rather than buy-in, and how leaders can achieve repeatable results by turning it into a system rather than a one-off campaign.
What strong engagement delivers
Gallup found that 61 percent of engaged employees strongly agree they feed off the creativity of colleagues, against 9 percent of actively disengaged employees.
Disengaged employees keep their perspective to themselves, and the effect compounds: the most engaged teams see 81 percent less absenteeism, 14 percent higher productivity, and 23 percent higher profitability than the least engaged, plus 10 percent higher customer loyalty.
Employee engagement drives better customer loyalty and satisfaction, since the same energy that pushes proposals forward also carries into how employees treat the people the business serves.
Few companies pull this off. McKinsey's State of Organizations 2026 found that 75 percent fail to build high-performance cultures, with disengaged employees and weak incentives ranking among the top barriers cited by 10,000 senior executives.
The stakes scale up from there. Gallup estimates that low engagement costs the world economy 10 trillion dollars a year, near 9 percent of global GDP. Companies that treat engagement as infrastructure connect employee proposals to business performance, converting them into results that compound year after year while freeing up the capacity that lower absenteeism creates for testing new value-generating concepts instead of backfilling roles.
That freed-up capacity is the innovation pipeline. Engaged people spot problems early, bring grounded suggestions and insights, and support change instead of blocking it, which is why academic research on innovative work behavior consistently links engagement to employees speaking up and turning insight into practical improvement.
This is how creativity becomes output in the best companies: employees treat innovation as part of the job because the culture and the system reward it. But rewarding effort isn't the same as building ownership of it, and that distinction is where most engagement efforts quietly stall.

Exhibit 3: Engagement frees capacity, freed capacity surfaces ideas, and results reinforce engagement. Each turn of the loop makes the next one easier.
From buy-in to ownership
Most companies define engagement as satisfaction or buy-in: people are content, and they support the plan. For innovation, that bar is too low. Buy-in is passive, meaning employees won't block an initiative. Ownership is active: employees treat a problem as theirs to solve, collaborate to solve it with others, and push proposals without being asked.
This shows up starkly in Gallup's own data: just 28 percent of employees strongly agree their opinions count at work. Most organizations haven't cleared the ownership bar on this most basic measure, let alone acted on what they heard.
Creating ownership means giving employees a real stake in shaping decisions. Ask which challenges matter before launching a campaign. That mindset needs a system to keep it alive beyond a single campaign.
Turning engagement into a repeatable innovation strategy
One hackathon produces a spike. Momentum fades within weeks when involvement depends on a single event. Creating a repeatable strategy means embedding employee participation into routines instead: standing challenges, a focused evaluation path, and visible outcomes that turn engagement into a habit while helping the organization prepare for the future.
A standing challenge stays open year-round and ties to specific business problems rather than a generic call for input, paired with a regular review cadence so proposals don't wait for the next big event to surface them and leaders can plan for upcoming business problems instead of only reacting to current ones.
Someone needs to own the pipeline too, tracking proposals so leaders can generate insights, assess progress, and see whether the process is helping achieve results, with the same discipline applied to any other business process.
Low participation usually signals a diagnosis problem. Knowing exactly why people stay quiet matters more than assuming they lack what it takes to contribute.
The Gallup Q12 pyramid: a framework for diagnosing engagement
Gallup's Q12 survey is the standard tool for measuring where engagement stands, built around 12 elements grouped into four levels, each resting on the one below it.
The base covers whether employees have the clarity and access to the information, tools, and resources needed to contribute and do the job. The next level asks whether they get to contribute individually, use their strengths, and feel backed by their manager.
Above that sits teamwork and belonging: whether people feel part of something and connected to colleagues. The top level is growth: whether employees see a path to develop. Companies that invest in employee growth consistently see higher engagement in return.
Innovation directors do not need a full Q12 rollout to spot which level is weak. A few pointed questions at each level, asked in a workshop or a handful of one-to-ones, usually surface it fast.
A pattern of "no" at one level, more than scattered complaints across all four, is usually the clearest signal of where to start. Diagnosing first means leaders invest in the right condition. Questions like these are examples leaders can use to diagnose engagement barriers.
Clarity and resources
-
Do employees know that submitting an idea is actually part of their job, or is "innovation" something extra nobody has time for?
-
Do they know where to take an idea and what happens to it once they do?
Individual contribution and management support
-
Would someone bring a half-formed idea to their manager before it's polished, or do they sit on it until it's safe?
-
Do employees believe a wrong call on a proposal won't be held against them personally?
Teamwork and belonging
-
When an idea succeeds, is credit shared across the team, or does it collapse to whoever presented last?
-
Do colleagues acknowledge each other's contributions, even for ideas that didn't make it through?
Growth
-
Does contributing ideas show up anywhere in a performance review or career conversation?
-
Can employees point to a case where submitting an idea led somewhere: a new skill, a new project, a promotion?
This diagnostic shows exactly which barrier is weakest. The conditions that follow show how to remove it.

Exhibit 4: Two diagnostic questions per Q12 level. A pattern of no at one level shows leaders where to start, since each level rests on the one below.
Conditions to overcome innovation resistance
Barriers require the right conditions to be in place. Conditions are the structural prerequisites for tackling innovation resistance and driving real engagement. They're something leaders can control directly in the business environment: a process, a cultural norm, a funding rule.
The diagnostic points to a specific barrier, and each barrier has a matching condition built to remove it, in the same order as the Q12 pyramid:

Exhibit 5: Each weak Q12 level points to one barrier, and each barrier has one matching condition. Diagnose the level, then build the condition it names.
Creating each one is the leaders' job, and companies that get this right compound their advantage over time.
Condition 1: design a clear innovation process for idea evaluation
The black box is the fastest way to kill morale. When proposals disappear without a decision, employees stop submitting. Creating a clear route from idea to decision is the fix.
A clear process defines what happens after a submission arrives. Who reviews it. Against what criteria. By when.
State the evaluation criteria upfront: strategic fit, feasibility, resource need, and potential impact. Leading companies across industries treat this as infrastructure.
A structured approach like this, moving concepts through defined phases with a quality gate and expert or peer review at each one, keeps the pipeline moving across markets, technologies, and business models instead of stalling.
Close the loop on every proposal. Companies that publish criteria get more submissions. Even a rejection with a clear reason keeps employees willing to submit again and explore the next one. Done well, that same discipline is what eventually turns submissions into new products and services instead of stalled pilots.
Recommended actions
-
Run challenge-based campaigns. Tie each one to a specific business problem instead of a generic call for input, and publish the evaluation criteria and decision timeline before it opens.
-
Send group-specific invitations. Invite the group closest to the problem rather than broadcasting to everyone. Targeted invitations produce fewer proposals and more usable ones.
-
Close the loop on every submission. Give each one a status, such as in review, approved, or paused, with a reason and clear communication. A workflow that moves proposals through defined stages and quality gates makes this easier to sustain once volume grows.
-
Offer multiple ways to contribute through easy-to-access software. Let people submit, comment, or explore and build on someone else's concept in minutes. Route proposals to real decision-makers with the resources to act, and score submissions against the same criteria so decisions stay consistent.

Exhibit 6: A challenge-based campaign in ITONICS. Every idea sits in a named phase, and each phase states who reviews it and what happens next.
Condition 2: build a culture of trust and innovative thinking
Trust is the precondition for every other step. Employees share raw, unfinished ideas only when a wrong call will not be held against them. Creating that safety is the first move in any innovation program.
The data is stark. McKinsey found employees at top innovators are 11 times more likely to say their organization incentivizes risk-taking. They're 5 times more likely to report encouragement of experimentation. Fear kills creativity, and people innovate only when it's safe to fail. The environment sets the ceiling on innovative thinking and creativity.
Managers set that environment. Gallup research shows managers account for 70 percent of the variance in team engagement, yet fewer than half receive formal training. Manager development is where a culture of trust is created or lost through daily practices.
Reward both the attempt and the win. Amazon's Correction of Error memos are among the clearest examples of this in practice: they capture lessons and help teams learn from failure instead of punishing it. That signals the company values learning and experimentation. Trust builds the confidence and the ability to speak up.
Recommended actions
-
Model open feedback behavior. Train managers to respond to every proposal within a set window, including ones you will not use, giving the person who submitted it clear communication about the outcome.
-
Hold transparent talks. Explain the strategy, the constraints, and why some proposals get declined. Employees who understand the reasoning submit better ideas next time.
-
Share internal stories, including the failures. Circulate one failed experiment each quarter and the knowledge it produced, alongside the wins, so people see that both outcomes are survivable.
-
Involve employees early. Ask which challenges matter before a campaign opens, and allow drafts, comments, and iteration in one shared space, so concepts get refined in the open instead of arriving fully formed or not at all.

Exhibit 7: A comment thread on every submission in the ITONICS software. Reviewers leave a reason in the open, and @mentions pull in the decider.
Condition 3: recognize and reward innovative behavior
Innovation that goes unrecognized becomes unpaid extra work. Employees notice quickly when effort earns nothing, and their motivation drops. Creating a habit of recognition costs little and returns much. Recognition drives high performance and fuels the next round of innovation.
Recognize contribution as well as winning concepts. Submitting a proposal, improving someone else's, and driving one to execution all deserve acknowledgment. Gallup ties strong recognition practices to higher profitability, so this is a performance decision. Recognition sustains innovation, and recognized people innovate again.
Good recognition programs mix the range. Cash and seed funding are obvious examples, rewarding the biggest wins, while a temporary rotation onto the project keeps the person who proposed it close to building it. Lower-cost mechanisms, like peer voting or a token-based "People's Choice" award, broaden participation and surface contributions leadership might otherwise miss.
Companies that build recognition into their culture keep employees submitting. Tie recognition to performance reviews and career development so it counts as professional growth, and helps good proposals succeed.
Recommended actions
-
Build a tiered recognition system. Cover submit, contribute, and execute as separate levels, and keep every idea linked to its contributors so credit stays clear at each stage.
-
Make it part of performance reviews. Add idea contribution to review and development criteria, using visible progress tracking to show contributors their proposals moving forward.
-
Recognize all contributors alongside the winners. Monthly shout-outs reach the people who improved someone else's proposal, and they cost nothing.
-
Gamify idea campaigns. Peer voting and token-based awards surface who's contributing beyond the loudest voices in the room. Recognize teams as well as individuals to break silos and strengthen relationships.

Exhibit 8: Tiered recognition in ITONICS. Activity points and badges credit contribution beyond the winning ideas, so effort shows up at every level.
Condition 4: build change capability and readiness
Strong proposals stall when the organization cannot absorb change. Creating change capability is the last barrier to clear, and it depends on a culture willing to fund experiments before they're proven. As volume rises, the constraint shifts from concept creation to value creation that delivers lasting impact.
Change readiness is skills, support, and safe-to-fail funding. Many strong concepts never surface because employees lack the confidence or ability to develop and pitch them.
Short, focused training in problem framing, business case building, new technologies, and experimentation builds the skills employees are missing. This is practical education. Change capability is essential once volume rises.
Metered funding gives people the ability to keep early experiments moving. Creating a small fund with limited scope, budget, and timeframe, aimed at learning rather than guaranteed success, lowers the risk of trying. Small experiments help teams act, learn, and turn promising concepts into durable outcomes without waiting for full approval.
Change ambassadors spread these practices. One per department, meeting quarterly, keeps knowledge and momentum flowing across the business.
Recommended actions
-
Offer skill training. Run short, focused sessions on the skills employees are missing: problem framing, business case building, and experimentation, tied to live business problems rather than taught in the abstract.
-
Implement innovation in team reviews. Make contribution a standing agenda item so the work counts as part of the job instead of an extra.
-
Build change networks. Assign one change ambassador per department and convene them quarterly to share best practices, using a shared roadmap so everyone can see where each initiative sits, categorized by market, technology, and business model.
-
Create safe-to-fail funds. Cap the scope, budget, and timeframe, give people the resources they need to experiment, and track each one from concept through to implementation.
/Still%20images/Kanban%20Board%20Mockups%202025/capabilities-views-kpi-aggregation.webp?width=1440&height=900&name=capabilities-views-kpi-aggregation.webp)
Exhibit 9: Ideas move through qualification rounds in ITONICS, grouped by strategic goal. Each round is a decision point for releasing the next tranche.
From resistance to results: how ITONICS helps
Innovation resistance comes from what happens to ideas after they are submitted. For most organizations, the honest answer was nothing. That's what this framework is built to change.
Structure makes contributing worthwhile. Trust makes it safe. Recognition makes it pay. Change capability makes it stick. Build them in that order, because a team that can't trust the process won't risk using it, and a team that isn't recognized won't keep using it once the novelty wears off.
Each condition needs something concrete to run on. A clear process needs a workflow that moves proposals through defined stages instead of a shared inbox. Trust needs a space where managers can respond to every submission and employees can see that response. Recognition needs contributors linked to their ideas so credit doesn't disappear at handoff. Change capability needs a roadmap showing where each initiative sits, from concept to implementation.
The ITONICS Innovation OS provides that infrastructure. Cisco ran exactly this playbook on it at scale: 36,600 employees, 49 percent of the workforce across 89 countries, submitted 769 ventures to its Innovate Everywhere Challenge. Four conditions created that result. The tool kept them from quietly falling apart once the organization got too big to run on memory alone.
Get the conditions right, and disengaged silence stops being the default. Proposals start moving instead, and the pipeline fills one at a time.
FAQs on employee engagement
How long before an employee innovation program shows results?
Plan for one full cycle of the innovation program, roughly three to eight months, depending on how many evaluation phases it includes. The first cycle produces early wins and the process knowledge needed to refine the innovation strategy going forward.
Later cycles compound as employees see their proposals move into development, which is why engagement functions as a performance strategy for organizations rather than a one-off initiative. Cisco's own Innovate Everywhere Challenge moved concepts through four phases over roughly eight months before its winning teams moved into execution, a useful benchmark for any organization sizing up its first cycle.
What is the single biggest reason employees stop submitting ideas?
The biggest reason is a lack of visibility after submission, often called a "black box": when nothing visibly happens after someone submits an idea, they stop trying. Giving every idea a status and a reason within a set window fixes this, since even a clear rejection keeps participation alive better than silence does.
This is a system problem: an employee who submitted a proposal once and never heard back learns that trying again isn't worth the effort, and that lesson spreads quickly once colleagues notice the same pattern repeating.
How do we validate new ideas before investing further in them?
Customer feedback is essential for validating new ideas before committing budget to them, since it reveals whether a concept has the ability to solve a real problem rather than one that just looks clever internally. Creating evaluation criteria that include customer input, alongside strategic fit and feasibility, keeps proposals grounded in real demand rather than internal opinion.
This works best with an engaged workforce: employee engagement is linked to innovation and proactive problem-solving, so ideas surfaced by an engaged team tend to hold up better once tested against real customer need. Treating validation as a standing step keeps this discipline consistent as proposal volume grows.
How do we recognize employee contributions without a large budget?
Use non-cash recognition tied to a tiered system that separates submitting, improving others' proposals, and driving execution into distinct levels. Monthly spotlights, team-based awards, and a line in performance reviews cost little and signal that contribution counts.
Recognition matters because effort that goes unnoticed starts to feel like unpaid extra work, and motivation drops accordingly. Tying recognition to performance reviews and career development helps it register as professional growth rather than a side gesture, and recognizing teams alongside individuals breaks down silos instead of pitting colleagues against each other for credit.
How do we make it safe to fail without wasting money?
Use metered funding: a capped fund with a fixed scope, budget, and timeframe reserved for early innovation experiments, aimed at learning rather than guaranteed success. Small stakes lower the risk of trying and produce more experimentation per dollar spent.
This works because most strong concepts never surface in the first place, since employees lack the confidence or resources to develop and pitch them without some kind of backing. A capped fund removes that barrier without exposing the organization to full-scale risk, letting teams act, learn, and turn promising concepts into durable outcomes without waiting for full budget approval.
Do we need software to run an employee innovation program?
A clear process and a shared decision path can run without software at first.
Software earns its place once volume, evaluation, and cross-team visibility outgrow spreadsheets and inboxes, centralizing idea capture, evaluation, and tracking so no proposal slips through. Cisco ran its own program on a platform for exactly this reason, once participation reached hundreds of proposals and outgrew a shared inbox.