Problem-Seeing Eyes Are Everywhere. Problem-Speaking Mouths Are Rare.

TL;DR: Organizations invest in teaching people to see problems and solve problems — but skip the middle step: making it safe and worthwhile to speak up about them.

I've seen blank huddle boards in hospitals. Cards and markers sitting untouched. Nobody filling anything out.

That's not a training failure. That's the system telling you something about whether people believe speaking up leads to anything constructive.

Employees see the workarounds, the recurring failures, the things that don't make sense. They've been seeing them for months. Sometimes years. They just stopped mentioning them.

Most organizations don't have a “problem seeing” problem. They have a “problem speaking” problem.

The Intelligence You're Already Paying For

Think about what this actually means. You have people on your payroll who understand the work better than anyone in the building. They see patterns their managers miss. They know which process step causes the rework, which handoff creates the delay, which workaround everyone has quietly agreed to pretend is normal.

That intelligence already exists inside your organization. You're already paying for it.

The question is whether any of it reaches the people who can act on it.

When employees go quiet — not because they lack insight, but because experience has taught them that speaking up isn't safe or isn't worthwhile — the loss is invisible. You'll never see a line item on a financial statement for “problems employees noticed but didn't mention.” There's no dashboard for it.

But the cost shows up everywhere: in repeated failures, in slow improvement, in the bewildered leadership team that can't understand why their problem-solving training isn't producing results.

The training worked. People can solve problems. They just aren't bringing any forward.

Why People Stay Quiet

Research by Ethan Burris from the University of Texas has consistently found two primary reasons employees choose not to speak up: fear and futility.

Fear is the one most leaders think of first. People are afraid of being blamed, marginalized, or punished.

But Burris's research shows that futility is actually more common. People say things like,

“I'm not afraid to speak up. It's just not worth the effort. Nothing changes.”

Both have the same effect. Problems that people can see don't get shared. And problems that don't get shared don't get solved.

What makes futility especially corrosive is that it often follows well-intentioned efforts. An organization launches a huddle board. Puts suggestion cards in the breakroom. Tells employees their voice matters. And then… nothing visible happens with the input. No feedback loop. No follow-through.

So people learn, rationally, that the effort isn't worth it. That's not a character flaw. That's pattern recognition.

The near-miss nobody reported because the last person who flagged one got asked why they let it happen. The process improvement nobody suggested because the last three suggestions disappeared into a spreadsheet. The question nobody asked in the meeting because the last person who questioned the plan got a cold response from the VP.

None of these show up in your data. They show up in the gap between where your organization is and where it could be — a gap that widens quietly over time.

What It Looks Like When Speaking Up Is Safe

In a conversation on my Lean Blog Interviews podcast (Episode 484), Keith Ingels from the Raymond Corporation talked about developing people who have “problem-seeing eyes” — the ability to recognize waste, abnormal conditions, and opportunities in their work. At Raymond, which operates under the Toyota umbrella, this is a core part of how they develop people.

Keith made the point that solving problems is usually the easier part. Seeing them clearly is the harder skill to develop.

I'd push that one step further. In most workplaces, the seeing is already happening. The real bottleneck is what happens — or doesn't happen — between seeing and solving.

Keith described Raymond's mindset:

“Critique the process, not the people.”

I love how he didn't use the far more common phrase “Be hard on the process, not the people.” I think “critique” is a much more neutral word than “hard” — even though the point is the same: don't blame people for systemic problems.

He gave a small example that's easy to overlook. At one of Raymond's customer sites, a VP of Operations was proudly showing off some coat hooks. The team had been talking with seasonal workers and learned that people didn't have a good place to put their coats while assembling bulb packages. Nobody had mentioned it before.

Coat hooks. That's the kind of thing that gets dismissed as trivial. But what actually happened there is important: someone felt safe enough to mention a small irritation, and a leader responded by fixing it.

That transaction — speak up, get heard, see a result — is what builds the muscle. The next time, the suggestion might be about how the work itself gets done.

Keith also emphasized that this isn't something you build once. “The best leaders focus on process improvements,” he said. The safe environment has to be rebuilt through daily behavior.

What Toyota Understood Without Naming It

Toyota's culture has long embodied psychological safety, even without using the term. Jeff Liker and Mike Hoseus wrote in Toyota Culture that:

“Toyota believes people must feel psychologically and physically safe” and that “any concerns they have will be taken very seriously.”

Mike Hoseus told me directly that while they didn't use Amy Edmondson's language at Toyota, the concept was deeply embedded. He described his early experience at Toyota's Georgetown plant, where the response to problems was so consistently constructive that it felt “refreshing.” Everyone could spend their time on the actual problem instead of deflecting blame.

That's what it looks like when the whole system is working. No energy wasted on self-protection. All of it directed at the work.

See, Speak Up, Solve, Share

Steve Spear, who has studied Toyota extensively, describes their approach as “See, Solve, Share.” See problems, solve them, share what worked.

It's a powerful framework — and it works at Toyota because the speaking-up part is so deeply embedded in the culture that it can be taken for granted.

Most organizations can't take it for granted.

I've suggested an expanded version: “See, Speak Up, Solve, Share.“ Because we can't solve a problem that nobody is willing to name out loud.

This points to three capabilities that any improvement culture needs:

Problem-Seeing Eyes — the ability to recognize waste, variation, and abnormal conditions.

Problem-Speaking Mouth — the willingness, and the safety, to say something about what you see.

Problem-Solving Brain — the skill and structure to work through root causes and test countermeasures.

Most improvement investments focus on the eyes and the brain. Organizations train people to see waste. They teach A3 thinking, PDCA, root cause analysis. Those investments are real and worthwhile.

But they skip the mouth — or assume it's already there. And that assumption is expensive.

A Diagnostic, Not a Program

One way to use this framing is as a quick diagnostic. When improvement stalls, ask which of the three is the bottleneck:

Are people struggling to see the problems? That's a training and coaching opportunity — help them develop those problem-seeing eyes.

Are people seeing problems but not saying anything? That's a psychological safety gap. Look at leader behaviors, not employee attitudes.

Are people raising problems but nothing gets solved? That might be a skill gap. Or a resource and prioritization issue. Either way, futility is building.

Most organizations have some combination of all three. But in my experience, the “problem-speaking mouth” is the one that gets the least deliberate attention — and it's the one that determines whether the other two matter.

Choosing to Speak Up Isn't a Character Issue

Telling employees to be more courageous doesn't fix this.

Choosing to speak up isn't a matter of character — it's a function of culture.

Leaders create the conditions. They reduce fear by modeling vulnerability: admitting mistakes, responding constructively to bad news, saying “thank you” instead of “why didn't you catch that sooner?” They reduce futility by closing the loop — making sure that when someone speaks up, something visible happens as a result.

Keith Ingels ended our conversation with a simple instruction:

“Make it yours.”

He was talking about Raymond's approach to adapting the Toyota Production System. That's similar to the advice given by Fujio Cho in the 1990s about making your Lean system your own.

The advice applies here, too. Whatever you call this framework — or even if you don't call it anything at all — the question is whether your organization has built all three capabilities, or just the two that are easier to train.

Every person who can see a problem but has learned not to mention it represents a quiet, compounding loss — one that gets a little larger every day and never appears on any report you'll ever read.

What would change if they believed it was worth opening their mouth?