The instinct to simplify is almost always wrong.
Over the past several weeks, I’ve noticed a recurring pattern in conversations about organizational design and management systems. At some point—often immediately after a system is introduced—the same request emerges: “Can we simplify this?” The instinct is nearly universal. Not because simplicity is undesirable, but because the assumption behind the question is flawed. It assumes the system is more complex than it needs to be. In reality, most well-designed systems are complex for a reason. They are built to manage inherently complex conditions—interdependent decisions, competing priorities, and the unpredictable nature of human behavior. That complexity is not accidental. It is functional.
There are cases where simplification is appropriate—specifically when unnecessary complexity has been introduced through redundancy or poor design. But those cases are the exception, not the rule, and they are especially unlikely when a system has just been thoughtfully designed.
So why does the instinct persist? Because complexity is uncomfortable. People don’t just evaluate systems analytically—they react to them emotionally. Complex systems feel harder to understand, harder to navigate, and harder to control. The desire to simplify is often a desire to reduce that discomfort. In that sense, the instinct operates less like a rational assessment and more like what I would describe as a Siren of Facility—an attraction to what feels easier, even when it leads the system away from what is actually required.
And this is where the risk begins.
When simplification is driven by discomfort rather than function, elements of the system are removed—not because they are unnecessary, but because they make the system feel complex. At first, the system appears improved. It is easier to explain, easier to navigate, and easier to accept. But something more subtle has occurred. The system’s functional integrity has been altered—not through an explicit decision, but through a series of small changes that were never evaluated against its intended purpose. This is the lullaby of simplicity. It doesn’t force a tradeoff. It conceals it.
By the time the consequences become visible, the system no longer fulfills the function it was designed to serve.
Effectiveness, in this sense, is not a sliding scale. A system either achieves its intended outcome—or it does not. When simplification removes the elements required to achieve that outcome, the system has crossed from simple to simplistic.
From that point forward, it may still operate.
But it no longer works.
Executive Insight
Simplicity is only appropriate when unnecessary complexity is present. Before simplifying any system, distinguish between unnecessary and functional complexity—and ensure that every element required to fulfill the system’s purpose is preserved. If simplification changes what the system is capable of doing, the tradeoff must be explicit—not assumed.
0 Comments