Prioritize Importance Over Urgency
Spend energy on what truly matters, not what screams the loudest
The Trap
Most teams spend their days reacting: fixing the bug that just got reported, responding to the email that just arrived, picking up the task that's easiest to check off. At the end of the week, everyone was busy, but nothing meaningful moved forward.
This happens because urgency and ease are powerful psychological forces. Important work — refactoring a fragile system, having a difficult conversation, rethinking a flawed process — is often neither urgent nor easy. So it gets postponed indefinitely.
The Eisenhower Distinction
| Urgent | Not Urgent | |
|---|---|---|
| Important | Do it now (crises, real deadlines) | Schedule it — this is where growth lives |
| Not Important | Delegate or timebox (interruptions, most emails) | Eliminate (busywork, unnecessary meetings) |
The key insight: the "Important but Not Urgent" quadrant is where almost all lasting improvements come from. Better architecture, stronger team skills, clearer processes, deeper relationships — all of these are important but never urgent, and they are exactly what separates great teams from mediocre ones.
How to Apply This
As a manager
- Protect time for important work: Block time on the calendar for strategic thinking, system design, and one-on-ones. Treat these blocks as non-negotiable.
- Question urgency: When something feels urgent, ask "What happens if we handle this tomorrow? Next week?" Often the answer reveals it isn't truly urgent.
- Resist the easy win: Completing ten small tasks feels productive but may matter less than making progress on one hard problem. Track impact, not task count.
- Make the important visible: If technical debt, team development, or process improvement are never on the sprint board, they will never get done. Put them on the board.
As a team
- Allocate capacity deliberately: Reserve a fixed percentage of each sprint for important-but-not-urgent work (tech debt, tooling, learning). Don't let feature requests consume 100% of capacity.
- Evaluate with "so what?": Before starting a task, ask "If we complete this, so what? What changes?" If the answer is small, it probably isn't important.
- Say no more often: Every "yes" to an unimportant task is an implicit "no" to something that matters. The team's most precious resource is focus.
Watch Out For
- Firefighting addiction: Some teams become so accustomed to reacting that they feel uncomfortable with proactive work. If you're always firefighting, something is structurally wrong.
- Confusing difficulty with importance: Hard tasks aren't automatically important. Easy tasks aren't automatically unimportant. The question is always "What impact does this have?"
- Planning without doing: Recognizing what's important is step one. Actually doing it — especially when there's no deadline forcing you — requires discipline and accountability.