How to Prioritize Tasks at Work When Everything Is Urgent

To prioritize tasks at work, do three things in order. Get every task onto one list, including the ones living in your inbox and in chat. Pick the two or three that matter most this week, judged by what your team is trying to achieve. Then rank everything else by urgency, meaning how soon it has to happen before the chance or the cost changes. When everything still looks urgent, the list becomes a conversation with your manager rather than a problem you solve alone: you show the ranking and ask which items can move. The rest of this guide takes each step in turn, then adds two quick tools and a weekly habit.

1. Get everything onto one list

You cannot rank what you cannot see. Spend fifteen minutes collecting every open commitment into one place: tasks you wrote down, emails you flagged, requests someone made in a meeting, and the thing you promised in a hallway. One line each, starting with a verb, so “Q3 report” becomes “Draft the Q3 report for Maria.”

• Include the recurring work. The weekly report takes time every week whether or not it is on a list.
• Split anything that is really three tasks. “Launch the new pricing page” hides copy, design, legal review and the release itself.
• Delete on the way. Anything nobody has asked about in three months is a candidate to close, with a line saying why.

A single list is enough for one person. If other people add to it and need to see where things stand, it is time to move it onto a board; kanban board vs to-do list covers when that happens.

2. Pick the few that matter

Before ranking anything, pick the two or three tasks that most move your team’s goal for this quarter. Not the loudest ones: the ones that, if they were the only things you finished this week, would still make it a good week. If you do not know your team’s goal, that is the first question for your manager, and it is worth asking even when you think you know.

These few get protected time. Block it on your calendar before the week fills up; time blocking shows how. Everything else competes for what is left.

3. Rank the rest by urgency

Urgency is how soon something must be done before the cost of waiting changes: a customer who cannot log in, a contract that expires Wednesday, a colleague blocked on your answer. Ask of each task, “What happens if this waits a week?” If the honest answer is “nothing much,” it is not urgent, however it was phrased when it arrived. If you want to separate urgent from important more formally, the Eisenhower matrix sorts tasks into four boxes on exactly those two questions.

Impact vs effort, for ties

When two tasks are equally urgent, compare what each is worth against what it costs. A rough guess of each on a scale of low to high is enough; the point is the comparison, not the numbers.

              LOW EFFORT            HIGH EFFORT
HIGH IMPACT   Quick wins:           Big bets:
              do these first        plan them, protect time
LOW IMPACT    Fill-ins:             Time sinks:
              batch them            question or drop them

Two cautions. People underestimate effort, so treat anything you rated low effort that involves another team as medium. And impact means impact on the goal you picked in step two, not on how pleased the person asking will be.

MoSCoW, in one paragraph

MoSCoW sorts the work in a fixed period into Must have, Should have, Could have and Won’t have this time. The Agile Business Consortium’s MoSCoW guidance↗ (opens in a new tab) describes Should haves as “painful to leave out” but survivable, and recommends keeping Must haves to “no more than 60% Must Have effort,” so the Could haves act as a buffer when things run late. It suits a project with a deadline and a scope to negotiate. For a personal to-do list it tends to put everything in Must.

A 1-10 priority habit

A number on each task makes the ranking visible to other people and survives past Monday. Ten levels sound like too many, but they leave room between “now” and “sometime,” which three levels do not. A habit that holds up:

• P1 to P2: this week, and no more than two or three tasks. If a fourth arrives, something already there moves down.
• P3 to P5: next in line. P5 is the default for anything you have not thought about yet.
• P6 to P10: when there is room. Most tasks live here, and that is fine.
• Re-rank rather than inflate. When a new P1 arrives, ask which current P1 it displaces, instead of making everything P1.

On fenbs every task carries this number, from 1, the most urgent, to 10, with 5 when you leave it out. The board filters by band: High is P1 to P2, Medium P3 to P5 and Low P6 to P10, so “show me the high ones” needs no argument about 2 versus 3. The number is separate from the lane, so a P1 still sitting in To Do is visibly waiting. The priority glossary entry explains why the scale runs to ten.

When everything is urgent: renegotiate, do not absorb

If the list has more P1s than you can do, the answer is not longer hours. It is a choice someone has to make, and often that someone is your manager. Scrum makes the principle explicit for backlogs: the Scrum Guide↗ (opens in a new tab) says “The Product Owner is one person, not a committee,” and ordering the backlog is part of that one person’s job. Your work needs the same thing: one person who can say which of two urgent things comes first.

So bring the ranking, not a complaint. Show what is on your list, what order you would do it in, and what will slip as a result, then ask them to change the order if they see it differently. A short message works:

I have three things due this week and time for two:
1. Q3 report for Maria (due Thursday)
2. Onboarding guide updates (the quarter's goal)
3. Vendor comparison for Sam (asked for "this week")

My plan: 1 and 2 this week, 3 next Tuesday.
Does that order match yours? If 3 has to happen this week,
which of the other two should move?

That is saying no without saying no. It gives your manager a real decision instead of a status update, and it puts the trade-off in writing. It is also normal: the Office of Personnel Management’s guidance on performance planning↗ (opens in a new tab) says plans “should be flexible so that they can be adjusted for changing program objectives and work requirements.” Priorities that never move are the unusual case.

For requests from peers, the same move works in a lighter form: “I can do this next Tuesday, or today if Maria agrees to move the Q3 report. Which do you want?” Most requests turn out to be less urgent once someone has to choose.

Re-prioritize once a week

A ranking goes stale within days. Set twenty minutes at the same time each week, Friday afternoon or Monday morning, and run the same steps:

1. Add everything new from the week to the list.
2. Close what is done, and close what no longer matters, with a line saying why.
3. Re-pick the two or three that matter most next week.
4. Re-rank the rest, and move anything that has sat at the same priority for a month either up or out.
5. Send the top of the list to your manager if it changed.

On a fenbs board the lanes do some of this for you: the few you picked go into Next Up, and only what you are actually working on goes into In Progress. Tasks you drop move to Completed and are marked Won’t fix or Obsolete, so the reason stays on record and only shipped work counts as delivered. Copy as Markdown, below the board, gives you the list as text to paste into that message to your manager. If an AI assistant is connected, ask it to propose a re-ranking with its reasons and change nothing; you decide, and the changes you make are recorded in History with your name.