How to capture & manage improvement ideas in JPD
Asked by David Nadri:

Hello JPD community,

I would love to understand how others capture, track, and manage ***improvement ideas*** for existing features of your product in Jira Product Discovery (JPD).

For example, let's say I have a shopping app and there's a bunch of good ideas for improvements to the cart, shared by our customers or internal stakeholders over time.

**Challenges:**

* Eventually, we'll want to look at this backlog of improvement ideas and select one to work on, create a separate idea for that improvement, and link a delivery epic to it.
* We want to have one place in JPD to find all the ideas/improvement ideas related to a specific area (Cart) to see the whole picture and decide which ones to tackle.
* This setup also helps CSMs \& other stakeholders check if an idea is already in our backlog for a specific feature.

**Current approaches**:

1. **One improvement idea**: Create one "Cart improvements" idea in JPD and add the individual improvement ideas to its description as we hear about them in the comments or insights (or elsewhere). However, there's no way to have one parent idea and the improvement ideas as sub-ideas - so they'll live in the description (i.e. as bullets?).
2. **Separate improvement ideas**: For each new cart improvement idea, create a separate idea in JPD, and tag them with a "Cart" component or product area field so that they can be grouped together.

**Question**:

What are the best ways to track and manage these cart improvement ideas in JPD? Would love to hear about other methods or best practices that have worked well for your teams.


Answers:
author: David Nadri
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) - I think I remember seeing a JPD video where you showed another approach for capturing \& organizing 'improvement' ideas in JPD. Could you please share this, and any other input you have?


author: Jens Schumacher - Released_so
body: #2 is most certainly the preferred way of organizing ideas.   

Separate ideas allow you to

* More easily discover what ideas have been raised already.
* Gather insights related to each individual idea.
* Use the prioritization tools in JPD to prioritize the ideas.
* Link the idea to a delivery ticket when the time comes to implement it.

comments: author: David Nadri
body: [@Jens Schumacher - Released_so](/t5/user/viewprofilepage/user-id/3653468) - thanks for your input. That makes sense.

But how do you recommend grouping/connecting 'improvement' ideas to an existing feature so they're in one place? I suggested using tags to group them by that tag in a view to see all the ideas/improvement ideas related to the tag. Curious if there are others.


author: Jens Schumacher - Released_so
body: [@David Nadri](/t5/user/viewprofilepage/user-id/3918237)

If the existing feature has an existing Epic or Idea, you could link each improvement idea to that ticket. If it doesn't exist, you could create it.   

Tagging could work as well, but it might get a little out of hand over time. Linking issues is a cleaner approach until proper hierarchies exist in JPD.


author: Nicolas Grossi
body: [@David Nadri](/t5/user/viewprofilepage/user-id/3918237) You might take a look at this link: <https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Difference-between-JSM-amp-JPD/qaq-p/2626253>

HTH

Nicolas

comments: author: David Nadri
body: [@Nicolas Grossi](/t5/user/viewprofilepage/user-id/676185) - thanks! This would be useful if we use JSM.


Tags: improvement