Jira Product Discovery - views and the fields

[Boleslaw Nowak]

Hey everyone, first of all we really enjoy the piece of software that the Product Discovery brings to the table, and how it helps to manage things on the product side.

Wanted to ask about few things though - the field structure is not really clear to me, and their configuration:

How do I define those fields, is there a way to add/remove those from this view? It looks pretty similar to Jiras View configuration for issues, but I couldnt find the setting anywhere.

Secondly I'm creating a custom view - which is aimed for less tech-savy ppl which I wanted to be pretty basic, and simple to use as of reportin their ideas but when I would want to have a pretty simply flow within the view so the user creates an idea - adds its title, 2nd step I would want is to add the description which I try to add as a column in the view:

but I can't really add a description to it, I can only add something that's called `Public description` and `Short description` which both are those hidden "other" fields, and they don't correspond to the main description - which I don't quite get the logic. 

thanks for help in advance!

[Adrian.Lester · Accepted solution]

I'm also in the B2B SaaS space so I feel your pain.

I've tackled this by using the Goal field and I select the user objective most affected by this work, and a custom field 'Strategic Theme' which is also a select field and contains the company objectives.   So far every idea we're considering manages to have both fields populated, and I can create separate roadmaps based on Goal or Strategic Theme.   I found this video from Tanguy on how you can set up JPD very useful 

[Joris Roulleau]

Thanks, I was edging towards a similar setup, but thought it might fail the KISS test.

On reflection, being able to generate different roadmap views for different audiences would be useful so  I'll go back to that idea and see if it works for me and colleagues.

[Lindsey Strong]

We also capture in "Insights" any documentation from the customer and identify the customer to help determine where the request came from, or if we're seeing consistent feedback from multiple sources. 

[Joris Roulleau]

Thanks, I'm also identifying the customer for the same reasons and to add a weighting element to the ideas.

[Kevin Sniokaitis]

Similar to the other responses we are doing dual categorization. We are utilizing Goal for our company strategic objectives where as a separate categorization for User Impact. In the latter I've connected the impact areas for our Users that then helps us balance work and prepares for how we will communicate the functionality to the user.

[Freddie Bendzius-Drennan]

They're going to be closely related for sure.

We have business objectives, in the form of OKRs, that we align to, and at the end of the day successfully achieving those OKRs is tightly coupled to delivering customer value.

An example of this is we have an OKR relating to churn reduction. That's a business objective to help us achieve our revenue goals (in conjunction with related OKRs around increasing net-new and cross-sell revenue). How do we successfully execute on those OKRs? By driving customer value. So for example if you can validate that building something to save customers time, reduce costs, can tie back to you achieving one of your OKRs (eg boosting retention), then you have tight alignment.

Hope that makes sense!