All automation is not alike, and if you are taking an Elemental Approach to your automation, you will miss out on the time and cost saving benefits that an Architectural, Layered Approach can provide. An approach to automation that allows you to manage your Workload Automation, IT Process Automation, Managed File Transfer Automation, Big Data Automation, and more, can enable you to streamline processes, coordinate and consolidate silos of automation, and scale and adapt to changing organizational requirements.
At a recent conference, Tracy Fleming from Avaya touched on both "digital transformation" and "automation." But in terms of helping IT make better technology decisions, there's more to consider. Not only must they be properly understood at face value, but also for setting broader strategy around new technology adoption. Making these plans should always be closely tied to business objectives, and that's actually where the difficulties lie. I've written before about how amorphous the term "digital transformation" can be, and the conversation easily gets muddier when loosely connecting it similarly amorphous terms like "cloud" and "Unified Communications."
A colleague of mine once quipped that automating a'crap' process just results in'automated crap,' and while the language might be a bit uncouth, the sentiment is absolutely correct. It can be tempting when tasked with automating a process to immediately start considering the systems and software to deploy; however, it's worth determining whether the process is currently valid, effective, and necessary before diving into automating it. Furthermore, some processes simply should not be automated. Sometimes pure technology is not the right answer for process automation, as the whole offshore process outsourcing business can attest to. While there are myriad risks and considerations to process outsourcing, considering non-technology options for process'automation' should be part of your evaluation and due diligence process.