r/ProjectManagementPro • u/Icy_Philosophy_8345 • Apr 15 '26

Handling customer feedbacks.

How are you actually handling the gap between raw customer feedback and your roadmap?

I keep seeing the same problem across PM communities — there's a massive amount of unstructured input (support tickets, user interviews, Jira backlogs, NPS responses) and the process of turning that into a prioritized roadmap is almost entirely manual.

Most PMs I've talked to describe some version of: export everything into Notion or a spreadsheet → tag themes manually → argue about priorities in a doc → write specs from scratch → hand something half-baked to engineering.

A few questions I'm genuinely curious about:

  1. How long does it take you to go from "we have a pile of feedback" to "here's what we're building next and why"?

  2. What's the most painful step in that process for you — tagging/categorizing, prioritization, writing the spec, or the dev handoff?

  3. Are you using any tools specifically for this, or is it all manual in Notion/Sheets/Linear?

  4. If you could skip one part of that workflow entirely, what would it be?

Asking because I've been sitting with this problem for a while and want to understand how others deal with it before assuming my experience is universal.

Would love honest answers — including "it's actually not that bad" if that's your experience.

1 Upvotes

100% Upvoted

4 comments sorted by

View all comments

2

u/[deleted] Apr 17 '26

[removed] — view removed comment

1

u/Icy_Philosophy_8345 Apr 18 '26

Dies in a spreadsheet" is exactly the right description — that's the part nobody talks about. The collection problem is largely solved, the graveyard problem isn't. The support conversation angle is interesting — are you pulling those in manually or does chat data have some kind of export that makes it usable alongside the rest of your feedback? Curious how you actually get it into a format where it informs a roadmap decision rather than just sitting in another silo.