Main Takeaways
- Quality is trust, not just test cases. QA leaders who speak in terms of customer trust and business risk gain more support and influence.
- Success metrics shift constantly. Teams must adapt their quality strategies to align with evolving company goals, especially during periods of change.
- Sometimes you need specialists, not support. External QA teams with focused objectives can drive stalled initiatives across the finish line.
- Pushback earns respect when grounded in value. Firm, data-driven quality standards can build long-term credibility, even in diplomatic environments.
- Don’t silo your QA partners. Whether internal or outsourced, QA only works when embedded in the product, process, and people, not treated as a separate fix-it function.
Bugs slipping into production, missed release dates, pressure from the board to ship more features, faster. These pressures are the daily reality for engineering leaders. We often look for solutions in new tools or processes, but what if the most powerful shifts in quality aren’t about what we do, but how we think and talk about it?
In a recent discussion between two agency leaders, Jay Aigner of JDAQA and Ben Fellows of Loop QA, we were struck by a recurring theme: the most effective QA leaders don’t talk about test cases; they talk about trust, risk, and business alignment. They speak the language of the C-suite. Their insights, forged from experience across dozens of companies, reveal some surprising truths that can help any team – whether internal or outsourced – reframe the conversation and elevate the role of quality.
1. Quality Isn’t a Technical Problem, It’s an Emotional One
The first and most fundamental shift is to stop talking about quality in purely technical terms. Ben Fellows argues that quality is ultimately about trust, a deeply emotional concept. When your product fails, it’s not just a bug; it’s a broken promise to your customer. This creates a tangible “emotional toll” that ripples through the entire organization, from the customer service team facing angry users to the developers doing late-night hotfixes.
Fellows powerfully contrasts the ongoing trust relationship of a SaaS product with a one-time transaction. A customer buying a pair of Nike shoes has a simple exchange, but a user relying on your software day after day is in a long-term relationship built on trust. QA’s job is to protect that relationship.
“What we say internally is we provide a technical solution for an emotional problem, right? Like, ultimately, quality comes down to the word trust.”
This isn’t just a clever line; it’s a strategic reframing. When you can articulate the value of QA in this “CEO language,” you move the conversation from bug counts to business impact, making it far easier to secure the buy-in and resources you need.
2. Your Team’s “Definition of Success” Is a Moving Target
Aigner and Fellows offer a powerful framework for ensuring your team’s work is always seen as valuable. It requires recognizing three realities: everyone in the organization has a “definition of success,” your team’s value is measured by how well you align with it, and most critically, that definition is a “living thing” that will change.
For example, a company might initially define quality success as “zero bugs in production.” But a year later, amid budget cuts, that definition might silently shift to “the best quality outcome for the cheapest possible spend”. A QA team that continues to operate under the old definition, demanding perfection at any cost, will suddenly be seen as out of touch and inefficient, even if their work hasn’t changed.
For any QA leader, the lesson is clear: constantly re-evaluate and align with the organization’s shifting priorities. Failure to adapt to this moving target is one of the fastest ways for a high-performing team to be perceived as unsuccessful.
3. Sometimes You Need “Assassins,” Not Just an Extra Pair of Hands
Many large companies have a graveyard of “half-baked” automation projects. According to Jay Aigner, these initiatives start with great intentions but are abandoned when the internal team gets pulled away to “fight other fires”. The project languishes, a monument to divided focus.
This is where an external team can act not just as help, but as “assassins.” Free from internal politics and the crisis-of-the-day, they can be deployed with a singular, ruthless focus: get the project done. This model isn’t about adding headcount; it’s a direct countermeasure to the internal fire-fighting culture that stalls strategic progress. It’s about deploying a dedicated force to break through organizational inertia and finally complete those critical, long-delayed initiatives.
4. In a World of Diplomacy, Pushing Back Can Earn Respect
QA leaders must walk a tightrope, acting as both a diplomatic partner and an unyielding guardian of quality. How do you push back without alienating the very teams you need to collaborate with?
Aigner points out that external teams must be highly “diplomatic” to navigate client relationships without the safety of being a full-time employee. Yet, Fellows offers a fascinating counter-point: “strength respects strength”. He argues that QA professionals earn more respect over time by being firm, communicating standards clearly, and holding the line on quality. The tension between these two stances reveals a crucial truth about organizational power.
Fellows provides the key to this paradox when he notes the structural advantage an external team has in these confrontations: “what’s the worst that they can do? Fire us? Like, we’re an outsourcing firm, so it’s not like it’s the end of the world.”
This political freedom allows them to advocate for quality without fear of internal reprisal. While internal teams can’t adopt such a cavalier attitude, they can learn from the mindset. By grounding their pushback in shared business goals and objective data (rather than personal friction), they can defend product quality with authority while still playing the long game of building collaborative relationships.
5. Stop Treating Your QA Partner Like a Silo or a Band-Aid
Drawing from years of seeing engagements succeed and fail, Jay Aigner identifies two critical mistakes companies make that doom QA initiatives from the start: treating the team as a silo or as a band-aid.
The first mistake is treating QA outsourcing as a silo. The old model of “throwing it over the fence” to a disconnected team in another time zone is dead. For alignment and effectiveness, a QA team – internal or external – must be deeply embedded, working in the same sprints, using the same tools, and collaborating in real time.
The second is underestimating onboarding and looking for a quick “band-aid fix.” It takes significant time for any person to become a subject matter expert on a complex product and integrate into a team’s culture. Expecting immediate, magical results is a recipe for disappointment. This reflects a common failure in leadership: viewing QA as a tactical expense to be minimized, rather than a strategic investment in customer retention.
A New Language for Quality
These truths are about more than just managing a QA team; they represent a fundamental shift in perspective. They challenge us to move beyond talking about tools and bug counts and start speaking the language of business value. By reframing quality as a driver of customer trust, aligning our work with a living definition of success, and communicating our standards with confident diplomacy, we can change the conversation.
Adopting this new language is the key to unlocking resources, earning respect, and transforming QA from a cost center into an indispensable strategic partner. Looking at your own team, which of these truths could you apply tomorrow to change the conversation about quality?
