--- title: "QA Manager to Head of QA: The Escape Bill That Wins Budget" author: "Harry" published: 2026-10-31T04:46:55.856Z updated: 2026-10-31T05:06:53.637Z category: "Career & Teams" tags: ["qa-career-path"] canonical: "https://fxblog.dev/posts/qa-manager-head-of-qa" --- # QA Manager to Head of QA: The Escape Bill That Wins Budget ## Key takeaways - A QA manager's output is decisions, plans, unblocked people and clear communication, not personal testing. - Ranking testers by bugs found turns collaboration into hoarding; offer escape rate and risk coverage instead. - A status report should open with a judgment, such as a release at risk and why, before any table. - The budget case that wins is arithmetic: the cost of last quarter's escapes in support and engineering time against the cost of the prevention you are asking for. - A Head of QA's product is the QA organisation itself: its shape, standards, budget, managers and career framework. > **TL;DR** A QA manager who reports counts nobody acts on, or asks for headcount with "we're overloaded", loses the room: bugs-per-tester turns collaboration into hoarding within a week, and "we're overloaded" loses to a competing roadmap every time. Report outcome metrics that lead with a judgment, and make the budget case as arithmetic: FieldFlow's escapes cost about £23k a quarter against £15k for the SDET who would prevent most of them. > > **Do this:** Pull last quarter's escapes, price each one as support hours plus engineering firefighting, and write one sentence comparing that bill with what prevention would cost. [Part 5](05-lead-or-staff-after-senior.md) ended with you as QA Manager, signing FieldFlow's releases, and two asks from above: a director who wants every tester to log 5 bugs a day, and your own case for one more SDET with last quarter's 11 escapes in the records. What do you put in front of them? Not a tester leaderboard, and not a plea. A number with a pound sign on it. **QA Career Path, in seven parts:** 1. The QA Career Path: Map Yourself by Scope, Not by Title 2. New QA Engineer? Test the Risk, Not the Ticket 3. Manual to Automation Testing in Six Months: Skip the Tutorial Loop 4. Senior QA: Depth Everywhere Is Depth Nowhere 5. After Senior QA: Lead the Release or Own the Platform? 6. **QA Manager to Head of QA: The Escape Bill That Wins Budget** (you are here) 7. Will AI Replace Testers? Make Your Judgment the Evidence ## Your output is decisions now A QA Manager's week has very little hands-on testing in it: triage, 1:1s, a release readiness review, an interview, the weekly status report. The output is decisions, plans, unblocked people and clear communication. > **Note** > > Your team is your product now. Cancelling 1:1s for "urgent" release work is one of the repo's five failure modes for new managers. ## Refuse the anti-metric, answer its question Every metric should answer a question someone is actually asking. When leadership asks for an activity count, offer the outcome metric behind the real question. | They ask for | Why it backfires | Offer instead | | ---------------------------- | -------------------------------------- | ------------------------------------- | | Bugs found per tester | Bug-count inflation and duplicate wars | Escape rate and risk coverage | | Test cases written | Rewards bloated, shallow cases | High-risk items fully tested, % | | 100% pass rate as a goal | Encourages weak tests | Flakiness rate and escapes | | Code coverage as a QA target | It's a developer signal | Coverage of the top critical journeys | The rule underneath is Goodhart's law: when a measure becomes a target, it stops being a good measure. So the director's 5 bugs a day gets a reply, not a yes: "you want to know if we're testing enough; here's escape rate and risk coverage." ![A one-page QA dashboard: readiness with a judgment, escape trend, hotspots, blockers](https://fxblog.dev/media/01a19048-1077-763f-b9d6-ac04e75b6d0e/1600) _One page, a judgment on top, a decision under each panel_ Then lead every report with the judgment: "Release is at risk: invoicing regression is 60% done with 2 Sev-2s open" beats a table with no conclusion. And never bury a Sev-1. Credibility is your whole currency. ## Price the escapes The argument that wins budget is arithmetic. Here it is on FieldFlow's fictional numbers from the repo: 11 escapes last quarter, 3 in invoicing. ```text Average escape ~12 support hours × £25 + ~2 engineer-days × £350 ≈ £1,000 Invoicing escape the same, plus customer recovery work ≈ £4,000 ≈ £5,000 Failure cost 8 × £1,000 + 3 × £5,000 ≈ £23,000 Prevention one SDET on invoicing and API regression ≈ £15,000 Projected effect no invoicing escapes, and half the rest ``` Presented as one sentence: each quarter we choose £23k of failure over £15k of prevention, and here is last quarter's evidence. Substitute your own rates; the shape is what carries. > **Tip** > > That sentence, with the trend attached, is also your executive report: judgment first, money language, one ask. ## At Head of QA, the organisation is the product A Head of QA has effectively zero hands-on time. The work is org design, budget, growing managers and leads, and the career framework itself, including the IC track from part 5. The repo's default shapes: 1. Up to 3 squads, one product: embedded testers and one QA Lead. 2. 4 to 8 squads on a shared platform: embedded testers plus a QA chapter that owns standards, tooling and the hiring bar. 3. Many products or heavy compliance: embedded testers plus a small central team for standards and audits. FieldFlow, at 6 squads, lands on the second row. Its 8 testers to 40 developers is 1:5, inside the 1:4 to 1:8 band the repo calls common. Benchmarks open that conversation; your escape data closes it. ## Try it ```text Here are last quarter's production escapes, with rough support hours, engineer-days and any customer recovery work for each: . Using my rates (, ), price each escape, total the quarter, and write one sentence comparing it with . Flag any number I gave you that looks like a guess. ``` The SDET gets funded. Then the tools move under everyone's feet: AI drafts test cases and test code in seconds, and a vendor demos an agent that "tested all of FieldFlow in 20 minutes, 0 failures". If tests are that cheap to produce, what is a tester's work worth, and how does anyone, at any level, show it to the next employer? Part 7, **Will AI Replace Testers? Make Your Judgment the Evidence**, closes the series there. ## Read this with your AI ```text Read the post "QA Manager to Head of QA: The Escape Bill That Wins Budget". 1. Summarise it in 5 bullets for a new QA manager. 2. Ask me 3 questions to check I understood; wait, then correct me. 3. Draft my reply to a director who wants each tester to log 5 bugs a day. ``` > **Success** > > You can turn a metrics request into a decision and a headcount plea into a cost comparison. Next: **Will AI Replace Testers? Make Your Judgment the Evidence**. ## FAQ ### What metrics should a QA manager report? Outcome metrics that answer a question someone is asking: escaped defect rate, open Sev-1 and Sev-2 trend, risk coverage, reopen rate and automation flakiness. Pair any activity metric with an outcome metric, and never rank individual testers. ### How do I justify QA headcount? Price last quarter's escapes as support hours, engineering firefighting and customer recovery work, then compare that failure cost with the cost of the prevention you want, in one sentence, with the trend attached. ### What does a Head of QA do differently from a QA Manager? A Head of QA has almost no hands-on time and owns the organisation's quality strategy and standards, its structure, the budget, the growth of managers and leads, and the career framework, including any IC track.