The Eisenhower Matrix
This is the simplest tool in the kit and the one I reach for most on a Monday morning when my list is screaming at me. It comes from a line attributed to Dwight Eisenhower, that what is important is seldom urgent and what is urgent is seldom important, and it was popularized by Stephen Covey. It is a 2×2 that separates two things we constantly conflate: urgency (this needs attention soon) and importance (this moves something that matters).
The distinction is load-bearing because urgency is loud and importance is quiet. Urgent things announce themselves: the ping, the escalation, the "quick question." Important things sit silently until they are overdue. Left to instinct, you will spend your whole week serving other people's urgency and never touch your own important work. The matrix forces the separation onto paper so you can see the theft happening.
#The four quadrants
| Urgent | Not Urgent | |
|---|---|---|
| Important | Do (now, yourself) | Decide (schedule it) |
| Not Important | Delegate (someone else) | Delete (drop it) |
Do (Q1): crises, hard deadlines. Necessary, but living here means you are firefighting. Decide / Schedule (Q2): strategy, discovery, relationships, growth. This is where a good PM should live. It is the quadrant that prevents Q1 fires. Delegate (Q3): urgent but not important to you, the work that feels productive but is not yours. This is the hardest quadrant to be honest about. Delete (Q4): the busywork and the meetings that should have been emails. Cut without guilt.
#The real lesson is Quadrant 2
Every Q1 fire was, at some point, a Q2 task you did not get to. Discovery you skipped becomes a launch crisis. The roadmap you did not socialize becomes an executive escalation. PMs who feel perpetually reactive are usually living in Q1 and Q3; the ones who feel in control have defended their Q2 time. So treat the matrix less as a sorting tool and more as an argument: spend deliberate hours on important-not-urgent work before it metastasizes into urgent.
#Where it fits and where it doesn't
Eisenhower is for personal and team triage: your task list, your calendar, the inbox of asks. It is not a roadmap tool, and using it as one is the most common misuse I see. It has no concept of business impact magnitude, effort, or strategic fit, and "important" here is a personal judgment, not a portfolio criterion. For sequencing the actual product roadmap, use The Impact-Likelihood Matrix or RICE. For deciding how much effort a given task deserves once it is on your plate, pair it with LNO: Eisenhower tells you whether to touch a task at all, and LNO tells you how hard to grind on it.
The other failure mode is relabeling everything urgent-and-important because saying "delete" or "delegate" feels uncomfortable. If all four quadrants are not populated, you are not being honest. The empty Q4 is the tell.
#Continue Reading
- The LNO Framework is Shreyas Doshi's effort-allocation companion: how hard to grind once a task survives triage.
- The Impact-Likelihood Matrix is my 2×2 for product-portfolio triage, where Eisenhower doesn't reach.
- Prioritization Frameworks for the full map of methods and matching them to the decision altitude.
- The Three Levels of Product Work for why "important" should mean impact, not optics.
- The Frameworks Toolkit for the full index of tools and when each earns its place.