Leaders often believe people will not change unless the situation feels urgent.
They warn that the business will be left behind, competitors are moving faster, technology is changing everything, or the current way of working is no longer acceptable. Deadlines tighten. New language appears. Employees are told the transformation must happen now.
Sometimes the urgency is real.
A serious financial problem, regulatory requirement, customer failure, or immediate safety concern requires decisive action.
But when every initiative is presented as a crisis, urgency stops creating focus. It creates fatigue.
Manufactured urgency has a short half-life
Fear can produce movement. People respond to a deadline, attend the meeting, complete the training, and adopt the language leadership is using.
That does not mean the change has taken hold.
Employees quickly learn whether the urgent initiative will receive sustained attention or be replaced by the next priority. If previous transformations faded after the launch, skepticism is reasonable.
Constant urgency also makes it difficult to distinguish what truly matters. When everything is critical, employees make their own choices about which messages to believe.
Momentum built on pressure often lasts only as long as the pressure remains.
People need a reason, not only a warning
Change communication frequently explains what is happening without explaining why it is worth the disruption.
Employees need to understand the problem in practical terms. What is not working today? Who is affected? What becomes possible if the change succeeds? What will be better for customers, employees, or the long-term health of the organization?
A credible reason does not require pretending everyone will benefit equally. Some changes create real inconvenience, uncertainty, or loss. Leaders build more trust when they acknowledge the tradeoffs honestly.
The case for change should be specific enough for employees to connect it to their work, not only to an executive presentation.
Clarity reduces resistance
Resistance is often treated as an attitude problem.
Sometimes it is a response to ambiguity.
Employees may not know what will change, when it will happen, how their role will be affected, what support will be provided, or which existing work will stop. They hear that the change is essential while watching leaders avoid the decisions required to make it possible.
Leaders should explain what has been decided, what remains open, who owns the next step, and how feedback will influence implementation.
Clarity does not eliminate disagreement. It prevents uncertainty from growing unnecessarily.
Participation improves the design
The people closest to the work often understand implementation risks leadership cannot see.
They know where information is missing, which customer exceptions matter, how workloads interact, and what previous attempts have taught the organization.
Involving employees is not simply a tactic for gaining buy-in. It improves the quality of the change.
Participation needs boundaries. Leaders should be clear about which decisions are fixed, which elements can be shaped, and how input will be used. Asking for feedback after every important choice has already been made creates cynicism rather than involvement.
Make the first change small enough to learn from
Large transformation language can make the work feel distant and overwhelming.
A smaller pilot creates evidence. It allows the organization to test assumptions, discover friction, build confidence, and demonstrate progress without committing everyone to an unproven design.
The pilot should be meaningful enough to reveal how the change works in practice. It should have a clear owner, a defined group, success measures, and a decision about what happens after the test.
A pilot is not useful when it remains permanently isolated. The organization needs a path for improving, expanding, or stopping based on what it learns.
Visible progress creates more momentum than slogans
Employees believe change when they can see something become better.
A customer handoff becomes faster. A duplicate report is removed. A manager begins using the new decision process. An employee suggestion changes the implementation. Leadership stops an old requirement rather than adding the new process on top.
These signals demonstrate that the organization is serious.
Progress should be communicated in concrete terms: what changed, what was learned, what remains difficult, and what happens next. Avoid presenting every update as a success story. Honest evidence builds more credibility than excessive celebration.
Managers need support, not only messages
Employees usually experience change through their immediate manager.
Managers are expected to answer questions, translate expectations, adjust work, address resistance, and maintain performance while dealing with their own uncertainty.
A communication package is not enough. Managers need context, decision authority, time, practical tools, and access to answers. Leadership should also listen to what managers are hearing across the organization.
If managers are left to interpret the change independently, employees will receive different versions of the strategy.
Create an honest change rhythm
A practical change rhythm can include:
- A clear statement of the problem and intended outcome
- Visible ownership and decision rights
- Regular updates that distinguish decisions from open questions
- Employee feedback connected to specific implementation choices
- Small tests with defined measures and review dates
- Removal of old work when new work is introduced
- Manager support and opportunities to surface patterns
- Recognition of progress, constraints, and lessons learned
The rhythm creates movement without requiring leadership to generate a new emotional peak every week.
Key takeaways
Urgency can focus an organization during a genuine crisis. Manufactured urgency loses credibility when every initiative is presented as immediate and existential.
Sustainable change comes from a credible reason, clear decisions, meaningful participation, manageable tests, supported managers, and visible progress.
The goal is not to make employees comfortable with every change. It is to create enough trust and clarity for people to engage honestly with the work.
Frequently asked questions
Is urgency necessary for organizational change?
A genuine reason to act matters, but leaders do not need to manufacture crisis. Clarity about the problem, consequences, and opportunity can create movement without constant fear.
Why do employees resist change?
Resistance may come from disagreement, previous experience, unclear expectations, workload, lack of trust, fear of loss, or practical concerns leadership has not considered.
How should employees be involved in change?
Invite input where it can influence the design, clearly distinguish fixed decisions from open questions, and explain how feedback affected implementation.
What makes a good change pilot?
A useful pilot tests a meaningful assumption with a defined group, clear owner, measures, boundaries, review date, and decision about expansion, revision, or stopping.
What is the role of managers during change?
Managers translate the change into daily work, answer questions, surface risks, support employees, and reinforce new behaviours. They need context, authority, time, and ongoing support.
Continue learning
If your organization is experiencing change fatigue, the answer may not be a louder message or a tighter deadline. It may be a clearer reason, fewer competing initiatives, and a more credible path from participation to visible progress.
Connect with Rob to discuss a more intentional approach to leading change.
Learn About AI Foundations