How to prevent culture of silence in a QA team and what to do if it already exists

Burnout among QA engineers is a systemic issue. While many attribute it to crunch periods before releases, the problem is often driven not just by workload, but by a culture of silence within teams — where speaking openly about problems and risks is simply not the norm.

For QA, this is a critical issue, as raising early warnings and helping prevent incidents is one of a QA engineer’s core responsibilities. This culture of silence is shaped by the leader — through their response to uncomfortable questions, bad news, and disagreements.

In this session, we will explore why control in QA creates an illusion of manageability, while in reality reducing personal accountability and increasing hidden risks. We will discuss why a blameless postmortem will not help if people were afraid to speak the truth before an incident happened. Most importantly, we will look at how to recognize when a culture of silence has already taken hold in your team and discuss 7 concrete steps that can help change it.