You always have choices. The single guiding light is the one metric the business cares about — usually revenue or engagement. Prioritize what moves that metric most.
Prioritization is the bread and butter of product management. You will always have multiple important things to do but limited time and resources. The trap is to try to do everything at once and end up doing none well.
Your actual job is to decide what to do first — and to do it calmly, rationally, and in alignment with your company’s core metric. That metric is your North Star. It could be revenue, engagement, retention, or another business goal. Everything else is downstream.
This lesson teaches you how to prioritize when two crucial tasks compete for your attention.
The context: prioritization is always about trade-offs
You will hear questions like: How do you prioritize product development when you have two important things to do but can only do one? The recruiter wants to see how you cope under pressure, think clearly, and apply your knowledge to real trade-offs.
The pattern is consistent: prioritization is about trade-offs between urgency, impact, effort, and strategic alignment.
Vaibhav Shrivastava put it clearly in a session: "You always have choices. The single guiding light is the one metric the business cares about — typically revenue or engagement. Prioritize what moves that metric most."
If you cannot answer that, you are not ready to prioritize.
Frameworks are your decision-making compass
Many PMs get stuck because they don’t have a structured way to compare priorities. Here are frameworks you should know and mention in interviews:
1. RICE
RICE stands for Reach, Impact, Confidence, and Effort.
- Reach: How many users/customers will this impact in a given time period?
- Impact: How much will it move the key metric for those users? (e.g., 3x, 2x, 0.5x)
- Confidence: How confident are you in the estimates? (0-100%)
- Effort: How many person-months or story points will it take?
Calculate a RICE score:
RICE = (Reach × Impact × Confidence) / Effort
Prioritize the highest RICE score first.
2. MoSCoW
MoSCoW categorizes features into:
- Must have: Essential for launch or survival.
- Should have: Important but not critical.
- Could have: Nice to have if time permits.
- Won’t have: Not in this cycle.
This is useful when you face scope cuts or time crunches.
3. Kano Model
Kano divides features into:
- Basic needs: Must be present or users are dissatisfied.
- Performance needs: More is better; directly impacts satisfaction.
- Delighters: Unexpected features that delight but are not expected.
Prioritize basic needs first, then performance, then delighters.
4. Weighted Scoring
Assign weights to criteria important to your business — e.g., business impact, customer satisfaction, technical risk, time to market. Score each feature against these and calculate weighted totals.
This helps balance competing factors systematically.
Sprint planning meeting at a Series A SaaS startup in Bangalore
You (PM): “We have two critical tasks: redesigning the onboarding flow and fixing payment gateway bugs. Both are important, but we can only do one this sprint.”
Engineering Lead: “Payment bugs are urgent; they cause failures for 5% of users.”
Growth Lead: “Onboarding redesign could increase activation by 10%, impacting revenue.”
You (PM): “Let's score both using RICE: payment bug fix reaches 5% users, high impact on retention, high confidence, low effort. Onboarding redesign reaches 100% new users, medium impact, medium confidence, medium effort. Payment fix scores higher, so we prioritize that.”
Product Designer: “Makes sense. We can revisit onboarding next sprint with more data.”
Balancing urgent technical fixes against growth opportunities
What factors to weigh when prioritizing
When deciding between two important tasks, consider:
- Urgency: Is there a critical deadline? Are customers blocked?
- Business impact: Which task moves the key metric more?
- Customer delight: Which one improves the user experience significantly?
- Return on investment (ROI): Effort vs value delivered.
- Time to complete: Can this be done quickly to unblock other work?
Vaibhav said it plainly: “You want your tasks to be in the top-left quadrant — least effort and most benefit. But we don’t live in an ideal world. So keep tasks in the ‘yellow’ and ‘green’ zones of impact vs effort. If a task is high effort and low benefit, avoid it.”
How to communicate your prioritization decision
Prioritization is not just about what you choose — it’s about how you communicate it.
- Be transparent about trade-offs. Explain what you deprioritized and why.
- Back your decision with data or assumptions. Show how you weighed urgency, impact, and effort.
- Manage stakeholder expectations. Let them know when their requests will be revisited.
- Keep focus on the North Star metric. Align your decision with business goals.
Role-play: Prioritizing conflicting requests
Scenario: You are a PM at a mobile e-commerce startup in Mumbai. The marketing team wants a personalized recommendation engine to boost sales. The engineering team wants to refactor the payment gateway to reduce failures. Customer support reports many complaints about missing real-time order tracking.
Your task: Decide which feature to prioritize for the next release.
Product leadership sync, Mumbai startup
Marketing Lead: “The recommendation engine will increase sales by 15%, according to our models.”
Engineering Lead: “Payment gateway refactor will reduce failure rate from 3% to 0.5%, improving retention.”
Customer Support: “Order tracking complaints are up 40%, hurting NPS scores.”
You (PM): “Let’s gather data on impact and effort for each. Then we’ll score them on business impact, customer satisfaction, technical risk, and time to implement.”
Balancing growth, stability, and customer experience
- List the three features: recommendation engine, payment refactor, order tracking.
- Define criteria: business impact, customer satisfaction, technical risk, time to implement.
- Assign weights to criteria (e.g., business impact = 5, customer satisfaction = 4, etc).
- Score each feature against each criterion (1-10).
- Calculate weighted totals.
- Decide which feature to prioritize based on scores.
- Write a short paragraph justifying your decision for stakeholders.
The trap of indecision and trying to do both
The biggest mistake is trying to do everything at once. This leads to:
- Diluted focus
- Missed deadlines
- Frustrated stakeholders
- Lowered team morale
Vaibhav warned: “Most new PMs try to do all important tasks simultaneously and end up doing none well. They optimize for responsiveness, not for clear calls. By week three, the team is behind, and no one knows what’s done.”
Make a call. Prioritize ruthlessly. Communicate clearly.
Test yourself: The prioritization dilemma
You are a PM at a Series B fintech company in Bangalore. The CEO wants a new dashboard for the board meeting in two weeks. The sales lead wants you on a key client call this Thursday. The engineering lead needs specs for an auth migration blocking sprint planning. You have five working days.
The call: What do you prioritize first, and how do you communicate your choice to the CEO, sales, and engineering?
Your reasoning:
You are a PM at a Series B fintech company in Bangalore. The CEO wants a new dashboard for the board meeting in two weeks. The sales lead wants you on a key client call this Thursday. The engineering lead needs specs for an auth migration blocking sprint planning. You have five working days.
Your task: What do you prioritize first, and how do you communicate your choice to the CEO, sales, and engineering?
your reasoning:
Where to go next
- If you want to master decision-making under conflicting priorities: Mastering Trade-offs
- If you want to learn prioritization frameworks in depth: Prioritization Frameworks
- If you want to improve stakeholder communication: Stakeholder Management
- If you want to practice product sense with real scenarios: Product Sense Practice