# Prioritization: 5 methods and how to pick the right one

https://salesbond.app/blog/prioritization-owner-sales-manager/
Published: 2026-11-07 · Updated: 2026-11-14

Prioritization is the process of ranking tasks, projects or decisions by importance, urgency and return, so that limited time and money go to what matters most. For an owner or a head of sales the ranking itself is rarely the hard part. The hard part is choosing a method that fits the thing you are ranking (a day of tasks, a quarter of projects, a pipeline of deals) and then coming back to the list often enough that it stays true.

## Quick answer

Name the object first, then pick the method. For your own day: the Eisenhower matrix or an Ivy Lee list. For projects that compete for the same two people: value versus effort, or RICE if real money is on the line. For a scope you have to cut: MoSCoW.

For deals and customers, rank on CRM data with a weighted score and let that ranking rebuild itself every morning.

Whatever you choose, keep one list per object and one person who owns the decision, because two lists for the same deals, kept by two people, turn priority into an argument.

## First decide what you are ranking

When an owner tells us “we need to prioritize”, it usually means one of four different things. The method depends on which.

Tasks are what one person does today and this week. The horizon is hours to days, the list changes daily, and it lives in a to-do app or a calendar. Projects are the hiring plan, the new pricing page, the CRM migration: weeks to months, and they compete for the same two or three people who also have to sell. Deals are the open opportunities in the pipeline, and the market rewrites that list without asking you. A buyer goes quiet, a close date moves, a competitor shows up. Customers are the accounts you already have, and the question there is not “who is biggest” but “whose next order is due”.

Each of these has a different half-life and a different data source. Tasks and projects live in your head or in a planning tool, so a method based on judgement works. Deals and customers live in the CRM, which already holds the amount, the stage, the expected close date, the last activity and the days since the last purchase. Ranking those by gut feel throws away data you have already paid your reps to enter.

This is also why prioritization is a skill you build over time. The people who get better at it are the ones who learn to tell the objects apart and stop forcing one tool on all four.

The common mistake is to take a framework built for a product backlog and apply it to sixty open deals, where it lasts a few weeks until nobody updates the scores. Tasks have their own trap when they keep growing to fill the week, and [Parkinson’s law for a sales team](https://salesbond.app/blog/parkinsons-law-sales-team-deadlines-owner-guide/) shows how to set deadlines that hold.

## Five methods, and where each one breaks

The same five methods show up in nearly every guide. The definitions are easy, and the useful part is what each one is built for and where it stops working.

The Eisenhower matrix puts every item into one of four quadrants by urgency and importance: do, schedule, delegate, eliminate ( [Deckary](https://deckary.com/blog/how-to-prioritize-tasks); [Slack](https://slack.com/blog/productivity/best-methods-for-prioritizing-tasks-and-projects-at-work) describes the same grid). It is built for your own day and week. It is fast because it trades precision for speed, telling you which pile an item belongs to and nothing about the order inside it. Our guide to the [Eisenhower matrix for a small business owner](https://salesbond.app/blog/eisenhower-matrix-small-business-owner-delegate-sales-team/) walks through it, including what to do with the delegate quadrant.

MoSCoW sorts items into Must, Should, Could and Won’t ( [Slack](https://slack.com/blog/productivity/best-methods-for-prioritizing-tasks-and-projects-at-work)). Use it when you have to cut a scope, a project or a quarter plan, and the conversation is about what is in and what is out. In practice it does not rank items inside a bucket, and it does not deal with urgency at all ( [Deckary](https://deckary.com/blog/how-to-prioritize-tasks)). Twenty “Should” items and no way to pick the first one is a common place to end up.

RICE gives each item a score: (reach × impact × confidence) ÷ effort ( [Slack](https://slack.com/blog/productivity/best-methods-for-prioritizing-tasks-and-projects-at-work)). It is good for initiatives that compete for budget, where you need a number to end the meeting. It is slow: Deckary puts scoring 30 items on RICE at 60 to 90 minutes, against about five minutes for an Eisenhower sort of the same list ( [Deckary](https://deckary.com/blog/how-to-prioritize-tasks)). Nobody does that every morning.

Value versus effort is a 2×2 that separates quick wins from time sinks ( [Slack](https://slack.com/blog/productivity/best-methods-for-prioritizing-tasks-and-projects-at-work)). It fits a project list in a small team, on a whiteboard. In our experience the scores are opinions unless “value” is defined in money, and then the loudest person in the room sets them.

With Ivy Lee, each evening you write down the six most important tasks for tomorrow, rank them, and work them in order ( [Slack](https://slack.com/blog/productivity/best-methods-for-prioritizing-tasks-and-projects-at-work)). Right for a rep’s day, or yours. It caps the list at six but says nothing about which six.

A few relatives are worth knowing by name. Asana describes the process as four steps: make a task list, choose a method, schedule the tasks in a calendar, communicate progress to the team. It also covers ABCDE, where tasks get grades from A to E, and MIT, where you pick one to three “most important tasks” for the day ( [Asana](https://asana.com/resources/how-prioritize-tasks-work)). Both are the Ivy Lee idea with a different cap. Time-blocking is the execution layer that comes after a ranking method ( [Deckary](https://deckary.com/blog/how-to-prioritize-tasks)), and teams that use it as the ranking end up with a full calendar of the wrong work; [time blocking for an owner or sales manager](https://salesbond.app/blog/time-blocking-owner-sales-manager/) shows how to place the blocks once the order is set.

Our position: the choice between these matters less than people think, and the ownership matters more. A mediocre method with one owner who re-ranks every week beats a perfect formula that three people argue about.

## Choosing a method in a minute

To prioritize work projects, rank them by value against effort and re-rank once a month; switch to RICE only when two projects fight over the same budget. Everything else follows from three questions. We ask them in order and stop at the first that gives an answer.

What is the object? If it is your own time, you are in Eisenhower or Ivy Lee territory and you can stop reading guides. If it is projects, go to the next question. If it is deals or customers, skip to the [sales section below](#deals-and-customers-let-the-data-rank-them); none of the five methods above is built for a list that changes daily.

How often does the list change? A project list that moves once a month can afford RICE, because you score it once and live with it. A list that moves weekly needs something you can redo in ten minutes, which is value versus effort on a whiteboard. If you find yourself re-scoring RICE every Monday, the method is too expensive for the object.

Can you measure what you are ranking? MoSCoW and Eisenhower run on judgement, which is fine for things with no numbers. If each item has a number attached (a deal amount, a reorder date, a cost), use a method that takes the number, or build your own weighted score instead of pretending a quadrant is precise.

![Decision tree that starts with what you are ranking and ends in a method: Eisenhower or Ivy Lee, RICE, value vs effort, MoSCoW, or a weighted CRM score](https://salesbond.app/wp-content/uploads/2026/11/prioritization-owner-sales-manager-2.png)

Planning is a separate step. Prioritization decides the order, and planning then decides the dates and the people. Asana’s sequence shows the split, with the list and the method first and the calendar after. Most teams that say they “can’t plan” actually have an order nobody agreed on.

Then the rule that outlives any method: one list per object, one owner of the decision. The owner does not have to do the work. The owner decides the order, and everyone else takes any disagreement to the owner.

## Where priorities go wrong

The failures we see are rarely about picking the wrong framework. They are about what people do around it. Deckary’s guide puts it bluntly: most professionals don’t have a prioritization problem, they have a bias problem, and it names recency bias and urgency bias first ( [Deckary](https://deckary.com/blog/how-to-prioritize-tasks)).

Urgency wins by default. The inbox is loud, the pipeline is quiet, so the day goes to whoever emailed last. The whole point of a second axis, importance, is to give the quiet thing a chance to be first. If your top three items this morning all arrived in the last twenty-four hours you are ranking by noise.

The most recent event feels like the biggest. A buyer who replied this morning jumps ahead of a larger deal whose buyer went silent two weeks ago, even though the silent one is the one at risk. The fix is mechanical. Rebuild the list from CRM data, where the silence shows up as a number of days.

One formula for everything. A team that loved RICE for the roadmap tries it on the daily queue, and within a month nobody has updated a score. Match the weight of the method to how often the object moves.

Two lists, two owners. The owner keeps a list of “strategic” deals, the head of sales keeps the pipeline, the rep keeps a third in thier head. Each one is defensible on its own. Together they guarantee that the top item on one list is nobody’s job on another.

And the quiet one: you rank once, then work a stale list. Look for items in your top five that were in the top five a month ago and have not moved. Either they were never that important, or they are blocked and the block is the real priority.

## Deals and customers: let the data rank them

For a sales team the object changes every day, and the data to rank it already sits in the CRM. Amount, stage, expected close date, last activity, next activity, days since the last purchase. That is enough to score every open deal and every account on one scale and put the reason next to each line. A whiteboard 2×2 cannot do that for sixty deals, and a manager’s memory cannot either.

How to build that weighted score, and what to do with the deals that land in the “drop” quadrant, is in our guide to the [prioritization matrix for sales deals, leads and customers](https://salesbond.app/blog/prioritization-matrix-for-sales-deals-leads-customers/). How a rep turns the ranked list into a morning queue with a stake written next to each item is in [task prioritization for sales reps](https://salesbond.app/blog/task-prioritization-sales-reps/). Teams on Pipedrive can start from the [deal priority criteria we use with Pipedrive scores](https://salesbond.app/blog/pipedrive-scores-deal-priority-criteria/).

Can you use the Eisenhower matrix for deals? For a handful, on a whiteboard, for one meeting, yes. For a full pipeline it sorts deals into piles with no order inside them, and twenty deals in “do” leave the rep where they started. Keep the matrix for the conversation about why the score says what it says. Its “delegate” quadrant is the one managers skip, and in sales it is the most valuable one: which deals and tasks a head of sales should hand off, and how the CRM owner field makes that stick, is a separate article on [delegation for the sales manager](https://salesbond.app/blog/delegation-sales-manager/).

How often to re-rank? Our view is every working day, automatically. The inputs (last activity, close date, the age of the stage) change daily, so a ranking from last week is already a guess. The manager’s job is to read the top of the list and check the reasons behind it.

A disclosure, since this is where the article meets what we build. We build SalesBond, a sales management layer on top of the CRM a team already uses. The part that does this ranking is Sales GPS: it takes Deal Health scores and violations and Repeat Sales statuses, ranks deals and customers by importance and urgency, and writes the reason next to every priority and recommended step. The limit is the obvious one. It ranks what is in the CRM, so if close dates are fiction and half the deals have no next activity, the ranking inherits that. That is why we start new teams with the free CRM audit: SalesBond reads the last 30 days of the connected CRM and sends a PDF report with money at risk, deal health, the pipeline bottleneck and what to fix, and seven days later a second PDF shows what changed. [Check your CRM with SalesBond](https://salesbond.app/) and you will see, before you rank anything, whether the data is ready to be ranked.

This week, write down the four objects you rank (your day, your projects, the pipeline, the customer base) and put one name next to each. The name owns the order. Then pick the method for each one using the three questions above, and check the the list again in a week to see what actually moved.
