OKR alignment vs cascading: how goals should move through an org

Every company that adopts OKRs hits the same question in its first quarter: once leadership has set the company OKRs, how do they reach everyone else? The instinctive answer, cascading the same goals down every level, is also the one that quietly breaks the whole system. Here’s why, and what works instead.

#Cascading vs aligning: the difference

Cascading is the top-down practice of passing OKRs down the org chart, level by level. In its crudest form, each level copies the level above. Aligning means each team writes OKRs that contribute to a parent OKR, in language and metrics the team controls, and links them explicitly so progress can roll up.

Both start from the same place, the company OKRs. The difference is what happens at each step down.

#Why copy-paste cascading fails

Copying looks tidy on a slide. In practice it creates four problems.

1. Nobody knows what they own. An SDR can’t move company ARR on their own, so a key result that says they should is either ignored or quietly reinterpreted.
2. Progress can’t roll up. If twelve teams all claim “Grow ARR to $10M”, the company number is counted twelve times and attributed to no one.
3. Teams lose agency. OKRs are supposed to let the people closest to the work decide how to reach the outcome. A copied goal removes that decision.
4. It’s slow. Strict cascades wait for each level to finish before the next starts. By the time OKRs reach the front line, a month of the quarter is gone.

#What alignment by contribution looks like

The rule is simple: a child objective states the part of the parent its owner can move. Take a company objective, “Win the mid-market”, with the key result “Grow ARR from $4M to $10M”.

Each aligned OKR is in a metric the owner controls, and each connects to the parent. For the additive ones (bookings, expansion), the targets are sized so they genuinely sum to the company number. We walk through the arithmetic in key results that add up.

#Top-down, bottom-up, or both?

Pure top-down OKRs are fast to set and slow to believe in. Pure bottom-up OKRs are motivating and rarely add up to a strategy. Teams that run OKRs well mix the two:

• Leadership sets the few company outcomes and the key results that define them.
• Each team proposes how it will contribute, including outcomes leadership didn’t think of.
• Managers review the fit: no gaps (every company key result has owners), little overlap, realistic targets.

Think of it as a negotiation in two directions. The parent sets the destination; the child decides the route and says what it needs from others.

#How to align OKRs in five steps

1. Publish the company OKRs first, with baselines and targets. Two to four objectives is plenty.
2. Each function lead drafts contributions. For every company key result, ask “what part of this do we control?” and write that as your OKR.
3. Link each child to its parent. A key result that rolls up names its parent key result. An objective that supports another says so.
4. Check coverage. Every company key result should have at least one owner below it, and additive targets should sum. Gaps and double-counting show up here.
5. Repeat one level down, in parallel rather than waiting for every function to finish. Managers can start as soon as their own manager’s draft is stable.

#Shared outcomes and dependencies

Real OKRs depend on each other. Product ships what Sales sells; Operations hires and funds both. Two practices keep this honest:

• Split shared outcomes by control. “Grow enterprise ARR” becomes bookings for Sales, the enterprise features it needs for Product, and retention for Customer Success. It isn’t cloned to all three.
• Write dependencies down. If your objective needs another team’s work, say so in the description (“Depends on: SSO shipping by week 6”) and link it. A dependency hidden inside a key result is a surprise waiting for week ten.

#The contribution test

Run every team objective through three questions before the quarter starts:

• Does it say what this team will change, in a metric it can move?
• Is it linked to a parent, or is there a clear reason it stands alone, like team health or tech debt?
• If every team hits its target, does the parent key result hit its target too?

#How OKR.ai handles alignment

OKR.ai is built around this model. Everyone works on one canvas with their manager above and their reports below.

• Pull & align with AI. From your manager’s OKRs, AI drafts yours so they support theirs, with key results sized to add up.
• Push to reports. AI splits your OKRs across your reports by role and function. Each report pulls their share and adapts it.
• Acknowledge and approve. Every change needs the owner to acknowledge it and their manager to approve, and anything new or changed since the last approval is flagged.
• Need-to-know visibility. You see full OKRs and progress for yourself, your manager and your reports. Further away, people see objectives and key results only.

See the full loop in the OKR workflow docs.

#Frequently asked questions