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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


program vision vs. program "priority" vision ?

when capturing a program vision in Jira Align, it also asks me to add one or several "priority visions" below. Why is this (I always thought there can only be one vision) and how can I proceed without creating additional priority sub-visions ? Thx

1 answer

1 accepted

0 votes
Answer accepted
Shawn Kessler
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 21, 2020

Hi ET,

Yes, you are correct, you start with one main program vision, where Product Management provides the overall, specific program context and vision. Next, the idea is to use the priority visions to further break down the vision into smaller vision statements, or sub or supporting visions--they are completely free form. For example, define how your competitors or your company's strengths and weaknesses fit into the overall vision. See the example below.


Basically, use the priority visions to help further define the vision--so that the parts help make up the whole. If you choose not to use the priority visions, just enter dummy text for the first priority vision or TBD as a placeholder. Hope this helps.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events