The Urgency Trap

Something I've been sitting with after recent work with a team: almost everyone in the room described themselves as busy. And almost everyone said they rarely felt like they were getting anything done.

That gap deserves attention.

These were not disengaged people. Not uncommitted. Not disorganised. They arrived early, stayed late, and responded to messages within minutes. By every visible measure, they were performing. And yet at the end of most days, the work that actually mattered — the thinking, the planning, the decisions that move an organisation forward — hadn't happened.

What had filled the time instead? Urgency.

A message arrives. It says urgent.

Another one follows. Also urgent.

A meeting is scheduled last-minute.

Someone drops by the desk.

A notification.

A call.

A request that can't wait.

By 11am, the day has already been handed over to someone else's timeline.

The report that needed two hours of focused thought gets pushed to tomorrow. Tomorrow, the same thing happens. The report gets lighter — not because the person is lazy, but because there is genuinely no space left to do it well.

Responsiveness becomes the job.

Not because anyone decided that. Not because it was written into a job description. But because the culture rewards the person who replies fastest, who never seems unavailable, who is always on.

Being effective quietly falls behind being present.

And here is where it becomes a design problem rather than a discipline problem: the people most susceptible to urgency culture are often the most conscientious. They are the ones who feel the pull most acutely. The ones who say yes because they genuinely care. The ones who stay late not out of poor boundaries, but out of a deep sense of responsibility.

They are not failing the organisation. The organisation has built a system that consumes them.

Consider a mid-sized team in a growing company. The leadership is capable, the strategy is sound, and the people are experienced. But the team operates in a permanent state of reaction.

Decisions that should take an afternoon take three weeks — not because anyone is stalling, but because no one can find two consecutive hours to think. 

Projects get started and stalled, not from lack of commitment, but because every priority competes at the same volume. The most senior people are also the most interrupted, because they are the ones everyone needs access to.

In a recent conversation with one such team, a manager said something that stayed with me: "I know what needs to happen. I just can't get to it."

That sentence is not a time management problem. It is a structural diagnosis. The work that requires depth — the work that is actually hardest to replace — is being systematically crowded out by work that only requires availability.

Urgency culture rarely announces itself as a culture. It arrives as a series of reasonable requests.

The leader who prides themselves on being accessible. The team norm of fast responses. The implicit message that being unreachable — even briefly, even for focused work — is somehow a performance risk.

Individually, none of these is damaging. Collectively, they build an environment where deep work becomes structurally impossible. Not because the organisation intended it. Because no one designed against it.

This is the distinction worth sitting with: most organisations manage urgency reactively. They add more tools, more processes, more meetings to align on priorities. What they rarely do is examine how the environment itself produces urgency — and then redesign it.

What would it look like to treat focused time as a structural resource, not a personal luxury? To examine which interruptions are genuinely urgent and which have simply been allowed to feel that way? To design team rhythms that protect the work that most requires thought?

These are not questions about individual productivity. They are questions about how work is organised.

Where in your organisation is responsiveness quietly competing with effectiveness — and winning?

These are conversations I'm increasingly having with leadership teams across Mauritius. If this reflects something you're seeing inside your own organisation, I'd genuinely enjoy hearing your perspective.