When urgency outruns authority
But the things required to move—decisions, assets, approvals, direction—lag just behind the demand to deliver. So teams accelerate into space that hasn’t been built yet. They prepare for work they aren’t authorized to finish.
They build around decisions that haven’t been made.
They rush toward milestones that assume alignment that doesn’t yet exist. This is the strange rhythm of modern project work:
move quickly, but wait often.
be accountable, but not empowered.
be responsive, but not decisive.
It’s a design flaw in how authority and urgency are distributed.
Where the Delay Actually Lives
From the outside, it can look like a failure of execution.
But most of the time, the delay isn’t happening at the level of effort.
People are working. Design is happening. Development is happening. Drafts are being
created. Interfaces are being assembled with placeholders and best guesses.
What isn’t happening is resolution.
Not because no one cares—
but because decisions are layered inside hierarchies, approvals, contracts, committees,
and competing priorities that move at a different speed than production.
Pressure travels downward easily. Clarity does not.
So urgency reaches the people doing the work long before authority does.
And that gap becomes the waiting room where entire projects quietly stall.
When Leadership Is Also Waiting
It’s easy to assume this is about bad leadership.
But more often, it’s about constrained leadership.
Managers are frequently relaying expectations that didn’t originate with them.
They’re translating commitments made above their pay grade.
They’re navigating political realities, shifting priorities, and incomplete information of their own.
In that position, certainty becomes performative.
Because saying “we don’t know yet” can feel risky when expectations are already set.
So momentum is signaled before direction is stable.
Schedules are published before dependencies are resolved.
Teams are asked to begin before the path is fully visible.
Not out of malice.
Out of necessity, optics, and institutional habit.
The problem isn’t that leadership is demanding speed.
It’s that speed is being requested without the means to actually move.
The Guilt That Creeps In
And somewhere inside all of this, something quieter starts to happen.
People begin to wonder if the problem is them.
Maybe they’re not communicating well enough.
Maybe they should be pushing harder.
Maybe they should be more proactive, more visible, more available.
Remote work doesn’t help this feeling.
When your effort is mostly invisible, it’s easy to assume that invisibility means inadequacy.
You start compensating.
You answer messages faster.
You stay online longer.
You over-explain progress that hasn’t been allowed to progress.
Not because anyone explicitly asked you to—
but because waiting under pressure feels too much like failing.
So burnout doesn’t just arrive as exhaustion.
It arrives as guilt.
Guilt for being tired.
Guilt for being blocked.
Guilt for not being able to move faster inside a system that won’t move with you.
And that guilt is heavy, because it feels personal…
even when the conditions are structural.
The Theater of Progress
From a distance, everything looks active.
Status meetings happen. Dashboards update. Tickets move through systems that suggest momentum.
But activity is not the same as forward motion.
When projects are forced to advance without stable decisions, they begin to loop instead of progress.
Work is started, paused, revised, restarted.
Designs are drafted, reworked, discarded.
Solutions are built for assumptions that change midstream.
And because no single person owns the whole picture, the cycle repeats without being named.
It feels busy.
It looks productive.
But it rarely feels complete.
This is how organizations exhaust teams without necessarily moving faster.
What Gets Lost
Not just time.
Not just morale.
But ownership.
When teams are consistently asked to move without meaningful control over outcomes,
they begin to feel like temporary labor inside permanent uncertainty.
They execute.
They comply.
They deliver what they can.
But the sense that the work truly belongs to them—
that they are shaping something, not just assembling it—
slowly erodes.
And once that disappears, craftsmanship follows.
Not because people stop caring,
but because caring without agency is unsustainable.
This Is Not About Blame
Most people inside these systems are doing their best with what they’re given.
The problem is not individual effort.
It’s the design of how responsibility, authority, and timing are separated.
When urgency arrives without permission,
and accountability arrives without control,
people get trapped in the narrow space between expectation and feasibility.
That space is where burnout grows.
That space is where quality quietly drops.
That space is where “hurry up and wait” becomes the normal rhythm of work.
And normal is the hardest thing to question.
Closing
Most people don’t mind working hard.
What wears them down is working fast while standing still.
Being told the moment matters
while being unable to change what happens next.
Being accountable for outcomes
without being trusted with the conditions required to reach them.
And after a while, even the waiting starts to feel like a personal failure.
Like you should be doing more.
Like you should be moving faster.
Like if you were better, sharper, more organized, somehow this would hurt less.
But this isn’t about individual effort.
Hurry up and wait is not a personal flaw.
It’s what happens when urgency is easier to distribute than authority,
and pressure moves faster than clarity.
Until that changes, teams will keep absorbing stress that belongs to the structure.
They’ll keep mistaking motion for progress.
And they’ll keep wondering why they feel so tired, even when they never stop working.
Not because they don’t care.
But because caring inside misaligned systems is expensive.
And eventually, someone always pays.
Leave a Reply