Comparing by fit
Two ways of thinking, side by side. There is no winner here — read across each row and choose the one that fits your situation.
Operations
Separate urgent from important, and notice how much of your week serves neither.
By 6days
Product
Score competing work on reach, impact, confidence and effort so the argument is about evidence.
By 6days
When to use — Eisenhower Matrix
Use it when you are busy but not progressing, when a team is permanently reactive, or during a periodic review of where a role's time actually goes. It works well as a recurring habit rather than a one-off, and it is a useful device for a manager and report to look at a workload together without it becoming personal.
When to use — RICE Prioritisation
Use it when you have many comparable candidates competing for one team's capacity, when prioritisation has become political and you need a neutral vocabulary, or when you need to explain to stakeholders why their request did not make the cut without it being personal.
When not to use — Eisenhower Matrix
Avoid it where you have little real autonomy — telling someone to delegate work they cannot delegate is just a way of blaming them for their constraints. It handles individual tasks better than long collaborative efforts, and it has nothing to say about work that is important to someone else and not to you, which is most of what makes a job hard. It also assumes you can tell importance from urgency, which is exactly the skill people struggling with this tend to lack.
When not to use — RICE Prioritisation
Avoid it for work that is not discretionary — security fixes, legal obligations and keeping the service up do not get scored, they get done. It handles strategic bets badly: anything genuinely new scores low on confidence and reach by construction, so a team that follows RICE mechanically will optimise itself into small safe increments forever. It also cannot see dependencies or sequencing.
Urgency is loud and importance is quiet. Work that matters — the strategy, the fix that prevents next quarter's incident, the conversation with the struggling team member — has no deadline, so it loses every day to whatever is shouting. Weeks pass full of activity and empty of progress, and the diagnosis is always 'no time', when the truth is that the important work never once won a scheduling contest against the merely urgent.
Every roadmap has more candidates than capacity, and the selection usually goes to whoever argues best — the loudest stakeholder, the most recent customer escalation, the executive's pet idea. The team cannot articulate why one item beat another, so the decision cannot be revisited when things change, and everyone suspects, often correctly, that the process is political rather than analytical.
The matrix sorts work on two independent axes: important (contributes to outcomes you care about) and urgent (demands attention now). The four quadrants get different treatment. Important and urgent: do it, but treat its existence as a signal, since most crises are the residue of neglected important work. Important, not urgent: schedule it, because this is where nearly all real progress lives and it will never demand attention on its own. Urgent, not important: delegate it, or resist it — it is usually someone else's priority wearing your calendar. Neither: stop. The insight is that urgent and important are genuinely independent, and most people's calendars silently assume they are the same axis.
RICE scores each candidate on four factors and combines them into a single number: reach (how many people it affects in a period), impact (how much it moves the thing you care about, per person), confidence (how much you trust your own reach and impact estimates) and effort (person-time to deliver). Multiply the first three, divide by effort. The output is deliberately crude. Its value is not the ranking but the conversation the scoring forces: confidence makes the team say out loud how much of the case is guesswork, and comparing two items usually reveals that a disagreement about priority was really a disagreement about an estimate.
List the actual demands — tasks, meetings, requests, the recurring things you have never questioned. Work from your real calendar and inbox rather than from memory, which reliably omits the routine items that consume the most hours.
Importance is meaningless in the abstract, so name the outcomes you are accountable for and judge each item against them. Anything that contributes to none of them is not important, however comfortable or familiar it is.
Ask what genuinely happens, and to whom, if this waits a week. Most 'urgent' items have a soft consequence and a loud sender. Rating this independently of importance is the whole mechanism; collapsing the two axes reproduces the problem you came to solve.
Do the important-and-urgent, delegate or decline the urgent-but-not-important, delete the rest — and then actually put the important-not-urgent work in the calendar as a booked commitment. If it stays on a list it will lose again next week, exactly as it lost last week.
A two-by-two matrix. The horizontal axis runs from Urgent on the left to Not urgent on the right; the vertical axis runs from Important at the top to Not important at the bottom. Top-left: Do now — Crises and hard deadlines, Pressing problems you must handle. Top-right: Schedule — Planning and strategy, Relationships and prevention. Bottom-left: Delegate — Interruptions and some meetings, Requests that are someone else's priority. Bottom-right: Delete — Busywork and time-wasters, Habitual activities that add nothing.
Worked example — Eisenhower Matrix
An engineering manager audits a week. Urgent and important: a production incident, four hours. Urgent, not important: eleven meetings where they were informed rather than needed, nine hours. Important, not urgent: hiring, the architecture decision blocking two teams, and a struggling report's development conversation — zero hours, as every week. Neither: two standing meetings inherited from a reorganisation eighteen months ago that nobody has cancelled. Declining six meetings and booking two protected blocks moves nine hours into the quadrant that was empty. The incident, it later turns out, was caused by the architecture decision that never got made.
Worked example — RICE Prioritisation
Two candidates. A bulk-export feature: reach 400 users/quarter, impact 1 (medium), confidence 80%, effort 2 person-months — score 160. A redesigned onboarding flow: reach 3,000 new signups/quarter, impact 2 (high), confidence 50% (the evidence is one small study), effort 6 — score 500. Onboarding wins by roughly three to one, which surprises the room because export is what customers ask for by name. The disagreement resolves to a single input: the sales lead thinks onboarding's confidence should be 20%, not 50%. At 20% the ranking flips. Now the team knows exactly what to go and find out, which the argument alone would never have produced.
The urgent-versus-important distinction is popularly attributed to Dwight D. Eisenhower, who quoted a formulation of it in a 1954 address and credited it to an unnamed university president. It was later developed into a four-quadrant tool by Stephen Covey and others in the time-management literature of the 1980s and 1990s. Eisenhower did not devise the matrix that bears his name.
The scoring model was developed and published by the team at Intercom in the mid-2010s to prioritise their own roadmap, and was shared openly rather than commercialised. It sits within a much older tradition of weighted scoring in project selection; its contribution is the specific inclusion of a confidence discount, which is what distinguishes it from earlier value-over-effort schemes.
Decide what 'impact' means before scoring anything — activation, retention, revenue, support load. Without one agreed metric, scores are not comparable and the whole exercise produces a number that means nothing.
Count how many users or events this touches per quarter, using real numbers wherever they exist. Reach is the factor most amenable to evidence, and grounding it prevents the whole score from floating free of reality.
Use a deliberately blunt scale — massive, high, medium, low, minimal — rather than pretending to precision you do not have. False precision here creates unearned confidence in the ranking.
Discount for how speculative your estimates are. This is the factor that does the real work: it stops a thrilling idea with no evidence from outranking a modest one with data, and it makes the team admit which is which.
Estimate total person-months across all functions, not just engineering. Compute the scores, then interrogate the ranking — where the number offends someone's intuition, find out which input they disagree with. That argument is the actual output.
Not specified