How Atlassian's Growth team uses Jira Product Discovery for program planning and execution

[#1]

Hi Community! This week as part of Jira Product Discovery June, we’ll be sharing examples of how different Atlassians use Jira Product Discovery. This is part 3 of 4.

✨ Challenge ✨

We want to hear from you too! Leave a comment with any questions, tips, or how you use Jira Product Discovery within your team and get the Alignment Architect badge.

---

*This spotlight highlights Jira Product Discovery Premium - learn more here.

Meet the Atlassian

• Name: @Jasmine Garrett 

• Role: Principal Program Manager, Growth

• Where you’re from: Dayton, Ohio

• Fun fact: I'm a lifelong vegetarian, plant-based cuisine and veggies have always been my jam 🥦

• Advice as a PgM: Sometimes, there’s no silver bullet for fixing process gaps or operational challenges, but it doesn’t have to be perfect from the start. The key is to start somewhere and iterate as you go. Progress beats perfection, and it’s better to fail fast than to get stuck in analysis paralysis.

1. What team are you on at Atlassian and what is your team responsible for?

I’m a Program Manager in Atlassian’s Growth org, leading strategic initiatives focused on user adoption and engagement. My role focuses on aligning cross-org and product teams to centralize prioritization, drive value faster, and increase velocity—all while ensuring we’re tracking impact and putting the right processes in place.

2. What challenges was the Growth team facing that prompted adopting Jira Product Discovery?

In my role, complex, cross-org programs often scale across 7+ teams at any given time, making it critical to capture a high-level view of what’s happening, when, and where. While this can be achieved via a shared doc/page, it is often very manual and time-consuming - leading our team to seek a more lightweight, flexible solution that:

• Enables teams to operate independently while maintaining transparency

• Facilitates better conversations around partnerships and existing work

• Reduces redundant efforts by leveraging shared views of learnings and wins from past projects

• Provides a centralized roadmap to track timelines, launches, and impact

3. What are the primary ways in which the Growth team uses Jira Product Discovery?

Jira Product Discovery has become the single source of truth for roadmap planning and execution for our programs. Our teams can quickly capture and update information while enabling them to view it in a way that best suits their needs. A few hero use cases for our team include:

• Intake & Backlog Grooming - it serves as an intake hub for partner teams requesting experiments or new functionality. Idea forms let us capture ideas and conduct a rough sizing of impact, helping us determine what should be prioritized on our roadmap.
• Roadmap Planning & Workstream Views - teams use JPD to not only draw from the intake backlog but also during quarterly planning, which includes assessing development capacity. By consolidating all project work into a single view for each quarter, we can show how prioritized work ladders into our OKRs. Plus, maintaining alignment around the relevant fields is super helpful, as teams can sort and group views as needed based on what’s relevant to them!
• Standardized Global Fields for Cross-Team Alignment - collaboration spans multiple teams, with each typically managing their own set of JPD projects. By establishing and a set of shared Global Fields that can be used across all JPD and Jira projects, teams create a unified view without compromising autonomy. This eliminates the need to manually track down upcoming work and makes it easier to see how individual team efforts contribute to overarching programs.

4. How has adopting Jira Product Discovery helped support your team’s way of working?

Adopting JPD has transformed how we track, prioritize, and collaborate across Growth programs. Key highlights include:

• A single source of truth for the team and leadership visibility with customizable views.

• More clarity across teams and partners, leading to better collaboration.

• Streamlined prioritization discussions that lead to better solutions, faster delivery and more alignment.

5. Any pro tips or advice to share as a Jira Product Discovery power user?

Set up a scalable template & framework

• Establish a standardized structure upfront to make cross-team collaboration easier

• Define Global Fields early so you can consolidate multiple roadmaps into a single view 

Work types & hierarchies

• Hot off the press, hierarchies (currently in beta in Premium) has been an absolute game changer in visualizing how projects across my team and org ladder up into more significant initiatives. The ability to set and link different work types allows the team to layer in a view that flags the list of experiments each delivered initiative or feature unlocks. The possibilities are endless with this one!

Demo

---

In case you missed them, here the other articles in this series:

• Part 1: How our Head of Program Management relies on Jira Product Discovery for portfolio management
• Part 2: How Jira Program Managers use Jira Product Discovery for design allocation and capacity planning

[Harrison Ponce]

Thanks @Jasmine Garrett, for sharing how you use JPD!

[Tomislav Tobijas]

Really nice use case for Roadmaps feature. This just gave me a few ideas for our implementation :))

Cheers for sharing! 🙌

[Katrin Erhardt]

Thanks for sharing this really inspiring use case for the Roadmaps feature!

[Sherry_Xie]

Nice use case, thanks for sharing 👍