Dell PM: One Prioritization System for Bugs, Roadmap, Engineering and Executive Asks

You are a product manager at Dell. Work reaches your team from four directions: requests from the engineering team itself (such as technical debt or tooling), product bugs, the planned product roadmap, and suggestions from leadership. How do you decide what the team works on? ```hint Compare unlike work on common terms A bug fix, a refactoring request and an executive's idea are hard to rank against each other directly. Think about what each one costs, what it is worth, and what happens if it waits. ``` ### Clarifying Questions - What is the product's main goal right now: growing new business, keeping existing customers, or running a mature product reliably? - Do customers of this product have support commitments that set deadlines for fixing defects? - How much of the team's time does unplanned work such as bug fixing take today? - Do leadership suggestions arrive with a business reason and a deadline, or as open ideas? ### What a Strong Answer Covers - Business goals as the anchor that every source of work is judged against - A distinct path for urgent defects versus planned work - A consistent way to compare roadmap items, engineering requests and leadership asks - Handling leadership input with transparency about trade-offs, including pushing back - Communication, review cadence, and how to tell whether the process is working ### Follow-up Questions - A senior executive wants a feature that would delay a release you committed to a major customer. What do you do? - Engineers say technical debt slows every release, but they cannot quantify it. How much time do you give it? - The bug backlog keeps growing even though the team fixes bugs every sprint. What would you change?