When Everything Is Urgent: Why Good Work Needs Time

Corporate culture has developed an uncomfortable habit: turning ordinary work into emergencies.

“Can you do this by EOD?”

“Need this ASAP.”

“Please prioritize this.”

“Can we have it in the next two hours?”

Sometimes these requests are genuinely urgent. But increasingly, urgency is communicated simply because someone wants faster execution—not because the work itself has a time-critical consequence.

The result is a workplace where speed is confused with productivity.

The better response to an urgent-looking request is not always “yes.” Sometimes the most professional response is to pause, understand the requirement, assess the consequences of rushing, and agree on a realistic timeline.

The problem with “EOD culture”

Imagine an employee is working on an important product specification when a manager sends a message:

«“Need a quick analysis by EOD.”»

The employee immediately switches tasks.

Twenty minutes later, another message arrives:

«“Can you also review this presentation urgently?”»

Then a call.

Then an email.

Then another Teams notification.

None of these tasks may individually require immediate attention. But together they fragment the employee's working day.

Research on workplace multitasking has highlighted the substantial cost of such context switching. One Harvard Business Review discussion reported that employees switched between apps and websites extremely frequently, with the accumulated switching time amounting to several hours per week.

The important lesson is not the exact percentage.

It is this:

Every interruption has a transition cost.

When people repeatedly stop thinking about one problem and start thinking about another, they don't simply lose the few seconds or minutes required to switch. They also lose mental continuity.

And complex work depends heavily on continuity.

Urgency should change the response—not eliminate thinking

There is a common misconception that responding quickly means beginning the work immediately.

It doesn't.

A mature professional response to an urgent request should first establish:

1. What exactly is required?

2. Why is it urgent?

3. What happens if it is delivered tomorrow instead of today?

4. What level of quality is expected?

5. What other work should be deprioritized?

6. Who needs the output and for what decision?

This takes perhaps five minutes.

Those five minutes can prevent five hours of unnecessary rework.

A useful response is:

«“I can take this up immediately. To give you a reliable output, I need about three hours. If this has to go out by EOD, I'll need to move X to tomorrow. Is that the priority?”»

This is not resistance.

This is prioritization.

Example 1: Healthcare

Consider a hospital analytics team asked at 4 PM:

«“Can you urgently prepare a report showing why readmissions increased?”»

A superficial response is to pull whatever data is immediately available and produce a report by 6 PM.

But healthcare data is rarely that simple.

The analyst may need to check:

- patient cohorts,

- admission and discharge dates,

- coding changes,

- exclusions,

- observation stays,

- transfers,

- case-mix differences,

- data-quality issues.

A rushed report can produce a completely wrong conclusion.

Here, “urgent” should mean start quickly, not skip validation.

A professional response might be:

«“I can provide a preliminary directional analysis today. For a validated readmission analysis suitable for management decisions, I recommend tomorrow afternoon because I need to verify the cohort and coding.”»

That distinction can protect both the organization and the patients it serves.

Example 2: Software development

A product manager tells a developer:

«“The client demo is tomorrow. Can you quickly make this change?”»

The developer can technically implement it in two hours.

But the change touches authentication.

Doing it immediately might mean:

- no proper code review,

- inadequate testing,

- regression risk,

- security vulnerabilities.

The right response is not necessarily “I can't do it.”

It could be:

«“I can create a prototype for tomorrow's demo. Production deployment will need testing and code review, so I'd recommend deploying it after validation.”»

The distinction between demo-ready and production-ready is crucial.

Urgency can justify a temporary workaround.

It should not automatically justify lower engineering standards.

Example 3: Finance

A finance executive receives a request:

«“Please send the quarterly numbers in the next hour. The leadership meeting is at 5.”»

The numbers may involve revenue recognition, accruals, intercompany adjustments and reconciliation.

Sending an unchecked figure simply because somebody wants it quickly can create a much larger problem later.

A better response:

«“I'll send an initial estimate within the hour, clearly marked as provisional. The reconciled number will follow after the final checks.”»

This preserves speed without pretending that speed equals accuracy.

Example 4: Legal

A lawyer receives:

«“Please quickly review this 50-page contract. We need to sign it today.”»

This is perhaps the clearest example of why “urgent” does not mean “rush.”

A lawyer might identify:

- indemnification clauses,

- liability caps,

- termination provisions,

- intellectual-property ownership,

- jurisdiction,

- confidentiality obligations.

Missing one critical clause can create consequences lasting years.

The appropriate response may be:

«“I can prioritize this immediately, but a proper review will take X hours. If signing today is mandatory, I'll first focus on the high-risk clauses and clearly identify what remains unreviewed.”»

That is what professional judgment looks like.

Example 5: Manufacturing

A production manager says:

«“We need to get this batch out today. Skip the secondary inspection.”»

This is where urgency can become dangerous.

Manufacturing systems exist precisely because certain checks cannot safely be skipped.

The correct response may be a firm:

«“We can expedite the inspection, but we should not bypass the required quality-control step.”»

Some processes are designed with non-negotiable controls.

Urgency cannot override them.

Example 6: Marketing

A marketing manager asks:

«“Can you launch the campaign by tonight?”»

The campaign itself may not be genuinely urgent. Perhaps someone simply wants to capitalize on a trend.

If rushing means launching with:

- incorrect pricing,

- broken links,

- unapproved claims,

- inconsistent branding,

- tracking errors,

the organization may spend more time fixing the campaign than it saved.

A good response is:

«“I can get the creative ready today. For a clean launch, I'd recommend tomorrow morning after QA and tracking validation.”»

Again, the answer isn't “no.”

It is “yes, but let's define what can responsibly be done by when.”

The most powerful question: “What is the consequence of delay?”

One of the easiest ways to distinguish genuine urgency from artificial urgency is to ask:

«“What happens if this is completed tomorrow rather than today?”»

The answer often reveals the real priority.

If the answer is:

- “The regulatory filing closes today.” → genuinely urgent.

- “The patient is waiting for the result.” → potentially urgent.

- “The board meeting is tomorrow morning.” → possibly urgent.

- “The client asked for it.” → needs clarification.

- “I just want it off my list.” → not necessarily urgent.

- “We've always done it by EOD.” → probably a process issue.

Urgency should be determined by consequences, not by the volume of the requester's voice.

Don't accept urgency without negotiating priorities

There is another important principle:

A new urgent task requires a corresponding reprioritization.

If someone gives you five tasks and suddenly adds a sixth as “urgent,” something has to change.

You can say:

«“I can complete this today. Which of the existing priorities should I move to tomorrow?”»

This simple question changes the conversation.

Instead of:

“How can I do more?”

the conversation becomes:

“What is most important?”

That is a much healthier management discussion.

Why rushing can actually make work slower

Suppose a person needs two hours to perform a task carefully.

Under pressure, they attempt to finish it in one hour.

They make mistakes.

Someone identifies the errors.

They spend another hour fixing them.

The organization has now spent three hours instead of two.

The apparent gain from urgency was an illusion.

This is particularly important for knowledge work because many tasks have nonlinear quality effects.

A report, strategy, analysis, software architecture, financial model or clinical interpretation may require a period of uninterrupted thinking before the answer becomes reliable.

You cannot always compress thinking simply by applying pressure.

The hidden cost: shallow work

Perpetual urgency also changes organizational behavior.

Employees gradually learn:

«“Don't work on the most important thing. Work on whatever is shouting the loudest.”»

This creates an inbox-driven organization.

Email becomes the task manager.

Chat notifications become priorities.

The person who sends the most urgent messages gets the most attention.

Meanwhile, strategic work gets postponed because it rarely screams.

Over time, employees become excellent at responding and increasingly poor at thinking.

That is a dangerous trade-off for knowledge-based organizations.

A better model: Urgency × Importance

Every incoming request can be classified into four broad categories:

1. Urgent + important

Act immediately.

Examples: patient safety issue, cybersecurity incident, regulatory deadline, production outage.

2. Important but not urgent

Schedule protected time.

Examples: strategy, product architecture, employee development, research, process improvement.

3. Urgent but not important

Delegate, batch or negotiate the deadline.

Examples: routine presentations, non-critical formatting, internal administrative requests.

4. Neither urgent nor important

Defer or eliminate.

The problem with “EOD culture” is that category 3 is constantly being promoted into category 1.

How employees should respond

Employees do not need to become confrontational to resist artificial urgency.

A few professional phrases are remarkably effective:

«“What is the actual deadline?”»

«“What is driving the urgency?”»

«“What is the consequence if this moves to tomorrow?”»

«“I can do this today, but which current priority should I deprioritize?”»

«“I can provide a preliminary answer today and a validated version tomorrow.”»

«“I can turn this around quickly, but I don't want to compromise accuracy.”»

«“If this needs to be done by EOD, I'll need to reduce the scope.”»

These responses demonstrate ownership rather than resistance.

How managers should respond

The larger responsibility lies with management.

A manager should distinguish between:

“I want this quickly”

and

“This genuinely needs to be completed quickly.”

Those are not the same thing.

Good managers communicate:

- the real deadline,

- the business reason,

- the expected quality,

- the priority relative to other work,

- and what can be deprioritized.

Instead of saying:

«“Need this ASAP.”»

say:

«“The client meeting is tomorrow at 9 AM. I need a validated summary by 8 AM. Please prioritize this over the dashboard enhancement.”»

The second message gives the employee something the first does not:

context.

Context allows people to make intelligent decisions.

There is a place for urgency

The argument is not that workplaces should become slow.

Some environments genuinely require rapid action.

Emergency medicine, cybersecurity, financial markets, newsrooms, disaster response, aviation and incident management can involve real-time consequences.

The problem occurs when crisis-management behavior spreads into ordinary knowledge work.

If everything is urgent, nothing is truly prioritized.

And if every task is a crisis, eventually employees stop believing the word “urgent.”

The cultural shift

The healthiest organizations do not eliminate deadlines.

They become better at using deadlines intelligently.

They understand that:

Speed is valuable when time matters.

Accuracy is valuable when consequences matter.

Deep work is valuable when complexity matters.

Rest is valuable when sustainability matters.

And good management is knowing which situation you are dealing with.

The future workplace will not necessarily belong to the organization that responds fastest to every message.

It may belong to the organization that knows which messages deserve an immediate response—and which deserve careful thought.

The professional who says, “I'll do it now,” is useful.

The professional who says, “I'll prioritize it, understand what is required, and give you the best reliable output within the right timeframe,” is far more valuable.

Because the objective of work is not to look busy, respond instantly, or clear the inbox.

The objective is to produce the right outcome.

And sometimes, the fastest way to get the right outcome is to stop rushing.