Urgency is useful only when it helps people distinguish what must move first.

Some organizations have four priority levels.

In practice, they use one: urgent.

The client request is urgent. The executive request is urgent. The project deadline is urgent. The audit question, access request, dashboard correction, and meeting follow-up are all urgent.

Eventually, “urgent” stops being a priority. It becomes punctuation.

Employees are left to decide what really matters by reading titles, relationships, escalation volume, and who appears most likely to complain. That is not prioritization. It is organizational noise converted into personal judgement.

The IT delivery example: the storage work that kept moving

Imagine a Storage Operations team supporting the virtual infrastructure behind several customer-facing applications.

Capacity monitoring shows one production array has reached 82 percent utilization. Growth projections suggest it could exceed the safe operating threshold within three weeks. The team prepares an expansion change, confirms the required hardware, and books a maintenance window.

Then the urgent requests begin.

A senior executive needs files restored before a board meeting. An analytics project requests additional capacity before a demonstration. A test environment must be cloned for a release team. Finance asks for an immediate backup retrieval to support an audit.

Each request arrives through a different leader. Each is labelled critical. Several bypass the queue through direct messages and meeting escalations.

The storage expansion is moved once, then again. An analyst raises the capacity risk during the operations call, but the team is told to “handle both.” No work is removed. No leader accepts the trade-off.

Two weeks later, a failed backup job leaves unexpected snapshots on the array. Utilization climbs rapidly overnight and reaches its limit. Virtual machines begin pausing. Database response times rise. Customer applications become unavailable, and the Service Desk is flooded with calls.

The organization declares a major incident.

The capacity work was never unimportant. It simply had no influential person creating noise on its behalf.

The consequences are wider than a crowded queue

For employees: priorities feel political and unstable. People spend energy renegotiating work, defending choices, and reacting to interruptions. Over time, they may stop trusting official priorities and focus on protecting themselves from the next escalation.

For service delivery: planned risk reduction is repeatedly displaced by visible short-term demand. Work starts but does not finish, technical debt grows, and the queue no longer represents the order in which work will actually be completed.

For customers: response becomes inconsistent. The loudest customer may receive immediate attention while a quieter but more consequential risk waits. When preventive work is delayed, customers eventually experience failures that were both foreseeable and avoidable.

For the organization: leaders mistake rapid reaction for responsiveness. Costs rise through rework, incident recovery, overtime, and delayed projects. The organization becomes very good at accelerating individual requests and very poor at protecting the whole service.

What human behaviour tells us

Urgent signals naturally attract attention. That is useful when a genuine threat requires fast action. The difficulty is that attention is limited, and repeated high-intensity signals make it harder to distinguish one important demand from another.

Related patterns are often discussed through attentional capture, habituation, and alarm fatigue. Those concepts do not prove what any individual employee is experiencing. The practical lesson is simpler: when everything carries the same warning label, the label loses information.

Employees then create substitute rules. They may prioritize the most senior requester, the newest message, the angriest voice, or the work most likely to appear on a dashboard. These are understandable adaptations to ambiguity—but they are poor replacements for leadership decisions.

Lessons for managers

  • Define urgency with observable criteria. Customer impact, safety, regulatory exposure, service interruption, and time sensitivity are stronger signals than job title or volume.
  • Name the trade-off. When new work moves forward, identify what will move back and who accepts the resulting risk.
  • Protect preventive work. Capacity, maintenance, patching, and documentation should not need a crisis to become important.
  • Limit work in progress. Starting everything quickly usually means finishing everything slowly.
  • Give the queue an owner. Employees should not have to negotiate conflicting executive demands one conversation at a time.

Lessons for organizations

  • Create shared priority definitions across business and technology teams.
  • Make out-of-queue and VIP requests visible in capacity and risk reporting.
  • Require leaders to approve the displacement caused by expedited work.
  • Measure completed outcomes, aging risk, and interruption cost—not merely response speed.

Key takeaways

  • If everything is urgent, employees are receiving pressure rather than direction.
  • Priority inflation moves decision-making from governance into personal judgement.
  • The loudest request is not necessarily the most consequential work.
  • Every expedited item creates a trade-off that should be visible.
  • Preventive work needs protection before it becomes an incident.

Discussion question: In your organization, what actually determines whether work moves to the front of the queue?