You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I normally use and like these levels:
- Problem/opportunity (normally a pain, job or gain)
Insights come from customer interviews, market research or competitors analysis and feed opportunities. (productboard does also differentiate like this)
I know you are working on a way to better distinguish problems from solutions inputs so that they can be visualised more easily from a tree.
However, my questions are:
1. Are there ways to register new insights from outside the main idea object so that you don't necessarily link an insight to a particular opportunity from the beginning but maybe later?
2. Thus, is there a way to visualise insights in a list?
For the moment, insights aren't an independent entity in Jira Product Discovery. They can only be stored and attached to an idea.
In that way, it is unfortunately not possible to create insights that wouldn't belong to an idea or to be able to search in JQL all insights for a specific project.
We've received a lot of feedback regarding this matter, so it is definitely something we are planning to improve, and I will add your feedback to it.
Regarding the solution/opportunity level, Tanguy had recorded a short demo to show how you could categorize your idea to create this type of structure.
@Hermance NDounga independent insights are definitely needed!! I would really like to be able to create a "note" in JPD, and then tag insights from that note to multiple ideas. This way I can have a single source of truth for an insight, rather than having to recreate it on multiple ideas.
This also ties to Can you pull customer data from Salesforce? (atlassian.com), because I'd like to have the customer information associated with the note instead of having to add a link from SF every time to pull that information.
I'd be happy to do a discovery call to provide more context!
Hi @Hermance NDounga , any news about Insights becoming independent entities? Is this a short-term thing or something you're still considering?
I just started exploring JPD and it's looking amazing, but I don't believe I can migrate my company to it without having independent insights.
A lot of our "feature request" workflows are dependent on this - today our technical support, sales, etc. submit their insights, and then the product team "triages" these insights and connect them to ideas/features. I don't expect our stakeholders to triage their insights by themselves.
Adding my 2 cents in here as I see there was some Atlassian discovery back in March
Having to have an idea before an Insight exists is putting cart before the horse.
Insights can come from anywhere, anytime and having an ability to note (capture) them in the system without doing anything else with them at that minute is paramount.
ProductBoard do this nicely so just take a look (again) at them
We get many insights captured by a range of people, places (and automatic integrations using smart tags that go into PB Notes. Basically a 'oh, this is interesting, lets keep a note on this'
A PM will periodically (make that regularly) review the notes in PB and as they will assign them to existing feature discovery items or when seeing common themese starting to appear, create new features (ideas) to follow up. A useful point here is also being able to assign same insight to multiple features (ideas)
My concern is if Atlassian has shoe-horned JPD into existing data structure of rest of the suite and insights have started as a child of ideas, then may have painted self into corner.
Hi all 👋
Rohan here from the Jira Product Discovery (JPD) Product Management team. I'm currently exploring how JPD users are collecting and managing feedback and insights.
This will be a 1 hour research session, conducted over Zoom – participants will receive a $100 gift card as a thank you.
If this sounds like you and you're interested to take part, please answer a few quick questions and I'll be in touch with participants who qualify to schedule in a session. https://forms.gle/zVvjfCqjTBHM9zFk9
I have the same problem. Also, why let me label an insight if there's no way to group insights? Is it just so when I look at that one insight I see a label?
Insights often come from many customers, have some overlap, or are entirely duplicated. I want a way to keep track of all the insights and their nuances and associate them with where they came from so that when we release features/bugs that address them, I know who to talk to
Do not have an answer to this but @Rohan Swami should we be hopeful here?
Obviously if you only do one thing well as a PM it is getting the order right between listening to customers (AKA Insights) -> Defining problems -> Collaborating on solutions.
Having to have an "idea" in place before being able to link Insights is insanely bad practice as a PM is it not? Your competitors like Product Board do this well so you didn't even have to invent it.
Can we expect a fix here because Oriol above is doing this right and Jira (apparently retrofitting Insights into a custom field of sorts) is doing it wrong?
@spencer.cox Jira Product Discovery is still free to use, we're in the early innings of building this out into a very powerful Discovery tool. We're going to get there, but I don't want to give you infeasible delivery timelines with these features, we're carefully and consistently adding value for our customers and taking care to prioritise our efforts where we see the biggest pain for our cutomers.
Merging a feature request / idea as an insight to another idea would also be very handy.
The amount of stakeholders that currently come up with great product ideas is increasing in our company. We encourage them to send these ideas to us, however very often an idea already exists and you want to quickly merge the description of the new idea (which contains the problem or a specific use case) as an insight for your existing idea.