Urgent vs important.
Eisenhower Matrix
Four quadrants: do, schedule, delegate, or delete. Forces ruthless honesty about where your time actually goes.
President Eisenhower observed that the most urgent things are rarely the most important — and the most important things are rarely urgent. His matrix splits every task into four quadrants based on two dimensions: urgency and importance. The insight is not the framework itself. The insight is what it reveals about where your time actually goes.
The four quadrants
Q1 (urgent + important): Do now. Crisis, deadline, system on fire. Q2 (not urgent + important): Schedule. Strategy, relationships, learning, prevention. This is where high performers live. Q3 (urgent + not important): Delegate. Most meetings, most pings, most requests. Q4 (not urgent + not important): Delete. Scroll, noise, busywork.
The real insight
Most people spend the majority of their time in Q1 and Q3 — reactive, urgent mode. Q2 is where you prevent Q1 from happening. Investing in Q2 (documentation, architecture, team processes, your own development) is the only lever that reduces the volume of Q1 long-term. If you're always firefighting, it's because you're not investing in prevention.
The delegation problem
Most knowledge workers under-delegate Q3 because delegating feels like overhead. 'It's faster to just do it.' That's true in the short term. Over time, you become the bottleneck for things that didn't require your involvement. The test: if this task disappeared entirely, would anything important suffer? If no — delete. If a capable person could handle it — delegate.
In engineering leadership
Q2 for eng leaders: 1:1s, technical roadmap thinking, architectural review before urgency forces a bad decision, investing in engineers' growth. These feel optional because they're never on fire. They are not optional — they determine whether everything else catches fire.
In practice
Your week: Monday standup, three Slack threads needing answers, two urgent bugs, a backlog grooming session, prep for your skip-level, reading about a new AWS service. Map them: bugs → Q1. Skip-level prep → Q1. Slack threads → mostly Q3 (can you delegate?). Grooming → Q2. AWS reading → Q2. Standup → Q3 (can it be shorter?). Now schedule the week around Q1 and Q2.
TL;DR
Urgent ≠ important. Protect Q2 (important but not urgent) — that's where prevention and growth live.