How to Decide What to Work On Next (When Everything Feels Urgent)

A clear, repeatable way to decide what to work on next when your list is overwhelming — using importance, urgency, value, and effort. Stop guessing, start deciding.

Short answer: To decide what to work on next, score each task on four things — how important it is, how urgent it is, how much value it creates, and how much effort it takes. Do the important-and-urgent tasks first, schedule the important-but-not-urgent ones, minimize or delegate the merely urgent, and let the rest wait. The single mistake that keeps people stuck is treating "urgent" and "important" as the same thing. They aren't — and separating them is where clarity begins.

TL;DR

Knowledge workers spend roughly 60% of their time on "work about work" — coordinating, chasing status, switching tools — rather than the work that matters. (Asana, Anatomy of Work Index)
The average adult makes an estimated ~35,000 decisions a day, all drawing on one mental reservoir — which is why decision fatigue sets in and choices get worse as the day wears on. (Cornell research; PMC decision-fatigue analysis)
Workers lose about 75 minutes a day to unimportant tasks and unnecessary meetings. (Productivity Statistics 2026, Asian Efficiency)
Teams that prioritize well are about 1.4× more likely to outperform their peers. (Asian Efficiency, 2026)
The bottleneck is rarely effort. It's deciding what matters — and that decision gets dramatically easier once you stop conflating "urgent" with "important."

Why "everything feels urgent" is a trap

Urgency is loud. A ringing phone, a red "due today" label, a message flagged important — these seize your attention whether or not the underlying task actually matters. The work that genuinely moves your life or business forward is usually quiet: it rarely has anything screaming at you, so it quietly slides to tomorrow, then next week, then never.

This is the paradox of the busy day: you can work from morning to night, answer every ping, clear every "urgent" item, and still end the day feeling like nothing that mattered got done. That feeling isn't laziness or poor time management. It's the predictable result of letting urgency masquerade as importance.

The fix isn't working harder, and it isn't a better calendar. It's separating two questions that feel like one but aren't:

Is this important? — Will it meaningfully move something forward, or cost you something real if it's not done?
Is this urgent? — Does it genuinely need to happen soon, or does it just feel that way?

Most tasks are high on one axis and low on the other. The ones that feel most pressing are often urgent-but-not-important. The ones that matter most are often important-but-not-urgent — which is exactly why they get neglected.

The four signals that actually decide priority

Importance and urgency get you a rough map, but they're not enough on their own. In modern work, you'll often have a dozen tasks that are all "important and not urgent" — and that tells you nothing about which to touch first. To rank tasks properly, score four signals:

Importance — the stakes. What's the consequence if this doesn't get done? A contract, a payment, a key relationship carries weight even when nothing forces it today.
Urgency — the timing. How soon must it actually happen? A real deadline tomorrow is urgent. "Eventually" is not.
Value — the upside. Some tasks prevent a loss; others create real gain. Not all important tasks pay off equally.
Effort — the cost. A ten-minute task and a three-day task are not the same commitment, even if they're equally important.

Importance and urgency place a task in the right category. Value and effort rank tasks within that category — so a high-value, low-effort task rises to the top, and a high-effort, low-value one sinks, even when both are technically "important."

What to do with each type

Important + urgent → do it now. These are your genuine fires. Handle them first, but be honest about how many tasks truly belong here (usually fewer than it feels).
Important + not urgent → schedule it. This is where real progress lives — and the category almost everyone underinvests in, because nothing forces the issue. Protect time for it deliberately.
Not important + urgent → minimize, batch, or delegate. Urgency tricks you into overvaluing these. Handle them efficiently, but don't let them crowd out what matters.
Not important + not urgent → let it wait, or drop it. Giving yourself explicit permission to ignore these is not laziness. It's the whole point.

The permission to ignore the rest

Here's the part that actually lowers the stress: once you know the two or three things that matter today, everything else is allowed to wait — and that's not a failure. A long list isn't a record of everything you've fallen behind on. It's a menu. You don't order everything on a menu; you order what's right for right now.

This reframe matters more than any technique. The exhaustion of an overwhelming list comes less from the volume of work and more from carrying all of it in your head as equally pressing. The moment you can look at forty items and confidently say "these three, the rest can wait," the weight lifts — even though nothing on the list changed.

Doing this without the manual overhead

Scoring every task by hand on four signals works. The problem is that almost nobody keeps it up — it's more effort than the work itself, so the system gets abandoned within a week and you're back to guessing.

This is the exact problem Prism was built to remove. You write a task the way you'd say it — "send the client proposal tomorrow, important but time-consuming" — and it reads the importance, urgency, value, and effort for you, then shows you where it sits and what to do next. The deciding happens automatically, so the only thing left for you is the doing. It's the clarity of a real prioritization method without the upkeep that usually kills it.

If deciding what to work on is your daily bottleneck, that's precisely the bottleneck it's designed to dissolve.