Speak-Up Culture vs. Psychological Safety: Safe and Worthwhile
A speak-up culture depends on people believing that raising an idea, concern, or mistake is both safe and worthwhile. Psychological safety addresses the interpersonal risk: will I be blamed, embarrassed, or punished? The “worthwhile” question concerns the response: will anyone listen and do something useful with what I say?
Those questions overlap, but they are not identical. A respectful response without follow-through can leave people feeling that speaking up changes nothing. A strong problem-solving process will miss important issues if people are afraid to use it.
Stephen “Shed” Shedletzky, author of Speak-Up Culture: When Leaders Truly Listen, People Step Up, helped make that distinction concrete when he joined me on My Favorite Mistake. Here is our conversation:
As Shed explained:
“Speak up is a culture, not an instruction. I can't say ‘speak up' if I haven't helped create the environment in which it's safe and worth it.”
What speak-up culture adds to the conversation
I find “speak-up culture” useful because it points to something leaders can ask about directly. Are people raising concerns? Do they disagree with a proposed plan? What happened the last time someone admitted a mistake?
That does not make “psychological safety” the wrong term. Amy Edmondson's research and explanations help us understand why these conversations can be difficult, including for highly capable people. The language should help a team understand its experience rather than become another slogan to adopt.
Shed describes the conditions this way:
“Safe and worth it to speak up with ideas–even if they're half-baked–feedback, concerns, disagreements, or mistakes.”
The point is not to abandon psychological safety. It is to connect the concept to what happens when a person actually brings forward information a leader needs to hear.
Fear and futility need attention together
People may fear blame, embarrassment, retaliation, or damage to their career. They may also have learned from experience that raising an issue produces no useful response. Fear and futility can coexist; there is no requirement to finish addressing one before working on the other.
I have heard people in healthcare organizations say, “I'm not afraid to speak up; it's just that nothing happens.” Before complaining about silence, a leader should ask how many times people have already raised the issue and what happened afterward. I explore that pattern further in fear and futility in healthcare improvement.
Shed asks:
“If I feel safe to speak up, but nothing happens, how many times do I go back to that dry well before I decide it's just not worth it?”
This is a reason to examine the response process, not to label people apathetic. Did anyone acknowledge the concern? Was a decision made? Did the person who raised it hear back? A problem may take time to solve, but leaving someone without an update adds a separate, avoidable frustration.
Respectful disagreement is part of the work
Shed also makes a useful distinction:
“A speak-up culture is not a hall pass to be a jerk.”
Honesty does not require humiliating someone or dominating the discussion. He shares three questions, credited to Craig Ferguson: does this need to be said, does it need to be said by me, and does it need to be said by me now?
Those questions can help someone be thoughtful about timing and contribution. They should not become a test that people must pass before reporting an urgent concern. Leaders also need to hear imperfectly expressed feedback rather than dismissing a valid issue because they dislike the delivery.
This applies especially to executives. Feeling free to express yourself does not justify behavior that makes everyone else afraid to speak. For a related discussion, see blame versus accountability in leadership.
Make the response visible
Lean leadership and continuous improvement provide practical ways to follow through. The team can investigate a concern, understand the work, test a change, and check its effect. That gives the conversation a purpose beyond collecting suggestions.
Consider a concern raised in a daily huddle. A useful response might be: “Thanks for pointing that out. Let's look at it together after the huddle. I will bring back an update tomorrow.” The value comes from doing what was promised, including reporting that more help or investigation is needed.
Not every idea should be implemented. An explanation of why an idea cannot proceed, or what the team learned from a test, can still show that the contribution received serious attention. Approval is not the only meaningful response.
When someone admits a mistake, first understand what happened and address any immediate risk. Then work on prevention. An automatic reprimand can discourage the next report; an automatic “don't worry about it” can skip learning. Neither is enough on its own.
Check the experience, not just the intention
Shed offers this reminder:
“Just because you think you have a speak-up culture doesn't mean you do.”
A leader's intention to listen does not establish that people feel heard. Look at a recent concern from the employee's perspective. What response did they receive? What changed? What remains unresolved? Asking those questions can reveal a manageable next step.
For more context, see psychological safety in Lean organizations. The next improvement might be a better question, a calmer response, or simply closing the loop on an issue that someone has already raised.
Explore learning from mistakes
In The Mistakes That Make Us, I explore how people respond to mistakes and how leaders can help turn those experiences into learning and improvement. Read a free preview before deciding whether the book would be useful for you or your team.
Read a free preview of The Mistakes That Make Us
Bring Lean thinking to healthcare
In Lean Hospitals: Improving Quality, Patient Safety, and Employee Engagement, I explain how hospitals use Lean to reduce delays and errors and to engage the people who do the work. It is a Shingo Publication Award recipient, now in its third edition.
