Employee Engagement and Continuous Improvement: What I Learned About Turning Ideas Into Results

You can collect hundreds of ideas and still have a disengaged workforce. Submitting an idea is participation. Engagement is what happens when people believe that their participation matters — and that depends almost entirely on what your organization does after someone speaks up.

Over the years, I've had the pleasure of working with a lot of organizations trying to improve how work gets done, and one thing shows up almost everywhere: the people closest to the work already know where a surprising amount of the friction is. They know which processes take too long. They know where the workarounds live. They hear from customers what's frustrating. They know what gets duplicated, delayed, or quietly ignored. And usually they have a pretty good sense of what would make things better.

The interesting part is that organizations often spend enormous amounts of time trying to diagnose problems that employees run into every day. That's the opportunity I want to talk about. Continuous improvement gives us a way to tap into that knowledge. But whether employees choose to share what they know depends on something else entirely: do they believe participating is worth it?

That's where employee engagement and continuous improvement meet. The challenge is rarely whether employees have ideas. The challenge is whether the organization has created a way to hear them, develop them, act on them, and show people that their contributions mattered.

Getting ideas and creating improvement are two different things

Before I joined HYPE Innovation, I helped build an innovation program inside a healthcare organization. Like a lot of organizations I've met since, we started with what seemed logical. We gave people somewhere to submit ideas. We had suggestion mechanisms, we ran workshops, we experimented with various tools to help us collect ideas. And we absolutely got ideas.

But getting ideas and creating improvement turned out to be two very different things. Some of the ideas weren't connected to an important business problem. Some didn't have an obvious owner. Some were really difficult to evaluate, so they sat for far too long. And employees often didn't know what happened to their ideas once they'd contributed. We were creating a lot of activity, but we hadn't built a system that consistently turned that activity into value.

That experience taught me a distinction I still use today:

Submitting an idea is participation. Engagement is what happens when people believe that their participation matters.

You can collect hundreds of ideas, like I did, and still have a disengaged workforce.

The three questions every employee is quietly asking

Every time we ask an employee to contribute, they're quietly weighing three questions:

• Why are you asking me?
• What will happen with what I give you?
• And will anything actually change?

Those three questions sit right at the intersection of employee engagement and continuous improvement. And the answers can't live in a launch email — they have to be visible in the way the program actually works.

Start with a problem people recognize — not "give us your ideas"

So if participation matters, the next question is: what are we actually asking people to participate in? One of the biggest changes we made in the healthcare program was moving away from the broad request — "give us your ideas." When you ask a very broad question like that, you get a very broad collection of responses.

Instead, we started working with leaders to identify problems that genuinely mattered: operations, patient experience, quality, cost, strategic priorities — the things leaders actually wanted help solving. Then we invited employees into those problems. That really changed the quality of the participation we were getting.

There's a big difference between asking "how can we improve the organization?" and asking:

• Where are we losing unnecessary time?
• Where are we doing work twice?
• What causes delays for the customer?
• What should we stop doing because it no longer adds value?
• What does your team do really well that other teams should copy?

Those are questions people can answer from experience. They don't require someone to think of themselves as an innovator — they just require someone to notice. We often tell employees we need them to "innovate," which can sound big and abstract, like something that belongs to R&D or strategy or some specialist team somewhere. But almost anyone can answer "what gets in the way of doing your job well?" or "if you could change one thing about this process, what would it be?"

That's continuous improvement, and it's one of the most accessible forms of employee engagement. People don't always need an invitation to innovate. They need an invitation to solve something that matters.

The real test comes after people respond

But asking the right question is only half the job. The real test comes after people respond — and that's where a lot of programs start to break down. We're generally pretty good at the front end. We can launch a campaign, run a workshop, send an email, build a portal, ask people to participate. But then what?

Who reviews the ideas we're getting? What makes something worth pursuing? Who makes that decision? Who owns the next steps, and how long should someone expect to wait? What happens to the ideas that aren't selected, and how will the contributor know what's happening?

Those can all sound like governance questions, but they're really engagement questions — because the process teaches your employees whether their contributions are worth their time.

This is exactly what a business performance system is meant to hold together. When Klauke replaced a system that made ideas hard to track, idea processing time fell from 30 to 15 days, with €120,000 saved in a year — results from their program, not a promise for yours.

A visible no is better than an invisible maybe

Most employees understand that every idea can't be implemented. They don't expect the answer to always be yes. What they find much harder is silence. Silence is hard to accept. If someone takes the time to contribute and nothing ever comes back, they learn something from that — they learn that their participation may not be worth the effort. And when that happens repeatedly, engagement starts to drop.

So one principle matters enormously:

A visible no is often better than an invisible maybe. Tell people what happened. Tell them why. Tell them what's going to come next.

Transparency doesn't require every decision to be popular — it requires the process to be understandable.

Spotting the problem isn't the same as owning the solution

There's another barrier we learned to remove: the assumption that the person who sees the problem has to own the solution. I know that probably sounds obvious, but it removes an enormous barrier — because think about what might go through an employee's mind. If I raise this issue, am I volunteering? If I submit this idea, am I now responsible for the project? Do I have to write the business case or find the funding? Am I going to have to convince three different departments to change the way they do things? If speaking up creates a new unpaid job, people will stop speaking up.

What helped us was connecting promising ideas with people who already had improvement skills and the capacity — in our case, that sometimes meant using our Lean Six Sigma resources or our Green Belts, who could pick up promising ideas that didn't have an obvious owner. I still think about the orphaned ideas: there was a real problem, the opportunity was valuable, but the person who identified it wasn't necessarily in a position to carry it through the organization.

That led to an important shift:

The employee's role may be to spot the opportunity, while the organization's role is to create the capability around it.

And that's a very different employee experience.

This is where champions, advocates and improvement leads matter — because a central innovation team or a centralized continuous improvement team can't be everywhere. They don't see every process. They don't understand every local constraint. They don't have a relationship with every employee. So mature programs build capability closer to the work. The name varies — sometimes it's champions, sometimes advocates, sometimes ambassadors or improvement leads — but the title matters a lot less than the behavior. These are the people who can help someone frame a problem, connect them to expertise, point them toward the right process, help them find an owner, or simply say, "you should share that." It sounds small, but it begins to distribute improvement capability across the organization. Then continuous improvement stops being something a central team owns, and becomes something the organization knows how to do.

This is how participation scales. When Bombardier built its program around real business challenges and made contributing easy, it grew from 2,000 to 5,000 participants in seven months as the approach spread. You can find more of these in our case studies.

Nothing builds engagement like evidence that engagement matters

Ultimately, employees are watching for one thing: did anything actually change? That might be the most important question of all.

Nothing builds engagement like evidence that engagement matters.

Imagine two organizations. In the first, an employee suggests an improvement, it goes into a system, and six months later nobody remembers what happened. In the second, someone identifies a problem, a small group takes a look at it, they test a change, they implement it, they measure it — and then the organization tells the story. Now there are three other teams using the same approach. Which organization do you think is more likely to get participation the next time it asks?

Stories make value visible, and they create a powerful loop. Insights lead to action. Action produces a result. The result becomes a story. And the story creates more participation. That's where employee engagement and continuous improvement start reinforcing one another.

And the value is broader than just the savings. Of course continuous improvement should generate business value — cost reduction, productivity, shorter cycle times, better quality, safety, customer experience. But in the meantime, your employees are also building a capability. They're developing problem-solving skills. They're learning how decisions get made. They're connecting with people outside their immediate teams. They're gaining visibility, developing confidence, and — most importantly — they begin to feel some ownership over improvement. Instead of change being something that happens to them, improvement becomes something they're participating in creating.

From a sentiment into a behavior

That leads to one last shift in the way we think about employee engagement. When organizations talk about engagement, the conversation often moves quickly to surveys. Do employees feel engaged? Do they feel connected? Would they recommend the company to someone else? Those measures have value. But there's another question worth asking: are we creating meaningful opportunities for employees to shape the organization they work in?

For context, Gallup's State of the Global Workplace research consistently finds that only a minority of employees feel truly engaged at work — a reminder that measuring sentiment isn't the same as giving people a role in change.

Because there's a difference between asking people how engaged they feel and giving them a meaningful role in making something better. Continuous improvement gives us a practical way to do the second. It turns engagement from a sentiment into a behavior: notice, contribute, collaborate, test, improve, share what worked — then do it again.

What this means in practice

So what does this mean in practice?

• Give people meaningful problems. Don't just ask for ideas. Help employees understand what matters and why their knowledge is useful.
• Make the process visible. Show people what happens after they participate — who reviews something, how decisions are made, what comes next.
• Build support around the employee. Don't make one person carry an idea from observation all the way through to implementation. Use managers, advocates, improvement professionals, subject matter experts and cross-functional teams.
• Close the loop. Tell people what happened, even when the answer is no. Measure the result. Recognize the people who were involved. Share the story. Then invite people to help again.

The goal is an improvement capability

Because ultimately, the goal is not to build an idea program or to maximize the number of submissions. It's not simply to get more people to log into the platform.

The goal is to build an improvement capability — where people across the organization know how to notice problems, speak up, share what they know, work with others, turn promising ideas into action, and see the results of that effort.

When that happens consistently, engagement stops being something the organization is trying to manufacture. It becomes a natural outcome of giving people a meaningful role and making the organization better. We end up with an organization where people believe that their knowledge matters, where speaking up is worthwhile, and where improvement can really become part of everyone's job.

For the wider framework this sits inside, read What Is a Business Performance System? The Seven Foundations That Turn Initiatives Into Results. To see how the pieces work together in one place, here's how HYPE supports employee engagement and participation.

Frequently asked questions

How does continuous improvement support employee engagement? It gives people a practical role in identifying problems and shaping better ways of working. When decisions, support and outcomes are visible, that participation feels worth it. Collecting suggestions on its own doesn't create engagement.

What's the difference between participation and engagement? Submitting an idea is participation. Engagement is what happens when people believe that their participation matters — because they can see it reviewed, acted on, and turned into something real.

Should employees implement their own ideas? Sometimes, when they have the skills, capacity and authority. But the person who spots a problem shouldn't have to own the whole solution. Often it's better to let them spot the opportunity while managers, experts or improvement leads help carry it forward — keeping the contributor involved.

How should we respond to an idea we decline? Tell people what happened and why, and what comes next. A visible no is better than an invisible maybe. Most people can accept that not every idea gets implemented; what they can't work with is silence.

How do you measure employee engagement in continuous improvement? Look at the process and the outcomes separately: how long decisions take, how many approved improvements actually get implemented, the results against a baseline like cycle time or cost, and whether people come back and contribute again. Then pair that with what employees tell you directly.

Get a free assessment of your business performance system

I run a 45-minute session that scores your organization across all seven foundations. You get a written report with your maturity score, the root causes behind the two or three constraints holding you back, and a prioritized action plan for the next 30 days, 90 days and 12 months. No preparation needed — and it isn't a demo.

→ Book your free assessment!