THE COST OF NOW: Poor Planning Is Not An Emergency
There is a particular kind of email that lands differently.
Not because of what it asks for.
Because of when it asks for it.
“Hi Adam,
Sorry for the late notice. We really need this back by tomorrow morning if possible.”
Of course you do.
You've known about it for two weeks.
I've known about it for eleven seconds.
Yet somehow we now appear to have exactly the same deadline.
This happens everywhere.
A client sits on a decision.
Then approves it late.
Now the supplier needs to rush.
A manager doesn't review something.
Then suddenly needs changes before a meeting.
Someone forgets to order something.
Now the delivery needs upgrading.
A project spends weeks drifting.
Then everybody works late in the final three days.
Someone doesn't think ahead.
Then somebody else loses their evening.
We tend to describe these moments as urgency.
I'm not sure that's always what they are.
Sometimes they're time debt.
Someone used more time than they had available earlier in the process.
The deadline did not disappear.
So the missing time gets taken from whoever happens to be downstream.
And that's a very different thing.
Time cannot actually be recovered
That's the first problem.
Imagine a project has twenty working days available.
The first person in the chain is supposed to use five.
They use ten.
There are still only twenty days.
Nothing magical happens because somebody says:
“Sorry for the delay.”
The remaining fifteen days have become ten.
Someone now has to absorb the difference.
Maybe the deadline moves.
Maybe the scope reduces.
Maybe extra people are brought in.
Maybe quality falls.
Maybe someone works faster.
Maybe someone works longer.
But the five days have gone.
There is no lost-time warehouse where we can pop down and collect them.
This seems embarrassingly obvious.
Yet organisations behave as though time can somehow be recovered without consequence.
“We're a little behind, so we'll have to make the time up later.”
No.
You'll have to take the time from somewhere else later.
That distinction matters.
Because “making up time” sounds neutral.
What it often means is:
less contingency,
less checking,
less thinking,
fewer breaks,
longer days,
postponed work,
compressed suppliers,
or somebody else's plans being sacrificed.
Delay doesn't vanish.
It travels.
We are surprisingly bad at predicting how long things will take
Some of this isn't selfishness or incompetence.
It's human.
Psychologists Roger Buehler, Dale Griffin and Michael Ross produced a series of classic experiments on what became known as the planning fallacy.
People repeatedly underestimated how long their own future tasks would take, even when they had previously experienced similar tasks taking longer.
One of the interesting explanations was that when people predicted completion time, they tended to focus on their imagined future plan:
First I'll do this.
Then this.
Then this.
Done.
What received less attention was the messy historical evidence.
Last time somebody was off sick.
Last time the client changed the brief.
Last time the information arrived late.
Last time something broke.
Last time the “quick approval” took four days.
When participants were encouraged to connect their forecast to relevant past experience, the optimistic bias could be reduced.
That is wonderfully recognisable.
How long will this take?
“Well, the actual work is probably two days.”
No.
The actual work might be two days.
The project is not merely the actual work.
It is:
getting the information,
checking the information,
waiting for the decision,
discovering something is missing,
asking a question,
waiting for the answer,
doing the work,
having it reviewed,
changing the thing someone forgot to mention,
sending it back,
and discovering the person who needs to approve it is now on annual leave.
Yet planning often imagines the perfect route through the system.
Reality uses the roads.
The perfect-day plan
I see this constantly.
People plan days as though nothing unexpected will happen.
Nine until ten: meeting.
Ten until eleven: proposal.
Eleven until twelve: calls.
Twelve until one: admin.
One until two: lunch and travel.
Two until four: client work.
Four until five: emails.
Lovely.
And then a human being actually lives the day.
The meeting runs fifteen minutes over.
Someone calls.
A customer has a problem.
The laptop updates.
You need the toilet.
One job takes longer than expected.
Someone asks a question.
You spend twenty minutes trying to find a document you definitely saved somewhere sensible.
Now it's 11:47 and the entire timetable is fucked.
The problem wasn't necessarily poor discipline.
The plan contained no reality.
There was no slack.
No transition.
No uncertainty.
No allowance for being a mammal rather than enterprise software.
Then the schedule slips.
And what happens?
We rarely remove work.
We compress the rest of it.
The future pays for the planning error.
Slack looks wasteful right up until you need it
Modern organisations have a complicated relationship with spare capacity.
An unused hour looks inefficient.
An employee who isn't operating at 100 per cent capacity looks underutilised.
A delivery vehicle with spare room looks wasteful.
A diary with gaps looks empty.
Inventory sitting unused costs money.
We understandably try to remove waste.
But resilience research suggests that organisational slack can also play a role in the ability to absorb disruption. One study examining resource slack and operational resilience found that slack could support resilience indirectly through greater organisational attention, although the relationship was not simple or automatically positive.
That's exactly the nuance we need.
Slack is not automatically good.
Too much spare capacity can absolutely be waste.
But zero slack is fragility pretending to be efficiency.
If a system only works when:
nobody is ill,
nothing runs late,
every estimate is correct,
every customer responds immediately,
traffic behaves,
technology works,
suppliers deliver perfectly,
and nobody ever makes a mistake,
then you haven't designed an efficient system.
You've designed a fantasy.
The inevitable deviation then gets converted into urgency.
And urgency gets handed to people.
We don't usually notice where the delay originated
This is where things become unfair.
Imagine five stages.
A → B → C → D → E.
A delivers two days late.
B loses two days.
But B doesn't want to look difficult, so B works faster and hands it to C only one day late.
C squeezes it further.
By the time it reaches E, nobody is talking about A anymore.
They're telling E:
“We really need this turned around today.”
E appears to be the bottleneck.
E isn't the bottleneck.
E is where the system finally ran out of road.
This happens constantly in supply chains, projects, management structures and client relationships.
The last person in the chain inherits everybody else's optimism.
And because they're closest to the final deadline, their work suddenly looks most urgent.
That's deeply misleading.
The immediate cause of lateness and the original cause of lateness are often completely different.
Yet organisations tend to manage the immediate cause.
Chase E.
Push E.
Escalate E.
Ask E to stay late.
Nobody goes back three weeks and asks why A sat on the decision.
Deadlines are social, not just personal
This is why poor planning becomes more serious when work is interdependent.
If I'm writing something for myself and I procrastinate, mostly I pay.
Fine.
My choice.
My consequence.
But the moment another person's work depends on mine, my relationship with time changes.
Research into project teams has found that shared understanding of timing matters for coordinated action. A longitudinal study of 48 project teams found that temporal consensus — a shared understanding of the timing aspects of collective work — helped teams coordinate and meet deadlines. Early temporal planning and later reminders helped develop that shared understanding.
That sounds academic.
In normal language:
Everyone needs to understand when their bit actually has to happen so the next person can do theirs.
A deadline is rarely just:
“When I need to finish.”
It may also be:
“When somebody else needs me to get out of their way.”
That is the part chronic late planners miss.
They see the final deadline.
The person downstream sees the time required between your deadline and theirs.
If I need your information on Monday to do three days of work before Friday, Monday matters.
You cannot send it Thursday morning and say:
“Well, the overall deadline isn't until Friday.”
Congratulations.
You've left me eight hours to complete twenty-four hours of work.
Your diary still says Friday.
Mine has just exploded.
Procrastination has a deadline trick built into it
There is another reason this pattern keeps happening.
Deadlines motivate us.
Unfortunately, they can motivate us rather late.
Piers Steel's major meta-analysis on procrastination described procrastination as a form of self-regulatory failure and found consistent relationships with factors including task aversiveness, impulsiveness, self-efficacy, conscientiousness and the temporal distance of outcomes.
This helps explain something most people recognise instinctively.
A task due in six weeks feels abstract.
A task due Friday feels more real.
A task due tomorrow suddenly becomes fascinating.
This is not universally true, and people differ enormously, but urgency can provide the motivational force that earlier importance failed to provide.
Which creates an unfortunate cycle.
Delay.
Delay.
Delay.
Deadline approaches.
Pressure rises.
Attention sharpens.
Action finally happens.
Task gets completed.
Relief.
And perhaps even:
“See? I work better under pressure.”
Do you?
Or have you simply become very practised at using anxiety as your project-management system?
There is a difference.
“I work better under pressure” can mean “other people work worse around me”
This matters particularly for leaders.
If you're the final person doing everything yourself, feel free to build whatever ridiculous last-minute ritual works for you.
Stay up until 3am.
Drink eighteen coffees.
Write the presentation in the taxi.
Your life.
Your consequence.
The moment you lead other people, your chaos becomes environmental.
Your delayed decision means they cannot start.
Your late feedback shortens their revision window.
Your changing priorities invalidate their planning.
Your failure to think ahead becomes their overtime.
Your adrenaline becomes their stress.
That is not a personality quirk anymore.
It is management.
And in Britain, the Health and Safety Executive explicitly treats workload, work patterns and whether demands are achievable within agreed working hours as part of managing work-related stress. Its Management Standards also emphasise giving people appropriate control over their pace of work where possible.
That makes sense.
There is a considerable psychological difference between choosing to work fast and having speed imposed upon you because somebody else ran out of time.
Same pace.
Different autonomy.
Time pressure isn't uniformly bad
We need some restraint here.
Pressure can help.
Anyone who has ever spent three hours doing fuck all and then completed an impressive amount of work in the final forty-five minutes knows that.
Research into daily workplace procrastination shows exactly why simplistic claims fail.
A diary study involving 110 employees found that time pressure could be appraised either as a challenge or as a hindrance.
When experienced as a challenge, it could be associated with less procrastination through reduced self-regulatory effort.
When experienced as a hindrance, it could operate in the opposite direction.
So the argument is not:
Pressure bad.
No deadlines.
Everyone work whenever they feel spiritually aligned with the spreadsheet.
Deadlines coordinate.
Pressure can focus.
Urgency can mobilise.
The problem is unnecessary pressure created by preventable delay upstream.
That adds nothing valuable.
It is the difference between a deadline helping work move and a deadline becoming a weapon because somebody failed to use the time before it.
Time pressure changes decisions
There is also good reason not to pretend that compressed time is neutral.
Research reviews on decision-making under stress identify time pressure alongside information overload, complexity and uncertainty as factors capable of affecting decision processes and decision quality.
Experimental work has found that people under time pressure can become more anxious and alter the strategies they use to process information, with effects depending on the structure of the task.
Again, this isn't a universal “fast decisions are worse” rule.
Experienced people can make exceptional decisions quickly.
Some tasks benefit from constraint.
But compressed time changes the conditions under which judgement occurs.
That matters when the task being rushed is:
technical,
safety-critical,
financial,
legal,
creative,
analytical,
or simply complicated.
“Can you just turn it around today?” sounds cheap when you aren't the person deciding what gets omitted to make today possible.
Quality is often the invisible thing being borrowed
Suppose you normally need six hours to do a piece of work properly.
Now I give you three.
There are several possible outcomes.
You become twice as efficient through some miraculous breakthrough.
Fantastic.
Or:
you don't check something,
you use the first workable answer rather than the best one,
you don't investigate an uncertainty,
you rely on an assumption,
you don't ask the awkward question,
you cut the thinking time,
you postpone something else,
or you work another three hours tonight.
The deadline is still met.
So from the outside, the system appears to work.
This is how organisations accidentally train themselves into bad planning.
Someone creates an unreasonable deadline.
Everyone performs heroics.
The job gets delivered.
The lesson should be:
We got lucky. Don't do that again.
Instead the lesson becomes:
See? It can be done.
That is dangerous.
Extraordinary effort gets converted into standard capacity.
The exception becomes the benchmark.
And the next deadline is planned using evidence produced by people overextending themselves.
Capable people are particularly vulnerable
I know this pattern.
For years, a significant part of my working identity was built around being the person who could sort shit out.
Something had gone wrong?
Give it to Adam.
Someone hadn't done something?
Adam would pick it up.
Client unhappy?
Adam.
Problem at the last minute?
Adam.
I was proud of being dependable.
And there is nothing wrong with dependability.
But reliability has an interesting side effect.
If you repeatedly rescue a system from the consequences of poor planning, the system loses part of the incentive to plan better.
Your competence becomes contingency.
Your willingness to absorb becomes somebody else's buffer.
Eventually the organisation does not merely appreciate your ability to rescue the emergency.
It starts quietly designing around the assumption that you will.
That is the Fixer Loop in a different form.
You think you're helping.
And you are.
Today.
But if your intervention prevents the system from experiencing the consequence that would have forced it to improve, you may also be preserving the cause.
That is uncomfortable.
Especially for capable people.
Because fixing feels useful.
Letting somebody feel a consequence can feel obstructive.
Sometimes it is exactly what the system needs.
Not every late request is poor planning
This point matters enough to make explicitly.
Sometimes shit happens.
A child gets ill.
A machine breaks.
A customer changes their mind.
A regulator changes something.
Weather intervenes.
Someone discovers information they could not reasonably have known earlier.
A supplier fails.
A colleague has a bereavement.
The building floods.
The server dies.
A genuine emergency occurs.
In those circumstances, good teams bend.
They help.
They work around each other.
They absorb things.
They show compassion.
I would hate to work in an organisation where every unexpected problem was met with:
“Your problem. Should've planned better.”
That's not boundaries.
That's being an arsehole.
Even delay itself is not always evidence of failure.
Very recent research on highly interdependent teams suggests people distinguish between chronic procrastination and delays they interpret as strategic or reasonable, using cues such as communication, trust and past performance. The same delay can therefore produce very different reactions depending on why it occurred and how it was handled.
Context matters.
The title of this essay is not:
Your Emergency Is Not My Problem.
It is:
Poor Planning Is Not An Emergency.
Different proposition.
Communication changes everything
Tell me on Monday:
“We're waiting on approval and there is a risk this is going to compress your timescale later in the week.”
Fine.
Now I know.
I can prepare.
Move something.
Protect some time.
Tell another client.
Ask for information early.
Create options.
Tell me Thursday at 4:37:
“Good news, approved! Need it first thing tomorrow.”
Now you've made your uncertainty my surprise.
Those are completely different management behaviours.
This connects beautifully with research into team timing.
The point isn't that everybody must predict the future perfectly.
They can't.
The point is that coordination improves when people share an understanding of time and update one another as reality changes.
You don't always control the delay.
You usually control how long you hide it.
And late communication can turn manageable uncertainty into artificial urgency.
There is a difference between asking for help and transferring responsibility
“Mate, I've fucked this up. Any chance you can help me?”
I respond quite well to that.
Most people do.
It contains ownership.
You know you've created a problem.
You're asking whether I can help solve it.
That's human.
What lands differently is:
“This now needs doing today.”
No explanation.
No acknowledgement.
No recognition that today's emergency has a history.
The language quietly transfers ownership.
It isn't:
I am late.
It is:
You are now urgent.
That's the behaviour worth challenging.
Because responsibility for a deadline should not migrate automatically simply because the work did.
Good planning is not accurate prediction
This is another trap.
We sometimes imagine good planners as people who somehow know exactly what will happen.
They don't.
Nobody does.
Good planning is often the opposite.
It starts from accepting that the plan will be wrong.
The question is whether the system survives being wrong.
What if approval takes two days longer?
What if somebody is off?
What if this takes six hours rather than four?
What if the supplier slips?
What if the client changes something?
What needs to happen first?
What is dependent on what?
Where is the point beyond which delay creates downstream damage?
That isn't pessimism.
It's adult planning.
The planning fallacy tells us our intuitive forecasts can be overly optimistic.
One response is therefore to stop treating the first optimistic scenario in our head as a contract with reality.
Use history.
Last three jobs took six days?
Maybe stop planning the next one at three because this time will be different.
Planning itself has evidence behind it
There is a useful distinction between wanting to do something and planning how it will actually happen.
Research on implementation intentions — explicit if-then plans connecting a future situation with an intended action — has accumulated a substantial evidence base.
A classic meta-analysis covering 94 independent tests found implementation intentions improved goal attainment, and a much larger 2025 meta-analysis covering 642 independent tests found benefits across cognitive, emotional and behavioural outcomes, with effects varying by how plans were constructed and used.
That does not mean every delayed project could have been rescued by writing:
“If it is Tuesday, I will open Excel.”
Organisational planning is far more complex.
But the underlying lesson is useful:
Intentions are not plans.
“We need to get this finished by the end of the month.”
That's an intention.
Who needs to do what?
By when?
What happens before that?
What information do they need?
What could block it?
When do we need a decision?
What happens if we don't get one?
Now we're planning.
An astonishing amount of workplace urgency starts with somebody confusing those two things.
The deadline should move backwards through the process
If something genuinely needs to be finished on Friday, don't only put Friday in the diary.
Work backwards.
Final check Thursday.
Draft Wednesday.
Information Monday.
Approval before that.
Decision before that.
Now the people upstream can see the consequences of delay.
Without that, everyone shares one visible deadline while carrying completely different hidden ones.
This is why temporal coordination matters so much in teams.
The deadline at the end is not enough.
People need a shared picture of the sequence.
Otherwise the person making the first decision feels they have weeks.
The person doing the final task discovers they have hours.
Sometimes the correct answer is no
This is probably the hardest bit for dependable people.
Someone arrives with an emergency.
You can save them.
Technically.
It will cost you your evening.
Or move another client.
Or cancel something with your family.
Or rush work you would rather do properly.
Can you?
Yes.
Should you?
Different question.
I spent years answering the first question and treating it as though it answered the second.
If I could physically absorb something, I did.
That's how capable people become overflow tanks for poorly designed systems.
Agency changed that for me.
Agency asks a better question.
What outcome am I creating by saying yes?
Maybe the answer is genuinely worthwhile.
A good client has been caught by something unpredictable.
Help them.
A colleague is normally excellent and has had a nightmare.
Help them.
The cost is tiny and the relationship matters.
Help.
But if the same person creates the same emergency every month and you repeatedly rearrange your life to make it disappear, what exactly are you helping?
The task?
Yes.
The behaviour?
Probably not.
Boundaries teach systems how to plan
This is one reason boundaries are not simply defensive.
They provide information.
“No, I can't do that today. Earliest is Thursday.”
Now the system has encountered reality.
Maybe Thursday works.
Interesting.
It wasn't actually an emergency.
Maybe Thursday doesn't work.
Then someone has to decide:
reduce scope,
find additional capacity,
move the external deadline,
pay for expedited work,
or acknowledge where the delay occurred.
Those are real choices.
What shouldn't automatically happen is:
Adam has boundaries, therefore Adam is the problem.
The absence of infinite capacity is not poor customer service.
It is physics.
Urgency should carry provenance
I think workplaces would operate differently if every urgent request had to answer one additional question:
Why is this urgent?
Not to challenge genuine need.
To expose the source.
Client deadline moved unexpectedly.
Fine.
Safety issue discovered.
Fine.
Regulatory deadline.
Fine.
Original instruction incorrect.
Fine.
Manager forgot.
Useful information.
Approval sat in inbox for nine days.
Also useful information.
Because without provenance, all urgency looks identical at the point of delivery.
And if all urgency looks identical, organisations cannot learn.
They simply become faster firefighters.
Imagine instead recording where rush work actually originates.
Not who eventually handled it.
What caused the compression.
Maybe the data shows customers repeatedly provide information late.
Then change the onboarding.
Maybe approvals sit with one senior manager.
Fix the bottleneck.
Maybe estimates are consistently optimistic.
Change estimating.
Maybe the sales team promises dates without consulting operations.
There's your problem.
Maybe nobody plans at all.
Also useful.
Urgency contains information about system design.
But only if we look backwards rather than merely shouting forwards.
A culture of rescue eventually needs rescuing
This is the irony.
The more an organisation relies on heroics, the more brittle it becomes.
Knowledge sits with a few rescuers.
Processes remain weak.
Planning remains optimistic.
Slack disappears.
Everyone learns that impossible deadlines are apparently possible.
The capable people get overloaded.
Eventually one leaves.
Or burns out.
Or simply says no.
Now the organisation discovers that what it called capacity was actually sacrifice.
I know what that looks like.
I spent years being rewarded for absorbing pressure until constant availability became normal and the system increasingly relied on the fact that I would keep solving what landed.
It took me a long time to understand that being excellent in an emergency and building a life made entirely of emergencies are two completely different achievements.
One is capability.
The other is a design failure.
The real test is what happens after the emergency
Emergencies happen in good organisations.
The question is whether they teach anything.
Afterwards:
Why did this happen?
Could we have known earlier?
Was the deadline realistic?
Did information arrive when it should?
Where did the process stall?
Did we have enough capacity?
Did someone fail to communicate risk?
Was this genuinely unforeseeable?
What do we change?
Without that conversation, emergency work becomes ritual.
Same rush.
Different week.
At that point it isn't an emergency anymore.
It's the operating model.
Poor planning is not an emergency
That sentence can sound cold.
I don't mean it that way.
I mean something more specific.
Urgency should not erase history.
The fact that we have reached the last twelve hours does not mean the previous twelve days cease to matter.
The person at the end of the chain should not automatically pay for every delay before them.
A capable person should not lose their autonomy simply because somebody else used theirs badly.
A team should absolutely rally around genuine unforeseen problems.
But repeated avoidable urgency deserves a different response.
Not:
Work faster.
Not:
Try harder.
Not:
Be more available.
Ask:
Where did the time go?
Because time doesn't simply vanish from projects.
People spend it.
Decisions consume it.
Silence consumes it.
Delay consumes it.
Optimism consumes it.
Indecision consumes it.
Then somebody eventually notices there isn't enough left.
And suddenly the final person is told to hurry.
That's the bit we need to stop accepting as inevitable.
Your poor planning may create a problem.
It may create a difficult conversation.
It may create a cost.
Sometimes I may even choose to help you rescue it.
But none of that automatically converts your lost time into ownership of mine.
Sources And Further Reading
Roger Buehler, Dale Griffin and Michael Ross, “Exploring The Planning Fallacy: Why People Underestimate Their Task Completion Times”, Journal of Personality and Social Psychology (1994).
Across multiple studies, people tended to underestimate their own task-completion times and focus heavily on future plan-based scenarios rather than relevant past experience. Encouraging participants to connect forecasts with previous experience reduced the optimistic bias in one study.
Piers Steel, “The Nature Of Procrastination: A Meta-Analytic And Theoretical Review Of Quintessential Self-Regulatory Failure”, Psychological Bulletin (2007).
A major meta-analysis drawing on 691 correlations identified task aversiveness, delay, self-efficacy, impulsiveness and facets of conscientiousness among consistent predictors of procrastination, and integrated the evidence through temporal motivation theory.
Roman Prem, Tabea Scheel, Oliver Weigelt, Katja Hoffmann and Christian Korunka, “Procrastination In Daily Working Life” (2018).
A diary study of 110 employees found that time pressure could operate through both challenge and hindrance appraisals, illustrating why deadline pressure can sometimes stimulate action while producing less helpful effects under other conditions.
Josette Gevers, Wendelien van Eerde and Christel Rutte, “Team Self-Regulation And Meeting Deadlines In Project Teams” (2009).
A longitudinal study of 48 project teams found that shared temporal understanding supported coordinated action and meeting deadlines, with early planning and later temporal reminders contributing to that consensus.
Josette Gevers and Christel Rutte, “How Teams Meet Deadlines: Towards Team Time Management” (2013).
Reviews evidence suggesting that effective team deadline performance depends not only on understanding the task but also on shared temporal perspectives, planning, monitoring and adaptation.
Mathieu et al., “Translating Time-Based Research Into Team Interventions” (2022).
An evidence-based review of temporal challenges in teams, including fluctuating deadlines, time pressure and the complexity of coordination between interdependent people and organisations.
Paschal Sheeran, Olivia Listrom and Peter Gollwitzer, “The When And How Of Planning: Meta-Analysis Of The Scope And Components Of Implementation Intentions In 642 Tests” (published 2024; 2025 volume).
A large meta-analysis found that implementation intentions — explicit plans linking situations with intended responses — were effective across a range of cognitive, affective and behavioural outcomes, while also showing that plan design and context matter.
Peter Gollwitzer and Paschal Sheeran, “Implementation Intentions And Goal Achievement: A Meta-Analysis Of Effects And Processes” (2006).
The earlier meta-analysis of 94 independent tests found a positive medium-to-large overall effect of implementation intentions on goal attainment, reinforcing the distinction between merely intending an outcome and specifying how action will occur.
Dominic Essuman et al., “Linking Resource Slack To Operational Resilience” (2022).
Found a more nuanced relationship than the simple claim that “more slack means more resilience”: resource slack supported operational resilience indirectly through organisational attention rather than showing a straightforward direct effect.
A. J. Maule, G. R. Hockey and L. Bdzola, “Effects Of Time-Pressure On Decision-Making Under Uncertainty” (2000).
Experimental research found that time pressure changed participants' emotional state and information-processing strategies, with effects varying according to task structure.
Research reviews on managerial decision-making under stress and time pressure.
Reviews identify time pressure, information overload, complexity and uncertainty as relevant stressors capable of influencing how decisions are processed and their resulting quality, while emphasising that effects vary by context.
Health and Safety Executive, Management Standards for work-related stress.
UK HSE guidance identifies workload and work patterns under “Demands” and recommends adequate, achievable demands within agreed working hours. Its “Control” standard includes, where possible, employee influence over work pace and breaks.
Kuok Kei Law and Jacky Hong, “Delay No More: Managing Temporal Diversity In Teams Through Temporal Attribution And Regulation” (2026 conference proceedings abstract).
Recent qualitative work suggests team members distinguish between strategic or understandable delay and chronic procrastination using cues such as trust, communication and past performance, reinforcing the importance of context when interpreting lateness.
Adam Fox, Authority And Origin Story: Adam Fox And The DROP System.
Source material for the lived experience of becoming the reliable fixer, repeatedly absorbing pressure and gradually having constant availability treated as part of the role.
Research Gaps
There is limited direct research on “exported urgency” as one unified phenomenon.
The central argument in this essay combines evidence from planning fallacy, procrastination, team coordination, time pressure, organisational slack and workplace stress. Research strongly supports each of those component mechanisms, but “time debt being passed downstream” is a conceptual framing used here rather than an established academic construct with one agreed measure.
The planning fallacy does not explain every missed deadline.
People may underestimate task duration, but delays can also result from changing requirements, dependencies, resource shortages, strategic choices, conflicting priorities, illness or genuinely unpredictable events. Optimistic forecasting should not become a catch-all explanation for lateness.
Slack is not automatically efficient or resilient.
Resource slack can create flexibility, but excessive unused capacity can increase cost and reduce efficiency. Research does not support the simplistic claim that every organisation should deliberately maintain large amounts of spare time or labour. The useful question is how much resilience a particular system needs and where contingency should exist.
Time pressure can help as well as harm.
Research shows that some people experience time pressure as a challenge that mobilises effort, while others experience it as a hindrance. Effects vary according to task, expertise, control, personality and context. The essay therefore criticises preventable transferred time pressure rather than deadlines or pressure in themselves.
There is no universal threshold for an “unreasonable” deadline.
A turnaround that is completely reasonable for one task may be reckless for another. Expertise, tools, staffing, consequence, complexity and quality requirements all matter. The distinction between urgent and artificially urgent ultimately requires contextual judgement.
Evidence on downstream effects of one person's procrastination remains comparatively thin.
There is substantial research on individual procrastination and separate research on temporal coordination within teams, but fewer studies directly quantify how one person's avoidable delay alters colleagues' working hours, stress, decision quality or error rates across an entire project chain.
The 2026 research on strategic versus chronic delay is preliminary.
The cited study appears in Academy of Management conference proceedings and is based on qualitative interviews with student project teams. It offers a useful emerging distinction but should not yet be treated as strong general evidence about professional organisations.
Implementation-intention evidence should not be overextended into project management.
If-then planning has an extensive evidence base for goal pursuit, but organisational projects contain dependencies, politics, resource constraints and uncertainty far beyond individual behaviour-change experiments. The research supports the value of translating intentions into action plans; it does not prove that a particular planning framework will prevent complex projects from running late.
The relationship between emergency rescue and organisational learning needs more direct research.
The suggestion that repeatedly rescuing poor planning may preserve dysfunctional systems is consistent with systems thinking and observational experience, but this essay does not cite direct experimental evidence that refusing rescue reliably improves future planning.
Power changes who can refuse transferred urgency.
Employees, freelancers and small suppliers may understand that a deadline was created by somebody else's delay yet lack the commercial or organisational power to reject it. A fuller treatment should examine how hierarchy, employment insecurity and client concentration affect temporal autonomy.
Some industries legitimately rely on variable and rapidly changing demand.
Construction, healthcare, emergency response, logistics, professional services and other fields can contain unavoidable peaks and genuine last-minute changes. Distinguishing preventable planning failure from inherent operational uncertainty requires sector-specific evidence.