Introducing the Atlassian Product Discovery handbook! 🙌

[Ravi]

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

[James Conway]

@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.

All the improvement ideas are linked to the original one.

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