nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the best way to gather feedback from stakeholders to add automatically as idea to JPD?

Dani Lanovyi

Hey there,

I was wondering if people found a good way to gather feedback from stakeholders and add it automatically to JPD as an idea.

Ideally, I'd like to create a form for stakeholders to fill (even those without a Jira account) and when submitted, the new idea should be created in my JPD project with the content of the form.

Did anyone try to realise something like this? Any tips would be appreciated!

Thanks!

Dani

Accepted answers

Marina Rambo_so6vt2

I created a two board intake system. The submission board is built in Jira Work Management, which has the built in capability of creating a web form. In that board, each field for that project is very specific - User Type, Description, Context, Product Area, Existing solution, Etc.

After a user submits a ticket to the submission board, automation then compiles it into a single description, and some discrete fields for categorization when it creates a ticket in our Jira Product Discovery (JPD) board. It also links the original ticket to the newly created one.

When a user submits, they can also say that they want to add more information to an existing idea, In that case, there is a field in the submission board for "related idea" they can enter the JPD board key in that field. Automation will not create a new JPD ticket in this case, it links to the existing, and adds comments to it.

The automation took more time to set up than the boards, but it saves so much time and effort in the long run.

Chris Timms

Hello @Dani Lanovyi

I currently work in this way, and we are struggling big time with it!

Users actually interpret adding it to the product project as "accepted, committed work" which could not be further from reality!
The inbox is very inconsistent, containing feedback and feature requests in a manner that is hard to quantify and have meaningful discussions around
It needs constant pruning, transformed into insights, merged, etc.
The list gets MASSIVE, too massive, really to properly manage so your users think their requests just disappear into a black hole

We are planning to move to the model similar to what @Marina Rambo describes below.

A JWM board where users can, via a form in our software, give feedback (we get user data and segmentation easily this way)
Collate this feedback into Dovetail (A tool the JPD team recommended and use) to sift for actionable problems
These problems are what then gets added to JPD and we can have good conversations around what to work on next based on the volume/importance of the feedback we are getting.

All that to say, reconsider using JPD as your inbox for raw feedback, it is much better used as a source of truth for curated feedback!

Regards,

- C

All comments

Marina Rambo_so6vt2

The automation took more time to set up than the boards, but it saves so much time and effort in the long run.

Yong Yang

smart

Chris Timms

Hello @Dani Lanovyi

I currently work in this way, and we are struggling big time with it!

Users actually interpret adding it to the product project as "accepted, committed work" which could not be further from reality!
The inbox is very inconsistent, containing feedback and feature requests in a manner that is hard to quantify and have meaningful discussions around
It needs constant pruning, transformed into insights, merged, etc.
The list gets MASSIVE, too massive, really to properly manage so your users think their requests just disappear into a black hole

We are planning to move to the model similar to what @Marina Rambo describes below.

A JWM board where users can, via a form in our software, give feedback (we get user data and segmentation easily this way)
Collate this feedback into Dovetail (A tool the JPD team recommended and use) to sift for actionable problems
These problems are what then gets added to JPD and we can have good conversations around what to work on next based on the volume/importance of the feedback we are getting.

All that to say, reconsider using JPD as your inbox for raw feedback, it is much better used as a source of truth for curated feedback!

Regards,

- C

Sebastian Pechhold

In this case, stakeholder must know, that similar or same ideas are already submitted, right?

Dani Lanovyi

Thanks, Chris, this is really useful and mirrors my concerns as well!

Dani Lanovyi

Thank you, Marina, that's a very clever way of getting stakeholder feedback. Can I ask how much time on average your PMs take to trim the submitted feedback?

One of my worries is creating another Zendesk that takes so much time to manage, respond to queries, ask for clarification and remove duplicate or irrelevant submissions.

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

feedback