#6 QA Automation Buy-In: How to Make Them Pay

The quest for QA automation buy-in can be more challenging than debugging a complex code on a Monday morning while riding a burning bike.?

This journey is often riddled with skepticism and budget constraints, yet it is crucial for future-proofing QA processes.

As an outsourcing company, we normally step in when the green light for automation is already on.?

But, oh, the tales we hear!?

The struggles endured to make QA automation projects happen!

So, we have pieced together a QuickBytes issue on QA automation buy-in — why it is so challenging to achieve, and how to achieve it with less friction.

(This will be a long one, but the topic demands some digging into.)?

Why Is It So Hard to Get a Buy-In on QA Automation?

Understanding gap?

You know the QA field, you see the trends and the risks, and you are anxious about the lack of up-to-date automation in your company.?

This knowledge, however, is not universal.?

People whose approval you struggle to get may see the request as “Let’s pay (tens of) thousands of dollars for the algorithm to do my job.”?

Not too inspiring.

Cost concerns

The initial investment in automation tools and training can seem steep. It actually may be steep. More of it, your company may truly not have the funds right now. But when they do have them, what will they invest in?

Comfort with status quo

Change is hard. Teams may prefer sticking to familiar processes over exploring new, automated options, especially when the benefits aren't immediately obvious. “This is how we do it, and it works for us,” is a common argument, though, often, “it” actually doesn’t work anymore.?

Immediate results vs. future gains

In the current economy we all slide into survival mode from time to time. We just want to make it to the next quarter.?

The focus on short-term results can often overshadow the long-term advantages of automation, making it harder to justify the transition.?

Paying now to see financial return even in half a year may seem like a stretch to decision makers.?

Integration challenges

Integrating new automation tools with existing systems may look too challenging, and potentially disruptive.?

In reality, if a company you hire to automate has been doing it for years, 90% of compatibility tweaks will be done without a squeak.?

Organizational culture?

The existing culture in an organization may not support technological innovation. Honestly, this one is truly hard to beat. As Peter Druker rightly said “Culture eats strategy for breakfast.”?

We have hired excellent QA engineers leaving loud-name enterprises with a stuffy, retrograde culture opposing any significant innovation. Now, they are among our best automation QAs, because they truly enjoy an opportunity to change clients' systems for better.?

The reasons for buy-in challenges are clear. What’s next?

Move the Needle Towards QA Automation Buy-In

There is a kind of “practical tips” we hate.?

They are cliche, superficial and theoretical, and may be summed up as an advice to “Preferably get born smart, handsome and healthy into a rich and loving family.”

Thank you for your advice, why didn’t we think about it before?!?

Our tips are more realistic, promise.?

Find Market Proofs: Cases, Numbers, Charts

Saying “Everyone automates, it is efficient, we should do the same” or even “X and Y competitors definitely use automation, let’s not tag behind,” is not enough.?

Here is what our AQA Team Lead, Taras Oleksyn, offers instead:?

“You need to draw a clear “if — then” picture in the decision-makers’ minds. If we automate, here are the results we can expect. This is why we want them. Here is how it works.

Gather quantitative data to support your QA automation offer and distill it for the most striking insights. Every source works — cases on outsourcing companies’ websites, MinistryOfTesting, LinkedIn, Reddit. If you put your mind to it, you can dig up convincing numbers and use cases.This research work may take weeks — don’t give up after the first useless 5-10 Google links.?

Put the numbers together, use charts and graphs, when possible. Don’t overwhelm the stakeholders. Small but coherent nuggets of QA automation truth are better than an endless PDF full of theoretical fluff and random numbers.”

Translate Tech Speak into Decision-Maker Language

Translate the benefits of QA automation into the language of business outcomes decision makers strive for. What you say should press their P&L buttons, instead of boring their tired minds.

Showcase Immediate Wins with Automation

Choose a small, yet critical area in your current process where automation can quickly show results. Now, we don’t know your process and your qualification, but here is an example of how you may do it.

1. Choose an “immediate win” field. For example, automate the regression testing process for the most commonly used features of the web application.
2. Select the top 3-5 most frequently used features by users, based on usage data.
3. Create automated test scripts specifically for these key features.
4. Set up these automated tests to run automatically every time there’s a new code commit or at regular intervals.
5. Track the time taken for automated tests versus manual testing, along with the number of defects caught.
6. Prepare a concise report or presentation showcasing the before-and-after scenario. Highlight the reduction in hours spent, increased frequency of testing, improved accuracy, and how the QA team’s time is now being utilized more effectively.
7. Emphasize the broader business impact.

Acknowledge the Costs and Risks, Offer a Perspective

Decision makers need to see that you get their side of things – the costs, the hassle, and the why now?

When bringing up automation, try to avoid the image of a tech geek chasing the next shiny thing. Be the practical one. Someone looking out for your team’s future.

Be upfront.?

Be the person who gives the idea, acknowledges the challenges and offers solutions. It only works 3 in 1.?

Yes, automation has costs. And yes, there may be bumps along the way, like figuring out how it fits into your current workflow.?

And if you're looking for support in making a compelling case for automation, our company can help. We can assist in drafting your automation strategy, and we even offer a commission if we land the project.?

In the end, the result matters more than how you get there, and if automation is an answer for your project, the longer it takes, the more difficult it gets.?

Ace your tests, enjoy your breaks, stay up to speed with QuickBytes.