Eisenhower Matrix Examples

The examples below show how an Eisenhower Matrix changes with context. The same task can sit in different quadrants for different people because importance depends on goals and responsibility, while urgency depends on real deadlines and consequences. Copy the reasoning, not just the labels.

Work example: a product manager

Do first

• Decide whether to pause a release after a confirmed critical defect.
• Send the final compliance response due at noon.

Schedule

• Interview three customers about the next quarter’s problem space.
• Draft a decision memo for retiring an underused feature.

Delegate

• Ask the analytics owner to refresh the weekly adoption dashboard.
• Route a standard vendor questionnaire to procurement.

Eliminate

• Decline a meeting with no agenda, decision, or necessary contribution.
• Archive duplicated “someday” feature ideas already recorded elsewhere.

The customer interviews may create more long-term value than the compliance response. They remain scheduled because there is no near-term consequence today. The important move is to reserve interview time before reactive work consumes the week.

Student example: one week before exams

Do first

• Submit the lab report due tonight.
• Email the instructor now about an inaccessible exam document.

Schedule

• Review two chemistry topics each morning before Friday’s exam.
• Meet the study group on Wednesday to compare practice answers.

Delegate or share

• Confirm which group member will combine the presentation slides.
• Ask a housemate to handle the agreed grocery trip during exam week.

Eliminate

• Leave an optional club event that conflicts with necessary recovery.
• Stop reformatting notes that are already clear enough to revise from.

Exam revision belongs in Schedule while there is still time. Waiting until the night before moves it into Do first, but does not make it more valuable; it only makes the plan more fragile.

Personal example: planning a move

Do first

• Return the signed lease before today’s deadline.
• Replace a broken lock that creates an immediate safety risk.

Schedule

• Compare moving services by Thursday.
• Pack one low-use room each weekend.

Delegate

• Ask the utility account holder to schedule the transfer.
• Assign agreed packing areas to household members.

Eliminate

• Donate items nobody wants to move or store.
• Cancel a subscription unavailable at the new address.

This example shows why projects should be broken into next actions. “Move house” is too broad for a quadrant. “Return signed lease” and “pack the guest room” have different urgency.

Ambiguous edge cases

“Reply to email”

Email itself is neither urgent nor important. A message confirming emergency childcare may be Do first. A thoughtful partnership proposal may be Schedule. A routine data request may be Delegate. A generic sales message may be Eliminate.

“Attend the meeting”

Ask what decision needs your contribution. A live incident review could be Do first. A strategic workshop next month is Schedule. A routine update can be delegated to a representative or replaced with written notes. A meeting with no purpose can be removed.

“Exercise”

Regular movement is often important and not urgent, so it belongs in Schedule. It is not low-value simply because nobody else created a deadline. If you have symptoms or medical restrictions, personal planning advice is not a substitute for appropriate professional care.

“Help a colleague”

Clarify consequence and role. If only you can unblock a time-sensitive launch, it may be Do first. If the request is useful but not immediate, schedule it. If another owner is better placed, route it responsibly. Boundaries matter when repeated “quick favors” displace your primary work.

A blank example to copy

Use these prompts when creating a fresh matrix:

• Do first: What has a real consequence before my next review?
• Schedule: What important outcome needs protected time?
• Delegate: What prompt task belongs with another capable owner?
• Eliminate: What can I decline, archive, simplify, or stop?

Keep only a handful of visible actions. Store project details elsewhere and rewrite broad entries as concrete next steps. If every quadrant is crowded, the problem may be capacity rather than classification.

You can compare the step-by-step method, explore the work-focused version, or turn your own example into a printable PDF.