How to Lead a QA Team — The First 90 Days (2026)

Last updated 2026-07-20 · 12 min read · By Avinash Kamble, reviewed by Priyanka G.

The jump from senior QA engineer to QA lead is bigger than any other move in a QA career — your output is now the team's output, and your worst habit becomes team culture inside 60 days. This is the 30-60-90 playbook I hand every new QA lead I coach, distilled from watching a dozen transitions succeed (and three fail).

Key takeaways

• The 30-60-90 structure.
• 5 listening-tour questions that surface real problems.
• How to pick a quick win that is not theatre.
• The one hiring mistake to avoid.

Do NOT ship a new strategy in the first 30 days. Instead, run 1:1s with every team member, every engineering manager, and 5 developers. Ask:

1. What is the most painful part of shipping software here?
2. What is the best thing QA does today?
3. What is the worst?
4. What would you change if you had a magic wand?
5. Who on this team is most senior — and who is most under-utilised?

Pick something small, visible, and cheap. Good candidates: cut CI pipeline duration in half, kill 20 flaky tests, ship a defect dashboard, run a bug bash with product. Avoid tool migrations, org restructures, or hiring pushes in this window — those are quarter-2 moves.

A one-page quality strategy: 3 outcomes for the next 6 months, the 5 metrics you will measure, and the 2-3 workstreams to get there. Share it with your team first, then engineering leadership. Use the QA metrics guide for the measurement half.

Do NOT clone yourself. The most common failure is a new lead who was a great automation engineer hiring 3 more automation engineers — and ends up with no exploratory, no process, and no accessibility skill on the team. Map skills you have vs skills you need first. Reference: Mind the Product — first 90 days. Related: SDET roadmap, shift-left playbook.