Cascading connects an objective to the one above it. Done well, it means everyone can see how their work adds up. Done badly, it produces a tree of restated sentences that nobody reads.

This guide covers the judgement rather than the buttons. If you use useful, the help centre covers the controls themselves.

What cascading is actually for

Alignment is not the same as repetition.

Repetition is what happens when a director’s objective becomes each manager’s objective, which becomes each employee’s objective, with the words gradually getting smaller. Everyone in the chain has the same objective. Nobody has one that belongs to them.

Alignment is when each level answers a different question:

  • The director’s objective says what must change: “Support resolves issues without engineering escalation.”
  • A manager’s objective says which part their team owns: “The billing team handles all tier-2 billing queries in-house.”
  • An employee’s objective says what they will do about it: “Every billing agent is signed off on refund processing.”

Read down that chain and you can see the contribution. Read down a repeated chain and you learn nothing.

The test is simple: if a child objective would be achieved automatically the moment the parent is achieved, it is repetition. A real child objective can succeed while the parent fails, and can fail while the parent succeeds.

When to cascade

Cascade when the parent objective genuinely cannot be achieved without work from people below.

Do not cascade because a level exists. Some objectives belong to one person and stop there. A manager objective about their own leadership behaviour has no sensible child. Forcing one produces a child objective that is a restatement, and teaches the team that this is a form-filling exercise.

Also consider how far down to go. Two levels is usually plenty. Three is occasionally right in a large organisation. Below that, the connection to the original objective is so thin that nobody uses it, and you are paying real maintenance cost for a diagram.

Optional and mandatory

useful lets you mark a cascade as optional or mandatory.

Mandatory means the people in scope must create a linked objective before their review is complete. Use it when the parent genuinely depends on everyone — a compliance deadline, a migration where every team has to move.

Optional means they may. Use it for everything else. Optional is the right default, and it is worth resisting the urge to change that. The moment every cascade is mandatory, people write filler objectives to clear the requirement, and filler objectives are worse than no objectives — they take up one of the three to five slots that should hold real work.

Who should cascade

You can direct a cascade at everyone in scope, at managers only, or at individual contributors only.

Managers-only is the useful one and the most under-used. It is how you cascade two levels without flooding the whole branch: the objective goes to your managers, each of them decides what their team owns, and their own objectives cascade onward if they need to. The alternative — sending one objective to a hundred people — produces a hundred near-identical children and no thinking.

Individual-contributors-only fits work that managers coordinate but do not do.

Team or branch

A team cascade reaches your direct reports. A branch cascade reaches everyone below you, at every level.

Branch cascades are blunt. They are right for something that genuinely applies to every person in the organisation — a safety standard, a company-wide priority for the year. They are wrong for anything that needs interpretation on the way down, because they skip the managers who would have done the interpreting.

There is a practical consequence too. When an objective is cascaded to a branch, the objectives created from it cannot cascade any further. The chain stops there. That is deliberate — a branch cascade has already reached everybody — but it means a branch cascade near the top of the organisation removes the option of sensible intermediate objectives.

Cascaded objectives are visible

This is worth saying plainly, because people are sometimes surprised.

When an objective is cascaded, the employees in scope can see it. They see its name and its description, because they need them to write a sensible child objective. Do not put anything confidential in an objective you intend to cascade — a specific person’s performance, an unannounced restructure, commercial detail that has not been shared.

If the context is sensitive, write a neutral parent objective and have the conversation separately.

Keeping it honest

Two habits keep a cascade tree useful.

Review the shape once a cycle, not just the objectives. Look at the tree itself. If every child is a restatement, the problem is not the individual objectives, it is that people have been asked to cascade something that should not have been cascaded.

Close the parent honestly, whatever the children did. A parent objective is not achieved because its children were. It is achieved when the thing it described is true. Rolling children up into a parent result is how objective systems quietly stop measuring anything.