Separate request, pain, and evidence
A feature request is not the same as the underlying pain. When a user asks for an export button, the pain might be reporting to a manager, moving data into another workflow, or keeping an offline archive. The roadmap should respond to the pain, not just the requested shape.
Attach behavior to the comment
A feedback item becomes stronger when paired with the session that produced it. Did the user hit an error first? Did they miss an existing control? Did three people on the same account repeat the behavior? This context changes prioritization.
Promote patterns, not anecdotes
Keep the anecdote, but promote the pattern. A good roadmap note says: Six trial teams asked for export after building their first report; four had already shared a dashboard link; two were blocked by compliance. That is evidence a team can act on.