People, Resources & Scheduling
Building high-performance quality cultures. Managing the "Who, What, and When" of testing.
1 The Hook
A Test Manager in Wellington was hired to "fix" a team that was missing every deadline. They found 10 talented testers who were burnt out because they were being used as "human bug-checkers" at the very end of the sprint. By changing the team's structure and coaching them on **shifting-left**, the TM reduced burnout and increased throughput by 40% without hiring a single new person. Management isn't about moving boxes on a chart; it's about unlocking the people inside them.
Senior engineer insight
The moment that changed how I think about people management was realising the Skill-Will Matrix only works if you actually know which quadrant someone is in — and most managers guess wrong. I had a Senior Tester pegged as "Low Will / High Skill" and almost put her on a performance plan. Turns out she was doing two jobs because we'd lost a headcount and nobody had told her the workload was permanent. Once I fixed the workload, she became the team's highest performer inside six weeks.
The most common mistake new Test Managers make is diagnosing a motivation problem when they actually have a workload or clarity problem — treat the cause, not the symptom.
From the field
A Wellington financial services QA team assumed their underperforming tester was "not cut out for the role" and asked HR to begin a PIP under the Employment Relations Act 2000. When we actually ran a structured 1:1 to ask what was going wrong, the tester revealed he had never received onboarding documentation and had been guessing the test process for four months. The team had confused poor output with poor capability. We cancelled the PIP, assigned a buddy, and documented the actual process. Within two months he was mentoring a new junior. The lesson that generalises: under New Zealand employment law, a PIP that skips a fair and reasonable process is a legal liability — but more importantly, it's a management failure before it's an employee failure. Always diagnose before you escalate.
2 Resource Management: The "Who"
Test Managers don't just assign tasks; they manage **Capabilities** and **Dependencies**.
Skills Matrix
A map of your team's technical skills (Automation, Security, API). Identifies single-points-of-failure (e.g. "Only Dave knows the legacy DB").
Capacity Plan
Predicts how many "testing hours" you have available vs. what the projects need. Factors in leave, training, and BAU support.
The Pro-Tip: Always maintain a 20% "Buffer" in your resource plan. In testing, the unknown always happens (environment crashes, critical bug outbreaks). If you plan for 100% capacity, you are planning for failure.
3 Master-Level Scheduling: The "When"
Test schedules are the most volatile part of any project. You must manage them with **Agility** and **Buffer Zones**.
| Phase | What Happens | TM's Role |
|---|---|---|
| Static Testing | Requirement reviews, Design audits. | Ensure testers are in the meeting before code is written. |
| SIT (Integration) | Testing how systems talk to each other. | Manage the environment schedule and data availability. |
| UAT (User) | Business users verify the value. | Act as the facilitator. Provide the "Safe Space" for users. |
| Regression | Ensuring old things still work. | Schedule automation runs to minimize manual overhead. |
"The Testing Squeeze."
Dev takes 2 days longer than planned, but the release date stays the same. The testing time is cut in half. **The Test Manager's Job:** Negotiate the scope. If time is cut, the "Must-Tests" must be re-prioritised. You cannot do 2 weeks of work in 1 week without increasing risk. State the risk, don't just "work harder."
4 The Skill-Will Matrix
How to manage the individual people in your team based on their profile.
| Quadrant | Profile | Management Action |
|---|---|---|
| High Skill / High Will | Your star performers. | Delegate. Give them autonomy and stretch projects. |
| High Skill / Low Will | Experienced but disengaged. | Excite. Find out what's blocking them. Pivot their role. |
| Low Skill / High Will | Eager juniors. | Guide. High coaching, clear instructions, frequent feedback. |
| Low Skill / Low Will | Underperformers. | Direct. Set strict goals and manage closely (Performance Plan). |
5 Career Ladders & Hiring
Building a career pathway keeps talent engaged and reduces turnover. In NZ's tech market, losing a Senior Tester costs 6-9 months of recruitment and onboarding.
QA Career Ladder: From Junior to Manager
| Role | Years XP | Key Competencies | NZ Market Salary Range |
|---|---|---|---|
| Junior Tester | 0-2 | Manual testing, test case writing, basic automation, following instructions. | $55-70k |
| Middle Tester | 2-5 | Automation in Python/Java, risk analysis, mentoring juniors, stakeholder communication. | $70-95k |
| Senior Tester | 5-8 | Test architecture, design decisions, leading squads, performance & security testing. | $95-130k |
| Test Lead | 8+ | Strategic planning, process improvement, vendor management, budget ownership. | $130-160k |
| Test Manager | 8+ | People development, org design, governance alignment, executive reporting. | $150-200k+ |
NZ-Specific Insight: Auckland and Wellington talent markets are tight. Expect 15-20% salary premiums for remote-anywhere roles. Many NZ testers are remote-first, so your hiring pool includes Australia and APAC.
Hiring Rubric Template
Use this during interviews to score candidates objectively.
| Competency | Interview Question | Score (1-5) | What You're Looking For |
|---|---|---|---|
| Problem Solving | "Tell me about a time you found a bug that stopped the team. How did you debug it?" | __ | Do they think systematically or just randomly click? |
| Communication | "Explain a recent project to me as if I were a non-technical stakeholder." | __ | Can they simplify complexity? Do they blame developers? |
| Automation Skills | "Describe your approach to test automation. What's a framework you've used?" | __ | Real experience or just "read the tutorial"? Can they defend design choices? |
| Growth Mindset | "What's a skill you've learned in the last year?" | __ | Continuous learners adapt to new tools and stacks. |
| Resilience | "Tell me about a failure and what you learned." | __ | Do they own mistakes? Do they learn from them? |
6 The 1:1 Meeting Framework
Weekly 1:1s are your primary tool for keeping people engaged and catching problems early. A 30-minute 1:1 costs you 30 minutes; skipping it costs you 10 hours of burnout or turnover.
Template: Weekly 1:1 Agenda (30 mins)
- 5 mins: Check-in. "How are you? Anything on your mind?" Let them lead.
- 5 mins: Wins. "What did you ship this week that you're proud of?" Celebrate small wins.
- 10 mins: Blockers. "What's slowing you down? Anything I can unblock?" Listen for patterns (unclear requirements, broken tools, toxic teammates).
- 5 mins: Growth. "What skill do you want to develop? How can I support you?" Point to training, projects, or mentors.
- 5 mins: Feedback. "Here's what I observed this week..." (Specific, timely, actionable. Not vague.)
The Red Flag: If someone says "Nothing's wrong" every week but seems withdrawn, ask directly: "I've noticed X. Is everything okay? Can I help?" Don't assume silence means contentment.
7 Diversity, Equity & Inclusion in Testing
Building a diverse testing team isn't just ethical; it's strategic. Diverse teams find more bugs because they think differently. Neurodivergent testers often excel at edge cases and detail work.
Inclusive Hiring Practices
- Remove degree requirements. Many great testers didn't finish university. Assess skills, not credentials.
- Offer structured interviews. Vague "tell us about yourself" questions advantage people with confident communication styles. Use the Rubric above instead.
- Provide accommodations. Offer interviews in text if verbal is hard. Provide code samples in advance if live-coding is requested. Neurodivergent candidates often need 24-hour notice.
- Advertise salary ranges. Hidden salary perpetuates pay inequity. NZ Equal Pay Act 2020 is strengthening enforcement. Be transparent.
Managing Neurodivergent Testers
Autism, ADHD, dyslexia are common in tech. With small accommodations, these people become your best testers.
| Neurodiverse Trait | Strength for Testing | Support Strategy |
|---|---|---|
| Pattern Recognition (Autism, ADHD) | Spots patterns other testers miss. Excellent at regression testing. | Pair them on detailed, systematic work. Avoid ad-hoc interruptions. |
| Hyperfocus (ADHD) | Can deep-dive into a single problem for hours. Finds root causes. | Let them own complex issues. Don't interrupt during focus mode. |
| Literal Thinking (Autism) | Catches edge cases. Tests exactly what the requirement says, not what was "meant." | Give written, explicit requirements. Avoid idioms like "just try it." |
| Sensory Sensitivity (Autism, ADHD) | Notices UI glitches, typos, colour contrast issues others miss. | Offer quiet workspace. Meetings on mute acceptable. Video optional. |
8 Performance Reviews & Development Plans
Annual reviews are too late to fix problems. Monthly check-ins + quarterly reviews keep people on track.
Quarterly Review Template
Reviewer: [Name] | Employee: [Name] | Period: Q2 2026
1. What went well this quarter?
Example: "You led the API automation framework redesign, mentored 2 juniors, and reduced test flakiness by 30%."
2. One area for growth?
Example: "Communication in standups is sometimes unclear. Let's work on explaining test results in non-technical terms."
3. Development goal for next quarter?
Example: "Complete the 'Advanced Python' course by end of Q3. I'll sponsor the cost ($500)."
When to Escalate: The Performance Improvement Plan (PIP)
Wrong: Surprise PIP without prior 1:1s
By the time you write a PIP, the employee should already know they're struggling. This should be the 3rd or 4th conversation, not the 1st.
Right: Clear escalation path
Month 1: 1:1 feedback. Month 2: Written warning + coaching. Month 3: PIP with specific metrics. Only if they fail the PIP do you terminate.
Why teams fail here
- Skipping 1:1s during crunch — exactly when people most need them — so small problems compound into resignations or personal grievances under the Employment Relations Act.
- Using a one-size-fits-all management style across the whole team instead of adapting to each individual's Skill-Will profile, leaving star performers bored and juniors overwhelmed.
- Building a Skills Matrix but never acting on the key-person dependency risks it surfaces — so when the one person who knows the legacy system goes on parental leave, the entire release is at risk.
- Treating performance management as a paper trail for eventual termination rather than a coaching process, which both fails the individual and exposes the organisation under NZ's good-faith employment obligations.
Key takeaway
Your job as a Test Manager is not to manage tasks — it is to remove every obstacle standing between talented people and the work they are capable of doing.
9 Self-Check
Q1. What should a Test Manager do during the "Testing Squeeze"?
Communicate the increased risk to stakeholders and re-prioritise the test scope. Never promise the same level of quality in half the time.
Q2. Why is a "Skills Matrix" critical for resource management?
It identifies "Key Person Dependency" risks. If only one person knows how to test a critical system, your schedule is at risk if they leave or get sick.
Q3. What's the first thing you should ask in a 1:1 meeting?
"How are you? Anything on your mind?" This sets a safe space and lets them lead. Don't jump straight to work tasks.
Q4. Why should neurodivergent candidates be considered an asset?
They often excel at pattern recognition, detail work, and edge case testing. With proper support, they find bugs others miss.