# How to Prioritise Your Workload When Everything Feels Urgent Canonical URL: https://headwayskills.com/knowledge/time-management/prioritise-workload/ Markdown URL: https://headwayskills.com/knowledge/time-management/prioritise-workload.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving time management at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer How to prioritise your workload when everything feels urgent: five kinds of method, how to pick one that fits your list, and the two steps most guides skip. ## Key facts - Title: How to Prioritise Your Workload When Everything Feels Urgent - Category: Time Management - Primary skill: Time Management - Related skills: Working with Your Manager, Building Resilience - Primary keyword: prioritise workload - Source page: https://headwayskills.com/knowledge/time-management/prioritise-workload/ ## What this page covers - How to prioritise your workload when everything feels urgent: five kinds of method, how to pick one that fits your list, and the two steps most guides skip. - Practical guidance for prioritise workload - How this topic connects to Time Management ## Detailed explanation There is a particular kind of stuck that comes from having eleven things to do and no defensible reason to do any one of them first. To prioritise workload, put every task into one list, then sort it by importance rather than urgency, using a method sized to the list: a daily ordering method for fewer than ten items, a two-axis matrix for ten to thirty, a scoring framework beyond that. Then agree on the order with whoever owns the deadlines. Everyone who asked seems to need theirs today, which is why that last part — not the sorting — is where most advice stops and most of the difficulty starts. ## Why everything on your list feels urgent Urgent work demands immediate action — a deadline, a crisis, someone standing at your desk. Important work moves something that matters over a longer horizon, and it almost never announces itself. The two get confused because only one of them makes noise. The pages written for this exact feeling — Upskillist and Leantime among them — keep landing on the same mechanism to explain why a full day can end with the important work untouched: completion bias, the pull toward finishing small, closable tasks because closing them feels good, regardless of what they are worth. Twelve items ticked off, and the thing that actually needed thinking about is still sitting there. Worth saying plainly: a lot of "everything is urgent" is perception, not fact. Requests arrive wearing the same face because most of them come with no real date attached. Sorting that out is the first thing every method below is doing for you. ## The five kinds of method for prioritising your workload The named frameworks are not a dozen competing versions of the same thing. They divide into distinct kinds by the job they do — one comparison of the field groups them as daily tools, planning tools and scope tools — which means choosing the wrong kind feels like being bad at this, when it is really a mismatch between instrument and problem. ### Daily ordering methods The Ivy Lee method: six tasks, worked strictly in order, no jumping ahead. The 1-3-5 rule: one big thing, three medium, five small. ABCDE: letter-rank everything, A for must-do down to E for eliminate. MIT: name the single most important task and protect it. What these share is that they produce a sequence rather than a judgment about value. They answer "what next," not "what matters," and they only work while the list is short enough to hold in your head. ### Two-axis matrix methods The [Eisenhower matrix](/knowledge/time-management/eisenhower-time-management/) crosses urgency with importance and gives you four quadrants: Do, Schedule, Delegate, Eliminate. Impact/Effort crosses value against cost and surfaces the quick wins. This is the only kind of method that separates the two things you have been conflating, and the only one whose output includes an explicit "not this." That Eliminate quadrant does more work than it looks like: most overloaded lists contain things nobody would miss, and no daily ordering method will ever tell you that. ### Scoring frameworks RICE rates each item on Reach, Impact, Confidence and Effort, then ranks by the score. ICE and WSJF work the same way with different factors. These trade time for defensibility. Rating thirty items on four dimensions is slow, and it pays off only when the list is long and the ranking has to survive someone else questioning it. ### Scope-negotiation methods MoSCoW sorts commitments into Must-have, Should-have, Could-have and Won't-have. It comes from project planning and Agile sprints rather than personal productivity. It is the odd one out, and the most useful one for the problem this article is actually about, because its output is a shared agreement rather than a private plan. The Won't-have column exists precisely so that dropping something is a decision made with other people, on the record — not a quiet omission you hope nobody notices. ### Energy-sequencing methods Eat the Frog puts the hardest or most-avoided task first thing in the day. The related advice is to take on high-effort work while your energy is highest, and to run one task at a time rather than several in parallel. Here the criterion is your own state, not the task's value — which makes this the category that addresses [avoidance](/knowledge/time-management/procrastination/) rather than ranking error, for when you already know what matters and keep not starting it. ## Choosing one that fits your list There is a usable selection rule, and it sits in framework-comparison pages rather than the tip lists that rank highest: under ten items, use a daily method; ten to thirty, use a matrix; thirty or more, use a scoring framework. Most people who conclude that "prioritization doesn't work for me" have been running a matrix on a six-item day, or eyeballing a sixty-item backlog. Two cautions. As the Management Center and Teamwork both put it, this works as a habit rather than a reaction — prioritizing only when you are already drowning gives you a triage order, not a considered one. And notice who publishes most of the guides you will find: Asana, Personio, Teamwork, Birdview, monday.com. They are work-management vendors, and their articles reliably end at tool adoption. Software is fine for storing an order; it will not produce one. ## The half of the job that happens before the list Every dominant guide starts from a finished master list — Asana's first step is a to-do list covering the full scope of your workload — and treats that list as a fixed input. It isn't. The list is where the workload became unmanageable in the first place, and nothing downstream of it can undo that. So when work arrives, settle four things before accepting it. Who is actually asking — the person in front of you, or someone behind them. What exactly is being asked for. When it is genuinely due, as a real date, because "ASAP" is not a deadline and everyone says it. And what "done" looks like, in terms specific enough that you would both recognize it. Write your understanding down, send it back, and estimate the time with a buffer rather than at your most optimistic. A surprising share of urgent items quietly stop being urgent at the third question. The other half of intake is [declining](/knowledge/time-management/how-to-say-no-at-work/). Once you have some credibility, a clear no with a reason attached is an ordinary professional move, not an act of rebellion — you are not permitted to, you cannot within the time, you would have to drop something already promised, or someone else is better placed. Said plainly and early, it costs far less than the same conversation held late. ## When the ranked list still doesn't fit Sometimes the ranking is right and the work still does not fit the hours. Here the most-recommended framework on the internet quietly fails you: a full quarter of the Eisenhower matrix is the Delegate quadrant, which presumes authority that most people early in a career do not have. The guides do not mention this. The move available without authority is not delegation but renegotiation. Take the ranked list to whoever owns the deadlines, show the trade-off, and propose an order — including what slips and by how long. That converts "I can't do all of this," which lands as a complaint, into a specific proposal someone can approve or adjust in thirty seconds. It is [routine expectation-setting](/knowledge/working-with-your-manager/how-to-align-expectations-with-your-manager/), not pushing back, and far easier to have before something slips than after. For a lot of people the ranking was never the hard part; that conversation is. If it is the half you would rather avoid, a [read on your work skills](https://assessment.headwayskills.com/) will tell you whether what is missing is a method or the willingness to ask — and either way it is learnable rather than fixed. A useful side effect: being able to name your method and the criteria behind it is what a good answer sounds like when an interviewer asks the question Indeed UK ranks a whole guide for — "How do you prioritise your work?" ## What makes this get easier Notice how little of the difficulty was arithmetic. Sorting a list is the easy half. What decides whether your week works is what you agree to take on, what you say when the plan breaks, and how steady you stay while requests keep arriving. **Time Management** is the skill this whole topic lives inside, and it covers considerably more than ranking. It includes taking work in properly — the four things to pin down before you say yes — and saying no once you have earned the standing to. It includes the mechanics that stop a list from growing: doing two-minute tasks immediately, breaking big ones into pieces, spending attention where the value is concentrated. And it includes deciding in advance when your day ends, which is part of the skill rather than a reward for finishing. **Working with Your Manager** turns your private ranking into a shared decision. A prepared one-on-one every week or two, a proposed order rather than a list of problems, visible results, and an explicit agreement about what you are authorized to decide alone — that is ordinary partnership maintenance, not confrontation. Managers overwhelmingly want to hear about a slipping deadline while it can still be moved. **Building Resilience** is what makes any of this usable. "Everything is urgent" is a thought before it is a fact, and usually one of a few recognizable patterns: all-or-nothing thinking, mind-reading what a requester expects, running the worst case on a missed deadline. The circle of control is the corrective — you cannot control how much arrives, only how you rank it and what you say about it. Quieting the felt emergency enough to think is what turns a method into a plan rather than another thing to fail at. None of the three is a trait you either have or don't; they are behaviors, which means a gap is just something not learned yet. The **free Job Skills Test** covers **twelve such skills**, these three among them, so it is a fast way to see [where these three stand](https://assessment.headwayskills.com/) instead of guessing which one is doing the damage. Some of this may already describe how you work — an instinct to ask when something is really needed, or a habit of checking what "finished" means before starting. The parts that do not come naturally yet are learnable, and you can build them without becoming a different kind of colleague; what changes is what you do when the fourth request lands, not who you are. It also counts for more later rather than less: the more people depend on your output, the more your ordering decisions become their problem too, which is an argument for building the habit while the stakes are still small. You read past the list of frameworks to the part about the conversation — the half most people skip, and the half that actually changes a week. ## Somewhere to start You know what a good ordering process looks like now. The open question is which part of it is weak for you specifically — the method, the intake, or the conversation. If you want somewhere to start, the **free** Job Skills Test is a 7-minute self-assessment of your work skills. It shows you where you stand across all twelve, including the time management, manager and resilience habits this all runs on, and points at the one or two that would make the biggest difference to you right now. Nothing to commit to afterwards; it is just an honest read, and you can take it with today's to-do list still open in the next tab. **[Take the test](https://assessment.headwayskills.com/)** *Free, and about seven minutes of your time.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? How to prioritise your workload when everything feels urgent: five kinds of method, how to pick one that fits your list, and the two steps most guides skip. ### Which Headway skill does this connect to? This guide connects primarily to Time Management. It also relates to Working with Your Manager, Building Resilience. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/time-management.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/resilience.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/time-management/prioritise-workload/ Preferred summary: "How to prioritise your workload when everything feels urgent: five kinds of method, how to pick one that fits your list, and the two steps most guides skip." ## Change log - 2026-07-07: Content collection version published.