How to Use an Eisenhower Matrix When Everything Feels Urgent
The Eisenhower Matrix looks simple because it asks only two questions about each task: Is it important? Is it urgent?
The difficulty appears when every task seems to deserve a yes.
A client is waiting. A colleague sent three messages. A report is due this week. An invoice needs attention. A long-term project has already slipped twice. The matrix becomes useless if every item lands in the same box.
The value of the method comes from making the two words mean something specific.
The four quadrants are different decisions
The matrix separates tasks into four groups:
- Important and urgent: Do first.
- Important and not urgent: Schedule.
- Urgent and not important: Delegate, simplify or contain.
- Neither important nor urgent: Remove, defer or leave.
The labels describe different responses. They are not grades of personal worth and they do not measure how stressful a task feels.
The Eisenhower Matrix Task Prioritizer lets you enter up to 12 tasks and classify each one by importance and urgency.
Define urgent before you start
Urgency should describe a real time constraint.
A task may be urgent when:
- a hard deadline is close;
- another person cannot continue until it is finished;
- a delay creates a concrete consequence;
- a short response window genuinely exists;
- a problem is actively getting worse while it waits.
A task is not automatically urgent because:
- it arrived five minutes ago;
- someone marked an email as high priority;
- it is visible on the top of your inbox;
- it is easy to finish quickly;
- you feel uncomfortable leaving it open.
That distinction matters because visibility can create false urgency.
If a request has no meaningful consequence when it waits until tomorrow, it may be active without being urgent.
Define important separately
Importance should connect a task to a meaningful outcome, responsibility or commitment.
A task may be important because it:
- affects a customer or client commitment;
- contributes directly to a major goal;
- protects a legal, financial or operational obligation;
- prevents future work from becoming harder;
- supports a person or responsibility that genuinely matters to you;
- develops capability you deliberately decided to build.
Importance is different from urgency because important work can have no immediate deadline.
A quarterly planning session may matter greatly without needing action today. That is exactly why the Schedule quadrant exists.
Why the “Do first” box should stay small
If ten of twelve tasks are important and urgent, the matrix has not reduced the decision problem.
Review the quadrant again and ask:
- Which deadlines are real rather than assumed?
- Which delays create the largest consequence?
- Which tasks block other work?
- Which items can be reduced to a smaller immediate action?
- Which tasks became urgent only because they were postponed earlier?
Then use the Priority Picker if several tasks still have a credible claim on the same time. The Priority Picker adds deadline pressure, consequence, importance, dependency and effort to create a more detailed ranking.
The matrix is useful for broad classification. It is not always enough for ordering several tasks inside the same quadrant.
The Schedule quadrant is where important work survives
Important work often becomes urgent because it was never given a place in the schedule.
Examples can include:
- preparing for a future presentation;
- preventive maintenance;
- hiring work;
- learning a system you will soon need;
- writing a proposal before the final day;
- preparing documentation;
- long-term planning.
If these tasks remain on a list without a time commitment, reactive work can repeatedly push them aside.
“Schedule” should therefore mean more than “do later”. Give the task a real review point, date or block of time.
The Time-Block Day Planner can help after you have chosen which important work deserves space in a particular day.
“Delegate” is not the only answer for urgent but less important work
Delegation assumes that another person can and should own the task. That is not always true.
You can also:
- simplify the requested output;
- batch similar requests together;
- create a template;
- automate a repetitive step;
- set a boundary on how much time the task receives;
- move responsibility to the correct person;
- answer with enough information to unblock the request without completing unnecessary work.
For example, a routine status request may be urgent because someone needs an answer before a meeting. The response may only require a short update rather than a new report.
The useful question is: What is the smallest appropriate response to this urgency?
“Remove” does not mean a task has no value
The fourth quadrant is often misunderstood.
A task can have some value and still not deserve space in the current plan.
Examples might include:
- reading an interesting article with no current purpose;
- polishing a document that is already good enough;
- researching an idea you have not decided to pursue;
- attending an optional meeting that does not affect your work;
- reorganising files that are not causing a real problem.
The decision may be to delete the task, but it may also be to leave it for a later review without giving it active attention now.
This distinction prevents low-consequence work from consuming time merely because it is easy to see and finish.
Use the matrix before the schedule, not after it
A common mistake is filling a calendar first and then using the matrix to justify what is already there.
A stronger sequence is:
- Capture the tasks.
- Classify importance and urgency.
- Rank tasks that share the same quadrant if necessary.
- Check available capacity.
- Place selected work into the actual schedule.
The Workload Check is useful at step four. It compares the hours available with fixed commitments, planned task time and the buffer you want to keep.
A task can deserve attention and still fail the capacity check. That is a scheduling problem rather than a prioritisation problem.
Example: an overloaded Tuesday
Suppose your list contains:
- finish slides for tomorrow’s client presentation;
- answer a routine internal request received this morning;
- plan next month’s campaign;
- renew a software subscription that expires today;
- reorganise the shared drive;
- review a colleague’s document needed for their 3 PM deadline.
A reasonable first classification might be:
Do first
- finish client slides;
- review the colleague’s document;
- renew the software if losing access today creates a real problem.
Schedule
- plan next month’s campaign.
Delegate or simplify
- answer the routine internal request, perhaps with a short response or by directing it to the correct owner.
Remove or leave
- reorganise the shared drive unless the current organisation is blocking work.
The matrix does not tell you whether slides or document review should happen first. That depends on timing, consequences and dependencies. The next step may therefore be the Priority Picker.
Review the matrix when facts change
A matrix is a snapshot.
A task can move from Schedule to Do First when a deadline approaches. An urgent request can disappear when another person handles it. A task may become less important when a project changes direction.
Do not preserve yesterday’s quadrant because you already invested time categorising it.
Reclassify when the underlying facts change.
The matrix works best when it creates fewer immediate decisions
The purpose is not to label every task perfectly.
The useful outcome is a smaller set of work that deserves attention now, a protected place for important work that can wait, a clearer treatment for reactive requests and permission to leave some things alone.
If the matrix still leaves you with too many immediate tasks, use the Priority Picker and Workload Check to narrow the list further.