Task organising

How to prioritise tasks when everything is 'urgent'.

Three working methods (Eisenhower, MITs, deadline-first), when each fits, and the email trap that makes urgency lie.

By Mathias CelisMarch 17, 20266 min readLast updated July 2026
TL;DR

Three prioritisation methods cover most situations: the Eisenhower matrix (urgent/important) for clearing a chaotic backlog, MITs (choose 1-3 must-finish tasks each morning) for daily focus, and deadline-first sorting for deadline-dense work. The trap to avoid: letting email arrival order masquerade as priority, since the loudest thread is rarely the most important task.

"It's all urgent" is almost never a description of reality; it's a description of a sorting failure. Real urgency is scarce by definition. What most overloaded task lists actually contain is a few genuinely time-bound items, a lot of important-but-patient work, and a loud crowd of recent arrivals impersonating priorities. Three methods handle this, each fitted to a different situation.

Eisenhower: for clearing a chaotic backlog

Sort everything on two axes, urgent and important, into four quadrants. Urgent-and-important gets done now. Important-not-urgent gets scheduled, and deserves protection, because this quadrant (the strategy work, the relationship maintenance, the skill building) is where careers are actually built and where procrastination does its damage. Urgent-not-important gets delegated or shrunk. Neither gets deleted without ceremony. The matrix is heavy machinery; use it to dig out, not to run every day.

MITs: for running every day

Each morning (better: the evening before), choose one to three Most Important Tasks: the items that would make the day a success if nothing else happened. They get the first focus block, before email. The forcing function is the tiny number; a list of ten MITs is just a to-do list wearing a trench coat. Everything else happens after the MITs or doesn't, and either way the day counted.

Deadline-first: for deadline-dense work

When the work genuinely runs on dates (filings, launches, client deliverables), sort by deadline minus estimated duration and work the nearest collision. The trap here is invisible dependencies: your deadline often waits on someone else's input, which is why a waiting-for list belongs beside any deadline-driven system; the chase you send today protects the date three weeks out.

The trap underneath all three: recency

Email sorts by arrival, and recent feels urgent; a message from twenty minutes ago outshouts a deadline three days away. Prioritising directly from the inbox therefore hands the decision to whoever wrote last. The fix is structural: clarify email into a task list first (Pidgy does this pass automatically, turning a Gmail or Outlook feed into verb-first actions), then prioritise the list with whichever method fits the moment. The loudest thread stops winning, and "it's all urgent" quietly stops being true.

Frequently asked questions

What is the Eisenhower matrix?

A two-axis sort: urgent vs important. Urgent-and-important gets done now; important-not-urgent gets scheduled (this quadrant is where careers are built); urgent-not-important gets delegated or minimized; neither gets deleted. Best used to clear a chaotic backlog.

What are MITs?

Most Important Tasks: one to three items chosen each morning that would make the day a success if nothing else got done. They get the first focused block, before email. The forcing function is the small number; ten MITs is a to-do list wearing a trench coat.

Why does everything feel urgent?

Because inflow channels sort by recency, and recent feels urgent. An email that arrived two minutes ago outshouts a deadline three days out. Prioritising from a clarified task list instead of the raw inbox removes the recency distortion.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works