When Urgency Becomes the Operating Model

I would put one question in the center of the leadership table: What are we teaching people when nearly everything arrives as urgent?

We may believe we are communicating importance. The organization may be learning something else.

It may be learning that priorities are temporary, that focus is unsafe, and that the fastest interruption has more authority than the clearest strategy.

Urgency has a legitimate place. A customer may be at risk. A system may be failing. A legal or safety issue may require immediate action. A critical commitment may be close to breaking.

The problem begins when that exception becomes the operating model.

Microsoft's 2025 Work Trend Index described what it called an infinite workday. Its analysis drew on globally aggregated Microsoft 365 activity and a survey of 31,000 knowledge workers across 31 markets. It found that the average worker received 117 emails and 153 Teams messages on a weekday. Nearly one in three employees surveyed said it was impossible to keep up with the pace of work.

That research reflects Microsoft users and knowledge work. It does not describe every worker or every organization. It does, however, make visible a pressure many leadership teams should examine: people can be busy from the beginning of the day to the end and still lack enough uninterrupted time to complete the work that matters most.

The American Psychological Association's 2025 Work in America survey adds another view. Conducted among more than 2,000 working adults in the United States, it examined how technological, economic, and policy changes were affecting workers. Its questions included workload, long hours, unclear expectations, lack of participation in decisions, and work interfering with personal or family time as possible sources of stress.

Those are not separate culture issues. They are signals about how work is being governed.

At the executive level, chronic urgency can look like responsiveness. At the manager level, it often becomes constant reprioritization without permission to remove anything. At the employee level, it can mean deciding which commitment to disappoint while trying to appear fully committed to all of them. Partners and vendors experience it as scope that changes faster than accountability does.

Then the system produces exactly what it trained people to do.

Teams hedge instead of committing. Managers protect their people by quietly delaying something else. Employees keep too many tasks open because closing one feels risky. Decisions move upward because no one wants to make the wrong call inside priorities that may change tomorrow.

The performance consequence is not only exhaustion. It is weaker judgment.

When everything is urgent, people have less room to notice a defect, question an assumption, improve a process, or tell a leader that the deadline and the standard no longer fit together. Speed may rise briefly while rework, missed context, and hidden risk accumulate behind it.

The industry response has included focus blocks, meeting-free days, workload surveys, employee listening, manager training, AI assistants, and new collaboration norms. Those moves can help. Microsoft itself argues that AI should be paired with a redesigned rhythm of work, because accelerating a broken system does not repair it. APA recommends that organizations respond proactively to change and build greater alignment between leadership and the workforce.

I agree with both directions.

I also believe neither works if the leadership table keeps adding priority without making a tradeoff visible.

A focus block cannot protect an employee from five executives who each believe their request is first. A listening session cannot restore trust if people explain the capacity problem and the portfolio remains untouched. An AI tool may process information faster, but it can also help an undisciplined system generate more work at greater speed.

The answer is not to remove urgency. It is to give urgency a standard.

Before labeling work urgent, I would ask four questions:

1. What specific consequence occurs if this waits?
2. What existing priority loses time, attention, or quality if this moves first?
3. Who has the authority to make that tradeoff?
4. When does the emergency status end?

If leaders cannot answer those questions, the work may be important, uncomfortable, visible, or late. It is not yet clearly urgent.

That distinction matters because people watch what receives protection. They notice whether a deadline can move when the facts change. They notice whether leaders remove work after adding it. They notice whether raising a capacity concern improves the decision or damages the person who raised it.

Those repeated experiences become culture.

I believe the next leadership challenge will not be producing more activity. AI and automation will make that easier. The harder work will be deciding which activity deserves human judgment, which commitment must remain stable, and what the organization will deliberately stop.

The answers are already present in missed handoffs, repeated rework, customer friction, quality exceptions, after-hours communication, delayed decisions, and the work people complete only by borrowing from their own recovery time.

Bring that evidence into the portfolio meeting.

For the next thirty days, require every new urgent request to name the consequence, the displaced priority, the decision owner, and the end of the exception. Then review what the pattern reveals.

You may find a team that needs more capacity. You may find a process that needs repair. You may find a decision that has been avoided. You may also find that the organization has been using urgency to avoid the discipline of choosing.

People can move quickly when the moment requires it. What they should not have to do is live permanently inside an emergency no one has defined.

Sustainable performance begins when leaders make the tradeoff as clear as the demand.