OKR Cascading vs. Alignment: Why Top-Down OKRs Fail by Q2

OKR cascading copies company objectives down the org chart until every team holds a smaller version of the same goal. OKR alignment does the opposite: leadership sets a small number of company objectives and each team writes its own contribution to them. Cascaded OKR programmes tend to look healthy in the first quarter and stall in the second. The reason is not the OKR framework. It is who holds the pen.

I have watched this pattern repeat across OKR Institute client engagements in more than 50 countries. The leadership team publishes OKRs in January. Managers translate them into team OKRs within days. By April, check-ins have turned into status reporting, half the key results have no owner who feels responsible, and the executive team is asking why “OKRs are not working here”. This article explains the difference between cascading and aligning, why cascading breaks down on a predictable schedule, and what a leadership team has to give up to make alignment work.

Punti chiave

• Cascading distributes goals by hierarchy. Alignment distributes goals by contribution.
• Cascaded OKRs fail in Q2 because the people executing them never made a commitment; they received an assignment.
• In the 2015 HBR study by Sull, Homkes and Sull, 84% of managers said they could rely on their boss and direct reports, while only 9% said they could rely on colleagues in other units all the time. Cascading reinforces the vertical and ignores the horizontal.
• Moving to alignment costs the leadership team control over wording, the comfort of full coverage, and the speed of the first cycle.
• The payoff is ownership, which is the only thing that keeps an OKR system alive past the first quarter.

What is OKR cascading?

OKR cascading is the practice of taking a company-level objective and breaking it into departmental, team, and sometimes individual OKRs, where each lower level is a direct subdivision of the level above. The CEO’s key result becomes the division head’s objective. The division head’s key result becomes the team lead’s objective. The structure is a tree, and the content flows one way: downward.

Cascading inherited its logic from Management by Objectives, where the point was control and accountability through the chain of command. It appeals to leadership teams for understandable reasons. It is fast: one workshop and a spreadsheet, and the whole organisation has OKRs by the end of the month. It is complete, since every key result can be traced to a strategic priority. Most executives also grew up with budgets and targets that were allocated top-down, so cascading OKRs feels like an extension of what already exists.

The weakness is structural. When a team’s objective is defined by the layer above, the team has no decision to make. Its job is to accept the goal and report on it. In OKR terms, the team never answers the question that gives the framework its value: “Given where the company wants to go, what is the most important thing we can change in the next 90 days?” The answer has already been supplied.

What is OKR alignment?

OKR alignment is a model where the leadership team sets a small number of company objectives (typically three to five, with measurable key results) and each team then writes its own OKRs that describe how it will contribute. The company OKRs set direction. The team OKRs set contribution. Nothing is copied; everything is connected.

In practice this means a product team reads the company objective “Become the default choice for mid-market finance teams” and writes a team objective such as “Make onboarding so simple that a finance manager can go live without a sales call”. The key results belong to the team. They can be measured by the team. The link to the company objective is explicit, and the leadership team reviews it, but the leadership team did not author it.

Alignment also works sideways. When teams publish their OKRs, dependencies between teams become visible before the quarter starts. Marketing sees that its lead-generation key result depends on a product release the engineering team has not committed to. That conversation happens in week two of the planning cycle instead of week ten of the quarter.

The approach is slower to launch. Teams need a window, usually two weeks, to write and discuss their contribution. Some first drafts will be weak. The leadership team has to tolerate that. In exchange, each team ends the planning cycle with a set of goals it chose and will be embarrassed to abandon.

Cascading vs. aligning: the differences that matter

Dimension	Cascata	Aligning
Who writes team OKRs	The layer above	The team itself
Direction of information	Top-down only	Top-down for intent, bottom-up for contribution, sideways for dependencies
Time to publish	Giorni	Two to three weeks
Coverage	Every team, every key result traced	Only the work that moves a company objective
Role of leadership	Author and allocator	Author of company OKRs, reviewer of team OKRs
Ownership felt by teams	Low; the goal was assigned	High; the goal was chosen
Cross-team dependencies	Invisible until something breaks	Surfaced during planning
Typical failure point	Quarter 2	Quarter 1 if leadership overrides the team drafts

Why do top-down OKRs fail by Q2?

Top-down OKRs fail in the second quarter because the first quarter runs on the energy of the launch and the second quarter runs on ownership, and cascaded OKRs do not produce ownership. The pattern is consistent enough that OKR Institute coaches now treat a quiet Q2 as a diagnostic signal rather than a surprise. It is one of the ten root causes covered in Why OKRs Fail, and the one most often misdiagnosed as a tooling problem.

Quarter one looks fine. The OKRs are new, the executive team is paying attention, and reporting against someone else’s goal is not hard for 12 weeks. The cracks appear at the first retrospective. Teams that received their OKRs have no opinion about whether the objective was right, because they never formed one. Key results that were missed are explained rather than examined. Nobody proposes to drop or rewrite an objective, because the objective was not theirs to touch.

Quarter two starts with the same objectives, lightly edited, pushed down again. This time the launch energy is gone. Check-ins get shorter and updates get vaguer. Managers start describing OKRs as “the reporting thing”. By May, the leadership team is receiving a dashboard that is green in most places and disconnected from what people are working on.

The research on strategy execution explains why. In the 2015 study published in Harvard Business Review, “Why Strategy Execution Unravels and What to Do About It”, Donald Sull, Rebecca Homkes and Charles Sull surveyed close to 8,000 managers in more than 250 companies. More than 80% said their goals were limited in number, specific and measurable. Goal quality was not the problem. The problem was horizontal: 84% of managers said they could rely on their boss and their direct reports all or most of the time, but only 9% said they could rely on colleagues in other functions and units all the time. When asked why execution failed, 40% named a failure to align and 30% named a failure to coordinate across units.

Cascading optimises exactly the dimension that already works (the vertical line between a manager and a boss) and does nothing for the dimension that fails (the horizontal line between teams). It produces well-formed goals, which is what the 80% figure describes, inside an organisation that still cannot coordinate.

There is a second, quieter cost. Gallup’s State of the Global Workplace report puts global employee engagement at 20% for 2025, the lowest level since 2020. An OKR system that assigns goals rather than inviting them adds one more thing employees are told to do. An OKR system that asks teams to define their own contribution is one of the few management practices that pushes in the other direction. Decades of goal-setting research by Edwin Locke and Gary Latham point the same way: people commit more strongly to goals they had a hand in setting, and commitment, not clarity, is what carries a goal through a difficult quarter.

What the leadership team has to give up

This is the part most articles on OKR alignment skip. Alignment is not a template change. It is a transfer of authority, and the leadership team pays for it in five specific ways.

Control over the wording

When teams write their own OKRs, they will phrase things differently from how the CEO would. Some objectives will be too modest. Some will be ambitious in a direction the executive team did not expect. The temptation to rewrite them is strong. Every rewrite converts an owned goal back into an assigned one. The leadership team’s job in the review is to ask whether the contribution is real and whether the key results are measurable, not to edit the prose.

The comfort of complete coverage

Cascading guarantees that every team has OKRs and every key result traces to a company priority. Alignment does not. Some teams will contribute to only one company objective. Some operational teams will have no OKRs at all for a quarter because their work is run-the-business, not change-the-business. Executives who equate coverage with control find this uncomfortable. It is also correct. OKRs are for the few changes that matter, not for describing every job.

Speed of the first cycle

A cascaded rollout can be done in a week. An aligned one takes two or three. The extra time is spent on conversations between teams, which is where the value sits. Leadership teams that compress the window to save time usually spend the difference in Q2 untangling dependencies that the planning window would have exposed.

The habit of adding priorities

In a cascaded system, a new executive priority can be inserted and pushed down at any time. In an aligned system, a new company objective in mid-quarter asks every team to re-examine its contribution. That friction is a feature. It forces the leadership team to decide whether the new priority replaces an existing one or waits for the next cycle. Teams can only hold a handful of objectives. A leadership team that keeps adding to the list is not setting strategy; it is forwarding requests.

Being the only author

The deepest change is cultural. In the cascaded model, strategy is something the leadership team does and the organisation receives. In the aligned model, the leadership team sets direction and the organisation works out the route. Some executives experience this as a loss of relevance. In practice it moves their attention from allocation to the two things only they can do: choosing the few objectives that matter, and removing the obstacles teams surface when they plan honestly.

What the leadership team gets back is a quarterly planning cycle in which teams argue about what matters, dependencies are visible before they bite, and the Q2 check-in is a working session rather than a reading of the dashboard.

How to move from cascading to aligning

Organisations that have already cascaded can switch without starting over. The following sequence has worked across OKR Institute engagements in companies from 200 to 20,000 employees.

1. Cut the company OKRs to three to five objectives, each with two to four measurable key results. If the leadership team cannot agree on five, that disagreement is the first thing to resolve.
2. Publish the company OKRs with context: why these objectives, and what was deliberately left out.
3. Open a two-week contribution window. Each team drafts its OKRs in response to the company set and publishes them where other teams can read them, whether that is a shared document or an OKR platform such as FlowyTeam.
4. Run alignment reviews, not approval meetings. The leadership team and team leads check that key results are measurable and that each team OKR moves a company objective. Wording stays with the team.
5. Hold a dependency session in the last planning week where teams confirm what they need from each other. Unresolved dependencies become a leadership escalation before the quarter starts, not during it.
6. Keep the cadence: weekly team check-ins, a monthly cross-team review, and a quarterly retrospective. In the retrospective, every team is expected to propose at least one change to its own OKRs, and the leadership team is expected to accept most of them.

The first aligned cycle will be messier than any cascaded one. The second will be better than any cascaded one. That is the trade.

What HR directors should watch

HR directors are usually the executives who inherit the OKR system once the strategy team has launched it. Four things deserve attention.

Separate OKRs from performance ratings. The moment OKR attainment feeds a bonus or a rating, teams write safe OKRs and the alignment model collapses into target negotiation. OKRs inform the performance conversation; they should not score it.

Invest in manager capability before rollout. Alignment asks team leads to facilitate goal-setting conversations, challenge their own teams, negotiate with peers, and defend a draft in front of executives. Most managers have never been trained to do any of this. Cascading hides that gap because managers only have to relay. Alignment exposes it.

Watch engagement and voluntary input, not just attainment. A healthy aligned system shows teams proposing changes to their own OKRs and dependencies being raised before the quarter starts. A cascaded system shows high completion rates and silence.

Protect the planning window. The two-week contribution period is the first thing a busy executive team tries to cut. HR is often the function best placed to hold it.

Frequently asked questions

What is the difference between cascading OKRs and aligning OKRs?

Cascading OKRs copies company objectives down each level of the hierarchy, so each team’s objective is a subdivision of the one above it. Aligning OKRs has leadership set a few company objectives while each team writes its own OKRs describing how it will contribute. Cascading is faster to publish; aligning produces ownership and surfaces cross-team dependencies.

Why do top-down OKRs fail?

Top-down OKRs fail because the teams executing them did not choose them. Assigned goals get reported on; chosen goals get defended. The failure typically becomes visible in the second quarter, when launch energy fades and the system has to run on ownership that cascading never created.

Should every team have OKRs?

No. OKRs describe the few changes an organisation wants to make in a quarter. Teams whose work in a given quarter is entirely operational can run on KPIs and skip OKRs for that cycle. Forcing OKRs onto every team is a symptom of cascading, not a sign of alignment.

How many company-level OKRs should a leadership team set?

Three to five objectives, each with two to four key results. More than five dilutes attention and makes it impossible for teams to write a meaningful contribution. If the leadership team cannot reach agreement on five, the strategy itself is not yet clear enough to execute.

Can OKRs be both top-down and bottom-up?

Yes, and this is the intended design. Direction flows top-down through the company OKRs. Contribution flows bottom-up through team OKRs. Coordination flows sideways through published dependencies. A system that only has the first flow is cascading, whatever it is called.

How long does it take to move from cascading to aligning?

One full quarterly cycle to switch the mechanics and a second cycle before the quality of team OKRs is reliably better than under cascading. Leadership capability, in particular the discipline to review rather than rewrite, is usually the slowest part to develop.

Conclusione

Cascading answers the question “how do we get OKRs everywhere fast?”. Aligning answers the question “how do we get the organisation to commit to a few things and coordinate on them?”. Only the second question is worth an OKR programme. The cost of alignment is paid by the leadership team: in control over wording, in the comfort of full coverage, in the speed of the first cycle, and in the habit of adding priorities. The return arrives in Q2, when the cascaded programme is quietly dying and the aligned one is holding its first useful retrospective.

If your leadership team is about to launch OKRs, or has launched them and is watching Q2 go quiet, the capability to build is not a better template. It is the ability of executives to set direction and then stop writing. The Certified OKR Leader (C-OKRL) programme from the OKR Institute is designed for exactly this: it trains leadership teams to set the few company objectives that matter, run alignment reviews without taking the pen back, and hold the cadence through the quarter where most OKR systems fail.

Explore C-OKRL for your leadership team.

Book an executive strategy session

Corsi correlati

messaggi recenti

Tag

#OKR

#OKR AI agents

#trends 2026