Home/Blog/OKRs/How to Align OKRs Across Teams Without C…
OKRs

How to Align OKRs Across Teams Without Cascading

How to align OKRs across teams without a tree of sub-goals: each team picks what it serves, writes its own results and every key result has one named owner.

Cover of the FIKR Space guide: How to Align OKRs Across Teams Without Cascading

To align OKRs across teams, give each team the company objectives and let it decide which it is best placed to serve, then write its own key results in service of that objective, with one named owner for every result. Do not break each objective down into sub-objectives for every team.

Alignment and decomposition sound like the same thing. They are not, and confusing them is the standard failure at scale. This article separates the two, describes the guide's two questions for checking a team's set, and covers the single-owner rule that stops results falling between people.

How to align OKRs across teams: align, do not decompose

The mechanical approach is called cascading. Each company objective is broken into sub-objectives for every team, and then again for the teams beneath those, until the organisation is carrying a bureaucracy of goals nobody reads. It looks rigorous. It produces paperwork.

The guide's point is that alignment does not require decomposition. A team should look at the company objectives, decide what it is best placed to contribute, and write its own key results in service of that objective. The team makes a judgement. It is not handed a fragment of someone else's number.

Cascading downAligning across
Who writes the team's resultsThe level above, by breaking its own downThe team, in service of a company objective
What coverage looks likeEvery team gets a piece of every objectiveA team may serve just one objective
What it producesA tree of goals that nobody readsA small number of goals people can recall
Where the judgement sitsAt the topWith the team, then reconciled in conversation

The cascading mechanics also fight the size discipline in how many OKRs a startup should have. A tree multiplies goals with every level, which is the opposite of the short list the method depends on.

A team can serve just one objective

The guide is explicit that a team may decide it contributes to only one of the company objectives, and that this is usually the honest answer. That surprises people who expect every team to appear under every objective.

Think about what the alternative requires. For a team to contribute to all of them, it has to invent something to say about objectives it has little influence over. The results become reports, not efforts, and that is the unownable pattern the guide warns about. Serving one objective well is better than touching three loosely.

If a team truly has nothing to contribute to any company objective, that is information about either the objective or the team, and it is better surfaced in the planning conversation than discovered at the end of the quarter.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

Two questions are enough

The guide gives two questions that suffice for any team's set.

  1. Which company objective does this serve?
  2. What would we do differently because of it?

The first checks that the result points at something the company has chosen. The second checks that the goal has teeth. If a team cannot say what it would do differently, the key result is an observation, not a goal. It is the same test as asking whether a goal has ever caused anyone to say no, which is described in what are OKRs.

The guide's checklist makes the same point in a line: each team can say which company objective they serve and what they will do differently. Use that as the entry test for every team set.

Two directions, and a real conversation

Alignment depends on goals travelling in both directions. Purely top-down goals produce compliance and no ownership, since the team executes something it was handed and feels no responsibility for whether it works. Purely bottom-up goals produce a set that is locally sensible and adds up to nothing, because nobody was accountable for coherence.

The working pattern in the guide is this. Leadership sets the small number of company objectives and the direction. Teams propose the key results they believe will move them. The two are reconciled in a conversation where the teams can genuinely push back.

Check whether the push back is real. If nothing changes in that conversation, you have top-down goals with extra steps, and everyone can tell. That is a sign the reconciliation is a formality, and the ownership you wanted will not appear.

One named owner for every key result

Alignment fails in the gaps between teams, and the most reliable gap is shared ownership. The guide's rule is that every key result has a single named owner. Not a department, not a committee: a person.

Shared ownership between two people is the most reliable way to produce a key result that neither of them drives, because both reasonably assume the other is on it. This matters especially when two teams both care about the same number. Decide who owns it, name that person, and let the other team contribute to the result without owning it.

Others will work on it too. The owner is simply the one who knows where it stands and says so early when it sticks, so ownership means speaking up rather than doing everything. The guide adds that each owner should agree out loud, rather than be assigned in a document.

What leadership does in the reconciliation

The conversation between leaders and teams is where alignment is actually produced, so it deserves some structure. Leaders bring the small set of company objectives and the direction. Teams bring proposed results and their reasons. The job of the conversation is to test whether the teams' proposals, taken together, move the objectives.

Leaders should expect to hear no, and sometimes expect to change their minds. A team that knows its work best may say that a company objective is poorly placed for it, or that a better route exists. The guide wants that pushback to be real. If leaders arrive with every answer already fixed, the exercise is theatre and the team will treat the resulting goals as something done to it.

The teams, for their part, should arrive with a view on what they are best placed to contribute, and be willing to say that they contribute to only one objective. That honesty is more useful than coverage.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Why this lowers the cost of coordination

The point of aligning goals is to avoid paying for alignment through endless meetings, status reports and managers relaying context. The guide describes shared, visible goals as doing much of that work at almost no running cost.

A cascaded tree undermines this. People cannot hold a tree in their heads, so they have to look things up, and then they ask someone, and the coordination cost returns. A short set of company objectives and a few team results is something a person can remember, which is why it changes decisions without anyone checking a document. The effect is strongest just past the size where everyone can still overhear everything.

A cross-team check you can run in a session

When teams have drafted their sets, run through this list before they are agreed.

  • Every team set points at a company objective.
  • Each team can say what it would do differently because of it.
  • Every key result has exactly one named owner who agreed.
  • Each owner can actually influence their number.
  • No team set exists merely to report on a number somebody else drives.
  • The set is short, so a person can recall it without reading it.

The qualities of a result that an owner can drive are covered in how to write key results.

Keep the weekly check shared

Alignment is also maintained by the weekly rhythm. When owners from different teams report the number, their confidence and what is in the way in one short session, dependencies show up in the open. A blocker that sits with another team can be given an owner and a date on the spot.

That is how a small number of shared goals does the job that status meetings and relaying managers do expensively. The format is in how to run a weekly OKR check in.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

What goes wrong when teams cascade anyway

The guide lists cascading mechanically among its nine biggest mistakes. The pattern is recognisable: teams cannot say which goals are theirs, results are fragments of someone else's number, and nobody reads the full tree. You can find the others in the same family in OKR mistakes founders make.

The fix is to delete the tree, restate the company objectives, and ask each team the two questions again. It is a smaller document and a harder conversation, and that trade is the point.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Frequently asked questions

Does every team need goals under every company objective?

No. The guide says a team may contribute to only one, which is usually the honest answer.

Who writes the team's key results?

The team proposes them, in service of a company objective, and leadership reconciles them in a conversation where the team can push back.

Can two teams own the same key result?

The guide recommends a single named person for each. Two owners tend to produce a result that neither drives, so name one and let the other team contribute.

How do I know alignment is working?

Every team can say which company objective it serves and what it would do differently because of it, and nobody is carrying a tree of sub-goals.

The full method, with the checklists, is in The OKR Playbook, a free 32-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us