Skip to content
Leadership and Competence Management | Part 6 of 12

Teams Need to Surface Problems Before They Become Failures

Create conditions for useful challenge while keeping standards and follow-through clear.

A team knows that a launch is not ready, but employees expect the messenger to be blamed. The formal review remains green until the customer experiences the failure.

A capable team needs a practical way to raise uncertainty, mistakes and disagreement. That requirement is compatible with clear standards and accountability.

Understand the evidence carefully

Edmondson’s original study examined 51 manufacturing work teams and found an association between team psychological safety and learning behavior. The findings support attention to team context and leader coaching, but do not prove that one exercise or phrase causes better performance everywhere.

Use the concept to investigate whether people can take appropriate interpersonal risks such as asking for help or challenging an assumption.

It is not a promise that every conversation will feel comfortable.

Define useful challenge

A concern should be assessable through four elements:

  1. the condition observed,
  2. the evidence,
  3. the consequence,
  4. the decision needed.

A hypothetical engineer can report missing verification without being required to solve the entire schedule problem first.

Distinguish an honest error, a capability gap and disregard for an agreed requirement. They may need different responses.

Avoid using “accountability” as a reason to suppress inconvenient information.

Make the response credible

Leaders should ask questions, examine evidence and explain the decision. A request for openness followed by retaliation teaches the opposite behavior.

Assign action where needed and close the loop with the team. Repeatedly collecting concerns without response can weaken confidence.

Provide escalation beyond the immediate manager when appropriate.

A meeting routine helps only if actual cases receive fair treatment.

Maintain standards and learning

Clear requirements make it easier to identify a deviation. Development and support make improvement possible.

A hypothetical launch review can retain strict release criteria while allowing the team to expose readiness gaps early.

Review the recurrence of problems and the quality of responses, not merely a survey score.

For the next team review, ask which important concern might currently remain unspoken and what happens when it is raised.

Psychological safety becomes operationally valuable when people can reveal the information needed for a good decision and the organization acts responsibly on it.

Reference

Psychological Safety and Learning Behavior in Work Teams (Edmondson, Administrative Science Quarterly)

Newsletter

One Lean idea.
Every two weeks.