How would you prioritize feature requests for an internal 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 tool, I would not prioritize requests by who asks loudest. I would look at how often the problem happens, how much time or risk it creates, how many teams are affected, and whether the request unblocks a critical workflow. Internal products succeed when they remove friction from important work, so the business context matters as much as the feature itself.

I would also review feasibility with engineering and watch for opportunities to solve a pattern rather than a one-off complaint. If two requests are close in value, I would usually favor the one that improves a core workflow for more users or reduces operational risk, then communicate clearly why lower-priority items are waiting.

Why this works

  • It shows prioritization discipline instead of defaulting to stakeholder urgency.
  • It uses the right criteria for internal tools: time saved, workflow impact, and risk.
  • It demonstrates clear tradeoff thinking and communication.

Related Questions