Skip to content
OKR guide
Chapter 9 of 22

Part 3 · Set goals

Cascading OKRs vs. aligning OKRs

Chapter 9 of 22

Watch on Cloudflare Stream

Once the company OKRs are written, someone will ask how to cascade them down to every team. Our advice is to skip the cascade. We are in good company: Christina Wodtke and Felipe Castro have been making the same case for years.

A cascade promises a tidy tree in which every goal traces back to the top. In practice it slows planning down and falls apart the first time the strategy shifts. This chapter covers why that happens, how to align teams around Objectives instead, and how to keep the traceability people like about a cascade without the upkeep.

First: what do we call cascading?

In a cascade, the Key Results of one level become the Objectives of the level below. Measure What Matters made the model popular. You will also hear it called laddering OKRs, or an OKR tree.

Take a company expanding into Europe.

Level Objective Key Results
Company Launch our offer in the European market 30% of new sales come from Europe. 50% of our press coverage is from EU publications
Sales 30% of new sales come from Europe Recruit 3 sales associates in Europe. 50% of new SQLs are in the European region
PR 50% of our press coverage is from EU publications Secure 12 press articles in Europe. Increase EU influencers from 20% to 50%

The table stops at two levels. A real cascade keeps going. Each department Key Result becomes a team Objective, and each team Key Result becomes a squad Objective. With two Key Results per Objective, four levels give you 15 OKRs chained together.

A four-level cascading OKR tree. One company OKR with two Key Results feeds two department OKRs, four team OKRs and eight squad OKRs. Each Key Result becomes the Objective one level down, so 15 OKRs are chained together

The appeal is obvious. Every team can point to the parent its goals feed, and the whole company fits on one diagram.

The model depends on two conditions: decisions are made at the top, and execution follows a plan fixed in advance. The book's best-known example comes from Intel in the 1970s. Most organisations now run smaller teams with more autonomy and expect them to act on what they learn during the quarter. A structure that only works when nothing changes is a poor fit for that.

Why cascading OKRs fails

Five problems come with a cascade.

Planning takes too long

Each level can only write its OKRs once the level above has finished. Planning takes about two weeks at each level, to draft, check dependencies and adjust. If the company finishes just before the quarter starts, departments take the first two weeks of it, teams the next two, and the squads at the bottom get their goals six weeks in.

How to set OKRs puts the limit at two weeks for a team's planning. A cascade cannot meet that in any company with more than two layers, so close to half the quarter is gone before everyone is tracking.

Planning timelines compared. In a cascade each level takes two weeks in turn: the company before the quarter, then departments, teams and squads, so squads get their goals six weeks into the quarter. When aligning, every level plans inside the same two weeks and tracking starts in week 1

It assumes your strategy is perfect

Every child OKR inherits the assumptions of its parent. Suppose the press coverage Key Result turns out to be a poor measure of success in Europe: coverage goes up and sign-ups stay flat. The PR team's Objective was that Key Result, word for word. Their plan is now aimed at the wrong thing, and so is every plan beneath it.

The cost grows with every layer. In the four-level tree, that one change invalidates seven OKRs: one department's, two teams' and four squads'. Each rewrite needs a conversation with the level above and the level below, and the people at the bottom hear about it last. Meanwhile they keep working towards a goal that no longer counts.

Strategy rarely gets through a quarter untouched. A competitor launches, a pricing test fails, a large customer changes what it needs. In a cascade, each change at the top means rewriting every level underneath.

The same four-level tree after one company Key Result changes in week 3. The branch under it is highlighted and struck through while the rest of the tree fades back: one department OKR, two team OKRs and four squad OKRs to rewrite, seven in total

It's expensive to maintain

A cascaded tree looks great on the day it is finished. Then a Key Result is reworded, a team is reorganised or a target moves, and the links are out of date. Repairing them takes hours each time. Teams that tire of the repairs stop updating the tree, and not long after they stop opening the OKRs at all.

It leaves many teams on the sideline

Support, Design, Legal and Infrastructure do not map neatly onto a sales target or a press target. That leaves two bad options. You can make those teams write goals against a number they barely influence, which produces OKRs nobody believes in. Or you can add company Key Results until every function has a parent, which produces a company with fifteen priorities.

It turns Key Results into tasks

Look at the bottom of the Europe tree. "Recruit 3 sales associates" and "Secure 12 press articles" are work to complete. They are initiatives, as OKRs vs. initiatives explains. Each step down a cascade narrows the goal, and by the third level there is rarely an outcome left to measure. Teams end up tracking delivery under an OKR label.

How to align teams instead: all eyes on the North Star

Aligning starts from the same company OKRs and gives teams a different brief. Read the company Objective, understand what it is trying to achieve, then write the OKRs that make sense for your team in that light. No parent link is required.

A cascading team answers to a Key Result. An aligned team answers to the intent of the Objective.

Back to Europe. The intent is to make an impact in the European market. The two company Key Results give the scale of the ambition, but they do not list everything the launch takes. Entering a new region also means:

  • product changes for local languages and currencies

  • compliance work for European regulation

  • hosting in the region, so the product is fast and data stays local

  • support during European working hours

None of this needs a company Key Result of its own. A clear Objective lets each team see its part.

An aligned example

Team Objective Key Results
Company Launch our offer in the European market 30% of new sales come from Europe. 50% of our press coverage is from EU publications
Sales 30% of new sales come from Europe EU pipeline from $200k to $1.2M. Win rate on EU deals from 12% to 22%
Product European customers can use the product in their own language 80% of EU sign-ups use a localised version. EU trial-to-paid conversion from 6% to 11%
Infrastructure Europe gets the same speed and data guarantees as our home market EU page load time from 3.8s to under 1.5s. 100% of EU customer data stored in the region
Support European customers get help during their working day First response time in EU hours from 9 hours to under 1 hour. EU satisfaction score from 82% to 92%
PR European buyers have heard of us before the first sales call EU branded searches from 400 to 1,500 a month. 20% of EU demo requests mention press coverage, up from 5%

Sales took a company Key Result as its Objective because one team owns that number. Product, Infrastructure and Support wrote Objectives that no company Key Result mentions, and the launch would fail without them. PR now aims at what coverage is for. If press articles stop producing awareness, the team can change tactics and keep the goal.

Now make the change that broke the cascade. The press coverage Key Result is dropped in week 3. Every team Objective still stands, because each one answers to the company Objective. PR adjusts one Key Result and carries on.

The aligned plan after the same Key Result changes in week 3. Sales, Product, Infrastructure and Support are unaffected. PR keeps its Objective and adjusts one Key Result

Every Key Result in the table has a start and a target. See how to write good Objectives and how to write good Key Results for the rules behind them.

Three ways a team can connect

  1. Adopt a company Key Result as the team's Objective. This works when a single team owns the number, as Sales does above.

  2. Write its own Objective in service of the company Objective. This is the most common case. The team states its contribution in its own words.

  3. Share an Objective with other teams. "Create a state-of-the-art developer community" can be the Objective for Product, Marketing and Developer Advocacy at once, each with different Key Results. Shared Objectives give teams a common language.

Some teams will have no part in a given company Objective this quarter. They should not invent one. Their own problems still deserve OKRs, and their KPIs still tell you whether the business is healthy.

Cascading vs aligning at a glance

Cascading Aligning
What a team answers to A parent Key Result The intent of the company Objective
Planning One level at a time All teams in parallel, inside two weeks
When strategy changes Every level below is rewritten Teams adjust their own Key Results
Teams far from revenue A forced fit, or more company Key Results The contribution only they can make
Upkeep Links break with each edit Few links, added where they are true
What gets tracked at the bottom Tasks Outcomes

How to replicate the benefits of cascading OKRs

A cascade does two useful things. It lets you trace how goals relate, and it lets you see at a glance where the trouble is. You can have both without the rigid tree, as long as you align first and link second.

Step 1. Start by aligning OKRs plans in your org

Put the company OKRs at the top. Each team then creates its own plan underneath. In Tability these are sub-plans.

The Strategy Map shows every plan in one view. Use it to:

  • see all the OKRs in progress

  • compare two plans side by side, for example to check that Marketing and Product are pulling the same way

  • spot the parts of the company that need attention

Step 2. Connect KRs together

Once teams have locked their OKRs, they can add a parent or a dependency to any Key Result. Links can cross teams, and they are optional.

Add a link only where one number really moves another. EU pipeline depends on the localised product, so that link is worth recording. If you have to argue for a link, leave it out.

Step 3. Visualise dependencies with the Cascading Map

The Cascading Map on the company dashboard draws the linked Key Results as a tree.

It is the picture a cascade would have given you, built only from relationships that hold. Teams with no linked Key Results still sit under the Objective they serve. These are also the views to open in the monthly business review.

How to cascade OKRs across departments

If you came here for the steps, this is the version we recommend. It fits inside the two planning weeks.

  1. Publish the company OKRs before team planning starts. Add a short paragraph of intent under each Objective.

  2. Let every department draft at the same time. Nobody waits for another level to finish.

  3. Run one alignment review. Each team presents its draft in five minutes and says which company Objective each of its Objectives serves. The other teams flag conflicts and dependencies.

  4. Fix the gaps. Look for a company Objective that no team picked up, and for two teams whose targets pull against each other.

  5. Lock the plans, then add the links.

A quick test for step 3: for each team Objective, finish the sentence "This helps the company Objective because…". If the team cannot finish it, the Objective either solves a problem of the team's own, which is fine as long as they say so, or it should go.

Top-down or bottom-up?

Both. Direction comes from the top: leadership writes the company OKRs and explains the intent. The team OKRs come from the teams, who know their work better than anyone above them. Goals written only at the top are a cascade. Goals written only by teams are a set of local plans with nothing tying them together.

Best practices for aligning and cascading OKRs

Focus on the Objectives

Cascading puts the weight on Key Results. Aligning puts it on Objectives. Company Objectives have to be clear enough that every team reads them the same way.

A metric can be read several ways. "30% of new sales come from Europe" can be reached by growing Europe or by letting sales at home fall. The Objective tells teams which reading is meant.

Make top-level OKRs easy to access

One company we know printed its quarterly OKRs and put them up everywhere, bathrooms included. That may be a step too far, but the instinct is right. People are busy, and a goal they have to search for is a goal they forget. Keep the company OKRs one click away and open them at the start of each team review.

Review progress on OKRs weekly

Early, frequent check-ins expose a bad OKR while there is still time to change it. Teams adjust as they learn, and alignment gets corrected a little every week. The weekly check-in takes a few minutes per Key Result.

Semantic focus rather than rigid networks

Forcing every team into a complete graph of links causes frustration and adds little. Shared focus comes from talking about the goals often: a weekly review in each team, a monthly company update on the top-level OKRs, and plans that are quick to adjust. A diagram can record alignment. The conversations are what produce it.

Aligning AND cascading OKRs

Measure What Matters brought OKRs to a lot of companies, and we are grateful for it. Its cascading model is the part we have seen teams struggle with most.

Align first. Then link Key Results where the relationship is real. In a complex organisation that order is much easier to live with, and it still holds when the strategy changes.

Questions about cascading and aligning OKRs

What are cascading OKRs? A way of structuring goals in which each Key Result at one level becomes an Objective at the level below, from the company down to teams.

What is OKR alignment? Teams write their own OKRs in support of the company Objectives and can show how each one contributes. Alignment is about shared intent, so it does not need every goal to have a parent.

Should OKRs cascade? Direction should flow down. The OKRs themselves should be written by each team. A strict cascade is slow to plan and breaks when the strategy changes.

What is laddering OKRs? Another name for connecting team goals upward to company goals. The same advice applies: connect to the Objective first, and link Key Results only where one moves the other.

Do we need an OKR tree? A tree is useful as a view and causes problems as a planning rule. Build it from the links teams add after their plans are locked.

Can a team have an Objective with no link to a company OKR? Yes. Teams have problems of their own worth solving. If most of a team's Objectives have no connection to the company's, check whether the company OKRs are clear.

How do you check that teams are aligned? Hold one review where each team says which company Objective its Objectives serve. Then look for company Objectives nobody picked up and for targets that conflict.

Free download

Get the PDF

Enter your work email and the PDF downloads straight away.

We'll email you occasional Tability updates. Unsubscribe at any time.