Technology Is Not the Transformation
We are living through an extraordinary time. ERP systems, automation, analytics, artificial intelligence, agents, and robotics promise to transform the way organizations operate. Yet before investing, we should ask an uncomfortable question: are we using technology to build the company we want to have, or simply to do faster what we are already doing poorly?
A business transformation occurs within a system. External variables—market, customers, competitors, regulation, legislation, and industry-specific conditions—interact with internal variables—strategy, structure, culture, organizational climate, capabilities, people, and processes. Most of these are not technological.
That is why technology is the third pillar—not because it is less important, but because its real power emerges when it accelerates something we have first understood and deliberately designed. We must first understand where we want to go and the context in which we compete. Then we must determine how the organization and its processes should work. Only then should we ask what technology can enable, accelerate, and scale that design.
Technology is not the transformation. It is an accelerator of transformation.
The Story of an Invoice
Some years ago, at a company in a country I will not identify, a customer returned to the counter where he had purchased an automotive product. He had lost his invoice and needed a copy. He provided the approximate date, time, and his details. After about fifteen minutes of searching, the employee found the document, made a photocopy, and the grateful customer left.
The employee thought, «To make sure this never happens again, I’ll keep all the invoices here.» He created a folder. Soon there were too many invoices. He then grouped them into bound volumes and arranged them alphabetically. The volumes kept multiplying until they filled an entire wall. Eventually, he developed an application to identify which volume contained each customer’s invoice.
He had created a procedure, bound volumes, physical storage, administrative work, and a system used almost exclusively by him. Everything looked organized and efficient.
There was only one small detail: no customer ever asked for a copy of an invoice that way again.
The question is not whether the solution worked. The more uncomfortable question is: was there ever a problem significant enough to justify building it?
Technology can turn an unnecessary process into an extraordinarily efficient one. It will still be unnecessary. That is digitized inefficiency.
A Company Is a System, Not a Collection of Departments
The story also reveals another common problem: local optimization. From the perspective of his own area, the employee acted reasonably. He saw a difficulty and solved it. Then he improved his solution and ultimately digitized it. What never happened was a cross-functional view of the entire business ecosystem.
How often does something similar happen? Sales optimizes Sales, Finance optimizes Finance, Operations optimizes Operations, and Technology implements a new tool. Each function may improve its own metrics, while the company as a whole ends up with more friction, controls, interfaces, and complexity.
A company is a system. Transforming it requires understanding the connections among customers, people, processes, information, structure, regulation, and objectives. Local optimization is not business transformation.
The Danger of Starting with the Solution
This is also where the issue of packaged solutions appears. Standard software is not the enemy; many solutions are excellent and allow companies to adopt proven practices quickly. The problem begins when we buy the tool before understanding the problem and end up adapting the business to the technology without first questioning how the business should actually work.
Today, the risk is even greater. «We need AI,» «we need agents,» and «we have to automate» are increasingly common statements. But one fundamental question is often missing: to solve what?
Before automating, we should understand the context, define the problem, challenge the current process, redesign it, assess the organizational and human implications, identify the capabilities required, and only then select the appropriate technology. After that, we must implement and measure value—not simply count installed features.
One simple question can prevent surprisingly poor investments: if this process did not exist today, would we design it this way again? If the answer is no, it is probably not yet time to automate it.
Technology should enable the way the company needs to work tomorrow, not digitally preserve the way it worked yesterday.
One Question Before the Next Investment
The Third Pillar was born precisely from this concern. We are living through one of the greatest technological accelerations in history, but access to more technology does not guarantee better decisions. AI, automation, robotics, analytics, and technologies yet to emerge can create extraordinary value. They can also help us execute faster, at greater scale, and with greater sophistication things we should never have been doing in the first place.
Before approving your next technology investment, ask one uncomfortable question:
Are we transforming the way we work, or simply digitizing our inefficiency?
Have you seen something similar in your organization? Share your experience. Perhaps questioning a practice everyone takes for granted is the real first step toward transformation.
“Technology should enable the way the company needs to work tomorrow, not digitally preserve the way it worked yesterday.”