September 2026·Operations

Simplify Before You Automate

Automation amplifies what already exists. Before investing in AI or automation, organizations need to understand whether they are automating a well-designed process or locking in a broken one.

There is a pattern that repeats itself across industries and organization types. A leadership team identifies a process that is slow, inconsistent, or expensive. Someone proposes automation. A technology vendor is engaged. A project is launched. And months later, the organization has a faster version of a broken process.

Automation does not fix bad process design. It accelerates it. If the underlying workflow is poorly structured, if handoffs are unclear, if decisions are made inconsistently, automation will reproduce those problems at scale and at speed. The result is not transformation. It is institutionalized dysfunction.

The discipline that is missing in most automation initiatives is process clarity. Before any technology investment, organizations need to be able to answer a basic set of questions. What is the process actually doing? Who owns each step? Where do errors occur and why? What decisions are being made, by whom, and on what basis? What would a well-designed version of this process look like?

These questions are not technical. They are operational. And they require the kind of honest assessment that most organizations find uncomfortable, because the answers often reveal that the process was never well designed in the first place.

Simplification before automation is not a slogan. It is a sequencing discipline. It means doing the hard work of process redesign before committing to a technology solution. It means being willing to eliminate steps, consolidate roles, and clarify decision rights before asking a system to execute them.

Organizations that follow this sequence get more from their technology investments. They implement faster, with fewer exceptions and workarounds. They build systems that are easier to maintain and adapt. And they create the operational foundation that makes future automation genuinely valuable.

The organizations that skip this step spend years managing the consequences. They build technical debt into their operations. They create systems that are difficult to change because the underlying process logic was never resolved. And they find themselves, eventually, back at the beginning: facing the same process problems, now embedded in expensive technology.

Simplify first. Then automate. The sequence matters more than the technology.

All Insights Get in Touch

All Insights

July 2026·Leadership

What Transformation Actually Requires

Transformation is not a technology project or a reorganization. It is a sustained effort to change how an organization operates, and that requires clarity, leadership, and the patience to do the hard work.

The word transformation is used to describe a wide range of organizational initiatives. Technology implementations, reorganizations, cost reduction programs, culture change efforts, and digital modernization projects are all routinely described as transformations. The word has become so broadly applied that it has lost much of its meaning.

This matters because the word shapes expectations. If an organization believes it is undertaking a transformation when it is actually implementing a new system or restructuring a reporting line, it will underinvest in the things that transformation actually requires. And it will be surprised when the results fall short.

Transformation, in the meaningful sense, is a sustained effort to change how an organization operates at a fundamental level. It involves changing the processes, systems, structures, capabilities, and behaviors that determine how work gets done. It is not a project with a defined end date. It is a program of change that unfolds over time, requires continuous leadership attention, and produces results that compound.

What does it actually require? First, clarity about what is changing and why. Transformation initiatives that lack a clear and shared understanding of the problem they are solving tend to drift. The scope expands, priorities shift, and the organization loses confidence in the program. Clarity about the problem is the foundation everything else is built on.

Second, leadership that stays engaged. Transformation cannot be delegated to a program office or a consulting team. It requires senior leaders who are visibly committed, who make decisions when the program encounters resistance, and who hold the organization accountable for the changes it has committed to. When leadership attention moves on, transformation stalls.

Third, the organizational capacity to absorb change. Most organizations underestimate how much change their people can absorb at one time. Transformation programs that move too fast, or that run too many workstreams simultaneously, create fatigue and resistance. Pacing matters. So does the quality of change management, communication, and capability building that supports the people who have to work differently.

Fourth, patience. Transformation takes longer than most organizations expect. The early stages are often slow and uncertain. Results take time to materialize. Organizations that lose patience and declare victory too early, or that pivot to the next initiative before the current one is embedded, rarely achieve the outcomes they were targeting.

None of this is complicated. But it is hard. And it is the work that separates organizations that transform from organizations that launch transformation programs.

All Insights Get in Touch

Simplify Before You Automate

The Operating Model Is the Strategy

What Transformation Actually Requires