OKR cascading: passing goals down without locking them in

Definition

Up front: cascading is an alignment mechanism, not a mechanical chain of orders. The point is to propagate strategic meaning from the company level down to the teams, not to copy-paste Objectives or push down a list of tasks.

Concretely, cascading is the mechanism that connects company Objectives to team Objectives, then potentially to individuals. It supports vertical alignment without turning OKRs into top-down planning.

The nuance matters: bad cascading copy-pastes company Objectives into every team and kills ownership. Good cascading hands down the "why" and lets each team frame its own "what".

Cascaded OKR: what it concretely means

A cascaded OKR is a team OKR that explicitly derives from a higher-level OKR (company, BU). It establishes a documented parent / child relationship.

Three cascading patterns exist:

Pattern	Mechanism	When to use it
Objective cascading	The team reuses the parent Objective and frames its own Key Results.	When the company Objective speaks directly to the team (e.g. the Sales team on a growth Objective).
Key Result cascading	A company Key Result becomes a team Objective.	When a company KR rests almost entirely on a single team (e.g. the KR "Reduce churn" becomes the CS team's Objective).
Contribution cascading	The team frames its own Objective that contributes to a parent Objective without copying it.	The most common and healthiest pattern: the team thinks for itself about how it serves the strategy.

Cascading vs top-down: don't conflate them

Cascading isn't top-down. Top-down imposes Objectives and Key Results at every level. Cascading imposes direction (the parent Objective) but lets each team frame its own Key Results and pick its Initiatives.

A mature OKR practice combines cascading with bottom-up: leadership sets the company Objectives, teams propose their own OKRs contributing to those, and an arbitration dialogue brings everything in line.

Watch out: excessive cascading kills ownership

The more systematically and finely an organization cascades, the more it risks killing team engagement. Three signs of excessive cascading:

Every team OKR is rigorously aligned to a parent, but no team could explain its Objective in their own words.
Cascading goes down to the individual level for roles that don't need it (see levels of OKR).
Managers spend more time documenting parent/child relationships than actually keeping Objectives alive.

Practical rule: better to have partial, living cascading than exhaustive, formal cascading. Not every team contributes to every company Objective, and that's fine.

Common cascading mistakes

Anti-pattern	Symptom	Fix
Cascading by copy-paste	Every team has the same Objectives as the company.	Each team must translate the parent Objective into its own words and its own KRs.
Exhaustive cascading	Every company Objective is cascaded into every team.	A team doesn't have to contribute to every company Objective. Pick 2-3 contributions explicitly.
Cascading without dialogue	Teams discover their Objectives at start of cycle.	An OKR planning phase with back-and-forth between levels.
Cascading down to the individual by default	Every contributor has personal OKRs.	Reserve individual OKRs for high-autonomy roles. For most, the team OKR is enough.

Serendly insight: the "restate" test

To check that cascading is healthy, ask each team to present its OKRs to the company in its own words, without quoting the parent Objective verbatim.

If the team can do it and keep the meaning, cascading worked. If they just read out the company Objective, it wasn't cascading, it was transposition.

Set up cascading that actually works

Cascading is the moment when a strategy either becomes the teams', or doesn't. Let's talk about how we structure those conversations in the organizations we work with.

Impact on the organization

Cascading done well turns a corporate strategy into team energy. Done well, it preserves ownership at every level. Done poorly, it becomes thinly-disguised planning that puts out engagement and de-empowers middle managers.

Key takeways for Cascading

Mechanism that propagates company Objectives down to teams through a parent/child relationship.
Three patterns: Objective cascading, Key Result cascading, or contribution cascading (healthiest).
Not top-down: it imposes direction, not the ''how''.
Should be combined with a bottom-up motion and an arbitration dialogue.
Avoid copy-paste cascading and exhaustive cascading to every team.

Curated related readings

Synonyms for Cascading : Cascaded okr; Goal cascading; Okr propagation; Goal alignment cascade;