Cascading Goals
What is Cascading Goals?
Cascading goals is the practice of breaking an organization's top-level goals into connected goals for business units, teams and individuals, so that work at every level supports the overall strategy.
Updated November 2026 · 5 min read
Cascading goals connects the top of an organization to the people doing the work. Leaders set a small number of company goals. Each business unit or function then sets goals that support them, each team sets goals that support its unit's goals, and individuals may set goals that support their team's. The result is a hierarchy of goals in which, ideally, every goal can be traced up to a company priority. When the cascade works, people understand how their work contributes to the strategy, and leaders can see whether the organization's effort adds up to its goals. When it fails, goals at lower levels drift from the strategy and effort is spread across unrelated priorities.
The idea is central to many goal-setting frameworks, including management by objectives, the balanced scorecard, Hoshin Kanri, OGSM and OKRs. Approaches differ in how strictly goals are cascaded. Some organizations require each goal to be a direct subset of the one above, while others encourage teams to propose their own goals that support the company's, a looser form of alignment. For strategy and planning teams, cascading goals is one of the main ways to turn strategy into action across a large organization.
Definition of Cascading Goals
Cascading goals is a goal-setting process in which organizational goals are translated into linked goals at successive levels of the organization, each supporting the level above, to create alignment between strategy and the work of units, teams and individuals.
It is a key method for strategic alignment and is used in frameworks such as objectives and key results and Hoshin Kanri.
How Goals Cascade
Company goals are set by senior leaders, usually a small number tied to strategic priorities. Keeping them few makes the cascade simpler and the connections clearer.
Business unit and functional goals describe how each part of the organization will contribute to the company goals.
Team goals describe how each team will contribute to its unit's goals, often more specific and shorter-term. They are usually where goals become concrete enough to guide daily work.
Individual goals, where used, describe each person's contribution to the team's goals and are often part of performance management.
At each step, goals should be linked explicitly to the level above, so that contributions can be traced and progress rolled up.
Strict vs Flexible Cascading
In strict cascading, each level's goals are derived directly from the level above, often by dividing targets. This creates tight alignment but can be rigid and discourage initiative.
In flexible cascading, teams propose goals that they believe will best support the level above, and goals are adjusted through discussion. This improves ownership and uses local knowledge but requires more coordination.
Many organizations now favor flexible cascading, sometimes called alignment rather than cascading, especially with OKRs. The change reflects a view that teams often know best how to contribute.
Some also allow a share of goals that are not directly cascaded, for work that teams believe is important but that does not map neatly to company goals.
Importance of Cascading Goals in Strategic Planning
Cascading goals connects strategy to daily work. People can see how their goals contribute to company priorities, which improves focus and motivation.
It improves alignment. When goals are linked, it is easier to spot work that does not support the strategy and conflicts between teams.
It also supports performance tracking. Linked goals allow progress to be rolled up from teams to units to the company.
Cascading Goals and Financial Management
Financial targets, such as revenue and cost goals, are often cascaded from company to business units and teams, with each level responsible for part of the total.
Cascading financial goals alongside budgets helps make sure that units have the resources to meet their targets.
Rolling up progress on cascaded goals gives finance teams an early view of whether company targets are likely to be met.
Linking investment decisions to cascaded goals helps direct spending to the work that contributes most to company priorities.
Common Challenges
Strict cascades can take a long time, since each level must wait for the one above to finish before setting its own goals.
Goals can become diluted or distorted as they pass down several levels, losing their connection to the original intent. Explaining the reasoning behind company goals helps preserve their meaning.
Cascades can discourage collaboration if each team focuses only on its own goals and not on shared outcomes.
How to Cascade Goals Effectively
Cascading goals effectively involves setting clear company goals, explaining them, inviting teams to propose supporting goals, linking goals visibly and reviewing them regularly.
The aim is clear connections between levels without slowing down the process or stifling initiative. Speed matters, since goals that arrive late in the period have little time to guide work.
Setting Up the Cascade
Start with a small number of company goals, linked to strategy, and explain the reasoning behind them.
Ask business units and teams to propose goals that support the company goals, using catchball-style discussion to refine them.
Allow levels to work in parallel where possible, rather than waiting for each level above to finish. Draft company goals can be shared early and confirmed later.
Making Connections Visible
Record goals in a shared system, such as OKR software or a planning tool, with explicit links to the goals they support. Make the links visible to everyone, not just managers.
Include shared goals for work that spans several teams, so that collaboration is encouraged. Give each shared goal a lead owner.
Review progress regularly at each level and roll it up, discussing goals that are off track and adjusting where needed. Celebrate shared wins.
Examples of Cascading Goals in Strategic Planning
The examples below show cascading goals in practice.
Both use illustrative figures. The first speeds up a slow cascade, and the second adds shared goals.
In each, changes to the cascade improved alignment and speed.
Speeding Up a Slow Cascade
A bank's goal-setting cascades through five levels in sequence, and front-line teams do not finalize their goals until about ten weeks into the year.
It moves to a flexible approach, publishing company goals first and allowing all levels to draft goals in parallel, then aligning them in a two-week review period.
All teams have agreed goals within four weeks of the start of the year, and alignment reviews find few gaps.
Adding Shared Goals
A software company's teams each have goals tied to their own features, and cross-team projects regularly stall.
For its company goal of improving onboarding, it creates a shared goal owned jointly by product, design, engineering and customer success.
The teams coordinate more closely, and the time for new customers to reach first value falls by about 40% over two quarters.
Conclusion
Cascading goals breaks top-level goals into connected goals for units, teams and individuals, so that work at every level supports the strategy. Cascades can be strict, deriving each level's goals directly from the one above, or flexible, inviting teams to propose supporting goals.
In strategic planning, cascading goals connects strategy to daily work, improves alignment and supports performance tracking. Setting a few clear company goals, inviting teams to propose supporting goals, working in parallel, linking goals visibly and including shared goals help organizations cascade goals effectively.
Related terms
Strategic Alignment
How well goals, resources and daily work all support the strategy.
Objectives and Key Results (OKR)
Qualitative objectives paired with measurable results that show progress.
Hoshin Kanri
A Japanese method for turning a few breakthrough goals into aligned action.
Catchball
Passing plans back and forth between levels until each commits to its part.