Third party testing
Third party testing
Third-Party Testing: Staff Augmentation Done Right
Third-party testing often sparks heated debates—should we use external vendors or keep everything in-house? There are strong opinions on both sides, and I’m happy to share my take (and keep the conversation going if you want to dive deeper).
My Stance: It’s All About Staff Augmentation
I have no problem with third-party testing—under the right conditions. Here’s what matters most to me:
1. It’s for Staff Augmentation, Not Cheap Labour
The fastest way to destroy morale and your reputation is to lay off full-time staff and replace them with cheaper third-party resources. That’s a recipe for bad press and even worse culture.
Staff augmentation should be about handling extra workload so your teams can deliver more when the pressure’s on. Third-party vendors can quickly bring in skilled people—often within a week or two—compared to the month or more it takes to hire directly in North America.
2. Scaling Up, Fast
Most vendors are built to scale. Need one extra tester? Ten? They can usually make it happen quickly. Sure, there might be the occasional hiccup, but it’s still typically much faster than hiring internally.
3. Quick Turnaround When Needed
If a third-party resource isn’t working out or leaves unexpectedly, vendors can often provide a replacement fast. That flexibility is a huge advantage.
Common Concerns (and My Perspective)
Argument #1: “They’re Going to Replace Our Jobs.”
I used to brush this off—until I saw it happen. The right approach is to utilize third parties to augment your staff, rather than replace them. When used effectively, these resources take over routine tasks, freeing your core team to focus on more complex and meaningful work. But yes, that message must be clear and consistent from leadership, or trust will erode.
Argument #2: “They Don’t Know Our System.”
That’s true—but so is every new employee’s first day! There’s always a learning curve, and you wouldn’t hand a new junior analyst a complex project on day one. The same logic applies to third-party testers. Invest in onboarding and training, and set realistic expectations for their initial contributions.
Argument #3: “The Time Delay Is Unmanageable.”
Time zones can be annoying, but they’re rarely a deal-breaker. With today’s communication and workflow tools, most vendors are flexible and will work around your schedule to keep things moving. Many successful organizations have successfully implemented this model.
Overcoming Fear of the Unknown
A significant amount of resistance to third-party testing stems from fear—especially if it’s a new experience for your team. However, once people see it for what it is—staff augmentation, not replacement—it can be a win for everyone. By offloading repetitive or lower-value work, your in-house team can focus on innovation and the “fun stuff.”
The Bottom Line
The key to successful third-party testing is clear intent: staff augmentation, not replacement. This message must come from the top and remain consistent. Any deviation erodes trust, productivity, and ultimately, quality.
Curious about how third-party testing could help your team scale and innovate? Let’s talk about how to do it right—so everyone wins.
"I help create ecosystems that become legacies.”
- Jeremy Berriault
Quick Links
Hours of Operation
Monday - Friday
9 am to 5 pm
Saturday - Sunday
Closed