Why use the Eisenhower Matrix for an engineering manager's week?

An engineering manager's week is dominated by interrupt-driven work — bug escalations, on-call pages, status meetings, hiring loops — that is loud and urgent but not always important. The Eisenhower Matrix is a triage system that forces a second axis (importance) onto each item, exposing the urgent-but-not-important pile that should be delegated or dropped. Without that explicit triage, the week defaults to whatever shouts loudest, which is rarely what advances the team.

How often should an engineering manager re-do this matrix?

Weekly is the right cadence — Monday morning or Friday afternoon, depending on whether you prefer planning or recovery framing. Daily is too granular; quarterly is too coarse. The weekly cycle matches the rhythm of sprints, on-call rotations, and one-on-ones, which are the units the matrix is sorting. Build it into the same recurring meeting as backlog grooming if you have one.

What's a common mistake when applying the Eisenhower Matrix to manager work?

The most common mistake is putting everything an EM does into 'Important' because management work always feels load-bearing. The matrix only triages when the Important column is selective — typically 30–40% of items, not 80%. The honest test is: 'if this didn't happen this week, would anything meaningfully change in the team's output or trajectory?' Items that fail this test belong in Delegate or Drop.

Should the Schedule quadrant include 1:1s with reports?

Yes — 1:1s are the canonical Schedule-quadrant item for engineering managers. They are important (career trajectory, retention, blocker identification) but not urgent (skipping one week rarely surfaces an immediate problem). That combination is exactly why they get deprioritized when the week gets busy, which is exactly why scheduling them as recurring blocks is the right defense.

Eisenhower Matrix applied to an engineering manager's week

The Eisenhower Matrix is simple in theory and routinely abused in practice. Most managers I've watched run it produce a list where 90% of items end up in "Important + Urgent". This worked example shows what an honest run looks like.

The setup

A real engineering manager (anonymized) at a mid-size SaaS company, working through Monday morning planning. Carrying 18 items across her desk:

Q3 OKR review with VP today at 4pm
PR review for a senior eng's refactor PR (sitting 3 days)
1:1 with struggling junior eng tomorrow morning
CTO Slack: "got a sec to discuss the platform migration"
Compliance training overdue (auto-reminder #3)
Hiring panel debrief for two candidates
Incident retro from last Thursday's outage
Team's planning poker session Wednesday
New laptop request for new hire arriving Monday
Vendor invoice approval ($2k, due Friday)
Spec review for upcoming feature (eng wants feedback today)
Recurring "all-hands" presentation prep for next week
Team budget reforecast (quarterly)
Direct report's promotion case write-up (target: end of quarter)
Slack channel cleanup (15 stale channels)
Conference invite to evaluate (talk slot offered)
Coffee with peer EM in another org (postponed twice already)
Self-development reading: just-published book on platform engineering

The sort

The manager scored each item on (a) urgency = real consequence in 48 hours? and (b) importance = ladders to her quarterly goals? Goals were: ship platform migration milestone 1, retain the struggling junior, hire 2 senior engineers.

Important + Urgent — Do now

Item 1 (OKR review at 4pm) — non-negotiable
Item 7 (incident retro) — engineering culture depends on doing these promptly
Item 11 (spec review blocking eng today) — unblocks team

Important + Not Urgent — Schedule

Item 3 (1:1 with struggling junior) — central to "retain junior" goal
Item 6 (hiring debrief) — central to "hire 2 senior" goal
Item 14 (promotion write-up) — important to direct report's career
Item 4 (CTO Slack about platform migration) — looks reactive, actually important; book proper time
Item 8 (planning poker Wednesday) — team velocity, not urgent until Wednesday

Not Important + Urgent — Delegate

Item 2 (PR review) — sr eng can pair with another sr; not the manager's bottleneck
Item 9 (laptop request) — delegate to IT directly
Item 10 (invoice) — finance team has the workflow
Item 5 (compliance training) — 15 min, do it during a low-energy slot but don't elevate

Not Important + Not Urgent — Drop

Item 15 (Slack channel cleanup) — no one cares; archive in batch later if free
Item 12 (all-hands prep) — wait until Friday; over-prepping a 10-min talk is waste
Item 16 (conference invite) — pass this round
Item 17 (peer coffee) — keep on the calendar at low cadence, don't agonize
Item 18 (reading the book) — important for career, not this week; schedule in personal time
Item 13 (budget reforecast) — has 2 weeks; not this week

What this run revealed

Two things the manager learned:

Items 4 and 6 had been re-categorized for weeks. Item 4 (CTO platform conversation) had been pushed off because it didn't feel "urgent". Item 6 (hiring debrief) had been postponed twice. Both were Important + Not Urgent items — exactly the ones the matrix predicts get ignored without explicit scheduling.

The Drop quadrant was bigger than expected. The manager had been treating items 12, 15, 16, 17, 18 as low-priority but still on the list. The matrix forced an explicit "drop" decision, which felt uncomfortable until she said it out loud: "these are things I would do if I had infinite time. I don't."

Decisions made in 30 minutes

4pm OKR review: prepared in 15 min between meetings.
Tuesday 9am: 1:1 with junior, focus on whether scoping was the issue (not skill).
Wednesday: 90 min blocked specifically for the CTO platform conversation prep. Marked unmovable.
PR review delegated to sr eng pairing partner.
Compliance training: 15 min at 4:45pm after OKR review.
Items 15, 16, 18 explicitly cancelled. The list ended at 14 items, not 18.

Lessons that generalize

The discomfort of "drop" is the matrix doing its job. A 4-quadrant matrix where the bottom-right is empty hasn't been used honestly.
Important + Not Urgent is the quadrant most managers under-invest in. This run identified two such items that would have continued to slip without explicit scheduling.
30 minutes is the right time budget. Going longer doesn't sharpen the analysis; it usually produces more reasons to keep items rather than drop them.

Run your own

Open the Eisenhower Matrix worksheet →, or read the full Academy guide for the methodology.