Thinking about the Product development lifecycle, where discovery and validation are all around determining whether an idea is valid and feasible, how are you using JPD to capture this?
I think using the out of the box insights feature to capture discovery information makes the most sense given functionality and purpose, but wanted to see how others are approaching this.
Hi @Lisa McCann here's a video for how we do this in the team building Jira Product Discovery (link to the part where I talk about this):
https://youtu.be/6P7HBBQyQ5U?feature=shared&t=1035
We've also tried to describe it in this product discovery handbook.
Hope that helps.
Many teams use insights to document user feedback, interviews, and market research, tagging them with themes for better visibility. Another approach is leveraging custom fields to track discovery phases or using Advanced Roadmaps to align research with product goals.
If structured validation is key, consider integrating Confluence to document findings and linking them back to JPD for easy reference.
How detailed do you need your tracking to be?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.