When “clear enough” turns out not to be clear at all.
I’ve learned to pay attention to the moment when everyone feels good about a decision.
That confidence right after the meeting ends, that says, we’re aligned.
Because that’s usually where the trouble starts.
What should’ve been a simple change (a tool update, a small process tweak) creates far more friction than anyone expected. The change is announced in a meeting, captured on a slide, and reinforced with a follow-up email. From the outside, it looks clear. From the inside, it often isn’t. In that moment, it feels sufficient. The message was sent. The expectation was set. Surely the team will adapt. Except… they don’t.
People are confused. Small mistakes pile up. Deadlines slip just enough to be annoying but not enough to trigger alarms. And eventually, someone asks the question everyone is thinking: “It’s not even a big change. Why is this so difficult?
The answer is usually simpler than it sounds.
The change was communicated, but it wasn’t translated.
People didn’t resist the tool. They resisted the ambiguity around it.
And ambiguity has a special talent for turning small shifts into unnecessary mess. Especially when everyone assumes someone else understands.
When clarity is assumed, confusion is guaranteed.
In technology rollouts, leaders often feel they’ve communicated enough because they understand the change deeply. They’ve lived with it for months. They’ve debated it. They’ve made peace with it.
The problem is that familiarity creates blind spots.
What feels obvious to the person announcing the change rarely feels obvious to the people who are expected to live with it. Especially when those people are already busy, already stretched, and already juggling more context than anyone realizes.
People don’t struggle with change because it’s hard.
They struggle because they’re not sure what it means for them.
Understanding was assumed, but orientation was needed.
Those are not the same thing.
Research has shown that the highest-performing transformations have one thing in common: people understand not just the “what,” but the “why” and the “how.”
And that employees who lack context are 2.5× more likely to resist changes, even simple ones.
And no, ambiguity is rarely the only thing at work.
When this pattern shows up, it’s tempting to treat it as a communication issue and move on. Send another email. Schedule another meeting. Clarify the slide.
But resistance rarely has a single cause.
What I see most often is a cluster of very human reactions. Normal ones. Predictable ones. Fixable ones, if you know what you’re looking at.
Here are the usual suspects.
Sometimes it’s not the change. It’s the timing.
Sometimes people aren’t resisting the tool at all.
They’re resisting one more thing landing on an already full plate.
This is called a “cumulative change load,” and it’s real:
Employees experiencing change fatigue are 35% less likely to adopt new behaviors, even when those changes are designed to help them.
In our case, the team was juggling a re-org, new reporting deadlines, and onboarding new hires… all before this “simple update” dropped.
It wasn’t the update. It was the season it arrived in.
Sometimes resistance is about identity.
This one surprises people the first time they notice it.
Not all resistance is about disagreement. Sometimes it’s about self-preservation.
A high performer who has mastered an existing system may quietly panic when a new one appears. Not because they’re unwilling to learn, just because competence is part of how they define themselves.
Change threatens that, even when no one says it out loud.
It’s not logical. It’s emotional. And it’s deeply human.
And sometimes silence is the loudest signal.
One of the most misunderstood forms of resistance is polite agreement.
You know the one:
“Yep, we’re good.” “Sounds fine.” “No questions from us.”
But behavior tells a different story.
Teams nod along when they don’t feel safe asking questions, when they assume everyone else understands, or when they don’t want to be the person who slows things down.
Amy Edmondson’s work at Harvard is clear:
“When psychological safety is low, silence becomes self-protection, not alignment.”
If no one is asking questions, it doesn’t mean they understand.
It often means they don’t feel they can.
When “one more thing” becomes the breaking point.
Even a helpful change can trigger resistance if people feel stretched thin.
The emotional bandwidth of the workforce has become one of the strongest predictors of transformation success.
In our scenario, the team had been carrying quiet burnout for months. The change wasn’t the problem; it was the weight underneath it. Small shifts feel big when people are tired.
A few things that actually help:
None of this requires a grand program. Just a little more intention.
-
- Say the same thing more than once. Repetition isn’t redundancy. Repetition is clarity.
-
- Translate the change, don’t just announce it. Answer the questions people won’t ask out loud:
-
-
- What does this mean for me?
-
-
-
- Why now?
-
-
-
- What should I expect to feel?
-
-
- Make space for hesitation. Give teams a safe moment to say: “I’m confused.” or “I’m not comfortable yet.” That honesty can save months of friction.
-
- Name the season people are in. If the team is overloaded, acknowledge it. People move faster when they feel understood.
-
- Pair empathy with expectation. The strongest leadership move is: “I know this is hard, AND I believe you can do it.” People rise when someone sees both their struggle and their strength.
In the end, it comes down to this:
Most resistance isn’t about the tool, the process, or the technology.
It’s about the human experience of being asked to change. Sometimes when they’re tired, uncertain, overwhelmed, or quietly afraid.
When leaders assume clarity, people struggle. When leaders create clarity, people move.
The change isn’t the challenge. The disconnect is.
And the moment we understand that, the resistance becomes less of a barrier and starts looking like a signal that tells us where people need us most.
About The Shift Series
Shift Happens is a series exploring how organizations can turn disruption into direction. We write about the real, human side of work, where change, technology, behavior, and leadership collide in ways no framework fully captures.
Every article follows one of the five currents that shape modern work:
The Human Side of Transformation, the heartbeat beneath the strategy.
Change Management as the Missing Discipline, the discipline hiding in plain sight, quietly determining who succeeds.
Technology, Tools + Human Behavior, the space where logic meets instinct, and where most rollouts live or die.
Organizational Structure, Power & Governance, the lines, ladders, and tensions that decide how work truly flows.
Leadership Micro-Shifts, Governance & Operating Models, the small shifts that create disproportionate impact.
We combine lived experience with practical insight. The kind you can apply the same day, not someday.
Shift happens! But with the right mindset, it happens through you.
If your organization is navigating a shift in technology, structure, or culture and needs practical, human-centered support, reach out.
This is the work we love! And the work we do best.
