Stakeholders & Communication
Navigating the "Human Layer" of quality. Learn how to speak the language of the business.
1 The Hook
A Test Manager in Auckland was 15 minutes away from a "Go/No-Go" meeting for a major retail launch. The CTO asked: "Is it ready?" The TM started explaining a defect in the CSS layout of the footer. The CTO interrupted: "I don't care about the footer. Can people buy things without the site crashing?"
Stakeholder management is the art of giving people the information they actually need to make a decision, not the information you happened to collect.
2 The Rule
Report for Decision, not for Status. If your stakeholder can't make a choice based on your update, your update is noise.
Senior engineer insight
The moment I stopped writing test reports "for the record" and started writing them "for the decision in the next meeting," everything changed — my status updates got shorter, my influence got larger. I realised that a 20-item bug list handed to a CFO is an abdication of the Test Manager role: you are asking them to do your job of interpreting risk. The real skill is distilling 200 open defects into one sentence a board member can act on.
The most common mistake: burying the Go/No-Go recommendation inside paragraphs of context, so the stakeholder never reaches the actual call to action.
From the field
On an NZ government programme — a major welfare benefit system replacing decades-old mainframe code — the test team assumed the SRO (Senior Responsible Owner) wanted a weekly defect-count dashboard, because that is what the project manager requested. Six weeks in, the SRO told the programme board she had "no visibility of quality risk," even though the dashboard was green. What she actually needed was a narrative: which scenarios could cause a ministerial complaint, and what is the plan? The team rebuilt their reporting entirely around two questions: "What could harm a beneficiary?" and "What are we doing about it?" — defect counts moved to an appendix. From that point, quality risk appeared on the weekly governance report going to Ministers, which meant issues got resource and decisions got made at pace.
3 Watch Me Do It: The "Executive Translate"
Observe how a "Raw Bug List" is translated into a "Business Risk Report" that a CEO can actually use. Pay attention to the change in language.
✕ Too Technical
- JIRA-101: 500 Error on checkout.
- JIRA-105: CSS padding wrong on mobile.
- JIRA-110: API latency is 400ms.
✓ The Test Manager Way
- Revenue Risk: High. 5% of checkout attempts fail. Est. loss: $10k/hr.
- Customer Trust: Low. UI issues on mobile look "unprofessional."
- Performance: Stable. Confirmed acceptable for launch load.
4 Strategy Lab: The Negotiation
In this exercise, you must handle "The Testing Squeeze." Use the following framework to negotiate a high-pressure deadline.
Your Task: The Saturday Deploy
It's Friday 3 PM. Marketing has a $50k ad campaign starting tomorrow. A critical bug is found. The PM says: "Just ignore it, we have to launch."
APPLY THE "OPTIONS FRAMEWORK":
- Path A (The Danger): Launch anyway. Document the risk in the Risk Register. Ask the PM to formally "Accept" it.
- Path B (The Pivot): Launch with the broken feature "toggled off." (Safe launch, missing value).
- Path C (The Safety): Delay 24 hours. Explain the cost of a PR disaster vs. the cost of a 1-day delay.
Which path would you recommend? Why? Write your justification in your notes.
5 Common Mistakes
⚠ Reporting "Bug Counts" to a CTO
Why it fails: Bug counts are vanity metrics. A CTO cares about **Risk Exposure**. One critical bug is worse than 1,000 spelling mistakes.
⚠ Being the "Quality Police"
Why it fails: If you just say "No" to every launch, people will stop inviting you to meetings. Be the **Risk Advisor** who provides paths forward.
Why teams fail here
- They speak in JIRA tickets and severity ratings — the CTO or SRO has no frame of reference for "P2 defect," so the information lands as noise rather than signal.
- They wait until the weekly report cycle to surface a show-stopper, instead of escalating the moment risk crosses a threshold — "no surprises" only works if you actually prevent surprises in real time.
- They frame every update as a problem without options, which trains stakeholders to associate the Test Manager with bad news and blockages rather than with solutions and paths forward.
- They let the PM mediate all executive communication, losing the direct relationship with the SRO or sponsor — when a genuine Go/No-Go call is needed, the Test Manager has no independent credibility to draw on.
Key takeaway
Your job is not to report what you found — it is to make sure the person with the authority to act knows exactly what they are deciding and what happens if they decide wrong.
6 Self-Check
Q1. What is the "Golden Rule" of Stakeholder Management?
**No Surprises.** If a project is trending Red, communicate it early so stakeholders can adjust their plans.
Q2. How do you move from a "Status Reporter" to a "Strategic Partner"?
By translating technical data into business impact (Money, Reputation, Risk).