A well-developed test automation strategy provides real benefits if done correctly. It involves restraint and tactical thinking and can be a string of simple efficiencies or a larger initiative. Whatever your organization ends up doing, do not be fooled by grandiose promises—you know what is best for your organization.
Embarking on such a program requires a strong business case. It is very difficult to convince management to provide budget for something called “automation” if it does not result in reduced testing staff and faster delivery in a very short period of time. Be careful when promising these things. Test automation does initially require more staff. You are doing more testing when you introduce an automation program.
The true benefits are higher-quality software—not an immediately smaller staff or shorter release cycles. Those benefits come much later, but they do come.