Eisenhower matrix examples: 8 filled-in matrices for real roles
Eight filled-in Eisenhower matrix examples, for a manager, a founder, a student, an accountant, a real-estate agent and more, plus a free interactive matrix.
On this page 16 sections
The Eisenhower matrix sorts tasks into four boxes by two questions: is it urgent, and is it important? It's easy to understand and surprisingly hard to apply to your own list, because real tasks rarely arrive labelled. Below are eight filled-in Eisenhower matrix examples for real roles, each with what changed once the list was sorted.
Try it with your list. Paste your tasks into the free interactive priority matrix and drag each one into a quadrant. It runs in your browser and needs no sign-up.
The four quadrants in one minute
| Urgent | Not urgent | |
|---|---|---|
| Important | Q1: Do it now | Q2: Schedule it |
| Not important | Q3: Delegate, shrink or renegotiate | Q4: Drop it |
Urgent means there's a real consequence if it waits, usually a deadline in the next day or two. Important means it moves a goal or responsibility you're accountable for. The trap is treating "someone is asking loudly" as both. For the longer definition and its history, see the Eisenhower matrix glossary entry.
Example 1: team manager
| Urgent | Not urgent | |
|---|---|---|
| Important | Fix tomorrow's rostering gap; approve a payroll correction; respond to a client escalation | One-on-ones with each report; next quarter's hiring plan; documenting the onboarding process |
| Not important | Most "quick question" chat messages; a meeting invite with no agenda; a report format change request | Tidying the shared drive's folder colours; reading every all-staff thread |
What changed after sorting: the one-on-ones had been rescheduled three weeks running. They moved into fixed calendar slots, and two agenda-less meetings were declined. Managers juggling several teams will find more on the page for multi-project managers.
Example 2: startup founder
| Urgent | Not urgent | |
|---|---|---|
| Important | Investor follow-up due Friday; the live site going down; payroll approval | Talking to five customers this month; the pricing decision; hiring the first salesperson |
| Not important | A podcast invitation with a 24-hour reply window; a logo tweak for a deck; partner "catch-ups" with no ask | Testing every new AI tool; rewriting the website's About page again |
What changed after sorting: customer calls had been the first thing cut every week. Two mornings were blocked for them, and the podcast got a polite "not this quarter". See the page for startup founders.
Example 3: university student
| Urgent | Not urgent | |
|---|---|---|
| Important | Essay due in 48 hours; group project slides due tomorrow; enrolment deadline | Weekly revision for the exam in five weeks; reading for next week's tutorial; booking a session with the tutor |
| Not important | A group chat debating the slide font; a club's last-minute volunteer request | Reorganising notes into a new app; endless "study with me" videos |
What changed after sorting: nearly everything in Q1 had started life in Q2. Revision went into the calendar as three short sessions a week, so the next essay wouldn't become an emergency. More on the page for students and researchers.
Example 4: accountant at month-end
| Urgent | Not urgent | |
|---|---|---|
| Important | Bank reconciliations before the close; the BAS lodgement due this week; a variance the CFO asked about | Automating the accruals spreadsheet; documenting the close checklist; reviewing a client's chart of accounts |
| Not important | Re-sending invoices that the client can download; formatting a report nobody has asked to change | Clearing old newsletters; testing a new dashboard theme |
What changed after sorting: the close checklist had never been written down, so every month-end relied on memory. One hour was booked in the quiet week after close to document it. See the page for accountants and finance teams.
Example 5: real-estate agent
| Urgent | Not urgent | |
|---|---|---|
| Important | Saturday's open inspection prep; an offer that expires tonight; returning a vendor's call about price | Following up past clients; building the local market report; prospecting a new street |
| Not important | Most portal enquiry auto-replies; re-sharing a colleague's listing; a supplier's "quick call" | Redesigning the email signature; scrolling competitor listings without a purpose |
What changed after sorting: prospecting only happened in quiet weeks, which meant listings dried up three months later. A standing two-hour block went in every Tuesday. More on the page for real estate and property.
Example 6: agency account manager
| Urgent | Not urgent | |
|---|---|---|
| Important | A campaign going live tomorrow with missing approvals; a client complaint; the monthly report due today | The quarterly business review deck; a scope document for the client's new request; improving the status-update template |
| Not important | Chasing internal sign-off on a minor typo; forwarding files the client already has | Re-labelling the CRM; joining every internal brainstorm |
What changed after sorting: the "new request" had been handled informally in emails, which is how scope creep starts. It moved to Q2 as a proper scope document. See the page for agency and client service teams.
Example 7: freelance designer
| Urgent | Not urgent | |
|---|---|---|
| Important | Final files due to a client today; an overdue invoice; feedback on a live job | Updating the portfolio; raising rates for new clients; following up past clients for referrals |
| Not important | Instant replies to non-urgent client messages; a "can you just" tweak outside the brief | Trying every new font; perfecting a personal logo |
What changed after sorting: out-of-brief tweaks had been going straight into Q1. They now get a quote or wait for the next revision round. More on the page for creative designers and the page for freelancers and consultants.
Example 8: parent working from home
| Urgent | Not urgent | |
|---|---|---|
| Important | A client deliverable due at 3pm; school pick-up; a sick-day handover to a colleague | Planning next week's focus blocks; a skills course for a promotion; agreeing a meeting-free window with the team |
| Not important | Answering every notification during school hours; unscheduled "got a sec?" calls | Reorganising the home office shelves; inbox zero for its own sake |
What changed after sorting: pick-up is fixed, so the day's deep work moved to the morning and the afternoon got shallow tasks. See the page for remote and hybrid teams.
Build your own matrix in 10 minutes
The examples work best as a model for your own list. Here's the routine behind them:
- Dump everything. Write every task, request and nagging idea on one list. Include things you've been avoiding, because they're usually Q2.
- Ask the urgency question with a date. "What happens if this waits until next week?" If the honest answer is "nothing much", it isn't urgent.
- Ask the importance question against your role. "Does this move something I'm accountable for?" Your job description, goals or current projects are the test, not who's asking.
- Limit Q1. If more than five items land there, some are probably Q3 in disguise. Check who actually owns each one.
- Give every Q2 item a first action. "Hiring plan" becomes "list the three roles and draft one job ad". A Q2 item without a next step tends to stay in Q2 forever.
- Decide what happens to Q3 and Q4. Write the name of the person you'll hand each Q3 item to, or the reply you'll send. Delete Q4 items, or move them to a someday list you don't look at every day.
Doing this in the interactive priority matrix is quicker than paper because you can drag items between quadrants as you change your mind. A whiteboard or a spreadsheet with four columns works just as well.
Patterns across the examples
- Q2 is always starved. In every example, the most valuable work (customer calls, revision, prospecting, documentation) sat in Q2 and kept losing to Q1. Most Q1 crises began as neglected Q2 items.
- Most "urgent" items are someone else's priority. Q3 was full of requests that felt urgent because someone else wanted them now. The fix is rarely to do them faster. It's to clarify who owns them, batch them or say no.
- Q4 is small but sticky. Few people list Q4 tasks honestly, yet they absorb the gaps between harder work.
- The matrix is a weekly tool, not a daily one. Sorting once a week, then planning the day from Q1 and Q2, works better than re-sorting every morning.
When the matrix doesn't help
The matrix is a thinking aid, not a scheduler. It doesn't help much when:
- Everything is genuinely urgent and important, as in a live emergency or a launch week. You need sequencing, not sorting.
- You can't delegate. "Delegate" assumes someone to hand to. Without that, Q3 becomes "shrink or renegotiate".
- Importance is someone else's call. If your manager sets priorities, sort together, or you'll be confidently wrong.
- Tasks are too big. "Write the strategy" doesn't fit a box. Break it into a first action, then sort that.
When one Q1 task is the most dreaded, pair the matrix with eat the frog: do that one first.
Eisenhower plus time blocking: put Q2 in the calendar
Q2 only survives if it has time reserved. After sorting, take the two or three Q2 items that matter most this week and give each a block in your calendar, ideally at your best-focus time. The free time blocking planner lets you drag those blocks into a day and send them to your calendar, and the time blocking calendar guide covers how to protect them.
A good weekly loop is: sort your list in the priority matrix, block Q2, then check on Friday which blocks happened.
How Plexii fits in
Plexii's focus tools keep your tasks and calendar together, and every task can have its own desk holding the files, notes and links it needs. When a Q2 block starts, the work is already laid out, so you start instead of spending the first 15 minutes hunting.
The free tier is free forever for personal use, Pro is US$12 a month or US$120 a year, and teams can try it free for 14 days.
Common questions
What is an example of an Eisenhower matrix?
A manager's matrix might put a client escalation in Q1 (urgent and important), one-on-ones in Q2 (important, not urgent), agenda-less meeting invites in Q3 (urgent, not important) and tidying folders in Q4. The eight examples above show complete matrices by role.
How do students use the Eisenhower matrix?
Put assignments due in the next day or two in Q1, regular revision and reading in Q2, group-chat noise in Q3, and procrastination tasks in Q4. Then block Q2 time each week so assignments stop turning into emergencies.
What goes in quadrant 3?
Tasks that feel urgent but don't serve your own goals: interruptions, many messages and meetings, and requests that are someone else's priority. Delegate them, batch them, shrink them or renegotiate the deadline.
How often should I use the Eisenhower matrix?
Most people get the most out of a weekly sort, plus a quick check whenever a large new request lands.
Is the Eisenhower matrix the same as the urgent-important matrix?
Yes. The names are interchangeable, and it's also called the priority matrix.
Can a team use the Eisenhower matrix together?
Yes, and it often works better than sorting alone. Put the team's shared backlog on one matrix in a planning meeting, agree what counts as urgent and important for the team's goals, and name an owner for every Q1 and Q2 item. Disagreements about which box a task belongs in are useful, because they expose different assumptions about priorities before the work starts.
Sources
- Stephen R. Covey, The 7 Habits of Highly Effective People (1989), which popularised the urgent/important time-management matrix.
- Dwight D. Eisenhower, address at the Second Assembly of the World Council of Churches, Evanston, Illinois, 19 August 1954, where Eisenhower quoted a former college president on "the urgent and the important" (The American Presidency Project (opens in a new tab)).