Coming Soon: New Objectives Tree

Jira Align is updating our objective experience with a new and improved visualization of the Objectives Tree. With version 10.106.0 on March 4, 2022, we'll be revealing the new Objectives Tree to the world!

For a short period after the feature’s release, you’ll see the new Objectives Tree by default, but will be able to switch between the legacy (current) and new experience. Later, we will deprecate the current experience.

The new experience completely rethinks the visual representation for objectives and key results based on your actual goals and needs.

Legacy (Current) Objectives Tree

Old_objectives_tree.png

The current experience requires excessive expansion and has no way to clearly visualize the overall status of your objectives.

New Objectives Tree

New_objectives_tree.png

Get clearer guidance on what's going well, what needs help, and what's off the rails from a single screen. Or, drill into additional details if needed.


What else you'll find in the new Objectives Tree

  • Simplified high-level reporting with quick filters helps portfolio managers focus on what’s most important, what needs attention, and how things are related. This helps organizations better visualize goals by providing a visual format that represents the status of objectives.
    Quick_filters.png
  • Richer status reporting vocabulary provides greater nuance to in-progress objectives.
    This new view has enabled us to mimic the statuses of objectives tracked within Jira Align to the status options available in Team Central, which provides greater nuance than the previous statuses could. Instead of just a Not Started, In Progress, and Completed status, the new experience provides more options. These include Pending, Paused, On Track, At Risk, Off Track, and Completed. These statuses are displayed at the top of the page and the objectives can be easily sorted by status for further investigation into why something may be at risk or off track.
    Status_column.png
  • Easier management-by-objective and course correction with at-a-glance portfolio views and drill-down capabilities including simpler reporting supported with visual controls, i.e., traffic-light indicators, progress bars, etc. The streamlined view puts the most important information on a single page and makes course correction conversations faster with a visual roll-up of the most pressing issues.
    • Portfolio objectives that drill into program level and team level objectives with the click of a button.Drill_into_Portfolio_objectives.png
    • Track how much work still needs to occur to achieve the objective with Work progress bars.
      Work_progress_columns.png
    • Easily visualize how many key results are associated with each objective in the Key results column. Key results are tied to the specific work item as in, you will only see portfolio-level key results associated with the portfolio-level objective, not a roll-up of all key results associated with ALL program and team level objectives tied to the portfolio-level objective.
      Key_Results_column.png
    • Easily see who is responsible for each objective in the Owner column.
      Owner_column.png

Why are we making this change?

Enterprises at scale are transitioning towards thinking and aligning on business outcomes (or the desired result) as opposed to focusing on work output or outputs. Enterprises also want to unlock ambition and inspiration at every level, encouraging all teams to strive above and beyond without fear of failure culture.

Objectives and Key Results (OKRs) are important in identifying the change organizations want to see in order to have an impact on the highest level needles or KPIs in the business.  More importantly, using them to develop hypotheses and measure impact, otherwise work will continue to be tracked by the traditional on time on budget with a focus on outputs as opposed to the impact it has on a business outcome or validating a hypothesis.

We are making this change for several reasons:

  • To provide a better user experience through improved visual representations of OKRs
  • To make high-level reporting more actionable by improving the nuance for in-progress OKRs
  • To ensure better understanding and prioritization of the work surrounding OKRs to achieve objectives faster

 

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.