Cascading goals, done right: 5 mistakes when connecting corporate strategy and team goals

Ask five executives from five different functions in your company to name the three most important strategic priorities for the year. How many of their answers would match?

Donald Sull of MIT Sloan and Rebecca Homkes of London Business School did exactly that in a survey of roughly 11,000 executives across more than 400 companies. Only about one-third could correctly identify their organization’s top three priorities. Even when given five attempts, on average only half agreed on the same single priority.

This is not a communication problem in the traditional sense. It is a goal cascading problem: The strategy has been defined and perhaps even presented in great detail, but it has not survived the journey from the executive level to the teams responsible for execution.

In practice, this almost always breaks down in the same five places.

‍

1. Goals are assigned instead of explained

‍

When organizations cascade strategy from the top down, they often reduce it to numbers: revenue target X, margin Y, growth rate Z.

What gets lost is the rationale behind those numbers. A sales team that receives a revenue target but does not understand why a particular market segment is strategically important may still work toward the target. But when priorities compete, that goal is much more likely to lose out because it feels like just another KPI rather than part of a larger strategic plan.

Goal cascading is not simply a matter of breaking down numbers. It is an exercise in translation. And that translation requires time – time that many leadership teams simply do not allocate during annual planning.

‍

2. Every level adds its own goals

‍

As goals move from the corporate level down to individual teams, the list almost always grows.

Each management level – often for perfectly valid reasons – adds one or two priorities of its own. By the time the cascade reaches a team, it may be dealing with twelve goals instead of three, with none of them carrying a clear sense of priority. Consider a mid-sized industrial manufacturer whose executive team defines three strategic priorities. At the business-unit level, five functional objectives are added. At the team level, several operational KPIs from day-to-day business are added as well. By the end of the cascade, a team leader is juggling fourteen goals atonce – and still ends up making decisions based on instinct because meaningful prioritization across fourteen competing objectives is virtually impossible.

Limiting each level to three to five goals can feel uncomfortable duringplanning. But it is one of the few ways to ensure an organization actuallystays focused rather than simply claiming that focus is a priority.

‍

3. The cascade only flows one way

‍

A purely top-down approach ignores the fact that teams closer to day-to-day operations have valuable information that senior leadership often does not: capacity constraints, direct customer insights, and early warning signals from the market. When goal cascading is treated as a one-way process, that knowledge never flows back into the goal-setting process itself.

The result is a set of objectives that may sound ambitious on paper but are operationally unrealistic from day one. Teams may already know this, but without a structured feedback channel, those concerns never reach leadership until the annual target has already been missed.

Effective goal cascading therefore cannot be a one-time waterfall process. It needs to be a dialogue, including at least one feedback loop before objectives are finalized.

‍

4. Strategy and operational initiatives live in separate systems

‍

This is a highly practical problem – and one that amplifies many of the others. Strategic objectives are documented in an executive presentation. The projects supposedly supporting those objectives live in an Excel spreadsheet owned by a business function – or are spread across three different tools, depending on what each department happens to use.

There is no single view that connects the two.

As a result, leadership often lacks visibility into whether an ongoing initiative actually contributes to the strategy or merely appears to. Without a shared data foundation, goal cascading becomes an assertion rather than a transparent and measurable structure.

‍

5. Goals are set once, left untouched for a year

‍

The final mistake is the least dramatic – and potentially the most expensive. Goals are defined during annual planning, documented, presented, and then barely reviewed until the next planning cycle.

By the time deviations become visible during the year-end review, it is often too late to course-correct.

Cascaded goals require more than an annual review. They need continuous feedback: short, regular check-ins that show whether an objective is still on track before it turns into a year-end report filled with explanations for why it was missed.

‍

The common thread

‍

All five mistakes share the same root cause: a lack of translation, a lack of a shared data foundation, and a lack of continuity. Strategy and operational goals are developed separately, documented separately, and tracked separately – and organizations are then surprised when they remain disconnected in practice.

This is exactly where the EVO-Cloud Business Strategy & ExecutionSolution comes in. It brings together goal cascading, AI-powered alignment of objectives and initiatives, and execution tracking within a shared data structure – from executive leadership all the way down to individual teams.

Strategy no longer remains confined to a slide presented in an executive meeting. It becomes transparent, adaptable, and actionable throughout the year – so organizations can continuously track progress, adjust when needed, and turn strategy into execution.