Q38 of 38 · Manual & exploratory
How do you advocate for testing investment with a leadership team focused on shipping fast?
Short answer
Short answer: Frame testing in their currency — escape rate, customer NPS, revenue at risk, MTTR. Show data, not opinions. Tie investment to specific outcomes ('this CI improvement reduces our cycle time by 40 minutes per dev per day'). Avoid 'we should test more because quality matters.'
Detail
Leadership doesn't undervalue testing because they're philistines — they undervalue it because the QA team often pitches in tester language ("we need 80% coverage", "we need a regression suite") rather than business language. The fix is translation.
Translate to leadership currency: escape rate ("our last 10 production incidents could have been caught by 4 specific kinds of tests we don't have. Cost of those incidents: £X in refunds + Y engineer-hours"); customer satisfaction ("every regression eats Z NPS points"); cycle time / developer experience ("engineers wait 90 minutes for CI; reducing that is N hours of focused engineering time per week"); revenue at risk ("the next outage on the payment path is conservatively £X per hour").
Make the asks specific and time-bound:
❌ Vague: "We need to invest in testing." ✅ Specific: "I'd like to spend 2 sprints rebuilding the payment regression suite. ROI: prevents an estimated 3-5 production incidents per year, each averaging £20k. Break-even after the first prevented incident."
Bring data, not opinions. Pull the production incident log; map each incident to "could this have been caught with [X type of test]?" That table makes the case better than any slide.
Pick battles strategically. Don't fight for "we need 100% coverage" — that's losing on principle. Fight for "we need to add 50 specific tests covering this area," which is winnable and concrete.
Reframe testing as an enabler, not a gate. "Faster, more reliable testing means faster, more confident shipping." Showing testing as the way to increase ship rate flips the framing.
Cultivate allies. Engineering leads, SRE, and on-call rotation members are usually allies — they bear the cost of poor testing. Joint pitches land better than QA-alone ones.
Be willing to lose well. Sometimes the ask is rejected. Document the trade-off and revisit when the predicted incidents materialise. "Told you so" is bad politics; "we tracked our predictions, here's what happened" is leadership.
// WHAT INTERVIEWERS LOOK FOR
// COMMON PITFALL
// Related questions
How would you mentor a junior tester struggling to write meaningful test cases?
Manual & exploratory
Tell me about a time you advocated for testing investment when leadership wanted to ship faster.
Behavioural
Tell me about a time you had to convince leadership to adopt a new testing approach.
Behavioural