When multiple teams are using the thing, talking to at least one developer on each of those teams is going to surface things you won't find out anywhere else.

When multiple teams are using the thing, talking to at least one developer on each of those teams is going to surface things you won't find out anywhere else. I agree that an individual user shouldn't be driving roadmap stuff directly, but getting their perspective, pet peeves, war stories etc. is still valuable advisory input to the overall process.