By Dakhalfani Boyd · Principal, BoydNorth

1.The execution gap.

Every year, organizations commit enormous sums to transformation. New systems, new operating models, new strategies meant to reposition the enterprise for the next decade. The investment is approved with confidence, launched with fanfare, and tracked on dashboards that turn from red to green as milestones are met. And then, often, nothing changes. Not in the way that mattered. The system is live, but the old process runs quietly alongside it. The strategy is published, but the organization keeps making the decisions it always made. The dashboards are green, but the outcome that justified the investment never arrives.

This is not a rare misfortune. It is the norm. Roughly seventy percent of large-scale change efforts fall short of their goals, and the figure has barely moved across decades, through new frameworks, new technologies, and several reinventions of the consulting vocabulary. That stability is the most important thing about the number. It tells you the cause is not any particular technology or method, because those have all changed while the failure rate has not. The cause is something more durable, something about how organizations execute.

A failure rate that high in any other discipline would force a reckoning. In transformation it is absorbed, rationalized, and repeated, because each organization experiences its own failure as a unique misfortune with local villains. The vendor underdelivered. The reorganization got in the way. A key leader left. Each explanation is specific, local, and exonerating, and each one prevents the organization from seeing that it has just participated in a thoroughly documented pattern.

Here is the hopeful part of a discouraging statistic. Because the failures are patterned, they are predictable, and because they are predictable, they are beatable. The seventy percent do not fail randomly. They fail in a small number of specific, recurring ways. An organization that learns to anticipate those failure points and build against them before they break is not relying on luck. It is relying on method. The organizations in the successful minority are not smarter or better funded. They have simply learned to treat execution as a discipline with known failure modes, the way a good engineer treats a structure with known stress points, and they reinforce the joints before they crack.

2.1Weak Governance.

Most transformations are governed like projects when they should be governed like enterprises. A steering committee meets monthly, reviews a status deck, notes the items trending red, and approves the move to the next phase. The meeting has the trappings of governance, the senior attendees, the structured agenda, the decisions recorded in minutes, and it makes none of the decisions that actually determine the outcome. The consequential decisions, the contested trade-offs between business units, between speed and adoption, between near-term cost and long-term capability, are made informally, made late, or not made at all.

Weak governance rarely announces itself. It shows up as drift. Scope expands a reasonable addition at a time, until the program is carrying twice what it was funded to carry. Decisions that should take a day take a month. The clearest symptom is the decision that keeps coming back, discussed in one meeting, seemingly settled, and reopened two meetings later because it was never truly owned. An organization that cannot make a decision stick does not have a meeting problem. It has a governance problem, and no amount of better facilitation will fix it until someone is accountable for the decision and empowered to close it.

Governance is the first failure point because it sits upstream of all the others. Unclear decision rights are a governance failure. Competing priorities go unresolved because governance will not resolve them. Sponsorship fades because governance does not hold sponsors accountable. Fix governance and the other four become tractable. Leave it weak and no amount of effort downstream will compensate.

2.2Unclear Decision Rights.

When no one can say who decides, everyone can delay. Unclear decision rights are the quiet tax on every stalled transformation, quiet because they never appear under their own name. They appear as slowness, as rework, as a meeting that should have ended in a decision and instead ended in a plan to meet again. A genuinely cross-functional question lands in a room where everyone has a view and no one has the authority to decide for the others, so it is taken away to be socialized, and socializing a contested decision among people whose interests conflict produces months of latency and no resolution.

Ambiguity persists because it is comfortable. As long as no one clearly owns a decision, no one is clearly accountable for it. Shared ownership feels collaborative and safe. But decisions distributed across many owners are decisions no one is positioned to make, and the comfort of shared ownership is purchased with the currency of speed. Sometimes the ambiguity is even deliberate, because a leader named as the owner of a decision can be held accountable for it, and vagueness preserves deniability.

2.3Competing Priorities.

A transformation rarely competes against opposition. Almost no one stands up to argue that the change should fail. It competes against everything else the organization is already trying to do, and it is the one initiative with the longest payback and the least immediate consequence for neglect. When priorities compete and leadership has not chosen among them, the default winner is whatever is most urgent today. The transformation, important but not urgent, loses a week here and a key person there, each concession reasonable, the cumulative effect a transformation that is always slipping and never quite failing.

This is why a transformation can be universally endorsed and still starve. Endorsement is free and protection is expensive. Saying the transformation is a priority costs a leader nothing. Protecting the time of the people it depends on means saying no to other legitimate demands, and that is the cost most leaders are reluctant to pay. The flattering belief that a key contributor can run their function and carry the transformation on borrowed evening hours is almost always false, and the borrowed hours vanish the moment their core role hits a crisis.

2.4Inconsistent Sponsorship.

Of every lever a leader can pull, sponsorship is the strongest. In Prosci's data, roughly seventy-nine percent of projects with strong, active sponsorship met or exceeded their goals, against about twenty-seven percent when sponsorship was poor. Few variables in management have an effect that large or that durable. Yet sponsorship is the lever leaders are least disciplined about, because they treat it as a designation rather than a behavior, a name on a charter rather than a sustained pattern of visible engagement.

Most sponsorship does not fail because it was never there. It fails because it was inconsistent. The sponsor is committed at kickoff, gives the rousing speech, and is then pulled toward the next urgent thing, reappearing at the go-live celebration and disappearing again precisely when the hard work of adoption begins. Organizations are exquisitely sensitive to where leadership attention actually goes, far more than to where leadership says it goes. A sponsor present only at the start and the end teaches the organization, more effectively than any memo, that the change is optional in the long middle where it has to happen.

2.5Low Adoption.

Every prior failure point eventually surfaces here. Adoption is where weak governance, unclear decision rights, competing priorities, and absent sponsorship all come due at once. The system goes live, the training is delivered, the dashboards turn green, and then usage drifts. Workarounds return, first as exceptions and then as habits, and an expensive capability, fully paid for, settles into a fraction of its intended use. The organization is left with the cost of the new system and most of the inefficiency of the old.

Adoption is a curve, not an event, and the curve dips before it rises, because the new way is harder than the old until it is practiced. Organizations that expected a smooth rise read the expected, temporary dip as failure and permit the reversion that kills the change. Reversion happens not through a decision but through a thousand small, individually rational choices to fall back on the familiar under pressure, which is why mandate alone never produces adoption. You can require compliance in the calm moments. You cannot mandate the choice people make when the old way is faster and no one is watching.

3.1How the five connect.

It would be convenient if the five failure points were five separate problems, because separate problems can be assigned to separate owners and solved one at a time. They are not separate. Pull on any one of the five and the other four come with it, because they are not really five things. They are one execution system breaking down in five visible places.

The causation runs in a consistent direction, downhill from governance to adoption. Weak governance leaves decision rights unclear. Unclear decision rights leave competing priorities unresolved, because resolving them requires someone with the authority to choose. Unresolved priorities undermine sponsorship, because a sponsor cannot protect a transformation the organization has never formally chosen. And faltering sponsorship guarantees low adoption, because adoption depends on sustained leadership attention through the fragile period after launch, which inconsistent sponsorship withdraws at exactly the wrong moment.

This is why low adoption, the symptom organizations most often attack directly, is the one furthest from its cause. By the time the failure surfaces as low adoption, it has already passed through four upstream failures, and a communications campaign aimed at the symptom is fighting a problem that originated in the governance structure four links upstream. The highest-leverage move is almost always to fix the most upstream weakness first, because fixing it relieves the pressure on everything downstream.

3.2The 5A Framework.

The five failure points describe how execution breaks. The 5A Framework describes how to close the gap, as a leadership and execution system rather than a methodology to be administered. It addresses the five as a connected system, intervening at the root and working downstream.

1. Assess Read the current state honestly. Map how the work actually flows rather than how the documentation says it does, locate which of the five points is weakest, quantify what the status quo is costing, and establish the baseline that every later claim of progress will be measured against.
2. Architect Design the future deliberately. Build the operating model, the governance, and the decision rights on purpose rather than inheriting them by accident, and sequence the work by value and dependency so the transformation proves itself early.
3. Align Build commitment, not just awareness. Convert nominal sponsors into active ones, establish decision rights everyone accepts, and surface resistance while it is still cheap to address. Communication transfers information; alignment produces commitment, and only commitment survives the moments of cost.
4. Activate Implement under real conditions. Hold the outcome fixed while adapting the method to what reality reveals, read resistance as information about a real problem, and treat go-live as a starting line, keeping attention and resources focused on the fragile weeks after launch.
5. Anchor Make the change permanent. Keep measuring against the baseline, reinforce the new way through the incentives and routines that shape behavior, and withdraw the external support deliberately so the change proves it can stand on its own. A transformation is finished only when the new way is simply how the organization runs.

None of this requires a new strategy. It requires treating execution as the discipline it has always been, and the one most organizations have never managed. That is the whole of the argument, and the work is in making it practical.