Surface the source of urgency before accepting it
Ask whose urgency it is and whether it was created by a missing upstream action.
Why it works
Team urgency is often manufactured: a task arrives as urgent because someone else didn’t plan, because a deadline was set without negotiation, or because a dependency wasn’t surfaced early. Accepting manufactured urgency rewards bad planning and punishes good planning — and over time, it trains the team to create urgency as a way to get priority. Tracing urgency to its source exposes the pattern and creates pressure to address it upstream rather than absorbing it as a permanent cost.
How to do it
- When a task arrives as urgent, ask: what event made it urgent today that wasn’t urgent last week?
- Identify whether the urgency is genuine (external deadline, new information) or manufactured (late planning, missed handoff).
- For manufactured urgency, handle the current task but name the upstream cause explicitly with the person who created it.
- Track patterns: which person or process consistently generates urgent tasks from avoidable causes.
Evidence
The mere-urgency effect shows that deadlines inflate the perceived importance of tasks independent of their actual value. In teams, urgency can also be a social signal — requesting something urgently gets it done faster, creating an incentive to escalate. (observational)
The mere-urgency research is on individuals, not teams; the social dynamics of manufactured urgency in groups is principled reasoning rather than a directly tested pattern.
Sources
- Zhu, Yang & Hsee (2018), the mere urgency effect, Journal of Consumer Research
Common mistake
Handling every urgent request without tracing its source, which makes the team a buffer for other people’s planning failures and means the root cause never changes.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Eisenhower Matrix for Teams
- Define "important" explicitly as a team
Before sorting tasks, align on what "important" means — which goals, for whom, over what time horizon.
- Protect important-not-urgent work as a team commitment
Schedule Q2 work on a shared calendar so urgent tasks can’t claim it by default.
- Establish an explicit delegation protocol for Q3 tasks
Define in advance who receives which types of urgent-but-not-important tasks — before they arrive.
- Run a regular team elimination review
Periodically review what the team is doing that no longer serves any current goal.
- Run a single weekly priority-setting meeting
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.