What cascading gets wrong
Rigid cascades assume strategy decomposes neatly along the org chart. It does not. Strategic objectives are mostly cross-functional, so forcing them down reporting lines creates OKRs that describe each function’s fragment of the work rather than the outcome anyone actually cares about. Teams end up owning arithmetic slices of a number, autonomy disappears, and OKRs become the performance-management paperwork everyone warned you about.
Alignment through articulation
- Keep hierarchies shallow: company objectives, then team OKRs that explicitly connect to them.
- Teams draft their own OKRs against the strategic bets, then alignment is negotiated, not imposed.
- Cross-team dependencies get surfaced and committed before the quarter starts.
- Every team can articulate how their OKR advances a strategic choice; if they cannot, it is not an OKR.
Alignment is a conversation the framework forces you to have, not a spreadsheet operation. That is why it works.
The distinction that resolves the debate
The cascading debate dissolves once two different things stop sharing one word. Choices cascade logically: the company's strategy choice cascade flows from aspiration to systems, and each level's choices constrain the next. Goals must not cascade bureaucratically: level-by-level OKR approval is slow, kills autonomy, and produces goals optimised for the approver rather than the outcome.
The methodology connection
What replaces the approval chain is comprehension: teams that can recall the strategy, as an argument rather than a slogan, set their own OKRs against it, with narratives explaining the connection. The mechanism is covered in our guiding principles, and the writing standard that makes it possible is strategic narrative: if the argument does not travel, autonomy cannot be safe, and cascading returns as a symptom. Alignment is an outcome of understanding, not a property of paperwork.