Building Psychological Safety on Improvement Teams: Why Belts Hide Bad News

Psychological safety influences whether bad news travels up or stays buried. The AHRQ psychological safety guidance describes a supportive environment as one where people can ask for help, try new approaches, and learn from mistakes without expecting blame.

When team members fear judgment, they may filter data, soften findings, or avoid raising concerns that could stall a project. That delay can leave leaders with less time to respond.

This article explains why trained practitioners — Green Belts, Black Belts, and project leads — sometimes withhold unfavorable results, and what improvement leaders can do about it. You will find a short meeting script, a mechanism for surfacing concerns, observable follow-through behaviors, and examples of separating accountability from blame.

Silence does not establish motive or prove that a team lacks trust. Patterns of silence are still worth examining carefully.

Key Takeaways

• Psychological safety makes candid reporting easier.
• Leader reactions shape what teams share next.
• Structured reviews help surface uncertainty early.
• Accountability works best when separated from blame.
• Visible follow-through strengthens team trust.

Understanding the root causes of withheld information is the first step. The sections below move from diagnosis to action.

Why Psychological Safety on Improvement Teams Breaks Down During Bad News Escalation

Belts may withhold bad news for structural as well as personal reasons. A Belt who spent weeks on a measurement system analysis guide may hesitate to report that the gauge is unreliable, especially when leadership has already announced a project timeline.

The perceived interpersonal cost of speaking up can feel immediate, while the cost of silence may seem distant.

Harvard Business School researcher Amy Edmondson defines psychological safety as a shared belief that a team is safe for interpersonal risk-taking. Her research on team learning links psychological safety with behaviors such as asking for help, experimenting, and discussing errors.

Three structural conditions tend to suppress bad news escalation on improvement teams specifically.

1. Status Pressure from Belt Credentials

A Black Belt who surfaces a failed hypothesis risks looking less competent than one who reports steady progress. The credential itself creates pressure to appear expert, which can work against honest reporting when tests do not confirm expectations.

2. Sponsor Behavior During Gate Reviews

If a sponsor responds to a stalled Measure phase with visible impatience, the team may become more selective about what it presents. During a DMAIC phase gate review, sponsors can keep discussion focused on evidence, risks, and next decisions rather than personalities.

3. Absence of a Structured Disclosure Channel

Teams that lack a regular mechanism for surfacing concerns — something separate from status reporting — have no low-risk way to raise uncertainty. Informal channels require more courage, so less gets raised.

Recognizing these conditions is not about assigning blame to leaders or practitioners. It is about identifying which structural levers are available to change the information environment.

Leader Response Behaviors That Support Speaking Up on Improvement Teams

Leader response is a practical lever for building psychological safety on improvement teams. A calm, curious response to bad news can make future reporting easier, while blame or dismissal can discourage it. Visible, repeated behavior gives the team clearer evidence than an open-door policy alone.

The following behaviors are observable and repeatable. They do not require a personality change — they require deliberate practice.

• Ask before evaluating. When a Belt reports that a pilot failed, respond with a question: "What did the data show specifically?" Evaluation can follow, but curiosity should come first.
• Separate the finding from the person. "This test did not confirm our hypothesis" is different from "You ran the test wrong." The distinction matters to the team watching the exchange.
• Name the value of the information. Saying "This is useful — it narrows where the problem actually is" signals that bad news has worth. Teams notice when leaders treat failed tests as data rather than failures.
• Follow through visibly. If a team member raises a risk and the leader says they will address it, the team watches what happens next. Follow-through that is visible and timely builds team trust more reliably than any single conversation.
• Avoid retrospective blame. When a project encounters a problem that was foreseeable, resist the impulse to ask why it was not raised earlier before establishing whether the environment supported raising it.

You might be wondering how to handle the situation in real time, when a Belt presents results that contradict the project charter baseline assumptions. The short meeting script below offers a starting point.

A Short Meeting Script for Receiving Unfavorable Data

This script is illustrative. It is not a formula, and it will not fit every context without adjustment. The goal is to model the sequence: receive, clarify, acknowledge, redirect.

Belt: "The capability data shows the process is not where we assumed. The baseline sigma is lower than the charter projected."

Leader: "Walk me through what the data shows. What did you measure, and over what period?"

Belt: [explains measurement approach and results]

Leader: "Okay. So the baseline assumption in the charter was off. That changes the improvement target. What options do you see from here?"

Notice what the script does not include: expressions of frustration, questions about why the baseline was not validated earlier, or pressure to reframe the numbers. The leader response stays on the problem, not the person who surfaced it.

Air Academy Associates' Lean Six Sigma Champion Training Course addresses sponsor behavior directly, covering how leaders can support improvement teams through phases where results are uncertain and assumptions are being tested.

Building a Mechanism for Surfacing Concerns on Improvement Teams — Team Trust in Practice

A single conversation about psychological safety rarely changes a team's information environment. Repeatable structures such as learning reviews give teams a regular place to discuss uncertainty, failed tests, and challenged assumptions.

A learning review is distinct from a project status report. Its purpose is to surface uncertainty, tests that did not confirm expectations, and assumptions that remain unvalidated.

Evidence on formal interventions is still developing: a systematic review of interventions found mixed results and called for multifaceted approaches with visible leader support. Treat the framework below as a practical starting point and assess how it works in your setting.

How to Run a Learning Review That Supports Psychological Safety

The following steps reflect common practice in improvement-oriented organizations. They are presented as a general framework, not as Air Academy Associates-specific protocol. [Note: The examples below are illustrative and do not represent verified client cases.]

1. Set the purpose explicitly at the start. State that the meeting is for learning, not for evaluating performance. This framing reduces impression management and encourages honest reporting of what did not work.
2. Ask structured questions, not open-ended ones. "What did we test this week, and what did the results show?" is more productive than "How is the project going?" Structured questions make it easier to report unfavorable findings without it feeling like a confession.
3. Record challenged assumptions publicly. When an assumption is found to be wrong, write it on the shared document or board. Making it visible normalizes the process of revising understanding based on data.
4. Invite the team to name obstacles before they escalate. Ask directly: "Is there anything slowing the project that has not been raised yet?" This question, asked consistently, signals that raising obstacles is expected and welcome.
5. Close with a follow-through commitment. If a concern is raised, the leader names a specific next step and a date. The team observes whether that commitment is kept, which is the actual test of team trust.

The A3 Lean Problem Solving Training offered by Air Academy Associates provides a structured format for making evidence and uncertainty visible in a shared problem story — a format that naturally supports the kind of honest reporting that learning reviews require.

Separating Accountability from Blame in Psychological Safety on Improvement Teams

Accountability and blame are not the same thing, and conflating them damages team trust in ways that are difficult to repair. Accountability means that people are responsible for the quality of their work and the integrity of their data. Blame means that a person is treated as the cause of a problem rather than as someone navigating a system.

Improvement teams operate in complex systems. A Belt who reports that a corrective action did not hold is not necessarily reporting a personal failure — they may be reporting a system problem. The distinction matters for how the team responds and what the team learns.

The accountability-oriented responses keep the team focused on the process and the data. They do not eliminate performance standards — they direct attention toward the system conditions that affect performance. Psychological safety does not mean that poor work goes unaddressed. It means that the conversation about performance stays grounded in evidence rather than in judgment of the person.

For practitioners who want to develop stronger facilitation skills in difficult project conversations, Air Academy Associates offers Coaching and 1-to-1 Training that can be tailored to the specific challenges a Belt or team leader is navigating.

Air Academy Associates Resources Connected to Psychological Safety on Improvement Teams

The following four resources from Air Academy Associates address practical aspects of building team trust, supporting honest communication, and developing the leadership behaviors that improvement teams need. Each course connects to a specific challenge described in this article.

Lean Six Sigma Champion Training Course — Developing Sponsor Behavior and Organizational Support

Sponsors who understand their role in the improvement system are better equipped to respond to bad news without triggering defensive silence. The Lean Six Sigma Champion Training Course covers the responsibilities of improvement leaders — including how to support project teams through uncertainty, how to conduct effective gate reviews, and how to build the organizational conditions that allow speaking up to happen without penalty.

• Covers sponsor roles and responsibilities across DMAIC phases
• Addresses how leaders can support teams when results are unfavorable
• Relevant for managers and executives overseeing improvement portfolios

A3 Lean Problem Solving Training — Making Evidence and Uncertainty Discussable

The A3 format creates a shared, visible problem story that the team builds together — which changes the dynamic of how findings are reported. The A3 Lean Problem Solving Training teaches practitioners to document current conditions, root cause analysis, and countermeasures in a single structured format. When uncertainty is part of the document, it becomes a normal part of the conversation rather than something to manage around.

• Builds a shared problem-solving language across the team
• Normalizes the documentation of what is unknown or unresolved
• Supports honest bad news escalation through structure rather than courage alone

Lean Six Sigma Black Belt Online Course — Connecting Technical Leadership with Team Responsibilities

Black Belts carry both technical and interpersonal responsibilities on improvement teams. The Lean Six Sigma Black Belt Online Course develops the analytical depth that practitioners need to interpret and present data accurately — including data that does not support the original hypothesis. Practitioners who are confident in their technical skills are more likely to report findings clearly, without softening results to manage how they are perceived.

• Covers full DMAIC methodology with statistical tools
• Builds confidence in data interpretation and presentation
• Self-paced online format for working professionals

Coaching and 1-to-1 Training — Seeking Feedback on Facilitating Difficult Project Conversations

Some of the most useful learning for improvement leaders happens in conversation, not in a classroom. The Coaching and 1-to-1 Training option allows practitioners and team leaders to work directly with an experienced instructor on specific challenges — including how to facilitate learning reviews, how to respond to failed tests in real time, and how to build team trust over the course of a project. This format is particularly relevant for those navigating the interpersonal dimensions of improvement work.

• Personalized support for specific project or facilitation challenges
• Access to experienced Master Black Belt instructors
• Flexible scheduling to fit active project timelines

Closing Thoughts on Psychological Safety and Team Trust in Improvement Work

Psychological safety on improvement teams develops through repeated, observable leader behavior. When leaders respond to bad news with curiosity, follow through on commitments, and separate accountability from blame, team members receive clearer signals that speaking up is welcome.

That shift can improve the information available to decision-makers and help improvement teams learn sooner.