Systems Error
Why management keeps breaking, and what designed leadership looks like instead
Essay 2 of 13
Why Excellence Fails to Scale
You have probably seen this movie.
I have seen versions of it in organizations of every size; the specifics change, but the arc is the same.
An organization has its moment. A new leader arrives with vision and energy. An unusually committed team assembles around a bold initiative. For a while, everything clicks. Performance spikes. The numbers move. Someone writes a case study.
And then, almost quietly, the wheels begin to wobble.
The same team that once moved mountains now struggles to move meetings. Projects slip. Customers notice small lapses that were not there before. The charts on the wall still show last year’s numbers, but the hallway conversations no longer match the posters. Nothing catastrophic happens on a single Tuesday afternoon. It is subtler than that. The excellence that once felt inevitable begins to feel fragile.
Leaders call it a rough patch. A transition. A cultural challenge that the right hire or the right offsite will fix. What they rarely say, because it is harder to name, is that the success was never truly systematic in the first place.
The star leader was carrying it. The exceptional team was carrying it. The concentrated moment of organizational will was carrying it. The moment any of those variables shifted, the performance gains began to evaporate. Not because people stopped caring, but because there was no architecture strong enough to carry them forward when the conditions changed.
Consider new product launches. Most leaders already know that strong launch outcomes are far from guaranteed. One product lands, another stalls, and a third never finds traction despite the same enthusiasm, planning, and internal optimism. The usual explanation points to execution, timing, or the market. Sometimes that is true. But the harder question is why the process itself is so rarely replicable with stellar results. If launch excellence were truly built into the system, it would not depend so heavily on extraordinary people, unusually favorable conditions, or another round of organizational heroics.
That is the pattern. And it is more common than most leaders are comfortable admitting.
McKinsey’s research on organizational health makes the financial cost visible: organizations with stronger system design consistently outperform peers on long-term results and show measurable operating improvement when the architecture gets better. What that research confirms, and what many of us have felt in operating roles, is that the gap between those two worlds is not talent. It is not passion. It is architecture.
The organizations that sustain performance across leadership changes, market shifts, and personnel turnover are not the ones with the most inspiring leaders. They are the ones that stopped treating excellence as something a handful of people produce and started treating it as something the system is designed to deliver.
That distinction is easy to say and hard to act on. Most organizations are built, implicitly, over years, around the assumption that the right people will figure it out. Hire the star. Train more. Motivate harder. When that fails, bring in a consultant, launch a new initiative, announce a new set of values. Repeat.
None of it is wrong, exactly. But none of it addresses the underlying architecture. And until the architecture changes, the performance will keep depending on whoever is currently willing to work hardest to compensate for it.
When excellence concentrates
The real warning sign is not simply that some people perform better than others. It is that the organization’s strongest results keep concentrating in the same few hands.
A team hits the deadline because one person knows how to push the work through three unclear approvals. A launch survives because someone quietly coordinates the handoffs that were never fully designed. A client relationship holds because a manager keeps translating between functions that should already understand one another. In many organizations, there is always somebody who knows how to work the system because the system itself is not doing enough of the work.
The organization often describes this as commitment, leadership potential, or resilience. In practice, it is usually a workaround.
That distinction matters. When repeated performance depends on a small number of people repeatedly absorbing confusion, delay, and ambiguity, the organization has not solved the problem. It has assigned the problem to a person.
What looks like strength on the surface is often evidence that the formal system cannot reliably produce the same result on its own. That is why excellence concentrated in a few people should never be read only as a compliment. It should also be read as a diagnostic signal.
How the story gets told wrong
When organizations do notice that excellence is concentrated in a small number of people, they often explain that difference through personal traits. Some people are more driven, more disciplined, more resilient, or simply more gifted at leadership. Those observations are not always wrong, but they are often incomplete in exactly the way that protects the system from scrutiny.
This is the leadership-traits story at its most convenient. It allows uneven performance to be explained as the natural consequence of uneven people instead of forcing a harder examination of structure, incentives, decision rights, role clarity, and the hidden cost of ambiguity. Once that frame settles in, the institution can keep praising exceptional individuals while avoiding redesign.
That is why so many organizations confuse adaptation with strength. Repeated heroics may be admirable, but they are still a workaround when the formal system cannot reliably produce the result on its own.
The result is a familiar managerial reflex: search for better people, ask current people for more effort, or celebrate the few who can repeatedly compensate for the confusion. All three responses mistake adaptation for design.
Why the standard remedies keep failing
When the heroic run ends and performance begins to drift, most organizations move through the same response sequence. It starts with people. Find better ones, develop the ones you have, hold them more accountable. When that does not produce the expected turnaround, the organization moves to tools: a new platform, a new process, a new dashboard. When the tools fall short, the next move is motivation: rallying language, culture initiatives, engagement surveys. And when engagement scores move without corresponding performance movement, the sequence begins again with a new round of hiring, developing, and replacing.
This is not negligence. It is what happens when the diagnosis stops at the individual and never reaches the system. Each intervention treats the person as the variable. The architecture stays intact.
Training is not the problem. High-quality leadership and skills development can improve individual capability. The problem is that individual capability does not translate reliably into organizational performance when the surrounding system resists it. A well-trained manager returning to unclear role boundaries, overloaded spans of control, muddy decision rights, and an accountability structure that punishes candor is not going to produce systems outcomes. They are going to use their new skills to survive the same broken system more elegantly.
SHRM’s research reinforces the point. Organizations widely acknowledge that managers are critical to business outcomes, yet far fewer rate themselves as highly effective at leadership development. That gap is not primarily a training-quality problem. It is an architecture problem. Development cannot permanently compensate for structural conditions that make managing well unnecessarily hard.
Technology investments follow the same logic. A new platform does not create role clarity where none exists. A new performance management system does not fix unclear ownership. A new communications tool does not resolve the meeting sprawl it was meant to replace. Tools amplify whatever system they enter. In a strong system, they extend capability. In a weak one, they add another layer of complexity for the same people who were already carrying too much to manage effectively.
And motivation cannot permanently compensate for broken architecture.
Even highly committed people burn out when the surrounding system resists their best efforts. When the work is harder to succeed in than it should be, when clarity is scarce, coordination is expensive, and accountability lands unevenly, the people most likely to keep pushing are also the people most likely to get depleted first.
This is where the systems problem becomes a human problem. The burden of holding everything together falls on a relatively small group: the informal problem-solvers, the quietly competent operators, the managers who can always be counted on to find a way. They work longer hours, absorb more uncertainty, and spend their days translating between the organization’s stated aspirations and its actual operating habits. Over time, they become exactly what the system most needs and exactly what the system burns through first.
Meanwhile, the people who are not in that informal hero category are often labeled as the problem when they may simply be responding rationally to the environment they were given. In a badly designed system, uneven outcomes do not necessarily reveal uneven character. They often reveal uneven tolerance for dysfunction.
What sustained organizations actually do
Organizations that scale excellence more reliably do not depend on permanent surges of effort. They reduce the need for heroics by making good performance easier to repeat. They clarify decision rights, simplify priorities, align incentives more carefully, and remove recurring friction from the path of execution.
They also stop confusing the presence of extraordinary people with the health of the institution. Strong organizations value talented individuals, but they do not build a model that requires exceptional people to compensate indefinitely for weak design. They understand that the point of management is not to search endlessly for better heroes. It is to create conditions in which ordinary competent people can produce reliable, high-quality results.
Microsoft under Satya Nadella is the most cited recent example, not because of charisma or inspiration, but because the turnaround involved a disciplined re-wiring of how the organization operated: clearer customer orientation, different measurement habits, different ways of empowering people, and a different organizational story about what success meant. The architecture changed. The results followed and held.
The U.S. military’s leadership development system offers a different kind of example. Commanders rotate. Units reorganize constantly. Yet the institution maintains a baseline of operational effectiveness because leadership development, role clarity, and institutional knowledge are treated as systems: deliberately designed, consistently applied, and not dependent on whoever happens to occupy a given position at a given time.
That does not mean a bad leader cannot gum up the system. Of course they can. Strong systems still experience defects, distortions, and local failures. The difference is that well-functioning institutions are designed to surface those aberrations, limit the damage they can do, and keep the larger system from being permanently bent around them. Weak systems absorb the defect. Strong systems work to discard it.
The pattern across these cases is consistent: the organization stopped treating excellence as a moment and started treating it as architecture. The real subject of improvement shifted from the individual to the system.
The signal hiding in heroic effort
There is a diagnostic use for the heroic-effort pattern that most organizations miss. When the same small group of people is consistently required to work at extraordinary levels to keep performance from slipping, that is not a tribute to their character. It is a signal about the system. The gap between what the system is designed to deliver and what the situation requires has been assigned to a person. That is not a sustainable arrangement. It is design debt.
The question is not whether you have people willing to carry that debt. Most organizations do, for a while. The question is whether the system is being designed so that carrying it becomes unnecessary.
That is the work beneath the performance conversation. Not whether the team is committed. Not whether the leader is inspiring. Whether the architecture is strong enough that excellence does not depend on any one person’s willingness to absorb what the system has not been designed to handle.
Excellence that cannot travel beyond a few unusually capable people is not institutional excellence. It is dependence disguised as performance.
Written by Mel Davis, Chief Strategy Officer & Systems Architect, EquitiFy®
Sources are drawn from management research and organizational design literature, including Harvard Business Review and Harvard Business School writing on motivation, burnout, incentives, and decision-making.
If there’s a pattern in here that feels uncomfortably familiar, I’m especially interested in how you’ve seen it show up in your world.
Editor’s note: Every essay in Systems Error will remain free. After the first five, I’ll begin adding a paid layer for readers who want to go further into the application: deeper operating analysis, diagnostic tools, and implementation guidance.
Next in Systems Error: why most organizations are not suffering from a shortage of talented people, but from a shortage of coherent systems, and why those are not the same problem.