Memorisely
Product Management

How to prioritise when everything feels urgent

Frameworks and habits that help product managers decide what matters most and explain the trade offs.

Zander Whitehurst

7 min read

Every product manager eventually reaches the week where everything is urgent. Sales needs a feature to close a deal. Support wants a bug fixed before the weekend. Leadership has a new strategic bet. Engineering is quietly asking for time to pay down debt. Each request sounds reasonable on its own, and together they are impossible.

Prioritisation is how you get out of that week with your roadmap, your team and your sanity intact. It is less about clever frameworks and more about making trade offs visible, so that decisions are made deliberately instead of by whoever shouts loudest.

Why everything feels urgent

Urgency usually comes from proximity, not importance. The request in front of you, from the person you spoke to this morning, feels more pressing than the problem affecting thousands of customers you have not heard from this week.

Urgency is also contagious. When one stakeholder escalates, others feel they need to escalate too, or risk being ignored. Before long every item on the list is marked as top priority, which means nothing is.

The first job of a PM is to slow this down. Not every request needs an answer today. Most need an answer that is considered, consistent and explained.

Start with a single list

Before you can prioritise, you need to see everything in one place. Requests arrive through Slack, email, meetings, sales calls and support tickets. While they are scattered, you cannot compare them.

Pull every request into one list. For each item, capture the problem it solves, who asked for it and what evidence supports it. Do not try to rank anything yet. Just get it all visible.

Each request captured with who asked and what evidence supports it, before any ranking.

This step alone often reduces the panic. Seeing twenty items side by side makes it obvious that they cannot all be done this quarter, which shifts the conversation from "when will you do this?" to "which of these matters most?".

Use RICE to compare like with like

RICE is a simple scoring model that helps you compare very different ideas on the same scale. Each item is scored on four factors:

  • Reach. How many customers will this affect in a given period?
  • Impact. How much will it change things for each of those customers?
  • Confidence. How sure are you about your reach and impact estimates?
  • Effort. How much work will it take from the team?

The score is reach multiplied by impact and confidence, divided by effort. The exact numbers matter less than the conversation they create. Scoring forces you to state your assumptions, and once assumptions are written down, people can challenge them.

Scoring very different requests on one scale turns loud opinions into assumptions you can question.

Confidence is the factor most teams underuse. An exciting idea with no evidence should score lower than a modest idea backed by research. That alone can stop a lot of roadmap drama.

Impact versus effort for quick decisions

When you need a faster view, plot items on a simple two by two grid with impact on one axis and effort on the other.

  • High impact, low effort. Quick wins. Do these soon.
  • High impact, high effort. Big bets. Plan them carefully.
  • Low impact, low effort. Fill ins. Useful when the team has spare capacity.
  • Low impact, high effort. Avoid these, however loudly they are requested.

This works brilliantly in a workshop. Put the items on sticky notes, ask stakeholders to place them together and watch the disagreements surface. When sales thinks something is high impact and support thinks it is low, you have found a conversation worth having.

Think about cost of delay

Some items are genuinely time sensitive, and RICE does not always capture that. Cost of delay asks a different question: what do we lose for every week this is not done?

A compliance change with a fixed deadline has a high cost of delay. So does a feature tied to a seasonal peak or a contract renewal. A nice improvement to settings can wait months without anyone losing anything.

Cost of delay is also the best tool for handling real urgency. When someone says something is urgent, ask what happens if it ships in six weeks instead of two. Often the honest answer is "not much", and the urgency fades. Sometimes the answer is "we lose the customer", and then you know it deserves to jump the queue.

Share a Now, Next, Later roadmap

Detailed roadmaps with dates create false promises. A Now, Next, Later roadmap communicates priority without committing to dates you cannot predict.

  1. Now is what the team is actively working on.
  2. Next is what comes once current work finishes.
  3. Later is what you believe matters but have not committed to.
Three columns make it obvious that moving something into Now pushes something else out.

This format makes trade offs visible. If a stakeholder wants something moved into Now, it is clear that something else has to move out. That makes the cost of a new request obvious without you needing to argue it.

I started using Now, Next, Later after a quarterly planning meeting where we presented a roadmap with dates for eighteen months. Within three weeks, half of those dates were wrong, and we spent the rest of the quarter explaining why. The next time, I showed three columns and no dates. The meeting took half the time, and nobody asked me to defend a deadline I had invented.

Use AI to score and challenge

AI tools are surprisingly useful for prioritisation, as long as you treat them as a sparring partner rather than a decision maker.

Try giving an AI your list of items with the context you have, then asking it to:

  • Produce a first pass RICE score for each item and explain its reasoning.
  • Identify which estimates look weakest or least supported.
  • Argue the case for the item you have ranked lowest.
  • Point out dependencies or risks you may have missed.

The value is not the score itself. It is the challenge. An AI has no favourite stakeholder and no attachment to an idea, so it will happily question assumptions your team has stopped noticing. Always check its reasoning against what you actually know about your customers and your product.

Communicate the trade offs

A good prioritisation decision can still fail if it is badly communicated. People accept being told "not now" far more readily when they understand why.

When you share priorities, explain the reasoning, not just the result. Show what was considered, what criteria you used and what was traded off. Be honest about what is not happening and when you will review it again.

A useful habit is to say the trade off out loud: "If we do this now, it means that moves to next quarter. Is that the right call?" Framed this way, stakeholders stop asking you to do more and start helping you choose. We practise exactly these conversations in our AI Product Management Bootcamp.

Saying the trade off out loud turns a demand for more into a shared choice.

Revisit regularly

Priorities are not set once a year. New evidence arrives, markets shift and customers surprise you. Review your list every few weeks, update scores where evidence has changed and move items between Now, Next and Later as needed.

The goal is not a perfect ranking. It is a team that knows what matters most right now, understands why, and can say so clearly when the next urgent request lands on Monday morning.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all