Unnecessary Urgency

Somewhere along the way, "urgent" became the default label for everything.

In field telecom, I watched it happen daily. The client marks a work order urgent. The crew lead marks the audit urgent. The office marks the timesheet urgent. By 9am, you have eleven urgent things and a crew standing around waiting to be told which fire to put out first. Here's what nobody says out loud: most of it isn't urgent. It's just loud.

Urgency is a currency, and like any currency, it devalues the more you print. When everything is urgent, the word stops meaning "this needs action now" and starts meaning "I want your attention." Those are very different things, and confusing them is how projects quietly fall apart — not in a dramatic failure, but in the slow bleed of a team that sprinted at everything and finished nothing.

I learned to run every "urgent" request through three questions before moving a muscle:

1. What actually breaks if this waits until tomorrow?
Not "what gets delayed" — what breaks. A missed client SLA with penalties is urgent. A report someone wants to glance at before a meeting is not, no matter how many exclamation marks are in the email. If nothing breaks, it's important at best, and important has a schedule.

2. Who decided this is urgent — and when?
Urgency set by the person doing the work, close to the deadline, is usually real. Urgency declared three weeks early by someone three layers removed is usually anxiety wearing a costume. Trace it to the source. The source tells you everything.

3. Is the deadline the real deadline?
There is the date something is due, and then there is the date someone said it's due because they wanted buffer, or because "ASAP" felt safer than a real date. Ask. Half the time, the real deadline is days later than the announced one, and the panic was entirely manufactured.

These three questions take ninety seconds. They have saved me more hours than any productivity system I've ever tried, because they do something no system does: they give you permission to not react.

There's a second half to this, and it's the harder one. Once you've identified what's actually urgent, you have to say no to the rest — out loud, to people, with your name on it. "This can wait until Thursday, and here's why" is a complete sentence. Most coordinators I know struggle here, not with the triage but with the telling. Say it anyway. A team that trusts your judgment on what can wait will trust your judgment on what can't.

And when something is genuinely urgent — the tower crew waiting on a design revision, the client escalation with a real clock on it — you'll have something left to give it. That's the whole point. Urgency is a finite resource. Spend it where it counts, and stop spending it where it doesn't.

The loudest request in the room is rarely the most important one. Your job is to know the difference, and to act like it.