The Accountability Cascade: From Board Strategy to Individual Ownership
A little over a year ago I was asked to sit in on a quarterly business review at a company that, on paper, did everything right.
The board had spent two days offsite refining a strategy that was genuinely good three clear priorities, a defensible view of the market, sensible capital allocation. The strategy deck had been distilled to a single slide, which is usually a sign that someone senior has done the hard work of subtraction. The CEO presented it to the executive team with real conviction. Everyone nodded. The priorities were, as the saying goes, cascaded.
Nine months later the same company was missing on all three. Not by a little. The first priority a shift toward a subscription revenue model had produced a pilot with fourteen customers and no plan to scale it. The second, a consolidation of the product portfolio, had quietly stalled because no single executive believed it was theirs to drive. The third had been reinterpreted so many times on its way down the organisation that the people executing it were working toward a goal that bore only a passing resemblance to what the board had approved. When I interviewed the head of one of the affected business units and asked what the company’s top priority was, she gave me a confident, articulate answer. It was wrong. Not vague wrong. She was executing diligently against a version of the strategy that had mutated three layers above her.
This is the part that should worry every board and executive team, because nothing in that story involved incompetence or bad faith. The strategy was sound. The people were capable and committed. The communication had, by every conventional measure, happened. The CEO could point to the all-hands, the emails, the OKR tool where the priorities were dutifully logged. And yet the strategic intent that existed with total clarity in the boardroom had, by the time it reached the people whose daily decisions would actually determine the outcome, degraded into something unrecognisable. This is not a communication problem, and treating it as one is precisely why it keeps happening. What I was watching was a failure of the accountability cascade the mechanism by which strategic intent at the top is meant to convert, layer by layer, into individual ownership at the bottom. In my experience across more than 1,200 projects, this is the single most under-diagnosed reason that good strategies fail to execute.
The Difference Between Communication and Cascade
The instinct, when strategy fails to land, is to communicate harder. More town halls, clearer decks, a snappier framing of the priorities. This almost never works, because it misdiagnoses the failure. Communication moves information. A cascade moves accountability and these are structurally different things.
When you communicate a strategy, you are transferring understanding. The recipient now knows what the priority is. But knowing a priority and owning an outcome are separated by a gap that no amount of clarity can close on its own. The head of the business unit in my opening story understood the strategy perfectly well at the moment it was communicated to her. What she did not have was a translated, owned version of it: a specific outcome she was personally accountable for, expressed in the terms of her own function, with the authority and resources to pursue it and a consequence attached to whether it happened. Communication ended at understanding. The cascade never completed.
Here is the pattern I have learned to look for, because it is remarkably consistent. Strategic intent degrades not through a single dramatic failure but through a series of small, reasonable-looking translations. At the board level, the priority is “shift to a subscription model.” The executive who owns it translates it into “grow recurring revenue to 40 per cent of the mix.” Sensible. Her direct reports translate that into “launch three subscription products this year.” Also sensible. Their teams translate that into “ship the subscription billing feature by Q3.” Each translation is locally rational. But somewhere in that chain, the strategic intent change how we make money, and therefore how we relate to customers has quietly become a feature-delivery task. The people at the bottom are now accountable for shipping a billing system, not for changing the revenue model. They can succeed completely at their objective while the strategy fails entirely.
This is what I call translation drift, and it is the mechanism through which most cascades fail. It is important to distinguish it from two things it resembles but is not. It is not misalignment, in the usual sense, because at every individual handoff the two parties are aligned. And it is not a lack of accountability everyone in the chain is accountable for something, often quite rigorously. The problem is that accountability for the *right thing* is not what got passed down. Each layer took ownership of its local translation, and the sum of all those locally owned translations did not reconstitute the original strategic intent. The cascade preserved the appearance of ownership while losing its substance.
The Cascade-Mapping Framework
What I use to diagnose and repair this, both in reviews like the one above and when designing delivery structures from the outset, is a cascade map built on four tests applied at every layer of translation. The map treats each handoff board to executive, executive to function head, function head to team, team to individual as a formal transfer that either succeeds or leaks. The four tests are what determine which.
The first is the Translation Test. At each layer, can the person receiving the objective restate it in a way that still contains the strategic *why*, not just the local *what*? This is not a comprehension check; it is a fidelity check. When I ask a team lead what they are working toward and they say “shipping the billing feature,” the cascade has leaked, because the why has been stripped out. When they say “we are shipping the billing feature because it is the enabling step in moving the company to recurring revenue, and if it does not drive adoption it has not done its job,” the translation has held. The test is whether the strategic intent survives the handoff, not whether the task is understood. Most organisations never test for this, because their OKR and objective-setting tools record the local what and have no field for the inherited why.
The second is the Ownership Test. For every strategic priority, is there exactly one named individual at each layer who owns it not a committee, not a function, not “the leadership team”? This sounds obvious and is almost never true in practice. In the portfolio-consolidation failure from my opening story, the reason nothing moved was that ownership was diffuse: three executives each felt partly responsible and therefore none felt decisively accountable. Diffuse ownership is functionally identical to no ownership. The Ownership Test forces a single name against each priority at each level, and it exposes the layers where a priority has been “assigned to the team” which is the polite organisational phrase for orphaned.
The third is the Authority Test, and it is the one most often missed. Accountability without matching authority is not accountability; it is a setup for blame. At each layer, does the owner actually control the decisions and resources required to deliver the outcome they have been made accountable for? I have repeatedly seen executives hold a function head accountable for a cross-functional outcome while withholding the authority to direct the other functions involved. When that outcome fails as it inevitably does the organisation records it as an accountability failure by an individual, when it was in fact an authority failure by design. The Authority Test asks, bluntly, at every layer: can this person actually cause the thing they are accountable for to happen? If the honest answer is no, the cascade is broken at that layer regardless of how clear the objective is. This connects directly to the logic of the Decision-Right Framework you cannot cascade accountability faster than you cascade the authority to act on it.
The fourth is the Consequence Test. Is there a real, observable difference in what happens to the owner depending on whether the outcome is delivered? Consequence does not mean punishment; the most powerful consequences in mature organisations are reputational and developmental rather than punitive. But if delivering the strategic priority and quietly not delivering it produce identical outcomes for the individual, then the priority is not actually being cascaded it is being suggested. The Consequence Test is uncomfortable because it usually reveals that the organisation’s real accountability structure, the one encoded in promotions and standing and who gets the interesting work, is decoupled from its stated strategic priorities. People are extraordinarily good at reading which one is real.
Applied together, these four tests turn the abstract idea of “cascading strategy” into something you can actually audit. You take a single strategic priority, trace it down through every layer of the organisation, and mark at each handoff whether the translation held, whether ownership was singular, whether authority matched accountability, and whether consequence was real. The layer where the first test fails is where your strategy is dying and it is almost never the layer people assume.
What Changed in Practice
When I mapped the subscription-model priority for the company in my opening story, the results were clarifying in a way that no amount of further communication could have been. The Translation Test held for the first two layers and failed sharply at the third: below the function-head level, nobody could articulate the revenue-model why, only the feature-delivery what. The Ownership Test failed at the executive layer for the portfolio priority three names, no single owner. The Authority Test failed for the subscription priority, because the executive accountable for the revenue mix did not control the pricing decisions that sat with a separate commercial function. And the Consequence Test failed almost everywhere, because the company’s promotion cycle rewarded shipping features on time, which is exactly the local translation that had displaced the strategic intent.
We did not fix this by relaunching the strategy. We fixed it one broken layer at a time. For the subscription priority, we reassigned authority so that the accountable executive genuinely controlled pricing, packaging, and go-to-market for the recurring line a change that required the CEO to override a functional boundary that had existed for years, and which was resisted precisely because it was consequential. For the portfolio priority, we collapsed three diffuse owners into one, and the executive who took it did so knowing it would now define her quarter. We rewrote the team-level objectives to carry the inherited why explicitly, so that “ship billing by Q3” became “drive subscription adoption, of which billing is the enabling step, measured by activated recurring accounts.” And we changed what the quarterly review actually examined not activity, but whether the strategic why had survived to the layer doing the work.
What worked was the diagnostic discipline of tracing a single priority all the way down before touching anything. What did not work, at first, was the authority reallocation: the commercial function experienced it as a loss of territory, and it took a direct and slightly uncomfortable intervention from the CEO to hold the line. The lesson there is that a cascade cannot be repaired by the layer where it broke it almost always requires action from the layer above, which is why boards that delegate cascade repair to the middle of the organisation watch it fail again.
Where the Cascade Model Falls Short
I want to be honest about the limits of this, because a framework presented without its failure modes is a sales pitch, not a tool. The cascade map is powerful for a specific class of problem: strategic priorities that must convert into individual ownership through several organisational layers. It is overkill for a flat organisation of thirty people where the founder and the person executing are one conversation apart. In that setting, formalising a four-test cascade would introduce exactly the bureaucratic drag it is meant to prevent.
The more serious limitation is that the model assumes the strategy is worth cascading. A perfectly executed cascade of a bad strategy simply delivers failure faster and with more conviction. The framework tests fidelity of transmission, not quality of intent, and it is entirely possible to pass all four tests at every layer while marching the whole organisation off a cliff with excellent alignment. I have seen this too, and it is more dangerous than translation drift, because drift at least tends to blunt bad strategies as much as good ones.
There is also a real failure mode in adoption: organisations that embrace the Consequence Test as licence for a blame culture. The test asks whether outcomes differ, not whether individuals should be punished. When leaders hear “consequence” and reach for punishment, the predictable result is that people stop taking accountability for anything ambiguous or risky which is to say, for anything strategically interesting. The cascade then optimises for safe, deliverable, locally rational objectives, which is precisely the disease it was meant to cure. Consequence must attach to ownership honestly held, not to outcomes that were never within the owner’s authority to control which is why the Authority Test must always be applied before the Consequence Test, never after.
The Real Test of a Strategy
The uncomfortable truth that this framework keeps surfacing is that most organisations do not have a strategy problem or a talent problem. They have a transmission problem, and it hides in plain sight because every individual link in the chain looks sound. The board is clear. The executives are aligned. The teams are diligent. And the strategy still fails, because clarity, alignment, and diligence at each layer do not add up to fidelity across all of them. Accountability is not a substance that flows downhill by gravity once you have communicated it well enough. It is transferred, deliberately, one tested handoff at a time or it is not transferred at all.
The most senior thing a board can do is stop asking whether the strategy has been communicated and start asking whether it has survived. Trace one priority to the individual whose daily decisions determine its fate, and listen to how they describe what they are doing. If the why is still intact when it reaches the bottom, you have a cascade. If only the what remains, you have an echo and an echo has never delivered a strategy in the history of organisations.