Every Lean practitioner can recite the two pillars: continuous improvement and respect for people. Ask them what continuous improvement looks like on a given day, and you'll get specifics -- huddles, PDSA cycles, A3s, gemba walks. Ask what respect for people looks like on the same day, and the answer gets vague fast. "We empower our teams." "We listen." "We value everyone's input."
Those aren't wrong. They're just not actionable. A newly promoted director of pharmacy who wants to be a respectful Lean leader can't do much with "be humble" or "empower people." What does humility look like at 7:45 AM when you're walking through the unit? What does empowerment sound like when someone brings you a problem?
This gap between principle and practice is one of the reasons Lean transformations stall. Organizations invest years in tools and training, then wonder why engagement plateaus. Often the missing piece isn't methodology. It's the specific, observable leadership behaviors that make people feel seen, heard, and safe enough to participate.
Here's what practitioners who've spent decades in this work say those behaviors actually are.
Help First, Coach Second
Karyn Ross, author of The Kind Leader and a longtime Lean practitioner, makes a sharp distinction that challenges how most of us were taught to lead at the gemba. We've internalized "ask questions, don't give answers" as a Lean leadership commandment. Ross argues we've overcorrected.
She points to a passage in Taiichi Ohno's Workplace Management where Ohno tells an engineer that if he can come running when the plant manager calls, it means nobody on the floor relies on him. The test Ohno describes: when you walk into the factory, it should take you hours to go 100 meters -- because people are stopping you, asking for help, telling you what makes their work hard. If you can walk through quickly, nobody sees you as useful.
Ross's reading of that passage reframes Lean leadership as helping people, not just coaching them. Not just asking questions that guide them to their own answers, but being present enough to actually do something that makes their work easier. When you do, she says, word spreads fast. People from other areas start coming to you. And now you're earning the kind of trust that makes everything else in your improvement system work.
The distinction she draws is between kind and nice -- and it matters more than it sounds like it should. A nice leader sees someone struggling and says nothing, because they don't want to make the person feel bad. A kind leader addresses it directly, with action. As Ross puts it, kindness is about action. The analogy she uses is simple: if someone has something in their teeth, nice ignores it. Kind tells them.
Applied to improvement work, this means a kind leader doesn't just ask "what do you think?" and walk away feeling participative. They stay. They help move a supply cart. They sit with someone and work through the problem together. They follow up the next day to ask if the change stuck.
The Words You Choose in the First Five Seconds
When a frontline worker tells you about a problem -- or worse, a mistake -- your response in the first few seconds determines whether they'll ever speak up again. This is where respect for people either lives or dies, and it plays out in language that most leaders have never examined.
Consider the difference between two questions a leader might ask after an error:
"Why did you do that?"
"What allowed that to occur?"
The first one sounds like root cause analysis. It's actually an accusation. The person on the receiving end hears judgment, closes off, and starts constructing a defense. The second question does the same analytical work -- it seeks causes -- but it directs attention to the process and the system rather than the individual. It signals that you're looking for what to fix, not who to blame.
In a KaiNexus webinar by Mark Graban on learning from mistakes, he shared a reflection model as a practical framework for these conversations. It consists of five questions:
- What was the plan?
- What actually happened?
- What can be learned from the gap?
- What actions will you take now?
- What do you predict will happen when you take those actions?
None of those questions contain the word "you" in an accusatory frame. They're structured to move from observation to learning to action. A leader who internalizes this sequence doesn't need to consciously remember to "be supportive" -- the questions themselves do the work.
The same webinar surfaced a point worth sitting with: if a leader asks people to speak up and then nothing changes, they haven't created psychological safety. They've confirmed futility. Research by Ethan Burris at the University of Texas found that the futility factor -- the belief that speaking up won't make a difference -- is at least as common as fear. People aren't always afraid to raise problems. They've just learned it's pointless.
This is why the response to the first complaint, the first reported mistake, the first half-formed improvement idea matters so disproportionately. The leader's reaction becomes the story people tell each other about what really happens when you speak up around here.
Trust Isn't a Warm Feeling -- It's a Structural Condition
Colleen Soppelsa, a continuous improvement leader with experience at Toyota, GE Aviation, and L3 Harris Technologies, frames the issue through a sharper lens than most Lean practitioners use. She defines trust using Charles Feltman's formulation: choosing to make something important to you vulnerable to the actions of others.
That definition reframes every act of kaizen as an act of vulnerability. You're working with others. You're brainstorming, which means saying things that might be wrong. You're testing changes that might fail. You're reporting results honestly, even when they're disappointing. Each of those steps requires trusting that the people around you -- especially the people above you -- won't use your openness against you.
In her experience across multiple industries, Soppelsa has found that trust isn't a personality trait or a vibe. It's a set of specific, measurable relationships that either exist or don't. She draws on the Great Place to Work trust model, which organizes trust into five dimensions: credibility, respect, fairness, camaraderie, and pride. Each dimension describes a relationship -- with management, with colleagues, or with the job itself -- and each has observable symptoms when it breaks down.
Poor strategy deployment, for instance, is a respect problem. When 70% of executives understand the strategy but the people closest to the product or service have no idea how their work connects to it, the message employees hear is: your role doesn't matter enough for us to explain the why. High turnover is a fairness symptom. Chronic firefighting -- where people are left to invent their own tribal ways of working because standards don't exist or aren't maintained -- is a pride problem, because it signals that the organization doesn't care enough about the work to define how it should be done.
Soppelsa has proposed something provocative: a Lean readiness assessment based on trust dimensions, with the argument that below a certain threshold of trust, attempting a Lean transformation is premature. The tools won't stick because the relational foundation isn't there.
During her Toyota onboarding in the early 2000s, she asked a sensei why Western organizations struggle with Lean. He went to the whiteboard and wrote a Japanese character: "gan," meaning cancer. His point was about internal competition -- the organizational equivalent of cancer cells consuming healthy ones. That image has stayed with Soppelsa for two decades because it names something most Lean frameworks politely avoid: the ego, insecurity, and internal competition that corrode trust from the inside.
Nice vs. Kind: A Distinction That Changes Everything
This thread runs through multiple practitioners' thinking and deserves its own emphasis, because "be nice" is terrible advice for a Lean leader. Nice avoids. Kind acts.
When someone makes a mistake, a nice response is to say nothing -- to spare them embarrassment. The person may not even realize the mistake happened, or they may feel guilty that it went unaddressed. Either way, there's no learning and no prevention.
A kind response acknowledges the mistake directly, reassures the person that it was unintended (mistakes by definition are), and then moves into problem-solving mode. What about the process made this mistake possible? How do we prevent it from happening again? That's where the real respect lives -- not in protecting someone's feelings, but in caring enough to help them improve and in building systems that protect everyone going forward.
Greg Jacobson, CEO of KaiNexus, models this distinction deliberately. When an employee shared with the entire company that a customer email had been stuck in a drafts folder unsent, Jacobson responded with two things: first, an admission that he'd made the same mistake himself ("dude, I've totally made that mistake"), and second, a practical countermeasure he uses -- a recurring weekly task to check his drafts folder. That response did three things simultaneously: it normalized the mistake, it modeled vulnerability from the most senior person in the room, and it offered a concrete improvement rather than a vague reassurance.
Compare that to the more common executive response: silence, or a generic "let's be more careful." Neither builds trust. Neither prevents the next occurrence. Neither teaches anyone anything.
Making It Structural, Not Personal
The practitioners quoted here converge on a point that's uncomfortable for organizations that treat culture as a leadership development problem: respect for people can't depend on whether individual leaders happen to be good humans on a given day. It has to be built into the management system.
This means the daily huddle isn't optional -- it's the structural guarantee that problems surface quickly and get acknowledged. The improvement tracking system isn't bureaucracy -- it's the mechanism that prevents ideas from vanishing, which is what teaches people their input matters. Leader standard work isn't micromanagement -- it's the commitment device that ensures gemba walks, coaching conversations, and follow-up actually happen instead of being crowded out by the urgent.
When organizations manage improvement work in spreadsheets or email, they're structurally unable to deliver on the "respect" part of respect for people. An idea submitted into a shared drive and never acknowledged is a small betrayal of trust. Multiply that by hundreds of employees and you've built a system that trains people not to bother. That's why purpose-built improvement infrastructure matters -- not as a technology play, but as a trust play. When every idea gets a response, every improvement has a visible status, and every person can see their contribution tracked through to impact, the system is doing the respectful thing whether or not a particular manager remembers to.
The Compound Effect
None of these behaviors -- helping before coaching, choosing careful language, building trust structurally, acting kindly rather than nicely -- is difficult in isolation. Any leader could do any one of them tomorrow. The challenge is doing all of them consistently, across hundreds of interactions, for years. That's where the compound effect kicks in.
Organizations that get this right don't have some secret methodology. They have leaders who've made these specific behaviors habitual. The first response to a mistake is always curiosity, never blame. The first response to an idea is always "thank you, let's work on it," never "we tried that before." The daily walk through the work area always includes at least one moment of making someone's job easier, not just observing and questioning.
Over time, these micro-behaviors build something that no training program or motivational poster can produce: a workforce that actually believes improvement is safe, valued, and worth their time. That belief -- earned through thousands of small leadership actions, not declared in a mission statement -- is what respect for people looks like on a Tuesday morning.
Related KaiNexus webinars referenced in this post (via YouTube):
- Why Kindness Is the Key to Lean Leadership with Karyn Ross
- Why Trust Is the Foundation of Continuous Improvement with Colleen Soppelsa
- Learning From Mistakes: How Leaders Build Cultures of Improvement & Innovation
- Q&A: Learning from Mistakes as Individuals and Organizations
- Extra Q&A from Psychological Safety as a Foundation for Continuous Improvement
.svg)
Add a Comment