One of the more reassuring things about working with organizations is that most of the people involved are intelligent.
This sounds obvious, but it is worth stating because it creates a useful starting point for understanding a puzzle that has fascinated me for years. If organizations were filled with careless people making irrational decisions, many of their problems would be relatively easy to explain. What makes organizational life so interesting is that the opposite is usually true. Most organizations are populated by thoughtful, experienced individuals who are trying very hard to make good decisions.
And yet those same organizations often produce systems that nobody seems particularly happy with.
A process requires multiple approvals. A decision must pass through several committees. A report is prepared for one meeting, revised for another, and eventually reviewed by people who can no longer remember why it was commissioned in the first place. New staff members arrive and spend months learning procedures that long-serving staff privately acknowledge are cumbersome. Everyone agrees the system is more complicated than it needs to be. Nobody is entirely certain how it became that way.
The easy explanation is bureaucracy.
The more interesting explanation is accumulation.
I’ve become increasingly convinced that organizational complexity rarely arrives as a single event. If it did, people would object immediately. Imagine proposing a process that required four committees, six approvals, three reporting structures, and two separate databases from the very beginning. Most reasonable people would reject it on sight. The complexity would be obvious.
Instead, complexity tends to arrive disguised as a series of sensible decisions.
Someone needs additional information, so a form is added. Someone wants greater accountability, so an approval step is introduced. Someone raises a legitimate concern about oversight, so a committee becomes involved. Someone identifies a risk, so a reporting requirement is established. Viewed individually, each decision appears entirely reasonable. In many cases, each decision is entirely reasonable.
The challenge emerges because organizations are much better at adding things than removing them.
A new layer is added to the existing structure. The previous layer remains. Another adjustment follows a year later. The original rationale may eventually disappear, but the process itself survives. Over time, what began as a collection of thoughtful responses to specific circumstances becomes a permanent feature of the organizational landscape.
Nobody designed the complexity.
People inherited it.
That distinction matters because it changes how we think about organizational problems. When people encounter a complicated system, they often assume somebody created it intentionally. They imagine a moment when a group of decision-makers sat around a table and consciously chose a convoluted approach. In reality, most organizational systems resemble old cities far more than master-planned communities.
Cities evolve.
Roads follow paths that once made sense. Buildings remain long after their original purpose has disappeared. Infrastructure reflects decisions made by different people responding to different realities at different moments in time. From a distance, the city appears coherent. Up close, it reveals layer upon layer of adaptation, compromise, and historical accident.
Organizations grow in much the same way.
The process becomes particularly visible during periods of growth. A structure that works perfectly well for five people often becomes strained at twenty. A process developed for twenty people may become awkward at fifty. The organization adapts, but adaptation frequently occurs incrementally rather than systematically. New pieces are attached where needed. Existing pieces remain in place. The resulting structure functions, but not always elegantly.
There is a certain irony in this because complexity is often created by people trying to solve legitimate problems. Few individuals wake up in the morning hoping to make their organization less efficient. More often, they are attempting to make it more accountable, more inclusive, more transparent, or more responsive. These are generally worthwhile goals. The difficulty is that each solution introduces its own demands, and organizations rarely stop to consider the cumulative effect of those demands.
I’ve noticed that this cumulative effect can become strangely invisible to the people living inside it.
New staff members sometimes see complexity more clearly than long-serving employees because they have not yet adapted to it. They ask questions that seem obvious from the outside and mildly disruptive from the inside. Why does this require three approvals? Why are we producing this report? Why is this committee involved? Long-serving staff members often respond with some variation of “That’s how we’ve always done it,” not because they are defending the process but because the process has become part of the organizational furniture.
Once something becomes familiar, it stops attracting attention.
That may be one of the reasons simplification is so difficult. Organizations are not merely redesigning systems. They are challenging assumptions that have gradually become invisible. The work requires people to examine routines they have stopped noticing and ask whether those routines still serve a useful purpose. This can feel surprisingly disruptive because familiarity creates a sense of legitimacy. If something has existed for years, people naturally assume it must be there for a reason.
Sometimes it is.
Sometimes the reason disappeared long ago.
The organizations that seem most effective at managing complexity are not necessarily the simplest organizations. Simplicity itself can become a kind of fetish if taken too far. Some processes genuinely require oversight. Some decisions benefit from consultation. Some reporting requirements create meaningful value. The goal is not to eliminate every layer of structure. The goal is to understand which layers continue to justify their existence.
That requires a particular kind of organizational curiosity.
Instead of asking how to add another process, people begin asking what would happen if an existing process disappeared. Instead of assuming every requirement is essential, they become interested in its purpose. Instead of treating inherited systems as permanent features of the landscape, they treat them as decisions that can be revisited.
These questions are rarely dramatic.
Nobody receives an award for eliminating a redundant approval process. There are no ribbon-cutting ceremonies for simplifying a reporting structure. The work often goes unnoticed because successful simplification tends to remove things rather than create them. Yet the cumulative effect can be significant. People spend less time navigating systems and more time pursuing the organization’s actual purpose.
The longer I work with organizations, the more I find myself paying attention to friction.
Every system creates some degree of it. Forms require time. Approvals require attention. Meetings require coordination. None of these costs are inherently problematic. The important question is whether the value produced by the system justifies the friction it creates. When organizations stop asking that question, complexity tends to expand quietly and steadily until it begins consuming resources that nobody intended to spend.
This is why I have become cautious whenever people describe organizational complexity as a problem of incompetence.
Incompetence can certainly create problems, but most of the complexity I encounter has been produced by capable people making reasonable decisions. The issue is not the quality of any individual decision. The issue is the accumulation of many decisions that were never reconsidered once circumstances changed.
That is a much more human explanation.
It is also a more hopeful one.
If complexity is primarily the result of thoughtful people responding to real challenges, then simplification does not require finding better people. It requires creating the space to examine inherited assumptions, revisit old decisions, and ask whether the systems serving the organization today are the same systems it would choose to build from scratch.
Organizations rarely have the opportunity to start over.
They do, however, have the opportunity to remain curious.
And curiosity may be one of the most effective tools available when complexity begins to feel heavier than the mission it was meant to support.