Insights / Perspective / Corporate strategy and long-term goals
PerspectiveWhy goal cascades fail, and how to make them work
Cascading goals from the top to every team often fails because goals are copied downward rather than translated. Three changes make cascades work.
Cascading goals from the top of the organisation to every team is one of the most common practices in management. The logic is sound: if each team’s goals connect to the organisation’s priorities, everyone pulls in the same direction. In practice, the result is often a spreadsheet of hundreds of goals that few people remember and fewer act on.
The problem is not the idea of alignment. It is the way cascades are usually run. Goals are copied downward rather than translated, they multiply at every level, and they are reviewed once a year when performance ratings are due. By then, they have long since stopped guiding anyone’s work.
Why copying fails
The most common cascade takes a corporate goal, such as growing revenue by a certain percentage, and hands the same goal to every division, which hands it to every department, which hands it to every team. Each level adds a smaller number or a regional label. The words barely change.
This approach fails for a simple reason: most teams cannot directly influence the corporate measure. A payroll team, a warehouse shift or an IT service desk does not control revenue. Given a goal they cannot move, people either ignore it or quietly substitute a goal they can move, which may or may not help the organisation.
Copying also hides the real question each team should be answering: what is our particular contribution to this priority? Without that question, there is no conversation about trade-offs, dependencies or what each team should stop doing.
Translate, do not copy
A sales team and a finance team contribute to the same priority in different ways. Each needs goals it can influence.
Suppose the organisation’s priority is to improve cash flow. The sales team might contribute by agreeing better payment terms with new customers. The finance team might reduce the time between delivery and invoice. The warehouse might cut the number of orders shipped incomplete, since incomplete orders delay payment. Customer service might resolve billing disputes faster. Four teams, four different goals, one shared priority.
- Start each team’s goal-setting with the question: how does our work affect this priority?
- Choose measures the team can move within a quarter, not only within a year.
- Check that the team goals, taken together, plausibly add up to the organisational goal.
- Identify dependencies, where one team’s goal relies on another’s support, and agree them openly.
Translation takes more time than copying. It requires managers to understand the priority well enough to explain it and to think about their own team’s contribution. That conversation is exactly what makes the goals meaningful.
It also changes the direction of the conversation. Instead of goals flowing down and being accepted, teams propose their contribution and leaders test it. Teams that write their own goals, within a clear frame, tend to own them. Teams that receive goals tend to treat them as someone else’s targets.
Limit the number
Teams with ten goals follow none of them. Three to five is a workable limit.
Goal lists grow because every function wants its concerns represented and because adding a goal is easier than removing one. The result is a list where everything is a priority and nothing is. People respond by focusing on whatever their manager asks about most, which may have little to do with the written goals.
A limit forces a useful conversation. If a team can have only four goals, which four matter most this year? What is left off, and is that acceptable? Leaving something off the goal list does not mean ignoring it. Routine work that is going well, such as meeting statutory deadlines, can be monitored without being a goal.
A simple rule for adding goals
If a team wants to add a goal, it must remove one, or explain which existing goal it replaces. The rule keeps lists short and forces explicit choices.
Review in public
A short monthly review where owners say what is blocked keeps goals alive. Annual reviews are too late to change anything, and quarterly ones are often too infrequent to catch problems before they become expensive.
Keep the review short and focused. Each goal owner states progress in a sentence, identifies anything blocking them and names what they need. Leaders spend the time removing obstacles rather than interrogating figures. The public element matters: when owners know they will report to peers each month, goals stay front of mind, and dependencies between teams surface quickly.
Resist the urge to turn the review into a performance discussion. If a goal is off track, the useful questions are what is in the way and who can help, not who is to blame. Owners who expect blame report late and optimistically. Owners who expect help report early and honestly, which is exactly what leaders need.
The monthly session took thirty minutes. Within two months, teams were resolving dependencies in the room that used to take weeks of emails.
Chief operating officer, manufacturing client
Where to begin
Take your organisation’s top three priorities and choose three teams that contribute to them in different ways. Ask each team to write three to five goals that describe their specific contribution, using measures they can influence. Check whether the goals add up. Then run a monthly thirty-minute review for one quarter and see what it surfaces. If it works, extend it. If it does not, the reasons will tell you what to fix.
Source: Intelliversal analysis.
