Not automatically. Goals add up when someone reconciles the commitments that conflict, when what teams learn travels back up, and when the system is built to enable work rather than to police it.
For the CHRO, HR leader or business leader who owns the performance system. Article 1 of seven in the performance management investigation.
This is for anyone responsible for making the system work, including the employee who has to live with its decisions.
Your question is not whether people have goals. It is how to get an entire organization pulling toward the same result, and how to know early when it is not.
Start where it usually goes wrong. A quarterly review, every department green. Sales met its target. Operations cut cost. Support is closing tickets faster. Customers are leaving anyway.
Nobody in that room underperformed. Each team delivered exactly what it was asked for. The organization still has a problem, and no individual goal describes it.
The choice you are actually making
Every mechanism you can put in a performance system leans one of two ways.
Control assumes the risk is people doing the wrong thing, so the design tightens: cascaded targets, tracked completion, distributions, sign-offs. Enablement assumes the risk is people not knowing what matters, or knowing and being blocked, so the design opens: clear priorities, fast conversations, and a route to remove obstacles.
As practitioners we have observed that many organizations say enablement and build control, because control is easier to audit. You can show a board that goals were set on time. You cannot show it that three teams were pulling against each other for two quarters.
The choice is not moral. A power plant needs more control than a design studio. But it is a choice, and most performance systems make it by accident, one process at a time.
Where the arithmetic breaks
Sales needs shorter delivery times to win orders. Operations needs longer runs to hold cost. Support spends its week explaining promises the other two cannot reconcile.
No amount of goal quality fixes that. Someone with authority across all three has to decide which promises the business will make and what it will fund to keep them.
So the design question is narrow and specific: who reconciles conflicting commitments, and how long does it take? In many organizations the honest answer is nobody in particular, and a quarter. That gap may matter more than the rating scale.
What each person needs from it
A system that serves only the top stops being fed the truth from below. Three different needs have to be met at once.
| Who | What they need from the system | What happens when they do not get it |
|---|---|---|
| The employee | To know what matters now, what good looks like, and that the judgment will be explainable | Effort goes to what is visible and measured, not what is useful |
| The manager | Simpler conversations, the standing to reprioritize, and a way to escalate a blocker | The form gets completed and the real conversation happens elsewhere |
| The leader | Alignment, early warning, and evidence for decisions about money and people | Reviews become reporting, and problems arrive a quarter late |
Notice that the employee's need and the leader's need are not in conflict. They fail together. When people cannot see how their work connects to anything, they optimize for the number. When leaders only see numbers, they lose the signal that would have told them the number was the wrong one.
What the cascade assumes
Goal setting itself is well supported at the level of one person. Specific, difficult goals beat "do your best", provided the person is committed, gets feedback, and can actually do the work 1.
The cascade is a separate claim, and it is thinly evidenced. Research reviews describe how organizations connect goals across levels and how that practice has evolved 2. Whether employees can see the connection at all has its own line of inquiry, usually called line of sight 3. Neither shows that translating goals downward improves what the organization achieves.
The side effects, in contrast, are documented: narrower focus, shorter horizons, more risk taking, more gaming when goals are pushed hard 4. A system can hit every number and leave the business worse off, which is precisely the quarterly review described above.
For a designer, the practical reading is this. Keep goal setting, because it works where the evidence is strongest, at the level of a person and a piece of work. Stop assuming the arithmetic upward takes care of itself, because that is the part nobody has shown.
Information has to travel back up
A cascade carries priorities down. The work generates information that has to travel up, and that direction usually has no route at all.
| At this level | What the review has to surface |
|---|---|
| Employee | Are the expectations clear, and is the person getting what they need |
| Team and across teams | Do the commitments fit together, and who resolves it when they do not |
| Organization | Are the combined results serving the business, and should priorities or resources change |
If what the front line learns stops at their own review, the organization keeps asking for a result its own decisions are making harder. That is not a motivation problem and no amount of goal rewriting touches it.
One test, and it is the most useful hour you will spend on the system this year. Take a real problem a frontline employee could see today. Could it reach someone able to resolve it, and could the answer come back, inside a month? If not, what you have is a reporting process wearing the name of a management one.
What the evidence supports, and how far
Goal setting at the individual level is well supported, given commitment, feedback and ability 1. The cascade itself is not: the reviews describe the practice rather than test it 2, and the question of whether employees can even see the connection is studied separately 3. The side effects of pushing goals hard are documented 4. AI changes what good work looks like faster than most systems adapt 5.
The stakeholder table and the three levels are ours, built from practice, not a validated model.
Evidence: contested. Strong for one person and one goal. Thin for the organization built out of them.
Our position
Keep goal setting where it works, at the level of a person and a piece of work. Then spend the design effort on the part nobody has shown works by itself: who reconciles conflicting commitments, and how what teams learn reaches the people who can act on it.
Take it into the room: the Set goals that add up worksheet turns this article into one printed page of questions, a framework and a table to fill in.
What would change this conclusion
Evidence that organizations changing only how goals connect across levels, with everything else held steady, get better results. Or a way to show that what teams learn reliably reaches the people who can act on it. If that reconciliation already happens in ordinary business reviews, the performance process is carrying far less weight than either its defenders or its critics assume.
Read next: Expectations, KPIs, KRAs, OKRs: does the label change anything?
Evidence map
- Locke and Latham (2002), Building a Practically Useful Theory of Goal Setting and Task Motivation. Research synthesis across 35 years. Relevant full text accessed. Supports specific and difficult goals at the individual level, given commitment, feedback and ability. Not a test of cascades.
- Pulakos, Mueller-Hanson and Arad (2019), The Evolution of Performance Management. Research review; full text accessed. Describes how practice has changed; does not test the cascade.
- Boswell (2006), Aligning employees with the organization's strategic objectives: out of line of sight, out of mind. International Journal of Human Resource Management. Record and title verified through Crossref; abstract not retrievable through the sources checked. Cited for the line of inquiry the title establishes.
- Ordonez, Schweitzer, Galinsky and Bazerman (2009), Goals Gone Wild. Academy of Management Perspectives. Bibliographic record verified. A review of documented side effects, not a new experiment.
- Dell'Acqua and colleagues (2026), Navigating the Jagged Technological Frontier. Organization Science. Randomized experiment with consultants; published full text accessed. Effects concern the tasks and model tested.
Sources checked September 22, 2026. Prepared with AI assistance.