When should I cascade an objective?
You should think carefully before you cascade an objectives to people. Ideally, if you want people to support one of your objectives, you should have already discussed why you are cascading an objective. When cascading an objective, you should make it more specific to them, by editing the description of the cascaded objective, as well as the context. This will reinforce the reason for cascading an objective.
The person/people you are cascading to should be key contributors to the overall objective. This will help to ensure the progress updates on the cascaded objective are directly relevant when viewed on the parent objective.
You should also consider how many objectives the recipient will have after you have cascaded. If someone has a larger number of objectives, they may find their load becomes unmanageable. Cascading objectives is particularly useful for people who wish to share objectives across their teams. Most cascaded objectives tend to come from business plans.
Key points to note:
- Cascaded objectives sent to you still need approving (unless sent from that person’s Lead Reviewer, or from a plan).
- You should use the Context box to explain why you are cascading the Objective.
- If you have added tasks under an objective, they are not cascaded with the objective.
- There is no automatic update by you to someone else's cascaded objective.
- If you have been cascaded an objective, you can cascade it on to someone else again.
- You will receive an email notification when someone has accepted (or declined) an objective you have cascaded to them.
- The original objective is commonly referred to as the 'parent' objective.