nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Atlassian Product Discovery handbook

Tanguy Crusson

The Atlassian Product Discovery handbook is full of the hard earned lessons we gained while building JPD.

There is a lot of great thought leadership content about product management out there, but we found it's often aspirational and lacking pragmatic, practical ways to get started. So @Axel Sooriah and I rolled up our sleeves and tried we tried to address these gaps in a handbook. Consider it our gift to the PM community!

👉 Atlassian Product Discovery handbook (online version) 👈
(or download the PDF version)

1️⃣ Product management practices and ways of working
2️⃣ Examples of how Atlassian applies these practices within our own teams, especially in the team creating JPD
3️⃣ Practical advice on how to apply these practices using JPD

It's version 1: far from perfect but we think it's got legs. Expect an online version of this handbook soon that we'll keep evolving based on what we learn working with y'all. Comments are welcome, and if you'd like to contribute let us know!

Here's a teaser: the stages of an idea:

Comments

Michael Dohan_ac7f6r

Thanks for putting this together. We are just getting started with JPD. This is a nice overview of how to think about using it.

Pavel Egorkin_trhfo0

Thanks, Tanguy and the entire team. I really like the direction Atlassian products have taken in recent years

Chad Walker_10lwdn

Your team is doing great work. I'm very happy I found Jira Product Discovery. I've never been so organized.

Eduardo Oliveira

@Tanguy Crusson - Awesome handbook and product, we use JPD in a daily basis and it's so easy, flexible and powerful. Keep rockin!

julvon

@Tanguy Crusson @Axel Sooriahwoow thanks for the playbook! We are already using JPD for a year and like how it is integrated with JSM for the delivery

Monika Marko

thank you for sharing this; we are in the process of rolling this out to the org, after having worked with JPD for over a year now, so this will come in handy.

Hamsa Ranganathaiah

Thank you so much , it was the need of the hour for me

David Holden_qvesaf

This looks great! At least one of the hyperlinks (page 23) tries to take me to a confluence that I don't have access to (pm-dev.atlassian.net)

Tim Balzer_c8bh1y

This is a fantastic resource—thank you for sharing! I'm noticing a handful of images that don't match the caption, though. Here are a few captions as reference (not exhaustive):

A user conversation, transcribed and analyzed in Dovetail
Research report in Confluence, ready to be distilled into Insights in JPD
A survey in Pendo, targeting specific customers
A closer look at our regular CSAT survey
Conversations in the Jira Product Discovery group

Tanguy Crusson

Thanks @Tim Balzer , you're right! We'll fix that 🙏

Tanguy Crusson

Hi everyone, it looks like we borked something up when generating the PDF version of this handbook and most of the images in there are wrong... Thank you @Tim Balzer for bringing this to our attention! It's a public holiday in the US today but we'll jump on it to fix it tomorrow.

In the meantime, you can access an earlier version (but with the right images) here: Jira Product Discovery handbook (beta)

Stephen.Lugton

Thanks for this light bedtime reading @Tanguy Crusson

Some of our product owners (who are more accurately senior business users) have been struggling with technologies other than hand written notes so hopefully this will give them more insights into how the rest of us work!

Tanguy Crusson

OK everyone the images in the handbook were fixed, an issue with the editing tool for the last export had thrown all images off for some reason... Thanks a ton for reporting this @Tim Balzer !

Florian Schmidt

@Tanguy Crusson Is the pdf from the "real" download page updated or is this in progress?

Link

Tanguy Crusson

@Florian Schmidt it is there 👍

Tommy Légaré

Good job! Really nice guide! It's great to have all those little examples of usages and practical advises. Thumb's up to all the team!

David_v4610x

Hi, thanks very much for this work.

unfortunately, i think the link is broken. Can't download the book

david

David_v4610x

Sorry, my mistake.

Everything is fine. couldn't download because of my firewall rules.

thanks

david

Frode Nilsen_wzsj4j

This is much appreciated

But, of course, some questions:

Regarding the large, medium and short lists. I understand this as how to "divide" the issues in the parking lot, and that it is the short list that get promoted to Wonder, Explore etc. Or did I misunderstand something?
Regarding Spikes in Wonder and Explore. You didn't seem to create tasks/stories for those in the teams Jira boards. Why is that, and how does the spikes get prioritized over other team work?
You did include bugs/paper cuts in JPD as Pebbles. Will you continue to do that when the product is released? I'm accustomed to set aside 20% of the team capacity to handle technical debt and bugs and just keep an eye on the prioritization of those in the team backlog.

Jaderson

I would to thanks the guys of Atlassian to creates this awesome and intuitive projects.

As a CEO and consultant of projects, It makes needed to structure all the creatives ideas that is emerging in the workflow of Product building. So when I connects the PD workflow, with worload management in Trello and Jira, I got a real strenght joined resources to be agile, efficient and aligned with my needs as PM.

Get a time to try a MVP of this joined resources, you will be metrified impressed with the save time of yours Projects lifecycle.

Regards!

CEO & PM at Alfa Fintech
Software Engineer & Lead & Financial Services Exp +20yr
Data Science | Disruptive computing & AI Techs Ind. Applied
Computer Engineering Experiences
IEEE Member⚛️🦾🧠📊 | APS Member[⚛️ℹ]☄🏭
Embracing|specializing in emerging engineering areas
🗪✈️ like to talk and new experiences

William Guerra

Nice work, I have used the prioritation matrix for years but in unlinked tools, now I can set the ideas and then conect the prioritized one with the team using Jira.

Islam Mezied

Thank you @Tanguy Crusson , I followed the link and tried to access the book download link but it is not working. could you please help with this?

Islam Mezied

@Tanguy Crusson I realized and resolved the issue. I was logged in using a non-business email, which is why the download link wasn’t working.

For anyone facing the same issue, logout and fill out the form using a business email, and the link will work without any problems.

Thank you!

Daniel Eden

Hi @Tanguy Crusson - I noticed that the link to the Boulder, Rocks, Pebbles framework (on p.23/114) is not accessible. I get the message: "You don't have access to that space"

here is the link: https://pm-dev.atlassian.net/wiki/spaces/PH/pages/1409080

Tanguy Crusson

@Daniel Eden that was an error when creating the PDF, you'll find the section later in the handbook

Ravi_4xnqsf

@Tanguy Crusson..Great help for the beginners like me.Overall it's a wonderful product.Look forward to more updates.Thanks

James Conway_bjz829

@Tanguy Crusson

this has been really insightful, thanks!

How do you recommend managing broad, genericised ideas that accumulate multiple small insights?

For example, in Boulders, Rocks and Pebbles, I see a screenshot with "Timeline view improvements" at the top, I imagine it represents a collection of minor enhancements and "even better if" feedback from users.

Would you keep such an idea open long-term, periodically delivering small fixes to improve specific aspects?

Context:

Customer Success reports three user pain points (A, B, and C) as "papercuts." These could be tracked as individual Jira issues (in JPD, JSM, or a Jira Software project).
The Product team decides to fix Papercut B.
How would you recommend closing the loop to confirm that Papercut B is resolved while maintaining the broader idea?

Tanguy Crusson

@James Conway when we ship a feature we typically create an "improvements" idea, where we keep collecting insights - typically feedback from customers on how to improve it, gaps, usability issues, etc.

Every once in a while we'll pick one of those, we'll allocate a budget (e.g. one team for X weeks) to iterate on the experience. The team will go through all the things and pick the top things to improve. They'll move the insights that didn't make the cut to another idea. Each of those can land on a team's roadmap.

Screenshot 2025-02-17 at 16.56.36.png

All the improvement ideas are linked to the original one.

We're actually started using idea hierarchies for that more recently:

Screenshot 2025-02-17 at 16.59.26.png

Tatiana Torset_mkk1uv

Great work @Tanguy Crusson Thank you for putting this together! We have been using JPD for more than a year now and some questions have accumulated during this period. They mostly concern the hierarchy of everything - I am playing a bit with different ways of categorising what we are dealing with in our own company. So it is super helpful to be able to have a look at how you did it in JPD team.

I assume, the top of your hierarchy is themes and they can have one or several focus areas.

Then there are boulders - rocks - pebbles. The main question here is: do you always split boulders into rocks (in other words do all rocks have a boulder they belong to)? And the same about the pebbles - do they ladder up to rocks and boulders?

Tanguy Crusson

Thank you @Tatiana Torset. I assume you mention Boulders, rocks and pebbles as we've defined them in this handbook?

Here's a Loom where I describe how that works for us.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jpd