Systems Error

Essay 13 of 13

This is the last essay in the first season of Systems Error. It is not a conclusion, because what this series has been pointing toward does not conclude. It begins. But it is a close, and a close deserves to be honest about what has just happened and what it was for.

Thirteen essays ago, this series opened with a premise: organizations are often not failing because of bad people. They are failing because of bad design. The effort is real. The intention is often genuine. But intention without architecture produces the same result again and again: people working hard inside structures that are quietly working against them.

The series named that condition Systems Error not to accuse, but to locate. If the problem is a system error, you do not automatically blame the operator. You look at the system that shaped what the operator could see, understand, decide, and do.

What CHAMPS® is, in its simplest form, is a design language for that work. Six nodes: Customer-Centric Mindset, High-Integrity Leadership, Agility and Accountability, Metric-Driven Excellence, People-First Culture, and Sustainable Success. Each represents a dimension of organizational life that has to be designed deliberately or will be designed by default.

And the defaults are not neutral. They tend toward familiar patterns: customer feedback that goes nowhere, leadership behavior that changes by audience, accountability that flows in one direction, metrics that measure activity rather than outcomes, culture built on programs rather than conditions, and success borrowed against until the account is empty.

These are not simply individual failures. They are often what organizations produce when design is left to habit.

But CHAMPS® is not the end of the story.

It is the score.

The question this final essay addresses is how leaders actually play it together, with different instruments, different instincts, different personalities, and different leadership styles, without producing noise. That question has been present since Essay 7, when this series first named Symphony Leadership™ and held it back as a promise.

The promise is kept here.

Share

Organizations contain leaders with different philosophies, instincts, and styles. There is the servant leader who subordinates ego to team capacity, the manager who engineers productive friction because better ideas sometimes survive harder rooms, the strategic realist who understands power and organizational politics, the visionary who sees three moves ahead, and the operator who makes sure the trains actually run on time.

Each of these can produce something useful. Organizations need what they produce.

The problem is not that these philosophies are different. The problem is what happens when they coexist inside the same organizational system without a shared floor beneath them.

A servant leader can spend two quarters building trust, momentum, and a way of working that gives a team confidence. Then a leader two levels up can reallocate the team’s resources to a more visible problem without involving them in the decision or explaining the logic. The decision may be completely rational from where that executive sits. But the team does not experience the executive’s calculus. It experiences what the system just taught them.

The organization is not what they thought it was.

Some people leave. Others stay and become more guarded. The servant leader, who never led selfishly, absorbs damage created by a system larger than the team.

A manager who believes in productive friction can face the opposite problem. The debate works until the participants stop competing for the best answer and begin competing to win. The manager may not have changed at all. What changed was the meaning of the conflict because there was no shared understanding of what the conflict was supposed to serve.

Both situations can contain good people, smart leaders, and defensible individual decisions.

What they lack is a score.

Every musician in a professional orchestra brings genuine skill and a distinct instrument to the performance. The oboist does not play like the cellist, and nobody expects them to. What makes them an orchestra rather than a collection of talented individuals producing simultaneous sound is that they share an underlying structure. They know what they are trying to produce together, what each part owes to the whole, when to yield, when to carry the line, and how to recognize when the ensemble has drifted.

Without that shared structure, everybody can be technically competent and the result can still be noise.

Symphony Leadership™ is not a leadership style. It is not a prescription for how every leader should behave, and it is not a personality profile for the ideal executive. It does not ask a Commander to become a servant leader, an introvert to perform extroversion, or a strategic realist to pretend organizational politics do not exist.

It asks something harder: leaders with different instincts have to share a score.

Symphony Leadership™ is the organizational practice of aligning diverse leadership styles around a shared structure of beliefs, commitments, and interpretive logic so that difference becomes generative rather than destructive.

The servant leader and the strategic realist do not have to become alike. Their styles can remain different. Their floor cannot.

The purpose of organizational alignment is not to make leaders more alike. It is to make their differences interoperable.

Without a shared score, differences in leadership philosophy can become corrosive because each leader interprets the organization through a private operating logic. With one, those same differences can become useful because they are bounded by shared commitments about what the organization exists to produce, what it will protect, what it will measure, and how it will respond when reality changes.

This is also why the conductor metaphor should not be mistaken for another heroic-leader model. Organizational coherence cannot depend primarily on the personality standing at the front of the room.

The system conducts. Individual leaders participate in conducting it.

The score supplies the foundational beliefs that allow diverse styles to remain diverse without becoming incoherent. Leaders do not have to think identically. They have to understand what the organization is trying to produce together, what each part owes to the whole, and how to treat dissonance as information rather than threat.

This is where CHAMPS® and Symphony Leadership™ meet. CHAMPS® defines the philosophy, what an organization must believe, measure, and protect if it intends to create value over time. Symphony Leadership™ describes how leaders with different capabilities and styles operate inside that philosophy together.

CHAMPS® is the score. Symphony Leadership™ is the practice of reading it together.

Customer-Centric Mindset is the Artistic Director. It defines who the work is for and what experience the organization is promising. Without it, the orchestra can perform beautifully for an empty hall, choosing repertoire no one asked for and calling it vision.

High-Integrity Leadership is the Conductor. It turns the promise into a shared standard and refuses to quietly lower that standard when pressure rises. The conductor here is not the heroic executive. It is the integrity function of the system, the visible floor beneath everybody’s behavior. When that floor holds, the rest of the organization can function. When it does not, other parts of the system begin compensating, and compensation is expensive.

Agility and Accountability is the Section Leader. It confronts divergence between plan and reality and helps the organization make disciplined, visible adjustments. When the section hears itself drifting, somebody has to be able to say so, and the system has to be capable of responding rather than defending the original plan.

Metric-Driven Excellence is the Sound Room. It tells the organization whether the performance it believes it is producing is the performance anyone else is actually hearing. Are the signals connected to the outcomes we care about? Are we learning from reality, or measuring what flatters the people being measured?

People-First Culture is the Orchestra. It creates the human conditions under which talent can hear, trust, challenge, and elevate other talent. A great orchestra does not require every musician to sense reality the same way. It creates enough safety and shared purpose for different minds, experiences, and rhythms of work to improve the performance rather than threaten it.

Sustainable Success is the Legacy We Build. The real question is not simply whether the orchestra played well tonight. It is whether tonight’s performance left the ensemble more capable of creating value tomorrow. Sustainable Success is what emerges when learning, trust, capability, and renewal compound instead of being consumed in pursuit of the current quarter.

The nodes reinforce one another. Customer focus supplies purpose. Integrity allows truth to enter. People-First Culture allows truth to travel. Metrics preserve reality. Agility changes behavior. Sustainable Success asks whether those improvements persist.

That interdependence is why CHAMPS® is a web rather than a hierarchy. The score recurs. The performance changes. The system learns.

At this point, a reasonable reader can accept the philosophy and still ask the question that matters:

How do I know whether I have actually built a good leadership system?

It would be easy to answer with financial results, engagement scores, retention, innovation, productivity, or market share. Those outcomes matter. But each can be temporarily strong inside a system that is quietly becoming weaker.

There is another test.

Look first at the people with the greatest freedom to ignore the system.

Michael Jordan once praised Tim Duncan’s leadership in a way that points directly at this distinction. Duncan was not a role player who had to comply to survive. He was the franchise player. His status gave him enormous freedom to decide that coaching was for everybody else.

He did the opposite.

Duncan took coaching. He allowed Gregg Popovich to hold him accountable. He did not require the organization to create a separate operating system for its most important player. By doing that, Duncan communicated something to every other Spur that no values poster or locker-room speech could communicate as powerfully: the system applies here.

That is more than followership.

The person with the greatest organizational permission to say, “That rule does not apply to me,” chose not to use it.

You know you have built a good leadership system when the people with the greatest freedom to ignore it choose to strengthen it instead.

That is the moment culture begins to move from enforcement to ownership.

And notice what Duncan did not have to do. He did not have to become Popovich. He did not have to be the loudest person in the room. He did not have to mimic some preferred leadership personality. His leadership was visible in what his behavior made possible for everybody else. If Tim Duncan could be coached, everybody could be coached. If Tim Duncan could subordinate personal privilege to the operating system of the team, nobody beneath him had a particularly persuasive case for exemption.

His exceptional status did not weaken the system.

It strengthened it.

General George C. Marshall gives us another version of the same principle.

Marshall operated in a world in which centralized authority could easily have become a substitute for leadership. The scale of the American military effort during World War II gave him every excuse to insist that critical decisions, key relationships, and institutional knowledge flow through him.

But an organization built that way becomes powerful only while the extraordinary individual remains in the chair.

Marshall’s larger achievement was helping create an institution capable of producing, selecting, developing, trusting, and coordinating other leaders. The measure of that system was not that everybody became George Marshall. Eisenhower did not lead like Patton. Bradley did not lead like MacArthur. Different personalities, capabilities, and instincts remained visible because wartime command required different instruments.

The system had to make those differences productive.

That is Symphony Leadership™ at institutional scale. Leadership is not demonstrated by proving that nobody can operate without you. It is demonstrated by increasing the ability of other people to operate successfully because of what you designed, clarified, protected, and made possible.

There is a profound difference between being indispensable to a system and building a system capable of sustaining excellence.

The first can feel like proof of leadership.

The second is leadership.

For decades, leadership discussion has spent enormous time asking what style of leader we prefer. Servant leadership. Transformational leadership. Transactional leadership. Charismatic leadership. Authentic leadership. Coaching leadership. Command leadership.

Those distinctions can be useful. Different circumstances may benefit from different tendencies. Some people work exceptionally well with a demanding Commander. Others perform better under a leader who creates more space, asks more questions, or distributes authority differently.

But style is not the final question.

The final question is what the organization needs to produce, what conditions make that production more probable, and what leadership capabilities are necessary to create and maintain those conditions.

That is why two organizations can hire people of comparable intelligence, credentials, experience, and ambition and produce very different results. Talent is an input. The organizational system determines how much of that talent becomes usable collective capability.

Brilliant people are not automatically brilliantly performing people.

They need clarity. They need the right constraints. They need access to information. They need appropriate agency. They need the ability to challenge assumptions. They need to understand what the work is supposed to produce and what boundaries cannot be crossed in pursuit of it. They need a system that allows their individual intelligence to combine with the intelligence of others rather than compete against it.

The leader’s job is to create those conditions.

Servant. Commander. Transformational. Introvert. Extrovert. Visionary. Operator.

Interesting distinctions.

Not the final test.

That brings us to the question underneath all thirteen essays.

We have spent a great deal of time asking what leaders should possess. What characteristics should they demonstrate? How should they communicate? How inspiring should they be? What personality should they project? Which style produces the strongest response?

Season 1 asks a different question.

What becomes possible for other people because you are leading?

Can they understand the objective more clearly because you are there? Can they exercise judgment without guessing what you meant? Can they challenge an assumption without threatening their standing? Can they coordinate across functions instead of protecting their piece of the organization? Can extraordinary people make the system stronger rather than require exemptions from it? Can someone who does not understand an assignment say so before the deadline instead of hiding until failure makes the misunderstanding visible?

Can the organization continue producing excellence when you are not in the room?

Those are leadership outcomes.

Tim Duncan did not make the Spurs stronger merely because people followed him. His status strengthened the system because he demonstrated that even the person most capable of exempting himself remained inside it.

George Marshall did not strengthen the institution by making every important decision personally. He helped build conditions in which other capable leaders could exercise authority, make decisions, and carry the mission forward.

Different people. Different environments. Different instruments.

Same question.

What becomes possible for other people because you are leading?

That is the essence of Symphony Leadership™.

The strongest leadership systems do not make extraordinary people less extraordinary. They create conditions in which extraordinary people strengthen the system for everyone else.

The goal of Season 1 was never to make readers experts in organizational design theory. The goal was recognition. If something in these essays gave language to a problem you could previously only feel, made an organizational behavior look different, or caused you to reconsider whether a “people problem” might actually be a design problem, the season has done what it was supposed to do.

Recognition is not implementation. But it is the precondition for it. You cannot deliberately redesign a system you have not learned to see.

Season 1 named the score.

Season 2 is rehearsal.

That means diagnostics, tools, practice, feedback, correction, repetition, and eventually a more deliberate operating rhythm. We will ask where clarity is breaking down, where people lack agency, where accountability is distorted, where the wrong signals are being measured, where integrity bends under pressure, and where leadership unintentionally makes strong people less capable rather than more.

The work becomes more specific because implementation always does.

Season 1 was about learning to see the system. Season 2 is about learning to operate it.

And the door is open.

• When you evaluate leadership in your organization, how much attention goes to the leader’s style and personality, and how much goes to what becomes possible for other people because that person is leading?

• Who in your organization has the greatest freedom to ignore the system? What happens when they are asked to follow a standard, accept coaching, honor a process, or live inside the same constraints as everyone else?

• Do your highest-status people strengthen the system through their behavior, or teach everyone else where the exemptions begin?

• If an extraordinary leader disappeared tomorrow, would the organization retain the capability that leader created, or would performance disappear with the person?

• Where are different leadership styles creating useful diversity, and where are they producing noise because there is no shared floor beneath them?

• When someone closest to the work hears dissonance, what happens when they name it? Does the system become curious, or does it become irritated?

• And finally: What becomes possible for other people because you are leading?

Dr. Mel Davis Jr., Conductor of the CHAMPS® Leadership System
Follow on LinkedIn and X (@DrMelDavisJr) for more essays and tools on high-integrity leadership, Symphony Leadership™, and sustainable success.
Systems Error is published on EquitiFy Substack. Season 2 continues the series with diagnostic and implementation tools for the CHAMPS® framework.

CHAMPS® is a proprietary organizational design system developed by Mel Davis / EquitiFy. Symphony Leadership™ is a trademark of Mel Davis / EquitiFy.

Share