How to model User-Solution Fit / Problem-Solution Fit?

[Jan-Hendrik Spieth]

As part of our general aim to understand and assess value, we are currently thinking about how to model user solution fit, and/or problem solution fit, in JPD.

This touches questions such as: How ideal is this solution? Does it address every aspect of the entire problem?

One place we'd find this could surface is insights:

For each insight (a user feedback) to an idea that describes a solution, we could determine a rating (1-5) that signifies how much that user's pain points would likely be remedied/improved.

Right now, we can only rate insight impact, though. We think the impact mostly relates to the "problem" nature of an idea, not to it's "solution" nature. But at least, if we used "impact" for our purpose, we think it could easily be confusing.

How are you fellow JPD users modelling user solution fit and problem solution fit?

Do you model it, at all? If so, do you make use of insights for this purpose?

Would you recommend for or against using insights for this purpose, and why?

And to the JPD team:

Have you thought about customization options on rating insights on one or several, custom dimensions (like, certain rating fields, but on insight level)? Does it sound interesting? Or to niche, or not recommendable, for some reason?

And what have you designed the insight impact rating for?

[Brandon Moberg]

We 100% need the ability for personal vs global filtering. This is the biggest blocker to Jira Product Discovery fully replacing our ability to completely roadmap in Jira.

[Hermance NDounga]

Hey Jeff, 

As Sam mentionned, you can disable Autosave on views, 

or create different views for different people (and put them in folders) 

We are aware that these solutions are still having some issues, so we will explore better solutions in the future. 

[Sam Hepworth]

@Jeff Maciorowski You can disable "View Auto Save", but my experience is that people still save customized views and confuse each other. I think, you can use access rules to prevent people for changing views, but that does not work for us, since people do need to customize views. A better solution is needed - until then people must create their own views. We have a section for each team member, but it is not a pretty solution.

[Tom Haapanen]

I think the only way (for now) is to create more views. Hopefully Atlassian will enhance this in the future so that you can filter without affecting others. 

[Jeff Maciorowski]

Wow, that is quite disappointing and very user unfriendly.  I thought I was doing something wrong. Thank you.

[Kaitie Warner]

I second the desire to enhance the view options to have personal views that aren't visible to everyone so you can make the changes most useful to you without effecting the big picture.