Eisenhower Matrix: Template, Examples and How to Use It

What is an Eisenhower matrix?

An Eisenhower matrix is a way to turn a long, mixed task list into four short lists with different treatments. Urgent tasks have a consequence attached to time: a deadline someone depends on, a cost that grows every day, a person or system that is blocked right now. Important tasks move a goal you have actually named, or protect something you cannot afford to lose, such as revenue, safety, legal standing, or trust. The two properties are independent. A task can be both, either, or neither, which is why the grid has four cells rather than a single ranked list.

The name comes from an August 19, 1954 address that President Dwight D. Eisenhower gave to the Second Assembly of the World Council of Churches in Evanston, Illinois. He quoted "a former college president" as saying: "I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent" ( The American Presidency Project). He was describing a dilemma of modern life, not presenting a planning tool, and the speech contains no grid. The four-quadrant layout most people use today was popularized decades later, notably through the time-management matrix in Stephen R. Covey's The 7 Habits of Highly Effective People (1989), whose Habit 3, "Put First Things First," sorts activities by urgency and importance ( Simon & Schuster). Attributing the matrix itself to Eisenhower is a common shortcut, and this article avoids it.

Use the matrix when the list is longer than the week, when several people keep asking for "just one quick thing," or when you notice that the tasks that matter most keep getting displaced by tasks that are merely loud. Skip it when you are choosing between options rather than sorting tasks, when the order of work is fixed by dependencies, or when the real constraint is hours rather than priorities.

The four quadrants: criteria and default actions

Every task gets two yes/no answers. The answers place it in one quadrant, and the quadrant decides what happens next. The table gives the decision criteria and the default action for each cell; the "watch for" column lists the pattern that shows up when a quadrant is being misused.

The two axes are questions, not moods. Each quadrant carries a signal, a default action, and a warning sign for the weekly review.

Two rules keep the grid honest. First, write the evidence, not the feeling: "due Oct 7, store review can take a week" is urgency evidence; "the CEO asked" is not. Second, every row leaves the matrix with one concrete next action. A task that is "in Q2" but has no blocked slot has not been scheduled; it has been postponed.

Eisenhower matrix template you can copy

There is no file to download here. The template is the two tables below. Copy them into a document, a spreadsheet, or a whiteboard, or type the headers into any table block. The first table is the visible grid; the second is the task register that feeds it. Most teams keep both, because the register holds the evidence that the grid cannot show.

Blank matrix

Task register

Keep the register to one line per task. If a row needs a paragraph to explain, it is probably two tasks, or it belongs in a different tool such as a project plan.

Eisenhower matrix example: 12 tasks from a fictional product launch

The example below is an editorial illustration. The team, the product, the people, the dates, and the tasks are invented for teaching. They are not a customer case, a survey, or AFFiNE's own launch process.

Scenario. A five-person team (Priya, product lead; Marcus, engineer; Elena, designer; Sam, marketing; Jordan, support) is preparing to launch a fictional scheduling app on Friday, October 16, 2026. On Monday, October 5, Priya captures every open task and sorts it. The urgency test is "does something break or cost more if this waits until next Monday?" The importance test is "does this move the launch or protect users, revenue, or commitments?"

The same 12 tasks on the grid. The dashed card in Q1 shows where the investor deck was first placed; the arrow shows where it ended up once the real date was checked.

The counterexample. Task 7 arrived as "investor deck, ASAP." Priya's first instinct was Q1, because the request came from the founder. The urgency test asks what breaks if it waits a week, and the answer was nothing: the investor meeting is on October 22, six days after launch. "ASAP" was a habit, not a date. The deck is important to the company, so it does not drop to Q4; it moves to Q2 with a blocked morning on October 19, after the launch. Reclassifying it freed the morning she would otherwise have spent on the deck in launch week.

What the sort produced. Three tasks to do this week, each with a time. Four tasks scheduled into specific blocks. Three tasks delegated to Jordan, each with a check-in, which the Friday review should watch, because three delegations to one person in one week is the pattern that turns Q3 into someone else's Q1. Two tasks eliminated, one parked and one dropped. Priya's own week now holds one Q1 task, two Q2 blocks, and two delegations to check on, instead of five open items with no order.

How to use an Eisenhower matrix in five steps

The matrix is a loop, not a one-time sort. The steps below take about 35 minutes the first week and less afterward, because the criteria and register are reused.

1. Capture every open task in one place

Pull tasks from your inbox, chat threads, meeting notes, and memory into a single list, one line per task with an owner and a deadline if one exists. Do not sort while capturing; mixing the two steps makes people drop tasks they would rather not classify. Fifteen minutes is enough for most individuals and small teams.

2. Define what urgent and important mean this week

Write two tests before you touch the grid. A workable urgency test is "due within seven days with a consequence if missed." A workable importance test names the goal: "moves the October 16 launch" or "protects an existing customer commitment." Defining a goal first is the step people skip; a SMART goal template is a quick way to make the goal specific enough to test tasks against. Reuse the tests until the goals change.

3. Classify each task and record the evidence

Apply both tests to every row and write the evidence in the register beside the quadrant. Do a fast first pass on instinct, then revisit only the borderline rows. The evidence column is what lets a teammate challenge a placement in the review without relitigating the whole list.

4. Assign one next action per quadrant

Turn each quadrant into something concrete. Q1 gets a time today or this week. Q2 gets a blocked day and time; a weekly planner template is where those blocks live, because the matrix itself holds no hours. Q3 gets a named new owner and a check-in date. Q4 gets a decision: dropped, or parked on a list with a monthly reread. No row leaves the matrix without one of these.

5. Review weekly and revise the criteria

Once a week, compare the matrix with what actually happened, remove finished rows, re-sort the rows that slipped, and send new tasks back to step 1. Twenty minutes is usually enough. Use the checklist below, and adjust the urgency or importance tests if the same kind of task keeps being misfiled.

The review step feeds the next capture. The four signals at the bottom right are the most common ways a matrix goes wrong between reviews.

Weekly review checklist

• Did every Q1 item get done? If not, what was the real blocker?
• Did the Q2 blocks hold, or did something push them out? Protect one block per person per week before adding more.
• Did each delegated Q3 item reach its check-in? Reassign anything that is stuck, and notice if every delegation lands on the same person.
• Reread the Q4 "later" list once a month and delete what stayed idle.
• Which Q1 items could have been Q2 a week earlier? Fix the trigger, not just the task.
• Recount the quadrants. More than about a third of tasks in Q1 usually means over-commitment or late capture, not a busy week.

Eisenhower matrix vs. decision matrix, Kanban, and weekly plan

The Eisenhower matrix is often asked to do jobs that belong to neighboring tools. The boundary is simple to state: an Eisenhower matrix classifies tasks by urgency and importance; a weighted decision matrix compares options across multiple criteria; a Kanban board visualizes the flow of work; a weekly plan assigns time. Each answers a different question.

Four tools, four questions. The strip at the bottom shows the order they usually run in: choose the option, sort the tasks, give the tasks hours, then track them to done.

A few practical notes on each neighbor:

• Decision matrix. The American Society for Quality describes a decision matrix as a tool that "evaluates and prioritizes a list of options" against weighted criteria, used "when a list of options must be narrowed to one choice" ( ASQ). If you are choosing a vendor, a feature, or a location, use a decision matrix template with weighted scoring and a sensitivity check, then bring the tasks that follow from the chosen option back to the Eisenhower grid.
• Strategy frameworks. A SWOT analysis produces candidate actions; it does not rank them. Run the SWOT analysis templates and examples first when you need to decide what to work on at all, then sort the resulting actions here.
• Kanban. The Kanban Guide defines Kanban as "a strategy for optimizing the flow of value through a process," built on defining and visualizing a workflow, actively managing items in it, and improving it ( Kanban Guide, May 2025). The two tools chain well: triage on the grid, then track on the board. The guide to integrating Kanban boards and Eisenhower grids walks through that combination.
• Value/effort grids. These look like the Eisenhower matrix but compare initiatives on payoff and cost, which makes them a two-criteria decision matrix rather than a task sorter. Use them for backlog triage, not for deciding what you personally do on Tuesday.

Limitations of the Eisenhower matrix

The two axes are the whole model, and several things that decide real priorities are not on them.

• Dependencies. A Q2 task that blocks three Q1 tasks is effectively Q1, and the grid cannot see that. Check predecessors before trusting a quadrant; a project plan or a dependency map is the right place to record them.
• Capacity. Ten tasks in Q1 is a fact about the list, not a plan. The matrix does not know how many hours the owner has. That is the weekly plan's job, and the review checklist's recount exists because the grid will happily let Q1 grow past what anyone can do.
• Budget, compliance, and hard gates. A cheap unimportant task and an expensive one look identical in Q4. Legal, security, or contractual requirements can force a task into Q1 regardless of what it "moves." Screen these before sorting.
• Multi-criteria trade-offs. Two important tasks that compete for the same week are both "Q1" or both "Q2"; the grid offers no way to choose between them. Use a weighted decision matrix when the trade-off has more than two dimensions.
• Subjectivity. Importance is relative to a goal, and the goal is a choice. Two people with different goals will sort the same list differently. That is why the evidence column matters more than the quadrant label.
• Size. Beyond roughly 20 to 30 open tasks the grid stops being readable. Split by project or by person, or sort only what is due within the planning horizon.

Keep the matrix, evidence, and review notes together in AFFiNE

The template above works in any tool. If you want the grid, the task register, and the weekly review notes in one document, an AFFiNE page can hold them side by side: the register as a table, the grid as a second table or as cards arranged on the Edgeless canvas, and the review checklist as a checklist block beneath them. AFFiNE's database blocks currently offer a Table view and a Kanban view, and a document can be switched between Page mode and Edgeless mode, according to the AFFiNE documentation on blocks with databases. You can also mark any page as a template so the blank register is reused each week ( AFFiNE documentation on templates).

If you would rather start from a prepared board, the AFFiNE template gallery has a Kanban Boards and Eisenhower Grids template that you can copy into a workspace with its "Use this template" button. It is a manual board: you still classify each card yourself, and there is no automatic sorting, scoring, reminder, or calendar step involved. Verify the current behavior in your own workspace before making it a team procedure.

Frequently asked questions

What is an Eisenhower matrix template?

An Eisenhower matrix template is a blank 2×2 grid, usually paired with a task register, that you fill in by classifying each task as urgent or not and important or not. The four cells map to four actions: do, schedule, delegate, and eliminate. The template on this page is two tables you can copy into any document or spreadsheet.

How do you fill in an Eisenhower matrix?

Capture every open task, write a one-line urgency test and a one-line importance test, apply both tests to each task and record the evidence, give every task one next action that fits its quadrant, and review the grid once a week. In the worked example above, this turned 12 launch tasks into 3 to do, 4 to schedule, 3 to delegate, and 2 to eliminate.

Did Dwight Eisenhower invent the Eisenhower matrix?

No. In an August 19, 1954 address in Evanston, Illinois, Eisenhower quoted a former college president on the difference between urgent and important problems. He described a dilemma, not a grid. The four-quadrant layout was popularized later, notably through Stephen R. Covey's time-management matrix in The 7 Habits of Highly Effective People.

What is the difference between an Eisenhower matrix and a decision matrix?

An Eisenhower matrix classifies tasks by two yes/no questions, urgency and importance, and assigns one action per quadrant. A weighted decision matrix compares several options against several weighted criteria and produces a ranked score. Use the decision matrix to choose an option, then the Eisenhower matrix to sort the tasks that follow.

Is there a free downloadable Eisenhower matrix template on this page?

There is no file to download. The blank matrix and the task register are shown as tables above so you can copy them directly into a document, spreadsheet, or whiteboard. AFFiNE's template gallery also has a Kanban Boards and Eisenhower Grids board you can copy into a workspace, which you fill in manually.

Conclusion

An Eisenhower matrix earns its place by being small. Two questions, four quadrants, one action per quadrant, and a weekly review are enough to keep a long list honest, as long as the evidence for urgency and importance is written down and every row leaves with a next step. The fictional launch above shows the payoff, 12 open items becoming a week Priya can actually run, and the catch, an "ASAP" that was never a date. Keep the register beside the grid, hand off option choices to a decision matrix, hours to a weekly plan, and status to a Kanban board, and the matrix will keep doing the one job it is good at.