How would you gather and prioritize feedback for an internal reporting tool?

Instruction: Answer this directly as a Product Manager candidate. Keep it practical, concrete, and grounded in real product work.

Context: Tests core PM fundamentals. Strong answers should be practical, concise, and grounded in real product work.

Updated

Example Answer

For an internal reporting tool, I would gather feedback from three places at once: what users say, what users do, and where the workflow breaks. That means short interviews with frequent and occasional users, intended users who avoid the tool or cannot complete their task, usage data on which reports or filters actually matter, and observation of how people are working around the tool today.

I would include different roles and accessibility needs, and record who is missing from the research. A small interview sample explains experiences; it does not by itself estimate how common a problem is.

I would then group feedback into themes and prioritize based on workflow importance, time saved, error reduction, and how broadly the problem is felt across the organization. Internal users usually have strong opinions, so I would make the prioritization logic visible and show which issues are being addressed now versus later.

Why this works

  • It uses multiple evidence sources instead of relying only on stated feedback.
  • It prioritizes according to workflow value and operational impact.
  • It shows transparent stakeholder management.

Related Questions