Good Leaders, Bad Execution

Organizations often respond to inconsistent results by investing in more leadership development. Executives receive coaching, and managers attend new programs. Teams learn frameworks for accountability and communication. Decision-making training usually follows. These efforts may strengthen individual capability, but the execution problem often remains.

The leaders may be intelligent and experienced. Commitment is rarely the missing ingredient. The strategy may be sound, and people understand what the organization wants. Results still vary because decision rights are unclear and accountability changes with the situation. Too much still depends on informal workarounds or individual heroics.

This argument grew from work I developed with Jason Robert Miller for an executive briefing on operating discipline. Jason's work examines the systems and routines that make execution reliable. It also looks at the decision structures holding them together. My focus has been the leadership behavior that either reinforces those systems or quietly weakens them. Together, the work points to a simple conclusion: capable leaders cannot produce consistent results inside an operating environment that asks everyone to interpret the rules differently.

Capability Is Only Part of the Equation

Leadership development usually focuses on what an individual leader knows or can do. Programs strengthen strategic thinking and communication. They build delegation and coaching skills. Decision-making rounds out the list. Those capabilities matter, but they do not determine how consistently the organization will operate.

A capable leader may behave one way when the issue is routine and another when the stakes are high. A decision may be final in one meeting and reopened in the next. Accountability may be enforced firmly in one part of the organization and negotiated indefinitely in another.

People learn from those variations. They pay attention to whose approval matters and which decisions can be challenged later. They notice, too, when a senior preference overrides the formal process. Over time, employees become skilled at navigating personalities because the operating rules are less dependable than the people exercising authority.

Execution then becomes uneven. Strong leaders compensate and find ways to move the work. Others hesitate or overconsult. Some simply protect themselves. The organization experiences variable results even though many of its leaders are individually capable.

Decision Rights Must Hold After the Decision

Organizations often define decision rights in charts or governance documents, though sometimes only in a responsibility matrix nobody consults. The real test begins after a decision has been made.

I have watched a leadership team agree on a location for an important meeting, only to have someone senior reverse the decision weeks later. There was no warning, and no one from the original group was consulted. No explanation followed, then or later. The team learned about the change the same way everyone else did, after it was already final.

Can someone with greater status reopen it informally? Does a leader who disagreed continue to support implementation? Are people clear about which issues require escalation and which belong to the person closest to the work? Does authority remain stable when the result becomes uncomfortable?

When the answers vary, execution slows. People begin checking decisions that should already be settled. They add meetings to protect themselves or seek approval from several leaders. Others simply wait until they can predict how senior stakeholders will respond.

This behavior is often interpreted as weak accountability. In many cases, people are responding logically to an environment in which authority is conditional. Acting decisively carries risk when the organization regularly revisits decisions after the fact.

Reliable execution requires leaders to honor the authority they assign. A person given responsibility needs enough room to act and make reasonable mistakes. They still need to own the outcome. Senior leaders may still intervene when new evidence or serious risk appears, but routine second-guessing gradually empties delegated authority of meaning.

Workarounds Hide Structural Weakness

Most organizations develop informal ways to get work done. Employees know whom to call and which meeting matters. They know how to move a decision when the formal process stalls. Some workarounds are practical. Others reveal that the operating system cannot support the work it should govern.

The danger is that successful workarounds reduce pressure to fix the underlying problem. A capable leader finds a way around a bottleneck, so the bottleneck remains unaddressed. An experienced employee knows the right person to call, so the process keeps failing for everyone else.

I have watched two executives argue over a research priority in a way that had little to do with the science. The one who argued longest and loudest carried the room, and the exchange grew personal enough that colleagues stopped bringing new evidence into the conversation. The disagreement returned within a month, because volume had settled it instead of a process built to settle it.

The same pattern appears in accountability. A few conscientious people remember what others forget and repair weak handoffs. They also push stalled work to completion. Their effort keeps results acceptable while concealing how much the system depends on them.

Organizations often praise these people for their commitment. The praise may be deserved, but it can obscure a more important question: why does ordinary execution require extraordinary effort?

A reliable system benefits from capable people without requiring them to rescue the work continually. Commitments are visible and ownership is clear. Missed obligations get addressed before they become emergencies. Improvisation still has a place, but it isn't the operating model.

Leadership Behavior Makes the System Real

Operating discipline can sound technical, as though it belongs mainly to processes and measures. Governance gets treated the same way. Those elements matter, but leaders determine whether they carry real authority.

A senior team can approve a decision framework and weaken it immediately by ignoring the agreed process. Leaders can ask for accountability while protecting favored colleagues from consequences. They can emphasize focus and then introduce new priorities without removing existing work.

I watched one organization agree, after real debate, not to roll out a new training initiative. The rollout happened anyway, and no one acknowledged that the earlier decision had been reversed. Trust in the next planning meeting was smaller because of it, and people stopped assuming that a stated decision meant very much.

Employees learn the real system from repeated behavior. They watch what happens when a leader misses a commitment. Those moments reveal whether the operating system is dependable or merely aspirational.

Consistency does not require mechanical leadership. Circumstances differ, and sound judgment will sometimes require an exception. The exception should be visible and reasoned. It should also be limited. When exceptions become routine and unexplained, people stop trusting the rule.

Calm authority matters in these moments. Leaders need to support decisions they did not personally prefer, and address performance without creating unnecessary drama. They also need to resist the urge to override a process just because they can. Their behavior either strengthens the system or teaches everyone that the system is optional.

Diagnose the Structure Before Prescribing Development

Leadership development remains valuable, but it should follow a credible diagnosis. Before prescribing another program, executives should examine where execution actually breaks down.

Are decisions unclear at the beginning or reopened later? Do leaders agree on priorities but compete for resources? Are commitments visible, and does anyone review them? Does accountability depend on who is involved? Which results require repeated intervention from senior leaders?

These questions direct attention toward the conditions shaping behavior. A leader may need stronger skills in delegation or conflict management. Performance management often belongs on that same list. The organization should also ask whether the system itself makes consistent behavior difficult.

A capable leader cannot create enterprise reliability alone. The surrounding structure must support clear authority and coordinated priorities. It also has to support visible commitments and predictable follow-through.

Reliable Execution Is Designed

Organizations often search for stronger leaders when they should examine the system those leaders operate inside. Talented people can produce strong results for a time through judgment and relationships. Effort alone can carry them further than it should. Their success may conceal how much the organization depends on improvisation.

Reliable execution emerges when leadership behavior and operating discipline reinforce one another. Leaders know where authority resides and respect it after the decision is made. Commitments remain visible. Accountability does not change according to status or circumstance. Escalation has a clear purpose, and informal heroics are no longer required to make ordinary work succeed.

Jason Robert Miller and I will continue this conversation on the September 8 episode of The People Dividend Podcast, "Why Strategy Fails Without Execution Discipline." His operating-systems perspective and my focus on leadership behavior arrive at the same conclusion: execution becomes reliable when the organization stops depending on individual interpretation and begins designing for consistent action.

Capable leaders remain essential. Their capability produces greater value when the organization gives them a system they can trust and reinforce. It matters even more when that system is one they actually use together.

‍