Quick Answer (TL;DR)
The Eisenhower Matrix is a 2x2 grid that sorts tasks into four quadrants based on two axes: urgency (time-sensitive or not) and importance (moves the needle on goals or not). The four quadrants are: Do (urgent + important), Schedule (important + not urgent), Delegate (urgent + not important), and Eliminate (neither). Named after U.S. President Dwight D. Eisenhower, who reportedly said: "What is important is seldom urgent, and what is urgent is seldom important." For PMs, the framework is a fast triage tool for incoming requests, stakeholder asks, and your own task list.
What Is the Eisenhower Matrix?
The Eisenhower Matrix (also called the Urgent-Important Matrix) is a decision framework that forces you to evaluate every task on exactly two dimensions: whether it requires immediate action, and whether it contributes to your goals. The insight behind the matrix is that humans are wired to respond to urgency. A Slack message pinging right now feels more pressing than a strategy doc due next Friday, even when the strategy doc matters ten times more to the product's success.
Dwight D. Eisenhower used this principle to manage his time as Supreme Allied Commander and later as President. Stephen Covey popularized the 2x2 grid format in The 7 Habits of Highly Effective People.
For product managers, the matrix solves a specific problem: you receive more requests than you can handle, from more directions than you can track. Feature requests, bug reports, stakeholder asks, team questions, customer escalations, strategic initiatives. Without a triage system, you default to working on whatever is loudest, which usually means the urgent-but-unimportant quadrant eats your calendar.
The Four Quadrants
Quadrant 1: Do (Urgent + Important)
These tasks require immediate action and directly affect your goals. Handle them now.
Characteristics:
- Clear deadline (today or this week)
- Direct impact on a key metric, customer, or team commitment
- Consequences of delay are significant
PM examples:
| Task | Why It's Q1 |
|---|---|
| Production bug blocking 30% of users | Urgent: users are affected now. Important: retention metric at risk |
| Board presentation due tomorrow | Urgent: hard deadline. Important: funding and strategic alignment |
| Critical customer escalation from enterprise account | Urgent: customer is waiting. Important: $200K ARR at risk |
| Sprint-blocking dependency from another team | Urgent: team is idle. Important: sprint commitment at stake |
The trap: If most of your week is in Q1, you are firefighting. Some Q1 work is inevitable, but a consistently full Q1 means you are underinvesting in Q2 (planning and prevention), which creates more fires.
Quadrant 2: Schedule (Important + Not Urgent)
These tasks move the needle on your goals but have no pressing deadline. This is where PMs create the most value and where most PMs spend too little time.
Characteristics:
- High strategic value
- No immediate deadline (or a deadline weeks/months away)
- Easy to postpone because nothing breaks if you skip it today
PM examples:
| Task | Why It's Q2 |
|---|---|
| User research interviews for next quarter's roadmap | Important: informs strategy. Not urgent: no one is asking for it today |
| Writing a product strategy doc | Important: aligns the team. Not urgent: ship dates don't depend on it this week |
| Building relationships with key stakeholders | Important: enables future decisions. Not urgent: no meeting on the calendar |
| Reviewing analytics dashboards for emerging trends | Important: catches problems early. Not urgent: no alert has fired |
| Improving onboarding flow based on funnel analysis | Important: activation is a key metric. Not urgent: current flow "works" |
The principle: Protect Q2 time aggressively. Block 2-3 hours per day for Q2 work. The more time you invest here, the fewer Q1 emergencies you will face in future weeks. Strategy work, relationship building, and proactive discovery all live in Q2.
Quadrant 3: Delegate (Urgent + Not Important)
These tasks feel pressing because someone is waiting or a deadline exists, but they don't contribute to your most important goals. Hand them off.
Characteristics:
- Someone else needs a response or action from you
- The work itself doesn't require your unique expertise or authority
- Saying "no" or redirecting feels socially awkward, which is why you end up doing it
PM examples:
| Task | Why It's Q3 | Who to delegate to |
|---|---|---|
| Formatting a slide deck for a stakeholder | Urgent request, but template work | Design or a PM coordinator |
| Triaging P3/P4 bug reports | Needs doing, but doesn't need your judgment | Engineering lead or QA |
| Writing release notes for a minor update | Has a deadline, but standard process | PMM or technical writer |
| Answering a routine customer question about pricing | Customer is waiting, but it's a known answer | Customer support or sales |
| Scheduling a cross-team sync | Calendar coordination, not product thinking | EA or project coordinator |
The challenge for PMs: Many PMs struggle with delegation because they feel responsible for everything. But time spent on Q3 tasks is time stolen from Q2 strategic work. Ask: "Am I the only person who can do this?" If the answer is no, delegate.
Quadrant 4: Eliminate (Not Urgent + Not Important)
These tasks contribute nothing to your goals and have no deadline pressure. Stop doing them.
Characteristics:
- No meaningful impact on any metric or relationship
- Often habitual (you do them because you always have)
- Feel productive in the moment but produce no output
PM examples:
| Task | Why It's Q4 |
|---|---|
| Attending a recurring meeting where you contribute nothing | Neither urgent nor important to your role |
| Polishing a roadmap slide that three people will see | Diminishing returns on visual perfection |
| Reading every Slack channel message in real time | Information snacking, not decision-making |
| Building a dashboard nobody has asked for | No audience, no decision it informs |
| Over-researching a decision that has already been made | Sunk-cost research behavior |
Be honest: Most PMs have 3-5 hours per week of Q4 activity hidden in their schedule. Identifying and eliminating these frees up a meaningful block for Q2 work.
The Eisenhower Matrix as a Visual
| Urgent | Not Urgent | |
|---|---|---|
| Important | Q1: DO (Crises, hard deadlines, blocking issues) | Q2: SCHEDULE (Strategy, discovery, relationship building) |
| Not Important | Q3: DELEGATE (Routine requests, formatting, low-stakes coordination) | Q4: ELIMINATE (Busywork, information snacking, unnecessary meetings) |
The goal is to spend most of your time in Q2. Q1 will always exist, but minimizing it is a sign of good planning. Q3 and Q4 should be as small as possible.
How to Use the Eisenhower Matrix Step by Step
Step 1: List Everything on Your Plate
Write down every task, request, and project you are currently tracking or feel responsible for. Include stakeholder asks, backlog items, meetings, and personal development tasks. Aim for 15-30 items.
Step 2: Define Your "Important" Criteria
Before sorting, define what "important" means for you right now. Tie it to your current goals. If your quarterly OKR is to improve activation rate, then tasks that affect activation are important. Tasks that affect something else may still be worth doing, but they are less important to you.
For feature prioritization, importance usually maps to impact on your key metric. For personal task management, importance maps to your career goals and team commitments.
Step 3: Sort Each Item into a Quadrant
For each task, ask two questions:
- Is this time-sensitive? Does it need to happen today or this week, or will something break if it waits?
- Does this move my key goals forward? Will completing this task affect a metric, decision, or outcome I am responsible for?
Place each item in the corresponding quadrant.
Step 4: Act on Each Quadrant
- Q1 (Do): Work on these first. Time-box them if possible to avoid them consuming your entire day.
- Q2 (Schedule): Put specific time blocks on your calendar for each Q2 item. If it doesn't have a calendar slot, it won't happen.
- Q3 (Delegate): Identify who can handle each item. Send a clear request with context and deadline.
- Q4 (Eliminate): Remove these from your to-do list. Decline the meeting. Unsubscribe from the channel. Let it go.
Step 5: Review Weekly
At the start of each week, re-sort your tasks. What was Q2 last week may have become Q1 as a deadline approaches. New Q3 requests may have arrived. A 10-minute weekly review keeps the matrix current.
Example: SaaS PM Using the Eisenhower Matrix
Sarah is a PM at a B2B project management SaaS. Her quarterly OKR is to increase 14-day trial-to-paid conversion from 9% to 14%. Here is how she sorts her Monday morning task list:
| Task | Quadrant | Reasoning | Action |
|---|---|---|---|
| Fix checkout bug that blocks 12% of trial conversions | Q1: Do | Urgent (losing revenue now) + Important (directly affects OKR) | Fix with engineering today |
| Design new onboarding flow based on user interviews | Q2: Schedule | Important (will improve activation) + Not urgent (current flow works, just suboptimal) | Block 3 hours Thursday |
| Write quarterly business review slides | Q3: Delegate | Urgent (VP wants it by Wednesday) + Not important (reporting, not product work) | Ask PM coordinator to draft first version |
| Attend weekly all-hands (no PM-relevant agenda items) | Q4: Eliminate | Neither urgent nor important to her OKR | Decline and read the recording notes |
| Respond to sales team asking for a custom demo | Q3: Delegate | Urgent (deal closing this week) + Not important (SE can handle it) | Forward to solutions engineer |
| Run RICE scoring session for Q3 backlog | Q2: Schedule | Important (sets next quarter's direction) + Not urgent (Q3 is 6 weeks away) | Schedule for next Tuesday |
| Research competitor's new pricing tier | Q2: Schedule | Important (strategic input) + Not urgent (no decision pending) | Add to Friday research block |
After sorting, Sarah's day is clear: fix the checkout bug this morning (Q1), delegate the QBR slides and sales demo (Q3), skip all-hands (Q4), and protect Thursday for onboarding design (Q2).
When to Use the Eisenhower Matrix
Good fit:
- Daily personal task triage (10 minutes each morning)
- Quick stakeholder request sorting during a busy week
- Sprint planning triage when the backlog is messy
- Coaching a junior PM on time management
- Team retrospectives to identify Q4 time sinks
Poor fit:
- Ranking 50+ features against each other (use RICE scoring or weighted scoring instead)
- Deciding between strategic bets with similar urgency profiles
- Complex multi-team prioritization where dependencies matter
- Any situation where you need a numerical score to compare items objectively
The Eisenhower Matrix is a sorting tool, not a scoring tool. It divides tasks into four buckets but doesn't rank items within each bucket. For backlog prioritization at scale, pair it with a quantitative framework. Use Eisenhower to filter your backlog down to the important items, then use RICE to rank them.
Limitations
Urgency is subjective. What feels urgent to a stakeholder may not actually be time-sensitive. PMs often overweight urgency because saying "this can wait" is socially uncomfortable. Before placing something in Q1 or Q3, ask: "What specifically happens if this waits until next week?"
Importance requires clear goals. If you don't have defined quarterly goals or OKRs, the "important" axis becomes arbitrary. The matrix only works when you have a clear definition of what matters right now.
Two dimensions aren't always enough. The matrix ignores reach (how many users are affected), confidence (how sure you are), effort (how long it takes), and dependencies (what blocks what). For a more complete picture, the RICE framework adds those dimensions. The MoSCoW method adds stakeholder alignment.
Delegation requires a team. Solo founders and one-person PM teams can't delegate Q3 work. In that case, Q3 becomes "batch and time-box": handle these tasks in a single, limited time block rather than letting them interrupt deep work throughout the day.
Combining the Eisenhower Matrix with Other Frameworks
Eisenhower + RICE
Use Eisenhower to sort incoming requests into four buckets. Then take everything from Q1 and Q2 and score it with RICE to determine execution order. This gives you the speed of qualitative triage plus the precision of quantitative ranking.
Eisenhower + MoSCoW
Use Eisenhower for your personal task management and MoSCoW for release scope discussions with stakeholders. The Eisenhower Matrix is individual-focused. MoSCoW is team and stakeholder-focused.
Eisenhower + Roadmapping
When building a product roadmap, the Q2 quadrant is where your best roadmap themes live. These are the important, non-urgent strategic initiatives that create long-term value. Q1 items belong in your current sprint, not on a quarterly roadmap.
Best Practices
Be Ruthless About Q4
The biggest productivity gain comes not from doing Q1 faster, but from eliminating Q4 entirely. Audit your calendar every two weeks. Any meeting or recurring task where you contribute nothing and learn nothing is a candidate for elimination.
Protect Q2 with Calendar Blocks
Q2 work is the first thing to get bumped when a Q1 fire erupts. Defend against this by booking Q2 time on your calendar as immovable blocks. Treat them like external meetings. Label them with the specific deliverable: "Q2: User interview synthesis" is harder to cancel than "Focus time."
Batch Q3 Tasks
Instead of letting Q3 interruptions fragment your day, batch them into a single 30-60 minute block. Respond to routine Slack questions, approve standard requests, and handle administrative tasks all at once.
Revisit "Urgent" Claims
When a stakeholder says something is urgent, ask three questions: (1) What happens if we don't do this today? (2) What happens if we wait until next week? (3) Who else could handle this? Half the time, "urgent" really means "I thought of this just now and want to get it off my plate."
Use It as a Communication Tool
The matrix is effective for explaining prioritization decisions to stakeholders. "I've classified this as important but not urgent, so I've scheduled it for next sprint" is clearer and less confrontational than "It's not a priority right now."
Getting Started
- Write down every task and request currently on your plate (15-30 items)
- Define your current quarter's top 2-3 goals (these determine "important")
- Sort each item into one of the four quadrants
- Block calendar time for your Q2 items this week
- Delegate or decline everything in Q3 and Q4
- Review and re-sort every Monday morning (10 minutes)
The Eisenhower Matrix won't replace quantitative prioritization for your product backlog. What it will do is help you reclaim 5-10 hours per week from busywork, stakeholder requests, and unnecessary meetings so you can invest that time in the strategic work that actually moves your product forward.