You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
There are several key distinctions between Objectives and Themes in Align, and people ask “Should I use an objective or a theme?” As we say in our house, why not both?
In Align, Objectives and Themes serve different purposes, and they may have different audiences, be reviewed on different cadences, and inform different decisions within your organization. There are two important distinctions between Objectives and Themes:
These two objects give you a way to track both Outcomes and Outputs.
In Align's People/Work/Objectives/Time structure, you can see how objectives and outcomes are lined up in the picture below:
Here's a brief list of the distinctions between the Objective and Theme hierarchy.
You can view the Objectives Tree to see how you're doing with achieving your desired outcomes (or Key Results, if you're using OKRs.) This view is from release 10.85.
(There are other ways to look at how well you're doing at reaching your desired outcomes, but this is one of the best views.)
Here's a view of the Roadmap, showing the progress of the epics that are connected to the Themes your program is working on.
(There are other ways to look at the progress of the work being done to deliver on big themes, but this Roadmap view is a common starting point for digging in.)
Align Solution Architect
40 accepted answers