The promise and the problem
The Eisenhower matrix sorts tasks into four boxes across two axes: important or not, urgent or not.
| Urgent | Not urgent | |
|---|---|---|
| Important | I — do now | II — schedule |
| Not important | III — delegate | IV — drop |
The model is clear, memorable and explainable in five minutes. And in practice it reliably fails — not because of the model, but because of how the axes get filled in.
Both axes are usually guessed. You look at a task and decide by feel whether it is urgent. The result is familiar: after twenty minutes of sorting, 70 per cent of tasks sit in quadrant I, a few in II, and boxes III and IV are empty because nobody enjoys admitting they do unimportant work. A matrix with almost everything in one box carries no information.
The fix is not to guess more honestly. It is to derive both axes instead of guessing them.
Disclosure: we build Balane Plan, an app that does this derivation automatically. The method works on a sheet of paper too — it just costs more time.
Urgency is arithmetic, not a feeling
Urgency is the one axis that can be calculated in full. It hangs on two quantities:
latest start = deadline − remaining effort − bufferA task with four hours of remaining effort due Friday at noon has its latest start on Thursday afternoon. Before Thursday it is not urgent, no matter how often somebody asks about it during the week.
This calculation clears a surprising number of tasks out of quadrant I. And it exposes the two most common confusions:
Visibility is not urgency. A task somebody asks about in person feels urgent. Whether it is depends on the latest start, not on the volume of the asking.
Age is not urgency. A task that has been sitting for six weeks is not urgent because of that. If it has no deadline, it has no urgency. It may have a problem — but a different one.
Handling tasks without a deadline honestly is the sore spot of nearly every prioritisation scheme. Two answers are legitimate: either give it a real deadline, or accept that it will never be urgent and let it compete purely on the importance axis. What is not legitimate is inventing a deadline — that devalues every real deadline in the same system.
Importance follows from a promise
The second axis cannot be calculated, but it can be derived. The useful question is not "is this important?" but: which promise does this work serve, and what happens if it does not get done?
Four classes cover almost all knowledge work:
| Class | Example | What happens if it is skipped |
|---|---|---|
| Client commitment | Agreed delivery, appointment | Loss of trust, contractual risk |
| Keeping the lights on | Accounting, security, maintenance | Slips invisibly, hits hard later |
| Growth | Sales, product work, learning | Nothing — today. Everything — in a year |
| Optional | Nice to have, curiosity | Nothing |
Work is important when its absence costs something you are not willing to pay. That phrasing has a practical advantage: it can be negotiated. "Important because I think it is important" cannot.
The typical mistake sits in the growth row. That line is the classic quadrant II work: important, never urgent, therefore permanently postponed. The bill only arrives months later, and by then it is large.
The quadrant that actually matters
The matrix is usually read as a tool for weeding things out. Its real purpose is different: to show how much time flows into quadrant II — important, not urgent.
Because quadrant II work is precisely the work that keeps quadrant I from overflowing. Maintenance, documentation, sales, learning, clearing technical debt — none of it is urgent today, and all of it produces firefighting in six months if it is skipped.
A workable target split for a normal working week:
- Quadrant I: 20–30% — real deadlines, real urgency
- Quadrant II: 50–60% — where the return actually comes from
- Quadrant III: 10–15% — delegate where possible
- Quadrant IV: ~0%
Anyone above 50 per cent in quadrant I does not have a prioritisation problem, they have a capacity problem. No sorting method cures that.
Using the matrix as a daily tool
The matrix is not a picture you paint once. The two axes move at different speeds:
- The importance axis follows goals and changes quarterly. Set it once, touch it rarely.
- The urgency axis changes daily, because remaining effort and distance to the deadline take new values every day. A matrix from the start of the month is wrong by day three.
In practice: the class of promise attaches to the task and stays. The latest start is recalculated every morning — which costs about a minute per task by hand and nothing at all automated.
That is exactly how the matrix is built in Balane Plan: urgency comes from real deadlines and measured remaining work, importance from the class of promise — until you move a card and know better. The move is remembered, not overwritten; a model that contradicts the person has no business in a tool for that person's work.
What the matrix cannot do
Three limits worth knowing:
It does not know dependencies. An unimportant task blocking three important ones belongs at the front — the matrix cannot see that. Dependencies need a different view, such as a timeline or a chain of unlocked work.
It does not know duration. Two tasks in the same box, one ten minutes and one two days — the matrix treats them alike. For day planning, duration is the decisive quantity.
It does not know your state. Important and urgent at 16:30 after six hours of meetings is not the same as important and urgent at 09:00.
The matrix is therefore a tool for sorting, not for planning. It answers what comes first. It does not answer what actually fits into today — that needs net time and durations.
In short
The Eisenhower matrix works as soon as you stop guessing its axes. Urgency is arithmetic from deadline and remaining effort. Importance follows from the promise the work serves. Both are derivable, and once derived, both are negotiable.
And if, after honest sorting, everything is still in quadrant I, the matrix has done its job anyway: it has shown that the problem is somewhere else.
Common questions
What is the difference between important and urgent?
Urgent is a statement about time — from when is it too late. Important is a statement about effect — which promise the work serves and what happens if it does not get done. The two get mixed up constantly, because urgent things feel important.
Why does almost everything end up in quadrant I for me?
Because urgency is guessed rather than calculated. Work out the latest start from remaining effort and deadline and most tasks sort into quadrant II — important with time left, but feeling urgent because they are visible.
How often should the matrix be redrawn?
The importance axis rarely; it follows goals that change quarterly. The urgency axis recalculates daily, because remaining effort and distance to the deadline change every day. A matrix drawn once a month is wrong within three days.
Is the matrix useful for teams?
For the importance axis yes; for the urgency axis only with shared deadlines and visible remaining effort. Without that data every team member prioritises by personal feeling, and the result is a matrix four people read differently.