A major production bug slipped past my QA lead last week and he waited five days to flag it because he wanted to fix it first. How do I get my team to stop hiding operational fires?

Question

Tyler Smith · Accepted Answer

It's critical to understand that your QA lead likely wasn't acting maliciously, but rather from a misguided belief that their value was tied to being a solo problem-solver. In growing companies, this heroism mindset is incredibly dangerous because it inevitably delays critical commercial interventions. To shift this culture, you need to establish clear communication protocols and expectations.

The Three-Question Communication Test

To prevent hiding operational fires, install this communication test across your entire company:

1. What do I know?
2. Who needs to know?
3. Have I told them?

When your QA lead discovered the bug, he knew the product was broken. He should have instantly realized that customer success, sales, and operations needed to know, and that he had not yet told them. This simple framework helps individuals quickly assess their communication responsibilities.

This shift in mindset is also crucial for [building vulnerability-based trust with your leadership team](/qa/building-vulnerability-trust-leadership-team), where team members feel safe to share bad news without fear of retribution.

Building a Culture of Immediate Escalation

To build a culture where bad news travels up immediately, take these three tactical steps:

1. Establish Clear Thresholds

Define exactly what qualifies as a Level One emergency. Examples include:

• Any bug affecting more than five percent of users.
• Any project lagging by more than three days.

These thresholds must be objective and communicated clearly to everyone. This prevents ambiguity and ensures everyone understands when to escalate an issue. Defining these parameters is a core part of developing [minimal processes](/qa/minimal-processes-12-employees) that prevent operational breakdowns as your company grows.

2. Separate Reporting from Resolving

Make it explicitly clear that raising a red flag does not mean someone has failed; it means they are doing their job. Create an environment where people are rewarded, not punished, for early detection.

• Praise people publicly when they raise a red flag early, even if the news is terrible.
• Emphasize that the goal is early detection and collective problem-solving, not individual heroics.

This approach helps to combat the natural tendency for executives to [hide department failures](/qa/stopping-leadership-team-hiding-failures) until it's too late.

3. Build an Escalation Path

Create a dedicated channel or protocol specifically for critical alerts. This could be a specific Slack channel, an emergency email distribution list, or a direct line of communication to specific leadership roles.

• Ensure that the moment an issue hits this channel, the immediate focus is on mitigation first and root-cause analysis second.
• This structured approach helps to avoid situations where [weekly leadership meetings devolve into status reports](/qa/stop-weekly-leadership-meetings-devolving-into-status-reports) instead of strategic problem-solving. It ensures urgent issues are addressed proactively.

By implementing these steps, you can transform your team's approach to problems, fostering a culture of transparency and proactive problem-solving rather than reactive firefighting. This is essential for preventing the chaos of daily fires that can consume an operations team and prevent them from [building better systems](/qa/how-to-find-time-to-build-systems).