Is the Eisenhower Matrix part of GTD?

Not officially. David Allen's original GTD is agnostic about prioritization — the assumption is that if your system is trusted and complete, you'll make good in-the-moment decisions. But most GTD practitioners add a prioritization layer, and the Eisenhower Matrix is the most common choice. The integration point is the Clarify step: when GTD asks 'what's the next action?', Eisenhower asks 'is that action urgent, important, both, or neither?'

Can I use the Eisenhower Matrix without GTD?

Yes, but you'll hit limits. The Eisenhower Matrix sorts tasks you already have — it doesn't help you capture new inputs or keep your system current. Without a capture-and-review workflow like GTD, items slip through, the matrix goes stale, and you end up re-deciding what to do every morning instead of trusting a system.

What's the biggest mistake when combining GTD and Eisenhower?

Prioritizing before clarifying. If you try to sort items into Eisenhower quadrants before GTD's Clarify step, you're sorting vague 'stuff' — emails, ideas, requests — rather than concrete next actions. Prioritization only works when you know what the task actually is. GTD's Clarify step must come first.

Which system is better for teams?

GTD is inherently personal — David Allen designed it for individual knowledge workers. The Eisenhower Matrix scales better to teams because the two axes (urgent, important) can be defined at a team level. For team backlogs, consider RICE or MoSCoW instead, which are built for shared prioritization.

Eisenhower Matrix vs GTD: which productivity system to use

The Eisenhower Matrix and GTD (Getting Things Done) are the two most-used personal productivity systems — and they solve different problems. The Eisenhower Matrix is a prioritization tool: it sorts the tasks you already have by urgent vs important, so you know what to do first. GTD is a workflow system: it captures everything that has your attention, clarifies what each item means, and organizes it into a trusted system so nothing slips through.

Most debates about "which is better" miss the point: they operate at different layers. The best practitioners use both — GTD as the workflow, Eisenhower as the prioritization engine inside it.

New to either? See the Eisenhower Matrix explained and the GTD catalog entry.

At a glance

	Eisenhower Matrix	GTD
Type	Prioritization tool	Workflow system
Core question	"What do I do first?"	"What has my attention, and what do I do about it?"
Inputs	Tasks you already have	Everything — emails, ideas, commitments, vague worries
Outputs	Four quadrants with action verbs (Do, Schedule, Delegate, Drop)	Trusted lists: Next Actions, Projects, Waiting For, Someday/Maybe
Cadence	Weekly or daily triage	Ongoing capture + weekly review
Weakness	Doesn't capture or process inputs — only sorts what you give it	Doesn't prioritize — assumes you'll decide in the moment
Origin	Dwight Eisenhower; popularized by Stephen Covey (1989)	David Allen (2001)
Best for	Deciding what to do today	Clearing mental clutter and trusting your system

What the Eisenhower Matrix is best for

Deciding what to work on next, by trading off urgency and importance.

The Eisenhower Matrix assumes you already have a list of tasks — and you need to triage them. It plots each task on two axes:

Urgent: Does it have a deadline or external pressure?
Important: Does it advance a goal you've committed to?

The four quadrants imply four actions:

Important + Urgent → Do now. Crises, deadlines, customer escalations.
Important + Not Urgent → Schedule. Strategy, learning, deep work — the quadrant most people under-invest in.
Not Important + Urgent → Delegate. Other people's priorities flowing through you.
Not Important + Not Urgent → Drop. Activities that feel productive but aren't.

Use the Eisenhower Matrix when:

You have too many tasks and need a triage rule
You're confusing "loud" with "important" and reactive weeks are eating strategic work
You want a quick 15-minute exercise to reset your priorities for the day or week

Its blind spot: it doesn't help you capture or process inputs. If tasks aren't already on a list, the matrix can't sort them. And if the list is stale or incomplete, the matrix's output is only as good as its input.

What GTD is best for

Capturing everything and building a trusted external system.

GTD's core claim is that stress comes from open loops — commitments, ideas, and worries stored in your head rather than a trusted external system. The 5-step workflow externalizes everything:

Capture — Collect anything that has your attention into an inbox (physical, digital, or both).
Clarify — For each item: Is it actionable? If yes, what's the next physical action? If no, is it trash, reference, or someday/maybe?
Organize — Put the clarified item in the right place: calendar (time-specific), next-action list (context-specific), project list (multi-step outcomes), waiting-for, someday/maybe, or reference.
Reflect — Weekly review: process all inboxes, review all projects, check the calendar, and ask "is this system current?"
Engage — Do the work, trusting that you're working on the right thing because everything else is captured.

Use GTD when:

You feel overwhelmed by the sheer volume of inputs (email, Slack, meetings, ideas)
You keep forgetting commitments or rediscovering the same tasks
You want a system that handles any kind of input without special-case rules

Its blind spot: it doesn't prioritize. David Allen's original GTD assumes that if your system is trusted, you'll make good in-the-moment decisions about what to do. But many practitioners find that a list of 50 next actions with no ranking leads to decision fatigue — and reach for a prioritization layer to fill the gap.

The decision rule

Use GTD as the workflow. Use Eisenhower as the prioritization layer inside it.

This isn't "pick one" — it's "use both at the right layer." Here's how they fit together:

GTD Capture — Everything goes into the inbox. Eisenhower doesn't touch this step.
GTD Clarify — Ask "what's the next action?" Once you know the action, then ask the Eisenhower questions: is it urgent? Is it important?
GTD Organize — Place the item based on both GTD category (calendar, next-action, waiting-for) and Eisenhower quadrant. A "Not Important + Urgent" task might still be a next action — but it's tagged for delegation or batching.
GTD Reflect — Weekly review includes re-triaging the Eisenhower quadrants. Items that were urgent last week may have dropped off.
GTD Engage — When it's time to work, filter by Eisenhower quadrant. Work the Important + Urgent items first, then the Important + Not Urgent items you've scheduled.

The Clarify-Then-Prioritize Rule

A named integration protocol: never apply the Eisenhower Matrix to unclarified 'stuff.' If you try to sort vague inputs ("that email from Sarah," "the marketing thing") into urgent/important quadrants before GTD's Clarify step, you're sorting fog. The Eisenhower Matrix only works on concrete next actions — and GTD's Clarify step is what produces those.

Step	GTD asks	Eisenhower asks
Capture	"What has my attention?"	(nothing yet)
Clarify	"Is it actionable? What's the next action?"	"Is this action urgent? Is it important?"
Organize	"Where does it live?"	"What's the default verb — do, schedule, delegate, drop?"
Reflect	"Is my system current?"	"Have any quadrants shifted since last week?"
Engage	"What can I do right now, given my context?"	"Am I working on Q1/Q2 or drifting into Q3/Q4?"

The integration point is Clarify. Once GTD has turned vague "stuff" into a concrete next action, Eisenhower can sort it. Not before.

How a Stripe PM would use both

To ground this in a real scenario: a product manager at Stripe running a payments-infrastructure squad.

Monday morning. The PM opens their inbox: 23 emails, 14 Slack threads, 3 docs shared for review, a vague reminder about "the compliance thing." This is stuff, not tasks.

GTD Capture + Clarify. The PM processes each item:

Email from legal about PCI audit → next action: "Schedule 30-min sync with compliance lead" → Important + Urgent (regulatory deadline)
Slack thread about a customer bug → next action: "Review Jira ticket #4521 and comment on severity" → Important + Urgent
Doc shared for review → next action: "Read and comment on API proposal by Friday" → Important + Not Urgent → Schedule for Thursday deep-work block
Vague "compliance thing" → Clarified: it's the same PCI audit, already captured

Eisenhower triage at the end of Clarify. 7 tasks land in Q1 (do now), 4 in Q2 (schedule), 3 in Q3 (delegate — the PM forwards to the junior analyst), 5 in Q4 (drop — outdated threads, FYI emails that require no action).

Weekly review (GTD Reflect). The PM asks: "Are all my projects current? Are any Q2 items now Q1 because deadlines shifted?" The PCI audit moved from Q2 to Q1 over the week — the matrix gets re-run.

Engage. When it's time to work, the PM filters by Eisenhower quadrant. Q1 first. Then the scheduled Q2 blocks. Q3 was delegated. Q4 was deleted.

This is the full integration: GTD provides the workflow (capture everything, clarify into actions, organize, review weekly, engage). Eisenhower provides the prioritization lens at the Clarify and Reflect steps.

Edge cases / combined use

What if I only have 15 minutes a day? Run the Eisenhower Matrix on whatever's in front of you — email inbox, sticky notes, mental list. It's better than nothing. But you'll eventually hit the limit: items slip through because there's no capture system. When that happens, add GTD's Capture and Weekly Review.

What if I'm a solo founder with no one to delegate to? The Delegate quadrant becomes "automate or batch." Low-importance, high-urgency tasks still exist — but instead of handing them off, you cluster them into a single time block (email hour, admin hour) so they don't interrupt deep work.

What if I need to prioritize a team backlog, not personal tasks? Neither system is designed for shared prioritization. GTD is explicitly personal. The Eisenhower Matrix can be adapted for teams, but "urgent" and "important" become contested terms. For team backlogs, consider RICE (quantified scoring) or MoSCoW (scope bucketing) instead.

Run them

Eisenhower Matrix explained → · GTD catalog entry → · Eisenhower applied to an engineering manager's week →

Also compare

Eisenhower vs Covey Matrix — the same urgent/important grid used to triage today vs to redesign where your weeks go
Eisenhower vs Impact/Effort Matrix — execution-layer triage vs selection-layer initiative picking
RICE vs MoSCoW — for team prioritization, not personal productivity

Sources

Dave Edwards Media — "Can the Eisenhower Matrix Be Used With GTD?"
Productivity Patrol — "Elevate Your GTD Game: The Key to Effective Prioritization"
GTD Forums — "Success with Eisenhower Matrix?"
David Allen, Getting Things Done: The Art of Stress-Free Productivity (2001).
Stephen Covey, The 7 Habits of Highly Effective People (1989).

Want to run the Eisenhower Matrix on your phone? Framework for iPhone & iPad — sort your tasks into the four quadrants with AI assistance. Free to start.