Most organizations that struggle to build a continuous improvement culture do not have an idea problem. They have a leadership problem. Employees almost always have ideas and want a better workplace. What's usually missing is the set of daily leadership behaviors that invite those ideas, respond to them, and make improvement feel safe, normal, and worth the effort.
In this webinar, Mark Graban, VP of Improvement and Innovation Services at KaiNexus, and Dr. Greg Jacobson, co-founder and Chief Product Officer, walk through 25 specific leadership behaviors they have seen build cultures of continuous improvement across manufacturing, healthcare, software, and beyond. The behaviors are practical and mostly free. As Greg puts it, this isn't about spending more time, it's about leading differently so the people you lead start behaving differently.
This page summarizes the core ideas. The full webinar goes deeper on each behavior with stories and examples.
The session opens with a familiar artifact: the locked, opaque suggestion box. Mark tells the story of submitting a diligent, carbonless-triplicate suggestion early in his career at General Motors, then receiving the pink "denied" copy in the mail nine months later, after a committee he never spoke to rejected an idea he believed in. That experience, repeated across countless organizations, is what teaches people not to bother.
The instinct is to blame employees who "don't care." Bruce Hamilton of GBMP names the real culprit: it's the system itself that squashes enthusiasm, not the people. When improvement isn't happening, the right move is the same as any Lean problem, ask why, understand root causes, and resist blaming individuals. In Mark and Greg's combined experience across hundreds of organizations, a lack of employee ideas is almost never the bottleneck.
The common barriers, lack of time, forgetting to follow up, lack of trust, fear of losing jobs, are real and legitimate. The key is that they have to be treated as problems to solve, not excuses to hide behind. If there's no time, make time. If there's no trust, build it. If there's fear of layoffs, make a no-layoffs-due-to-Kaizen pledge, which the leading healthcare organizations do.
Before the behaviors themselves, the webinar names the three pillars that consistently show up in organizations with strong improvement cultures: effective leadership, a systematic methodology, and enabling technology. Leadership doesn't mean spending all day on improvement; it means leading smart. Methodology means picking an approach (Kaizen, Six Sigma, A3, PDSA) and sticking with it rather than chasing the flavor of the month. Technology means tools that spread ideas and break down silos, whether within one large site or across many.
The first cluster of behaviors is about leaders making improvement explicit and personal. Publicly state your belief in continuous improvement, because people will not assume you want their ideas unless you say so, repeatedly and in many ways. Explain why improvement matters by tying it to the organization's goals, so people can focus their ideas on what moves the needle, not just on what bugs them. And lead by example by doing your own Kaizen first.
Mark's favorite story here is a nurse manager who asked a nervous second-week nurse whether she'd found any Kaizen ideas yet. When the nurse tensed up, the manager didn't push. She shared her own small example: a 25-cent rubber ring around an office key that solved a daily annoyance of grabbing the wrong key. The nurse relaxed and smiled, "Oh, I can do something like that." The leader made Kaizen unintimidating by demonstrating that it starts with me.
Several behaviors center on the scale and cadence of improvement. Ask for opportunities for improvement as an ongoing dialogue, in huddles and hallway conversations, not a once-a-year campaign. Don't require everything to be an event or a project; small daily improvements matter as much as week-long Kaizen events. Mark recalls Kaizen events at a former employer that, by day two, turned out to address problems too small to have justified a week of people's time.
Emphasize small ideas deliberately. Greg frames continuous improvement as a lifestyle change, not a fad diet: you build it by stacking small, low-cost, low-risk changes that are easy to undo if wrong. And the small ideas are where the surprises live. Across thousands of opportunities for improvement in the KaiNexus system, roughly one in 25 to one in 50 produces an unexpectedly large impact you'd never have found by hunting only for big ideas. As a hospital CEO in Japan told Mark, the best way to find big ideas is to find lots of little ones.
Don't just ask for cost-savings ideas, either. Asking people to make their own work easier produces more participation and develops problem-solving skills, which makes them far more willing to engage when a financial goal genuinely needs to be hit. And keep asking, continuously. Greg's image is the leader as drum beater: a quick reminder in every email, five or ten minutes in every huddle, until the late adopters realize this isn't a January fad but the new way the organization works.
Behavior eight is the one Greg calls most critical for healthcare: look at the process instead of blaming the people. When you shift from "who made the error" to "why was the error made," and you treat frontline staff as experts rather than as careless, people relax and engage. They surface more problems because they're not afraid of getting in trouble. Mark loves the principle "no problems is a problem," because it usually means people are sweeping things under the rug. He recounts a manager at an unnamed hospital who explained a problem by calling a colleague "a dingbat", exactly the bad-apple thinking that decades of patient-safety work has tried to replace with systems thinking. Deming estimated that 94 to 95 percent of errors trace to the process, not the person. The knee-jerk reaction should be to look at the process and pursue root cause.
A cluster of behaviors deals with how ideas are handled. Don't hide ideas, be transparent, because transparency both drives more improvement and lets one team's solution surface for another team facing the same problem. Quickly respond to every idea; not within minutes, but within 24 to 48 hours, with at least an acknowledgment. Nothing undercuts a leader's stated commitment faster than asking for ideas and then ignoring them.
The goal is to turn a complaining culture into a problem-solving culture. When a complaint comes in, a leader who looks for the root cause instead of getting defensive starts building a team of problem-solvers rather than carrying every problem alone. This is supported by Alan Robinson's research in "The Idea-Driven Organization," which found that roughly 80 percent of an organization's improvement potential comes from frontline staff. That means turning bad ideas into better ones rather than rejecting them. Greg tells of an employee who suggested putting a door in a spot where, for reasons the employee couldn't have known, it was a bad idea. Instead of voting it down, the leader asked why, and a few minutes of brainstorming turned it into something they could implement. A suggestion box would simply have rejected it, ending any possible improvement.
That leads to working to find something to implement. The reason KaiNexus customers see roughly 80 percent of opportunities for improvement lead to a change isn't luck; it's that submitting the idea is just the beginning. Maybe you can't put a door there, but you can add signage or move a supply. The work of finding something to implement is what turns a disgruntled person into an engaged problem-solver.
Help share and spread ideas actively, not just passively through transparency. When a workgroup has a win, broadcast it so other parts of the organization can adopt it. And help create time for people to take action, because asking overworked people to improve on top of everything else, without protecting any time for it, just adds stress. At the Toyota truck plant near where Mark has lived, improvement happens when the line is down, or managers approve overtime for a good idea, rather than sending people home. Either way, time gets made for Kaizen, not just talk about it.
Be prepared to fail is its own behavior. Not every improvement will be a winner, and the antidote is small, low-cost, low-risk changes plus the mindset that a "failure" is just something you tried and learned from. Greg pairs this with the reminder that the enemy of good is better; at some point you have to start rather than plan forever.
Be a servant leader who empowers without abandoning. Empowerment isn't dumping everything on staff and saying "you're empowered, go." It's collaborative, top-down and bottom-up, as John Shook describes it. A practical version: when something is overdue, ask "do you have a barrier I can help with?" rather than "why is this overdue?" Coach, but don't nitpick. If an employee's idea is merely different from what you'd do, sometimes you let them try it, because sometimes they're right and you're wrong. You step in only when something is unsafe, against regulations, or genuinely suboptimizing, like an emergency department proposing to stop admitting patients during its busiest hours, which helps that unit while hurting patients and everyone else.
Use PDSA properly. Don't overdo the planning, but don't skip the study and adjust either. The failure mode is "plan, do, declare victory," or planning something to death that could have been tested cheaply. A change that's easily undone deserves a quick test, not a long debate.
One of the behaviors Greg says could fill its own webinar: be careful with rewards and quotas. Incentives work, but as Daniel Pink documents in "Drive," they come with side effects. People get addicted to rewards, or a "one Kaizen per person" quota produces trivial ideas submitted only to hit the number. Greg's telling example is the person who held back a good idea in May because the month's "best idea" prize was already locked up by someone else, the reward system actively suppressing improvement. The better path is recognition: thank-yous, small tokens, points toward merchandise, the things Mark's co-author Joe Swartz's organization uses. Get people oriented around the right goals, including making their own work less frustrating, and intrinsic motivation does the rest. Be careful that extrinsic rewards don't tamp it down.
Finally, compile results and celebrate. Close the loop. Share that half the organization implemented an improvement this year, or the accumulated financial benefit, or the count of safety improvements. Letting people feel good about both participation and results inspires more of both.
Every one of these behaviors gets easier when improvement work is visible, tracked, and shareable. The webinar names three pillars of an improvement culture, and technology is one of them, the layer that lets the other two scale.
KaiNexus is built for exactly the behaviors above. It makes ideas transparent instead of locking them in a box, so a solution in one department surfaces for another facing the same problem. It routes every submission so it gets a fast response and an owner, addressing the "ideas go into a void" failure that kills suggestion systems. It tracks not just how many improvements happen but their impact across cost, quality, safety, satisfaction, and more, so leaders can close the loop and celebrate results. And it spreads proven improvements across departments and sites, so the same problem doesn't get re-solved five times. The behaviors create the culture; the platform keeps it visible and sustainable as the organization grows.
What are the three pillars of a continuous improvement culture? Effective leadership, a systematic methodology, and enabling technology. Leadership means leading smart, not spending all day on improvement. Methodology means choosing an approach (Kaizen, Six Sigma, A3, PDSA) and sticking with it rather than chasing the flavor of the month. Technology means tools that spread ideas and break down silos within and across sites.
Why do suggestion boxes fail? Because the failure is in the system, not the employees. Ideas go into a locked, opaque box, get reviewed slowly by a committee, and often get rejected with no explanation or conversation. That teaches people their ideas don't matter, and they stop submitting them. The fix is transparency, fast response, and working to find something to implement rather than looking for reasons to reject.
Should we pay employees or set quotas for improvement ideas? Be cautious. Incentives and quotas work in a narrow sense but carry side effects, as Daniel Pink documents in "Drive." Quotas produce trivial ideas submitted just to hit the number, and reward systems can actually suppress good ideas (as when someone holds an idea back because a monthly prize is already spoken for). Recognition, thank-yous, and small tokens tend to sustain intrinsic motivation better than cash incentives or quotas.
How do you handle a bad idea from an employee? Don't reject it outright, the way a suggestion box would. Ask why the person suggested it and what underlying problem they were trying to solve. Often a few minutes of brainstorming turns a "bad" idea into a good one. Working to find something to implement, even if it's not the original idea, is what turns a frustrated employee into an engaged problem-solver.
How do you coach an authoritarian manager toward these behaviors? Start with a private conversation, not a public one, and not a directive. Mark's approach is to explain why improvement matters, model an improvement of his own, and draw out the manager's interest through questions. Greg adds a root-cause angle: authoritarian leadership is often driven by insecurity or by emulating past leadership, so understanding that motivation, then showing how a more collaborative style improves the metrics the manager is judged on, tends to work better than simply telling them to change.
How do you measure these leadership behaviors? Directly measuring the behaviors is nearly impossible, they happen constantly and everywhere. Better to coach than to monitor: senior leaders should get out of their offices, observe team huddles, and give feedback on how managers are coaching. Then measure results, the number of improvements and, ultimately, the impact on what the organization cares about: quality, safety, cost, satisfaction. Improvement count is an intermediate measure; the real test is whether the metrics that matter are moving over quarters and years.
Does continuous improvement only work in manufacturing or healthcare? No. These principles originated in automotive manufacturing but apply everywhere, healthcare, software, architecture, startups, and more. Continuous improvement is fundamentally about people, creativity, a scientific approach to problems, and leadership, and that formula is largely universal even when the work is very different.
Do you have to fix the culture before you can do Lean? It goes hand in hand. You don't develop a culture of continuous improvement and then start improving, you develop the culture by doing the improvement. As Greg puts it, you can't buy a culture of continuous improvement off the shelf; you have to do the work to build it.
This webinar was presented by Mark Graban, VP of Improvement and Innovation Services at KaiNexus and author of "Lean Hospitals" and co-author of "Healthcare Kaizen," and Dr. Greg Jacobson, co-founder and Chief Product Officer of KaiNexus.
Explore more free webinars on continuous improvement, Lean, and leadership in the KaiNexus webinar library.
See KaiNexus in action and see how KaiNexus helps organizations capture ideas, coach improvement, and connect daily work to strategy.
Learn what you as a leader should be doing to create (and sustain) a culture of continuous Improvement!
.svg)
Copyright © 2026
Privacy Policy