• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : OKR Cascade Alignment Score

Description

OKR Cascade Alignment Score measures how well team-level OKRs connect to and support organisational objectives — assessing the structural integrity of the goal hierarchy from enterprise intent to team execution. This measure directly reflects a leader's ability to translate strategic direction into work that genuinely moves the needle at every level.

Without deliberate cascading, teams frequently optimise for locally coherent goals that diverge from organisational priorities. Leaders who achieve a high alignment score demonstrate disciplined translation of strategy, not just distribution of targets.

How to Use

What to Measure

  • Number of team-level Key Results that can be directly traced to a parent Objective at the portfolio or organisation level
  • Number of team-level OKRs with no traceable link to any organisational objective
  • Proportion of objectives in the cascade where the parent-child contribution logic is explicitly articulated
  • Frequency of alignment reviews during the OKR cycle

Formula

OKR Cascade Alignment Score = (Team KRs with traceable organisational link / Total Team KRs) × 100

Optional:

  • Weighted Alignment Score: weight each KR by its planned capacity allocation to surface misalignment where it consumes the most effort
  • Bi-directional coverage: also check that each organisational objective has at least one contributing team-level KR

Instrumentation Tips

  • Use OKR tooling (e.g. Lattice, Gtmhub, Perdoo, Notion) that supports explicit parent-child linking between objectives
  • Tag orphaned KRs (those with no upward link) and review them monthly with leadership
  • Run a cascade audit at the start of each OKR cycle before goals are locked
  • Include alignment score as a standing agenda item in QBRs and leadership reviews

Benchmarks

Score Interpretation
90–100% Excellent — near-complete strategic coherence across team and org levels
70–89% Good — minor gaps; most team work is strategically anchored
50–69% Moderate — significant portions of team effort lack strategic traceability
Below 50% Poor — widespread misalignment; substantial effort potentially off-strategy

Why It Matters

  • Prevents strategic drift Teams working on unlinked OKRs consume capacity on work that may be locally valuable but strategically irrelevant, creating the illusion of busyness while organisational goals stall.

  • Enables coherent prioritisation Leaders with a high cascade score can make confident trade-off decisions because all work has visible strategic weight — enabling deprioritisation of lower-value efforts without guesswork.

  • Improves accountability When every Key Result has a traceable organisational link, accountability conversations shift from activity reporting to outcome contribution — a fundamentally higher-quality leadership dialogue.

  • Surfaces planning quality A low score is often a diagnostic signal that either organisational OKRs are too abstract to cascade meaningfully, or that leaders are setting team goals before strategy is sufficiently clear.

Best Practices

  • Conduct a cascade review workshop at the beginning of every OKR cycle before goals are finalised
  • Require explicit articulation of the contribution hypothesis for each team KR (i.e. "achieving this KR contributes to parent objective X because…")
  • Make cascade visualisations available to the whole team, not just leaders, so everyone understands strategic context
  • Review the cascade mid-cycle to catch drift introduced by changing priorities or team restructuring
  • Use the score trend over multiple cycles as a leadership development indicator, not just a one-time audit

Common Pitfalls

  • Treating cascade alignment as a bureaucratic tick-box exercise rather than a genuine strategy dialogue
  • Setting organisational OKRs so broadly that almost any team activity can be loosely linked — inflating the score without genuine alignment
  • Only cascading downward without checking that team-level KRs collectively cover organisational objectives (bottom-up coverage gap)
  • Allowing the score to remain high on paper while the actual work diverges due to mid-cycle priority changes that are never reflected in OKR updates

Signals of Success

  • Team members can explain how their day-to-day work connects to organisational strategy without referring to documentation
  • Mid-cycle reprioritisation decisions reference the cascade explicitly, removing lower-alignment work first
  • Leadership reviews consistently use cascade visualisations to anchor outcome conversations
  • OKR cycle retrospectives show improvement in cascade completeness over time

Related Measures

  • [[Strategic Narrative Retention Score]]
  • [[Priority Alignment Rate]]
  • [[Strategy-to-Execution Lag]]
  • [[OKR Achievement Rate]]

Aligned Industry Research

  • Measure What Matters (John Doerr, 2018) Doerr's foundational OKR framework emphasises bidirectional alignment — objectives cascade down while contributing upward — as the mechanism that converts strategy into coherent organisational action.

  • The Execution Premium (Kaplan & Norton, 2008) Research from the Balanced Scorecard tradition demonstrates that organisations with strong strategy-to-execution linkage outperform peers on financial and operational metrics by a significant margin.

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering