Home / Guides / How should OKRs cascade and align?

How should OKRs cascade and align?

Short answerOKRs should align by negotiation, not by rigid top-down cascade. Leadership sets a few company objectives, and each team writes its own OKRs and connects them to a parent objective. The goal is that every team OKR ladders up to strategy, without leadership dictating the goals. An objective with no parent is a goal with no strategy behind it.
Company objective the direction Product OKR aligned Sales OKR aligned CS OKR aligned
Alignment done right. Leadership sets a short list of company objectives; each team writes its own OKR and connects it up. An objective with no line to the top is the flag to chase.

Cascade is not the same as dictation

The old model was strict cascade: the CEO's goals split into VP goals, split into team goals, split into individual goals, straight down the tree. It looks tidy and it kills ownership. Teams handed goals they did not write do not fight for them.

The better model is alignment by negotiation. Leadership sets three to five company objectives. Teams read them, write their own OKRs, and connect each one to a parent. Direction comes from the top. The goals come from the teams. Both hold.

What good alignment looks like

1/ A short list of company objectives everyone can see. 2/ Every team OKR linked to one of them. 3/ Cross-team dependencies named, not hidden. When a team objective has no parent, that is a flag: either the work does not matter, or the strategy above it was never made clear.

Alignment you can measure

Alignment is countable. Take every team and individual objective and check whether it has a parent. The share that do is your alignment score, one of the four pillars of program health. When the number is low, you have teams working on things that connect to nothing, or a strategy nobody understood.

The failure to avoid

Do not confuse alignment with agreement on everything. Teams should push back, negotiate, and own the result. What you want is a visible line from every team's work to the company's direction, not a hierarchy of copied goals.

By the numbersAlignment is countable: the share of team and individual objectives that have a parent. When the number is low, teams are working on things that connect to nothing.

Frequently asked

What is OKR alignment?

Alignment is the degree to which team and individual OKRs connect to the company's objectives. High alignment means every team's goals ladder up to strategy; low alignment means teams are working on things that connect to nothing.

Should OKRs cascade top-down?

Direction should come from the top, but goals should come from the teams. Leadership sets company objectives; teams write their own OKRs and link them up. Strict top-down cascade kills ownership.

How do you measure alignment?

Count the share of team and individual objectives that have a parent objective. That percentage is your alignment score. Objectives with no parent are the flags to chase.

Sources: Andy Grove, High Output Management (Intel, origin of OKRs). John Doerr, Measure What Matters and whatmatters.com. Christina Wodtke, Radical Focus. Felipe Castro on outcomes vs output. Google re:Work OKR guide. Keel market research, July 2026.

Measure this, don't hope for it.

Keel scores your OKR program on all four pillars and shows the teams letting it slip. Request early access.

No spam. We only reach out about early access.