There’s a kind of energy that shows up in helping organizations.
Fast. Focused. Responsive.
It feels like purpose.
It feels like impact.
It feels like: this is why we’re here.
And sometimes, it is.
But over time, that same energy can quietly become something else.
An addiction to urgency.
When Everything Is Urgent
In organizations serving vulnerable populations, urgency makes sense.
Needs are real.
Consequences are immediate.
Delays can matter.
So teams respond quickly. They step in. They solve.
And again…for a while…it works.
But when urgency becomes the default, something shifts:
Everything starts to feel equally critical.
And nothing gets fully addressed.
The Illusion of Progress
Urgency is rewarding.
You can see the result immediately:
- The problem is handled
- The client is supported
- The situation is stabilized
It creates a sense of momentum. Even meaning.
But here’s what often goes unexamined:
Most urgent fixes are temporary solutions to recurring problems.
So the same issues come back, just in slightly different forms.
And the team responds again.
And again.
And again.
The Cycle We Don’t Name
Over time, a pattern forms:
- A problem emerges
- The team responds quickly
- The immediate issue is resolved
- No time is taken to examine root causes
- The problem reappears later
- It’s treated as a new crisis
What feels unpredictable…
is often structurally reproduced.
This is where helping can start to hurt.
Not because the response is wrong.
But because the system never changes.
Why Urgency Gets Rewarded
Organizations don’t just tolerate urgency; they often reinforce it.
The people who:
- jump in fastest
- stay late
- fix things under pressure
are seen as indispensable.
And they are.
But the system starts to value responsiveness over reflection.
And reflection is where learning happens.
There’s a parallel here to what’s explored in When Helping Hurts: the idea that well-intended, immediate responses can sometimes prevent deeper, more sustainable change.
Inside organizations, urgency can function the same way.
It solves the moment while preserving the pattern.
What Urgency Crowds Out
When urgency becomes constant, several things quietly disappear:
- Space to analyze patterns
- Time to redesign processes
- Clarity around roles and decision-making
- Opportunities to prevent problems instead of reacting to them
The organization becomes highly skilled at responding
and increasingly limited in its ability to improve.
Why This Leads to Burnout
This is the part that often confuses high-capacity professionals:
“I’m doing meaningful work. I’m helping people. Why am I so exhausted?”
Because you’re not just solving problems.
You’re solving the same problems repeatedly
without the ability to change the conditions creating them.
That’s not just exhausting.
It erodes a sense of progress.
And over time, it creates a quiet kind of fatigue that isn’t about effort, it’s about futility.
The Shift That Has to Happen
This doesn’t mean urgency is the problem.
It means urgency without reflection is the problem.
Healthy systems are built on a pause point. They ask:
- What needed to be handled immediately?
- What needs to be understood so this doesn’t happen again?
Without the second question, the first one never ends.
A Different Definition of Strength
The strongest organizations aren’t the ones that respond the fastest.
They’re the ones that:
- reduce how often urgency is needed
- learn from patterns instead of repeating them
- build systems that hold under pressure
Because constant responsiveness doesn’t create stability.
It creates dependence on the people who can keep up.
The Question to Sit With if everything feels urgent, it’s worth asking:
What are we not making time to understand?
Because what we don’t examine, we will continue to experience.
And eventually, the cost shows up in the people doing the work.
Not because they can’t handle urgency.
But because the system never stops needing it.
Leave a comment