When everything looks urgent, the urgency usually belongs to someone else's worry
On a Monday morning most of the messages carry the same word: urgent. The executive spends the day putting out fires, looks at the calendar in the evening to find that nothing has moved, and lives the same day again the next morning. This is usually described as a time-management problem. Looked at closely, it is a language problem: everyone on the team uses the same word, and the word no longer means anything.
Urgency, in its first sense, is a claim about time: if this waits, something breaks. Like any claim, it carries weight only when it is tied to a date and a cost. An urgent request with neither carries only the sender's worry, and hands it to the recipient.
Worry becomes urgency when it is handed over
When a sender marks a task urgent, they are often saying something else: I would rather not carry the weight of this any longer. It is rarely a deliberate move. The uncertainty starts with the sender, ends with the executive, and only a single word travels in between. When everything is urgent, the trouble is not the number of tasks; it is that urgency was never tied to a cost. A word with no cost behind it inflates, and as the team notices, it reaches for a louder one.
A team learns urgency from what the leader answers fastest, not from meetings
No team learns urgency in a meeting. It learns it from which messages the leader answers within minutes and which they answer days later. From the inside this does not feel like a choice; it feels like being attentive. From the outside, for the team, it reads as a price list.
Speed of reply is a reward
A fast reply is a reward, and rewarded behaviour multiplies. When a message with urgent in the subject line gets an answer quickly, two more people use the word the following week. The leader has said nothing and has still built a system. The team reads three signals from it:
- An email with urgent in the subject line is answered the same day.
- A topic caught in the corridor after a meeting jumps ahead of the one waiting on the weekly agenda.
- A short message that arrives in the evening outranks a detailed note that arrived in the morning.
The team is rarely the source of the urgency; it is repeating the tariff it learned from the leader. This is not an accusation. The leader set the tariff out of good intentions, wanting to be attentive and reachable, and what it produces is the opposite of what was intended.
Urgency grows with whoever gets the fast answer.
A task called urgent is urgent only when it can answer three questions
Three questions are enough to turn urgency from a word into a claim. Their purpose is not to turn the sender away but to complete the claim; a completed claim either earns the priority it deserves or shrinks on its own.
Three questions
When a task is called urgent, the leader asks:
- What breaks if this waits until tomorrow?
- Whose work does the broken thing touch?
- On what date does the damage become irreversible?
The answers are short, and they often surprise the sender too. Most tasks turn out to be movable to next week or passable to someone else. The small remainder is genuinely urgent and deserves a whole day, because what it is, whom it touches and how long it lasts are now known.
When no answer comes
If no answer comes, the task does not stop being urgent; it is only set aside. Urgency without an answer is a mood, not a claim, and a leader does not rank work by mood. When the sender brings the answer, the task moves to the front of the queue; when they do not, it waits. Either way the leader has made a decision, and it rests on a rule rather than on a person. A decision that does not rest on a person leaves no resentment behind.
Slowing the response is a harder decision than ranking the work
Asking the questions is easy. Slowing the reply is the hard part, because speed gives the leader something: being needed. The executive who answers within minutes feels important all day long. That feeling appears in no report, but it steers behaviour more strongly than almost anything else.
The cost of being reachable
Reachability is described as a virtue, and in most cases it is one. Past a certain point it also consumes the last uninterrupted hour in which the leader could do their own work. What remains is a leader who answers other people's questions and has no time to ask their own. In the coaching room we often ask one thing: at what moment in the day do you feel most truly needed, and why has that moment never been handed to anyone else.
Answering slowly is not indifference; it is attention tied to an hour and a sequence. A leader who opens two fixed response windows a day teaches the team that urgency is received with an answer rather than a word, and gives themselves an hour back.
From the field
Executives who come to talk with us about this usually ask for a ranking method. They describe their calendars, their message counts and their fires. Before offering any method we ask them to record one thing for a week: which message they answered, and how quickly.
A one-week reply log
At the end of the week most of them see the same thing: the work they answered fastest was not the most important work but the loudest. The log is not an accusation. It is a photograph that shows the executive, in their own hand, which language the team speaks and why.
Redefining urgency is not a calendar adjustment; it is teaching the team a new tariff, and the tariff changes only through the leader's own replies. The question in the piece on what an executive should focus on and the idea of choosing the ordering rule before the pressure arrives are the two sides of this one; how we work begins in that order. Other pieces from the same cluster are collected on the Perspective page.
When the speed of reply changes, the word the team uses changes with it. At the end of the day the leader sees not a calendar that went nowhere but a few chosen pieces of work that moved.