Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Do you use Objectives or Themes? Why not both?

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:

  1. Objectives represent a description of the desired outcomes your organization wants to achieve; long-term objectives can be decomposed into shorter-term objectives that help you track whether you're getting the results you want.
  2. Themes represent a decomposition of work your organization might do, from a very high-level item that could take several parts of your organization multiple years to complete all the way down to the stories that are completed by a team in a sprint. 

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:

Screen Shot 2021-01-12 at 9.52.12 AM.png

 

Here's a brief list of the distinctions between the Objective and Theme hierarchy.

Objectives

  • Goals and objectives are intended to define the outcomes the enterprise is seeking with its different investment decisions.
  • Goals and objectives can be arranged in a hierarchy where a high-level goal can be achieved by different portfolios achieving specific objectives; portfolio objectives can be decomposed into solution, program, and team objectives.
  • Team or program objectives may not necessarily be related to a higher-level objective. It is possible (even desirable) for a team to have local objectives that are roughly aligned with enterprise objectives.
  • Goals can be achieved over one or many years. (This depends on how the Strategic Pyramid is configured for your enterprise.) Usually a goal is achieved over a year. Objectives are related to quarters: a portfolio objective may be achieved over many quarters, but a program objective is expected to be completed in a single quarter.
  • Objectives can be achieved by one to many work items being completed. Work objects (epics, capabilities, features) may contribute to multiple objectives.

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. 

Screen Shot 2021-01-12 at 10.46.25 AM.png

(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.)

Themes

  • Themes are intended to be used to track work that is being done to meet the enterprise’s strategic goals.
  • Themes sit on top of the Work Tree and represent the transition from strategic intent (goals in a strategic snapshot) into portfolio-specific investment opportunities (i.e, initiatives.)
  • Themes are large efforts for the enterprise, and may take from 4 to 8 quarters to complete.
  • Themes have target budgets that can be used for managing investment guardrails. Theme owners can set a total budget they want to spend on the specific theme, then see how different teams or programs are allocating their work compared to those budget guardrails.
  • Themes represent the highest level of the work decomposition structure. Themes are made up of epics, which are made up of features, then stories. A subordinate work object can have only one superior or parent work object (i.e, an epic can belong to only one theme.)

Here's a view of the Roadmap, showing the progress of the epics that are connected to the Themes your program is working on.

Screen Shot 2021-01-12 at 10.50.03 AM.png

(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.)

1 comment

Emily Koch Atlassian Team Jan 12, 2021

Great article! I love how this shows how both themes and objectives can work together and connect the rest of your work to strategy.

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Align

Best Practices in Jira Align

Hello Jira Align customers! In order to better serve you on your journey with Jira Align, the Community team has worked with the Jira Align team to curate the content in this collection to better s...

947 views 1 13
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you