We live in an era in which speed seems to matter more than direction. Tasks are carried out, processes are automated, and technologies are adopted with a sense of urgency that rarely leaves room for reflection. Automate, integrate, optimize… these are words that sound like innovation, but on many occasions, they simply describe movement without direction.
We invest heavily in innovative platforms, AI, and automation solutions, convinced that technology alone will transform the organization. But accelerating something without understanding what is being accelerated is not transformation; it is haste. And sometimes, it is self-sabotage.
The real problem is not technology itself, but the lack of prior understanding of how and where to apply it. The rush to demonstrate results leads organizations to digitize without truly understanding how their processes work. And when that happens, technology does not organize; it amplifies. If the process is sound, technology propels it forward; if it is confusing, it simply accelerates the disorder.
The Speed Trap
We frequently encounter statements such as: “We need to automate all of our processes this quarter” or “We need to implement an artificial intelligence assistant.”
However, the questions that follow are rarely addressed: “Was this really the process we should have automated?” “Why isn’t the implemented tool being used?” “Why do our workflows remain unchanged?”
In my view, the answer is usually the same: processes are not truly understood before they are changed.
Several studies, including those conducted by Boston Consulting Group (BCG) and McKinsey & Company, indicate that only 30% to 35% of transformations achieve their objectives and generate sustainable change. The difference does not lie in the tool itself, but in how and where it is applied.
The challenge is not a lack of technology, but a lack of knowledge about how to implement it in alignment with strategic objectives.
When organizations understand isolated and disconnected activities but lack a clear understanding of their complete operational processes, exceptions, temporary workarounds, and improvised assessments emerge to mitigate shortcomings that technology has failed to resolve. In these situations, digital transformation becomes a façade: digital in appearance, but manual in execution.
Diagnosing Chaos
It is more common than we might think to find organizations with repeated activities performed by people from different departments, gaps in accountability, duplicate processes across different systems, Excel macros supporting critical operations, or decisions that depend on a single person “who knows how it works.” This is the reality that does not appear in reports but defines day-to-day operations.
Organizational culture has a predominant influence on strategy. Departments tend to protect their own operating methods, creating fragmentation that makes it difficult to develop an integrated view and, consequently, achieve true transformation. Technology implementation is hindered by silos perpetuated by organizational culture, and a digital architecture cannot be sustained by a culture that does not understand its own processes.
In many organizations, people have performed their roles autonomously within their departments for years. From their perspective, no one is better positioned than they are to provide valuable insights into how things could be improved from a broader, long-term perspective. This lack of cross-functional knowledge is one of the main obstacles to any transformation initiative.
When each area prioritizes its own procedures and objectives, technology encounters an intangible barrier: the inability to integrate what organizational culture keeps segmented.
Despite this, we continue to believe that acquiring state-of-the-art tools will solve the problem.
Understand Before You Change
Understanding is the quintessential transformative act: modeling a process is not merely a bureaucratic exercise, but a way of revealing what is otherwise imperceptible. This involves identifying and defining the steps, roles, and decisions that underpin the process.
Representing a process, even through a simple diagram, has a powerful effect: it establishes a common language among those involved. This shared understanding is the foundation of every sustainable improvement.
For this reason, I firmly believe that, before automating or implementing advanced solutions, organizations should prioritize investing in visibility. This means mapping, understanding, and reaching a consensus on how their processes actually work. Visualizing workflows is the first crucial step toward aligning strategy with operations.
Visualizing workflows is the starting point for aligning strategy with operations. Organizations that understand their activities not as independent entities, but as interconnected value-generating chains, achieve more significant progress and require fewer corrections before making investments. The key is not to increase spending, but to optimize how resources are allocated.
Visualizing the connections between processes and resources creates a shared understanding and consensus around the future solution.
Diagrams should not prioritize visual aesthetics at the expense of functionality. Their primary purpose is to provide accurate information about the current situation and possible paths forward, facilitating a thorough understanding of the processes and data involved.
This is when automation and technology implementation can truly accelerate the execution of processes and procedures that have already been understood.
AI: The Copilot
Artificial intelligence is a captivating technology. However, in many organizations, it has become a recurring mantra: if a solution does not incorporate “AI,” it is perceived as lacking innovation.
Still, artificial intelligence is not an all-powerful solution, but rather a highly powerful tool in the hands of those who know how to ask the right questions.
Consequently, when we lack an understanding of the interconnections between activities and operations within an organization, AI can also help us with much more “ground-level” tasks before we embark on advanced implementations, such as identifying hidden workflows, detecting bottlenecks, and even suggesting improvements. However, having a clear view of organizational objectives remains essential.
The same AI that summarizes reports or answers questions can be deployed as an analytical copilot that brings underlying processes to light.
In environments characterized by low process management maturity, I believe its intrinsic value is particularly evident during the discovery phase, when processes have not yet been properly defined and are often not explored in sufficient depth because of the rush to reach an ideal TO-BE state.
At these maturity levels, technology, particularly AI, enables a rapid and in-depth understanding of the organization. It can quickly transcribe meetings, analyze emails, compare tasks, and uncover information that had previously remained unarticulated. This facilitates the definition of ideal future states without the need to skip essential steps.
Therefore, we can say that technologies such as AI facilitate faster understanding without encouraging premature action before there is a clear sense of direction. If the process analyst takes on the role of orchestrating understanding by integrating intuition, data, and natural language, technology becomes a strategic ally in driving change.
What I Learned from Projects That Did Not Go as Planned
Throughout my professional career, I have had the privilege of participating in projects presented using terms of great significance, such as “transformation,” “innovation,” and “agility.” I have also been part of initiatives that, unfortunately, failed to achieve the expected impact, resulting in the creation or implementation of a set of tools that were neither adopted nor understood by end users.
From both experiences, I drew precisely this fundamental lesson, which is the subject of this post: technological success cannot be achieved without operational truth. This operational truth is built through humility, intellectual curiosity, and constructive, collaborative dialogue—not through haste or recklessness.
Every failed attempt at change teaches us more than any investment can. I learned that successful projects are those that understand that technology does not replace reflection; rather, it requires it.
The desire to automate processes is not the main problem. The real challenge lies in failing to first understand the essential elements that should have been properly assessed beforehand.
Transformation Starts with People
Even with the most advanced technology in place, if the organizational culture continues to foster fragmentation, with each department operating autonomously and in isolation, without a comprehensive understanding of how its contributions connect to a shared objective, we will continue accumulating tools without achieving the transformation required to become a digital organization.
Processes are the foundation of all digitalization. Without clear processes, there is digital chaos. Transforming without understanding, therefore, means digitalizing chaos. And chaos, even when dressed in “digital,” is still chaos.
True transformation begins when people understand their role within a shared value flow and the conversation evolves from a departmental perspective to a collective process-oriented view.
Likewise, change becomes an established practice rather than being perceived as a one-time initiative.
Business success goes beyond simply using cutting-edge software. It requires capable leadership, empathy, and effective communication that establishes an unequivocal connection between the corporate mission and strategic objectives.
Understand, Formalize, Then Accelerate
In short, the sequence is simple, but almost no one follows it:
1st – Understand: discover how things actually work, not how we believe they work. Even when we think they could work better, the first step is to understand them. I call this: “Take the picture, even if we don’t look good in it.”
2nd – Formalize: represent and reach a consensus around shared collective knowledge in order to bring order to processes and create a common, shared view.
3rd – Accelerate: apply technology, AI, automation, or continuous improvement, but only once the previous steps are clear.
Skipping steps is like building a skyscraper without foundations or trying to run without even knowing how to crawl: it may appear solid at first, but it will eventually collapse under its own weight.
Before embarking on automation or implementing technology, it is essential to take a moment to understand, model, and formalize processes as they currently operate. This helps ensure that automation is successful.
At this point, the business analyst, project manager, or transformation leader takes on a critical role—one that goes beyond executing operational tasks and focuses instead on creating a common, shared understanding. Their job is to translate organizational complexity and noise into structured, accessible knowledge, thereby creating clarity and coherence in an environment characterized by speed and constant change.
The Meaning of Moving Forward
Ultimately, after many projects throughout my professional career, I came to understand that the most costly mistakes were not technical, but related to a lack of understanding.
When I speak with colleagues in my field and see so many organizations rushing toward change without a clear direction, I am reminded of when I first started running as an amateur.
At the time, I believed that improving simply meant running faster every week. But I soon discovered that speed without planning only leads to exhaustion.
I realized that, to truly move forward, I should not focus on being the fastest, but on understanding my starting point, listening to my body, planning each step, and measuring my progress. Only by knowing my limits and adapting my training to my capabilities was I able to improve sustainably.
In the same way, organizations are not about moving faster toward transformation, but about first understanding how we operate, what is holding us back, and what we need to strengthen. True improvement begins when we stop competing against speed and start building from knowledge.
This shift in mindset changed everything: I stopped training impulsively and started doing so with purpose and realism. I understood that it was not about flying through the 42 kilometers of a marathon, but about finishing it with purpose, knowing how far I could go and how to get there well.
In an organizational context, before implementing advanced technologies, improvements, or widespread task automation, it is imperative to have this comprehensive and interconnected understanding of the countless individual activities that make up the system. This process requires an exhaustive analysis of operational processes, identification of their weaknesses, assessment of their limitations, and a deep understanding of their capabilities and potential.
Because transforming without understanding is like running without direction: you may move very fast… but get nowhere.
It is not about moving fast, but about moving forward with purpose. It is about looking at processes not as mere procedures, but as the living narrative of how an organization creates value, revealing the reality of how its activities are carried out from beginning to end. It is about understanding that technology is not the end goal, but rather an amplifier of what we truly understand.
Author: Raúl Fernández Cuenca – IIBA Member and Interact Latam Partner.
