Communicating quality to stakeholders: why testers get ignored in meetings (and how to change it)
If you’ve ever tried communicating quality to stakeholders in a planning or review meeting, only to be brushed aside with “let’s move on” or “we’ll deal with it later”, you’ll know how frustrating it feels.
It’s not that you wanted to be right for the sake of it. You could see the rework coming. You knew that late nights and emergency bug-fixes were on the horizon. And sure enough, a sprint or two later, the problem comes back around.
I’ve been in that position more times than I care to remember. Early in my career, I chalked it up to stakeholders not caring about quality. I thought they were rushing, or ignoring the risks because they didn’t want to hear them.
But over time I realised that wasn’t the whole story.
The disconnect in stakeholder communication
The truth is, most stakeholders do care about quality. What they don’t always see is how the issue you’re raising links to the things they are measured on in that moment, deadlines, budgets, customer satisfaction, or delivery promises.
So when you say:
“The test environment isn’t stable enough for us to continue.”
they hear:
“The release is going to slip, and I have no options.”
Or when you say:
“The requirements aren’t clear enough to test.”
they hear:
“You’re blocking us from starting work.”
The problem isn’t that your observation is wrong. It’s that the way it’s framed doesn’t connect to their priorities.
Why communicating quality to stakeholders matters
When testers get ignored in meetings, two things happen:
- Quality risks don’t get the attention they deserve, leading to rework and unhappy customers.
- Testers get disheartened and start speaking up less, which only makes the first problem worse.
It’s not a matter of shouting louder. It’s about learning to bridge the gap between your quality insight and their business goals.
A better way to frame quality conversations
The good news is, you don’t need a new job title or a louder voice, you just need to reframe how you bring quality issues to the table.
That doesn’t mean sugar-coating problems or hiding risk. It means translating them into language that resonates: cost, confidence, predictability, customer impact.
| Instead of saying… | Try framing it as… |
| “The test environment isn’t stable enough for us to continue.” | “Our environment instability is delaying validation by two days. That increases the chance of late rework and puts our release confidence at risk.” |
| “The requirements aren’t clear enough to test.” | “Unclear requirements are creating rework mid-sprint. If we resolve them now, we can reduce delivery delays and avoid blocking the team later.” |
Same observation, but phrased in a way that connects to what stakeholders care about: predictability, confidence, and avoiding waste.
I’ve been working on something short and very practical to help testers practise this skill, turning those brushed-aside warnings into conversations stakeholders actually listen to.
I’ll share more on that later this month.
Photo by Redmind Studio on Unsplash
The post Communicating quality to stakeholders: why testers get ignored in meetings (and how to change it) appeared first on Kato Coaching.