Preview of the new Jira Product Discovery handbook

[#1]

Update on 10 October: the handbook is now available here: 

Introduding the Jira Product Discovery handbook

It's in PDF form, we're working on an online version that we'll keep up to date as we iterate, and we'll share a link as soon as it's ready.

---

@Axel Sooriah and myself have been hard at work writing a handbook to be used alongside Jira Product Discovery (JPD). Its purpose is to offer a pragmatic view of product practices to guide product managers and their teams when adopting JPD.

It's in beta, not fully ready for prime time yet, but we wanted to make sure the community could have early access to it and the opportunity to give feedback. 

---

👉 Jira Product Discovery handbook (beta, now outdated) 👈

---

In this handbook you can expect 3 things:

• Product management practices, i.e. advice on the ways of working.

• Practical advice on how to use JPD and other Atlassian products to enable these practices.

• Real examples of how Atlassian applies these practices within our own product teams.

We’ve tried to keep it pragmatic, focusing both on the ways of working and how to use tooling. The first few sections contain more theory, and as you progress in the handbook it will contain more and more practical examples.

Our team doesn’t have the audacity to claim there is one best way to do product management. Instead this guide reflects what we’ve learned when creating Jira Product Discovery, and we hope that by sharing it will give you different ways to think about your product management practice and how to approach the implementation of tooling to support it.

[Ana Eva Lopez]

I just wanted to comment that the handbook has been so handy and timely for us!  We are just getting Product Discovery up and running so the handbook has provided not only valuable insights into setting up and using the tool but also why we are doing this.  Tools are only meant to support the processes we follow.

Thank you so much and can't wait to keep getting updates!

I have 2 pieces of feedback:

1) For the views, it would be good to see what the filters are when setting up the view since that helps to put into further context why we only get to see certain things.

2) The Confluence link that is in the What to add to the product backlog is set to restricted so we can't access that content.

[duncan.crowell]

Great reading so far - This might be too early given there is no direct integration yet but would love to see an extension of the view in where JPD fits in the Atlassian portfolio to include Jira Align.  This is a key part of my Enterprises ability (outside of my direct team) to report on delivery measures however it falls short in the product discovery space hence my team having moved to JPD.   I have not been able to get a clear view on how these map together in best practice though. 

[Mirko Grahnert]

Thanks so much for sharing! I really enjoyed going through the handbook and found a lot of nuggets of insights.

There’s just one part I found a little confusing: the connection between your Product Delivery Lifecycle (Wonder, Explore, etc.) and your Product Roadmap. You mention that the ‘Now’ phase should should be a reflection of ‘what team is currently focusing on in terms of discovery and delivery, and particularly the Explore/Make/Impact stages of an idea.' But then it also seems like Wonder & Explore are mapped to the Next/Later stages of the roadmap. 

[Jason M.]

Quite helpful, I've shared w/our teams, we need more of this from Atlassian in general for all the fancy new products.

[David Beacham]

Thanks - this is a great overview. And very much looking forward to a better way to organise ideas more directly into a tree-like structure.

FYI: there's a link in the "Product backlog" section to more information on boulders, rocks, pebbles that appears to be inaccessible.

[Daniel_Domene_Kolekti]

At The Adaptavist Group, many of our product teams use JPD, and we absolutely love it. This handbook is incredibly valuable, so thank you for putting together all this information! While the content is already pretty good, I have some feedback on the handbook itself and the content delivery you chose. I’d like to invite you to explore Guided Pathways, a tool we developed to help build handbooks and other tree-like structured content or guides in Confluence (I see @David Beacham likes the idea!).

It might be a great option for delivering this content to JPD users? Feel free to reach out, I'd be happy to discuss how we could help.

[Camilla Gjengseth]

We started off using JPD for collecting customer feedback to our product team in one place and are now gradually expanding it as a tool for what it is truly made for, product discovery, ideation, prioritization and roadmaps. For one that is already convinced that Product Discovery is an awesome tool for collecting all the ideas in on place - from high level roadmap view to what we actually end up doing in delivery - this handbook has been helpful in explaining the principles on why we need to improve on how we work in order to be more focused and remove "waste" in time spent on "low value/gain" items/ideas. Thank you! :)

[Devan Bretz]

is this HIPAA compliant? I was hoping to find any documentation around that and I am having a tough time. If someone could answer this for me that would be great!