Aligned, Not Cascaded
Cascading OKRs level by level is slow, bureaucratic, and quietly kills autonomy. Real alignment comes from three things instead: strategy comprehension, outcome-focused execution capability, and clear narratives explaining why each OKR matters now.
The instinct to cascade is understandable. Leadership sets goals, each layer breaks them into sub-goals, and the org chart fills top to bottom with neatly nested objectives. It looks aligned. In practice it is slow (every level waits for the one above), bureaucratic (goals need sign-off before work starts), and corrosive to ownership (teams execute someone else’s decomposition rather than their own thinking). By the time the cascade reaches the front line, months have passed and the goals belong to nobody.
The three ingredients of real alignment
Alignment without cascading rests on three things. First, strategy comprehension and recall: everyone can actually reconstruct the strategy, not just nod at it. Second, outcome-focused execution capability: teams that know how to turn a goal into measurable progress without being told the steps. Third, clear impact narratives: every OKR explains why it matters now and how it connects to the strategy, so the reasoning travels with the goal. Give teams those three, and they set good OKRs on their own, faster and with more ownership than any cascade produces.
Input without approval
The operating rule is that teams seek input but do not wait for approval. They share drafts, invite challenge, and check alignment with neighbours and leaders, but they are not blocked pending a sign-off chain. This only works when trust and strategic clarity are high enough to replace the approval process, which is why comprehension is the precondition: you cannot safely remove the approvals until the strategy is genuinely understood. Where that understanding is missing, cascading returns as a symptom, and the fix is to build the understanding, not reinstate the bureaucracy.
A precision point on Martin’s cascade
There is an apparent contradiction worth clearing up. Roger Martin’s Strategy Choice Cascade does cascade, so does it conflict with this principle? No, and the distinction is exact: choices cascade logically, each strategic choice constraining the next, in both directions; goals must not cascade bureaucratically, level-by-level, for approval. The logic flows down as constraint and up as feedback; the paperwork does not. Confusing the two is why so many organisations think they must choose between alignment and autonomy, when the whole point is that you can have both.
Why it is faster
Counter-intuitively, removing the approval chain speeds alignment rather than loosening it. A team that understands the strategy and writes its own goals commits to them in a way no assigned goal can match, and it starts work in week one rather than week six. The organisation trades the illusion of control, a tidy nested chart, for the reality of momentum: many teams moving in a genuinely shared direction because they understand it, not because they were instructed.
Instead of the exec team decomposing the company goal into nine team sub-goals over six weeks of sign-off, each team reads the strategy, drafts its own OKR with a narrative linking it to the company’s How to Win, and shares it for challenge. Alignment is checked in days, and every goal has an owner who chose it.
Doesn’t removing approval risk misalignment? +
Only if comprehension is weak. When teams can recall the strategy and every OKR carries a narrative linking it upward, misalignment surfaces in the sharing step, without a formal gate. The narrative is the alignment mechanism.
How is this different from letting teams do whatever they want? +
Autonomy is bounded by shared strategy, not absent of it. Teams choose their goals, but those goals must trace to the strategy in a narrative anyone can read. Freedom within a frame, not a free-for-all.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
Alignment without approval chains only works when strategy is genuinely understood. We build that comprehension, then install the narrative discipline that keeps autonomous teams pointed the same way.