Urgency and Fear are not the same thing.
- Rachel

- Jul 20
- 4 min read
Several years ago, I was involved in a healthcare process improvement initiative. We had assembled a strong team, spent time understanding the problem we were trying to solve, and developed a plan that felt ambitious but achievable. The work was moving forward, not always quickly, but steadily.
Then a leadership transition occurred.
The project itself didn't change. The objective was the same, the team was the same, and the work still needed to be done. What changed was the expectation around how quickly we could get there.
During one meeting, we were asked whether we could accelerate the timeline. It wasn't presented as a demand, and the reasons were understandable. People wanted to see progress. There was interest from stakeholders. Momentum felt important.
Around the table, heads nodded. Questions were answered. The discussion moved on.
On the surface, it looked like alignment.
What I remember most, though, is what happened after the meeting.
In the days that followed, I started noticing small changes in the way people talked about the project. None of them were dramatic. In fact, if you'd asked me at the time whether anything was wrong, I'm not sure I would have said yes.
What struck me was how often conversations seemed to begin after the meeting had ended.
Someone would stop by my office and mention a concern they hadn't brought up during the discussion. A quick question in the hallway would turn into a thoughtful conversation about a risk the team might not be accounting for. Occasionally, a colleague would close the door, take a seat, and share an observation that felt important enough to discuss, but apparently not important enough to raise in front of the group.
At first, I chalked it up to the normal rhythm of project work. Process improvement initiatives are complex, and people often need time to think through an idea before they're comfortable sharing it. That seemed reasonable.
But the pattern continued.
What made it interesting was that the concerns themselves weren't particularly controversial. Most weren't new. They were thoughtful observations from people who cared about the work and wanted the project to succeed.
A question about whether the timeline was realistic.
A concern that a dependency hadn't been fully considered.
An observation that a decision made sense in theory but might create challenges when it reached the front line.
None of these conversations felt disruptive. In fact, they were exactly the kinds of conversations that help projects succeed.
What I couldn't understand was why they were happening in offices, hallways, and parking lots instead of around the conference table.
The project itself continued to move forward. Progress was being reported, milestones were being updated, and from most perspectives things appeared to be on track. If you looked only at the project plan, you would have seen a team moving with purpose and speed.
Yet I found myself paying less attention to the project plan and more attention to the conversations surrounding it.
In meetings, I began listening for questions that weren't asked. Sometimes someone would start to raise a concern, then soften it before finishing the thought. Other times a question would be framed so carefully that it almost sounded like an apology for asking it. People still contributed, but the discussions felt different than they had only a few weeks earlier.
I couldn't quite explain why.
No one was being unreasonable. No one was demanding silence. There were no tense confrontations or impossible expectations.
And yet something had changed.
The more I reflected on it, the more I realized that what I was observing could easily be mistaken for urgency. Everyone was moving quickly, working hard, and focused on meeting the revised timeline.
From a distance, it looked like the team had simply become more urgent.
Looking back, I'm not sure that's what I was seeing at all.
For years, I thought what I was seeing was urgency.
The timeline had accelerated, expectations had increased, and people responded the way professionals often do: they adapted.
But the more distance I gained from that experience, the more I began to question that interpretation.
I've been part of other projects with similarly aggressive timelines. In some cases, the pressure was even greater. Those teams worked hard, moved quickly, and faced significant expectations.
Yet they felt different.
What distinguished those teams wasn't the absence of pressure. It was a shared understanding of why the pressure existed.
People understood the objective. They understood what needed to happen and why it mattered. As a result, difficult conversations remained part of the process. Concerns surfaced early, assumptions were challenged, and disagreement was viewed as a contribution rather than an obstacle.
Looking back at the process improvement initiative, I think the leadership transition changed more than the timeline.
It changed the conversation.
The new expectations created uncertainty, and uncertainty has a way of changing how people assess risk. Concerns that may have been voiced openly a few weeks earlier now seemed to require more careful consideration. Questions became prefaced with explanations. Observations became side conversations.
Not because people cared less.
Because they cared enough to wonder how their concerns would be received.
That distinction matters.
Urgency invites people into the conversation because everyone is focused on solving the same problem.
Fear causes people to become more cautious about entering the conversation at all.
That's why the hallway conversations stayed with me.
The concerns weren't hidden because they lacked value. They were hidden because they no longer felt as safe to raise in the room where decisions were being made.
And that's what I've come to believe is one of the clearest differences between urgency and fear.
When urgency is rooted in understanding, people bring their concerns into the room.
When fear begins to take hold, the conversation slowly moves out of it.
I've come to believe that the most effective urgency isn't created through pressure.
It's created through clarity.
When people understand what matters, why it matters, and how they contribute to the outcome, they don't need to be pushed forward.
They move together.





Comments