Urgency is one of the most powerful forces in institutional life.
Deadlines compress decisions. Budgets tighten timelines. Conflict escalates pressure.
In these moments, leaders often say some version of the same thing: “We just need to move quickly.”
And sometimes that’s true. But urgency has a pattern.
When urgency enters the room, three things often happen simultaneously:
- criteria become implicit
- consultation narrows
- decisions move closer to positional authority
None of this is necessarily malicious. It’s structural.
Urgency compresses deliberation. And when deliberation compresses, power concentrates.
That concentration has consequences. Not evenly distributed consequences but patterned ones.
The people most comfortable speaking in fast-moving decisions are often those with:
- institutional credibility
- positional authority
- proximity to leadership
- confidence navigating ambiguity
Those without those advantages often experience something different.
They experience urgency as exclusion.
Ideas surface quickly and disappear just as quickly. Decisions move forward before questions can fully form. Concerns are framed as slowing the work.
And the message becomes subtle but clear:
Speed matters more than relationships.
The Action Bias Beneath Urgency
Another dynamic often sits quietly underneath urgency: action bias.
Action bias is the tendency to prefer doing something quickly over pausing to understand a situation more fully, even when the action itself may not improve the outcome.
In leadership settings, action bias often appears as momentum.
A problem surfaces. A solution is proposed quickly. The group moves toward implementation before the underlying conditions have been fully examined.
Speed feels productive. It signals responsiveness.
But speed can also bypass the questions that would have changed the decision.
Urgency and action bias reinforce one another.
Urgency creates pressure to move. Action bias provides the psychological comfort of doing something immediately.
Together, they can produce decisions that feel decisive in the moment but generate more work later.
Case Example: Hiring
I once worked with a team that needed to fill a role quickly after an unexpected resignation.
The language of urgency entered the conversation almost immediately.
“We need someone in the seat as soon as possible.”
A job posting was drafted quickly based on the previous description. The hiring committee moved directly to screening applications.
A few weeks later, concerns surfaced.
The role had been designed years earlier around a different set of priorities. Important accessibility considerations hadn’t been built into the hiring process. The team’s needs had shifted in ways the posting didn’t reflect.
What looked like efficiency at the beginning created additional work later: redesigning responsibilities, revisiting expectations, and repairing trust with candidates who had been evaluated through an outdated lens.
The urgency wasn’t the problem.
The absence of a brief pause to examine the role design was.
Case Example: Responding to Conflict
In another situation, a leader was informed that tensions had escalated between two members of their team.
Wanting to address the situation quickly, the leader scheduled a joint meeting the same day.
The intention was good: bring everyone together, clear the air, move forward.
But neither person had been asked beforehand what had happened from their perspective, or whether they felt ready for that conversation.
When the meeting began, the conflict intensified rather than settled. Both people felt misunderstood and unprepared to navigate the conversation in front of each other.
The leader had moved quickly in the name of resolution.
But the situation needed something slightly different first: individual conversations to understand the dynamics, the risks involved, and what kind of engagement would actually support repair.
In care-centered and trauma-informed approaches to conflict engagement, readiness and consent matter. People need space to share their experience before being asked to negotiate it publicly.
By moving straight to a joint meeting, the process unintentionally created more rupture. Each person arrived feeling exposed rather than supported, and the conversation quickly polarized.
Speed created a response.
But it bypassed the conditions needed for repair.
When Urgency Becomes a Leadership Habit
The irony is that urgency is often invoked to solve problems created by speed in the first place.
Policies drafted without consultation. Processes implemented before accessibility is considered. Hiring decisions rushed under staffing pressure.
Later, leaders find themselves repairing trust that could have been preserved with a slightly slower start.
This doesn’t mean urgency is always wrong.
Some situations genuinely require rapid action.
But urgency becomes a trap when it becomes the default operating condition rather than a conscious choice.
Inclusive leadership asks something slightly different.
It asks leaders to notice when urgency is shaping the process and to name it explicitly.
You might say:
“This timeline is tight because of the budget cycle.” Or “We need to move quickly on this piece, but there are elements we can slow down.”
Naming urgency changes the dynamic.
It moves urgency from an invisible pressure to a visible constraint.
And visible constraints can be negotiated.
Invisible ones cannot.
A Small Practice
When urgency enters a decision, pause and ask:
- What part of this truly requires speed?
- What part could benefit from reflection?
- Who has the ability to speak in this timeline — and who doesn’t?
- What would change if we slowed, not the whole part but one step?
Sometimes the most responsible decision is the fastest one.
But often the most responsible decision is the one that pauses just long enough to see what urgency might be hiding.
-sd