MY EXPERIENCE WITH ENTERPRISE AUTOMATION
July 17, 2026
3 min read
English
66 views
Professional space
#enterpriseautomation
Less info
More info
During 2018, I was working in a Demand Planning department focusing on data management duties. At that time, I used to write notes about my professional experiences, and I recently came across a text in which I reflected on the use of system information across the organisations I had collaborated with up to that point.
By way of general context, up until that year, I worked with companies that relied on proprietary transactional systems housing the commercial information of their core activities, such as telecommunications services, retail sales, and similar operations. A common trait among those systems was that they had been operational for many years and, consequently, felt outdated to me. In some companies, data extraction from these systems was performed by the information technology department, whereas in other cases, I carried out the extraction myself. In all instances, the main objective was always to conduct feasibility studies for new products or services based on historical performance, evaluate efficiency, assess the success of commercial campaigns, prevent claims, forecast sales, and determine the optimal purchasing strategy, among others.
Whether performing manual extractions or requesting them from the information technology team, I always began by applying transformations and calculations that answered the decision-makers' questions numerically. Whenever I identified a recurring transformation, I set out to automate it using the tools I had at my disposal, ranging from Microsoft Excel, VBA, and AutoIt, to Microsoft Access and Microsoft SQL Server.
Automation proposals for data extraction and transformation were almost always well received by the departments and companies where I worked, as they pursued operational efficiency and process simplification. However, they were rarely analysed in depth by the team, and the subsequent transfer of knowledge regarding the automation had a vulnerability in terms of maintenance and continuous improvement. As a company evolves, automation workflows and their enhancements inevitably need to be reconsidered.
Data extraction and transformation tasks may begin as a pilot project; however, if they add value and align with company strategy, they ought to be candidates for becoming formal projects, ideally carried out by an information technology department. Nevertheless, sufficient technological maturity does not always exist to implement a solution that automates decision-making. This stems from various factors: perceived loss of autonomy and control within analytical teams, initial deployment and future maintenance budgets, overall technological maturity, and guidelines for data governance, among others.
From an operational perspective, however, in every automation project I have participated in, adapting to diverse corporate circumstances, it has always been immensely satisfying to identify areas for improvement and to assist teams in converting complex extraction and transformation processes into a set of executions and button clicks. This minimised repetitive operational tasks and enabled a sharper focus on higher-value activities, such as the in-depth analysis of efficiency indicators, dashboard reviews, and numerical decision-making.
On a recurring basis, I made applications available to operational professionals that displayed the outcomes of these extraction and transformation processes to assist in decision-making as an effective adoption strategy. These applications seamlessly integrated into the department's day-to-day workflows and came to be viewed as indispensable operational tools once their added value was proven and the information technology department approved their use and provided ongoing support.
Following years of progress, it is highly likely that the fundamentals of how operational improvements emerge remain valid. Nevertheless, I am certain that implementing applications driven internally by business departments still encounters the very same difficulties. This is particularly evident with the emergence of agentic technologies which, although delivering value and efficiency in isolation, must pursue a joint implementation aligned with corporate strategy. This presents notable challenges regarding precision, availability of valuable information, costs, technical requirements, and the capabilities of development teams. Yet, wherever an idea for improvement exists, there is purpose and an entrepreneurial drive.