Eisenhower Matrix: Urgent vs Important, With a Template

An Eisenhower matrix sorts every task by two questions, is it urgent and is it important, into four boxes: urgent and important (do it now), important but not urgent (schedule it), urgent but not important (delegate it), and neither (delete it). The value is in the second box. Important work that has no deadline is what gets pushed aside by whatever is shouting loudest, and the matrix makes that visible. A template to copy, a worked example for a small team, and a way to turn the boxes into priorities on a board are below.

The four boxes

• Do: urgent and important. A production outage, a contract that must be signed today, a customer who cannot log in. Work on it now, yourself.
• Schedule: important, not urgent. Planning, hiring, fixing the cause of a recurring bug, writing the onboarding guide. Give it a set time, or it will never happen.
• Delegate: urgent, not important to you. Most meeting requests, routine reports, questions someone else can answer. It needs doing soon, but not by you. Hand it to the person who should own it.
• Delete: neither urgent nor important. The report nobody reads, the tool nobody asked for, the nice-to-have that has sat untouched for six months. Drop it on purpose.

Two definitions keep the sorting honest. Urgent means it has a short window: if it is not done soon, the chance is gone. Important means the outcome is large: doing it or not doing it changes something that matters to your goals. A task can be one without the other, which is the whole point.

Where it comes from, and what Eisenhower actually said

The matrix is named after Dwight D. Eisenhower, but he did not draw it. In an address to the World Council of Churches in Evanston, Illinois, on August 19, 1954↗ (opens in a new tab), Eisenhower quoted someone else: “I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent.” He attributed the line to “a former college president” and did not name him. So the quote is real and documented, but Eisenhower was repeating it, not claiming it.

The four-box grid came much later. Stephen R. Covey’s The 7 Habits of Highly Effective People popularized a time matrix of urgent and important quadrants, and FranklinCovey still teaches it under Habit 3, Put First Things First↗ (opens in a new tab), which says the best return on your time comes from “things which aren’t urgent but are important. For example, planning, creative thinking, and learning and renewal.” That is the Schedule box, and it is the box the method exists to protect.

There is research behind the worry. In five experiments, Meng Zhu, Yang Yang and Christopher K. Hsee found what they called the mere urgency effect↗ (opens in a new tab): people chose unimportant tasks with objectively lower payoffs over important ones with better payoffs when the unimportant tasks merely looked urgent, for example because of an illusion that they would expire. The pull of urgency is real, and sorting tasks on paper is one way to notice it.

An Eisenhower matrix template to copy

Eisenhower matrix: [team or person], week of [Month day, year]

Urgent = must happen within [2 working days] or the chance is gone
Important = moves [this quarter's goal] or protects customers

1. DO (urgent + important)            -> this person, now
   - [task]
   - [task]

2. SCHEDULE (important, not urgent)   -> a set time this week or next
   - [task]  when: [day, block]
   - [task]  when: [day, block]

3. DELEGATE (urgent, not important)   -> named owner, same week
   - [task]  owner: [name]
   - [task]  owner: [name]

4. DELETE (neither)                   -> close it, say why
   - [task]  reason: [nobody uses it]

Check: more than 3 items in DO? Some of them are really box 3.
Check: nothing in SCHEDULE? The week is being run by urgency.

Write your own definitions of urgent and important at the top. Without them, every person on the team sorts by gut feeling and the boxes stop meaning anything. “Within two working days” and “moves this quarter’s goal” are examples; pick lines that fit your work.

A worked example for a small team

An invented five-person software company on a Monday morning. The goal this quarter is to cut new-customer setup time in half. Eight items are waiting:

1. DO
   - Checkout fails for customers paying by card (reported 7:40 a.m.)
   - Sign the renewal with the hosting provider (expires Wednesday)

2. SCHEDULE
   - Rewrite the setup wizard (the quarter's goal)      Tue + Thu mornings
   - Interview two support candidates                   Wed afternoon

3. DELEGATE
   - Monthly usage report for the investor update       owner: Priya
   - Reply to the partner asking for a logo             owner: Sam

4. DELETE
   - Dark mode for the admin screens (2 requests in 9 months)
   - Weekly metrics email that nobody opens

The pattern is typical. The two Do items are fires, and they will get done because they are loud. The setup wizard is the only item that serves the quarter’s goal, and without a block on the calendar it would lose to the usage report every day this week. The deletes are not failures; closing them with a reason means nobody raises them again next Monday without new information.

From four boxes to a priority number and lanes

A matrix on paper goes stale by Wednesday. The durable version is to translate the boxes into the fields your board already has. On fenbs every task has a priority from 1 to 10, where 1 is the most urgent and 5 is the default, and the board filters priority in three bands: High (P1 to P2), Medium (P3 to P5) and Low (P6 to P10). Tasks sit in four lanes: To Do, Next Up, In Progress and Completed. A starting map:

• Do: P1 or P2, straight into In Progress. If more than two or three tasks are here, re-sort, because some of them belong in Delegate.
• Schedule: P3 to P5, in Next Up. Priority alone will not protect these, because a P3 always looks less pressing than a P1. Give them a block in your week; time blocking shows how.
• Delegate: P3 to P5, in Next Up, with the owner named in the first line of the note. fenbs has no assignee field, so the note is where the name goes. The task’s history records who filed it and who moved it.
• Delete: move it to Completed and choose Won’t fix or Obsolete as how it ended. The task stays on record with its history, and only a task that ended as Completed, not Won’t fix or Obsolete, counts as delivered in the board’s figures.

Notice what the number cannot hold: importance on its own. Priority on a board mixes urgency and importance into one ranking, which is why the Schedule box needs protecting outside it. The same trap shows up with bugs, where a severe bug is not always the most urgent one; bug severity vs priority works through it. fenbs has no due dates or reminders, so “when” for a scheduled task lives in your calendar, not on the task.

A connected AI assistant can do the first pass. Ask it: “List the tasks in To Do and Next Up, and sort each into do, schedule, delegate or delete using the definitions in our AI context. Do not change anything; show me the list.” Put your definitions of urgent and important in the board’s AI context so the assistant uses the same lines your team does. Then you decide, and the changes you approve are made on the board where everyone sees them.