How to communicate software testing needs to C-Suites
It's not new to say that test automation helps companies deliver better software in shorter cycles. Almost everyone uses 'some' form of it these days, according to a survey last year β although exactly how much of it they use is another matter entirely.
In another study, 79% of testers said that up to 40% of their software hits the market without being properly tested. If you ask CEOs, four in ten say over-reliance on manual testing is a major reason, along with a lack of skilled developers and insufficient time.
However, this has not translated into major concerns, as 85% of CEOs believe it is within acceptable limits to release software that has not been properly tested. Where things get contradictory is that 95% of those same CEOs fear job loss after a software bug.
There is clearly a disconnect here between QA teams and C-Suite. The reason? These two camps speak very different languages. So how can QA teams communicate to C-Suite managers that improperly tested software is not a good idea?
Vice President at Leapwork.
The art of persuasion
Convincing C-Suite executives that test automation is a good thing is like convincing people that vegetables should be in their diet. You want to start the conversation about how they can maximize their chances of survival (and yes, you should really eat that broccoli).
Keep in mind that C-Suite executives (your CEO, CFO, or CIO) are far removed from the ins and outs of software testing. They speak in terms of the bigger picture, which includes cost, quality and time to market. All of these can be significantly affected by software testing.
The good news is that it doesn't take long to prove that point. In 2017, a four-hour AWS outage cost S&P 500 companies $150 million, all because of a single typo a developer made while fixing bugs (yes, ironic). When you break this down further and realize that this means a loss of $37,500,000 per hour, it's easy to see the extent of the damage that can be caused in such a short time.
People can also literally die from buggy software. The most infamous example? Boeing's 737 Max, whose faulty MCAS software (among other things) caused two tragic crashes and 346 lives lost.
Even in blockbuster entertainment, we've seen how poor quality can cost companies millions of dollars in both lawsuits and refunds. That's exactly what happened with 2020's infamous Cyberpunk 2077, a video game so plagued with bad code that Sony removed it from sale on the PlayStation Store.
There are many ways to justify the urgency of good software QA to C-Suite executives, but the point is that without it, poor quality software can bring businesses to a standstill, decimate stock price and revenue, and lead to job losses to lead. , cyber breaches, dissatisfied customers and even loss of life.
How to talk about quality assurance βthe C-Suite wayβ
Think of talking to C-Suite executives about quality assurance and test automation like a sales pitch.
Keep communication clear and concise. Remember, every member of the C-Suite has many demands vying for their attention. Think about the headline you want managers to see front and center, for example: βIf we don't test our software properly, we're going to lose a lot of money and be torn up by lawsuits.β
Show them the bigger picture! CEOs worry about delayed product launches and excessive costs; testers worry about dissatisfied customers and a loss of brand reputation. Your job as a QA team is to connect the dots and explain how the latter can lead to the former.
Skip the jargon! The term 'technobabble' exists for a reason. The moment you start using terms like 'regression testing', you lose the managers.
Use data and show value. If you're trying to advocate for more test automation in your organization, don't walk in unprepared. The C-Suite will inevitably want to see industry data and case studies that justify the transition and demonstrate measurable business results.
Be prepared for the questions they will ask: Executives will ask why automation tools should be prioritized as an investment, how the solution meets regulations, how secure it is, and what additional resources the team needs. Be direct and realistic about this, and be prepared to rebut objections regarding budget, familiarity with existing processes and IT issues.
Quality software should be treated as a fundamental pillar of business success, but the trick is not to assume that your C-suite understands from the start how test automation will get your organization there. At a time when the skills gap is on every IT department's minds, choosing a test automation approach that relies on less coding is critical to mitigating risk and boosting innovation. Please don't talk about regression testing.
We have highlighted the best monitor for programming.