The System Beneath Predictable Growth

Nine execution patterns share one cause. Here is the system beneath them, and why its parts only work together.

The last article in this series ended on a claim: nine execution patterns, one problem.

This article names what sits beneath them.

In the companies I work with, the patterns tend to travel together. Where decisions route to the CEO, meetings end without decisions. Where the business runs nineteen priorities against a stated three, every function hits its number and the enterprise misses. Where forecasts move without a decision attached, cross-functional conflicts get settled by whichever two leaders happen to get along.

That is not coincidence, and it is not a general condition of corporate life. It is a specific and diagnosable failure in the layer between strategy and execution — a layer that goes undesigned when nobody tells the leadership team it is theirs to design.

Start with what you actually want

Start with the outcomes, not the methodology.

For executives running companies between $100 million and $1 billion, the outcomes at stake are narrower and more concrete.

Predictability. The number is the number. The forecast holds. Surprises arrive early enough to do something about, and commitments made in January are worth something in June.

Growth that does not consume more than it produces. Revenue rises without a matching rise in escalation, rework, and executive intervention. Complexity gets absorbed rather than compensated for.

Operating discipline that survives scale. What works at this size still works at twice this size, without the leadership team working twice as hard to hold it together.

Those are the outcomes this work is meant to support. Everything else is mechanism.

They are hard to reach for one reason. All three depend on the same underlying system. When nobody deliberately designs that system, it accumulates instead.

Why fixing one layer never holds

If your executive team has already tried to solve these problems, the skepticism that follows is reasonable. It deserves to be taken seriously.

The strategic offsite produced alignment. Weeks later the alignment was still intact and execution was unchanged — because agreement on what matters does not establish who decides.

The new dashboard produced visibility. Visibility produced better explanations of the same results, because measurement without ownership creates reporting.

The meeting redesign produced tighter agendas. The same issues kept returning, because a well-run forum with no decision authority still produces no decisions.

The accountability push produced pressure. Pressure without structural clarity becomes blame, and blame slows the rate at which problems surface — which leaves the original condition worse than it was.

Each of those initiatives addressed a real problem. Each addressed one layer. And each was undone by the layers left alone.

There is a reason the untouched layers win. Execution breaks between functions far more often than inside them. One large study found that 84 percent of managers could rely on their boss and direct reports all or most of the time. For colleagues in other functions, only about half could rely on them most of the time. And managers were three times more likely to miss a commitment because another unit did not deliver than because their own team fell short (Sull, Homkes and Sull, Harvard Business Review, 2015).

Execution breaks at the joints. An initiative that strengthens one layer leaves every joint around it exactly as it was.

The five disciplines

What sits beneath predictable growth is a leadership execution system: five disciplines, each named for what it does, built to operate as one.

Focus. Enterprise Priorities Alignment. A limited set of enterprise priorities that govern resource allocation, decisions, and leadership attention. The test is not whether they are written down. It is whether they changed what the organization declines to do.

Decide. Decision Rights. Every material decision has exactly one accountable owner, with input roles and escalation rules set before conflict shows up. This is not a responsibility chart. Decision rights establish who makes an enforceable call — and who does not.

Measure. Enterprise KPI Scoreboard. One shared enterprise performance view, connected to the priorities, with one accountable owner for each KPI — built so that a miss produces action rather than explanation.

Operate. Operating Rhythm. The recurring forums and preparation standards that turn priorities, decisions, and measures into a repeatable cadence of review, decision, and follow-through. Designed as a connected set rather than accumulated one meeting at a time.

Resolve. Enterprise Frictions & Ownership. A short, active list of the cross-functional barriers limiting performance, each defined at root cause rather than symptom, with one owner, a next action, and a standard for closure.

Read separately, none of those is novel. That is exactly the point. The value is in how the five operate together.

Each discipline closes a gap the previous one opens

The value is in the sequence. Follow it one step at a time and the logic is hard to argue with.

Focus without Decide produces debate without resolution. The leadership team agrees on what matters. Nobody is clear on who makes the call when two priorities compete for the same resources, so the call gets made in the hallway, or twice, or by the CEO.

Decide without Measure produces fast decisions pointed in different directions. Owners are clear and moving quickly. There is no shared view of whether their choices add up, so each function optimizes against its own numbers.

Measure without Operate produces visibility without action. The team can see the miss. There is no forum built to turn a miss into a decision, an owner, and a commitment, so the scoreboard becomes a report.

Operate without Resolve produces recurring meetings about the same unresolved problem. The cadence runs well. The cross-functional barrier that shows up every week has no owner and no closure standard, so it becomes part of the agenda instead of leaving it.

And Resolve feeds back into Focus. What the frictions reveal tells leadership whether the priorities are still the right ones — which is how the system corrects itself instead of drifting.

Stop anywhere in that sequence and the gap you left open is where execution slides back. This is why a leadership team can do excellent work on one discipline and watch it fade. The problem was never solved. It moved one joint over.

Focus. Decide. Measure. Operate. Resolve. Five disciplines. One system. Predictable execution.

It also explains why a leadership offsite can disappoint. An offsite can improve one discipline well and leave the others untouched.

What this is not

It is not a leadership workshop, an offsite, or a meeting-improvement initiative. It is not a strategic planning process, a culture campaign, a software platform, or a collection of templates.

An offsite may be part of building it. Tools support it. Meetings get redesigned in the course of it. None of those is the system.

The distinction worth holding: this is not an initiative. It is how the business runs.

A change like this is not rolled out to an organization; it is built by the leadership team that has to run on it. And it is not done until leadership behavior changes — how leaders prioritize, decide, measure, meet, escalate, commit, and follow through.

How it starts

It does not start with a system. It starts with a conversation.

A Blueprint, a few coaching conversations, or a working discussion with several leaders can surface where execution is breaking — and point to one or two adjustments worth making first.

Start there. One recurring decision given a single owner. One meeting redesigned to end in decisions. One cross-functional friction named and owned.

The difference from the initiatives above is not size. It is aim. Each small fix is chosen at a joint, with the whole system in view — so the next one builds on it instead of starting over.

Then build, as the organization is ready. The goal is ownership that stays with your team. A system that works only while an outside advisor is in the room has not been built; it has been borrowed.

Some small changes feel worse before they feel better. That is what replacing familiar habits can feel like. It is not evidence the change is failing.

Where this work comes from

This work did not start as a model. It came out of years of working with leaders where strategy has to turn into decisions, commitments, measures, and follow-through.

Three things have shaped it.

Where the work starts. The Blueprint — the individual-and-team tool at the front of this work — has been used with more than 6,000 leaders across more than 50 organizations. That is the reach of one tool, not a count of organizations running the full system.

What leaders surface. We keep an anonymous working record of the execution frictions that come up in coaching and advisory work across multiple organizations. Many come from managers, directors, and vice presidents in the middle of the business, where strategy turns into work. The record does not prove which solution works. It does show where execution gets stuck and what sits underneath it.

What holds up in practice. For more than 25 years, my colleagues at Excel Leadership Group and I have worked alongside leadership teams as they make decisions, set priorities, run meetings, manage commitments, and work through the frictions between functions. We have seen what leaders keep using six months later and what quietly disappears.

The disciplines in this series were shaped in that work. Each has been used in real organizations and refined through practice. Connecting all five into one integrated system is newer. It is the next step in what that work has been teaching us.

Test it against your own leadership team. If the pattern is real, you will be able to see it.

Try this now

You do not need to build anything to get something out of this.

Take the two execution problems that have cost your business the most over the past year. For each, identify which discipline appears to be breaking — then test the connections on either side of it. The visible problem may sit in one discipline while the open gap sits in the joint next to it.

A meeting that never produces decisions can be a decision rights gap: nobody in the room holds the authority to call it.

A scoreboard nobody acts on can be an operating-rhythm gap: there is no forum built to turn a miss into a decision and an owner.

An accountability problem can be a priorities gap: people are being held to commitments that compete with each other.

That reframe changes where you start.

Growth exposes what individual effort used to absorb. Build the system before complexity demands it, and the business depends less on heroics.