Context
I’ve had the opportunity to sit in the middle of organizational change more than once — close enough to leadership to understand intent, and close enough to teams to experience how that intent actually landed.
In each case, leaders were trying to bring clarity to situations that felt uncertain. The paths they chose were different. The motivations were similar. What interested me most wasn’t whether any particular approach was right or wrong, but how much else was happening at the same time.
What I noticed (by sitting between)
From the leadership side, the arrival of new language and rhythm often felt grounding. There was relief in having something concrete to point to — a way to describe priorities, decisions, and expectations more clearly. Structure created a sense of forward motion.
From the team side, the experience was more nuanced. People participated. They adapted. They did what was asked. But alongside that, I could sense questions forming that didn’t yet have a clear place to go.
Not objections, exactly. More like quiet uncertainty.
Is this what we were trying to solve?
Is it okay that parts of this still feel unclear?
Sitting between those perspectives made it clear how easily meaning can diverge, even when everyone is acting in good faith.
How this tension shows up
A system can arrive and immediately reduce ambiguity for leaders while increasing it for others. New structure can feel like stability on one side of the organization and constraint on the other — not because of the system itself, but because of how differently people experience change.
This divergence is subtle. It doesn’t announce itself. There’s no obvious failure or visible resistance. Instead, it shows up as careful language, fewer questions, and a quiet narrowing of what feels safe to say.
None of this appears on a rollout plan.
What often makes the difference
What I noticed over time is that there’s usually a narrow window around these moments where a different kind of work is possible.
Not refining the framework.
Not adding more meetings.
But slowing down just enough to surface how the change is being experienced across the organization.
When that happens, leaders gain insight into what the system is actually touching. Teams gain confidence that their experience matters. And the structure — whatever form it takes — has a better chance of being absorbed rather than endured.
What became clearer over time
This isn’t about fixing anything or choosing the right methodology. It’s about recognizing that clarity doesn’t travel evenly, and that tension can exist long before it becomes visible.
Having someone who can remain in that middle space — listening in both directions, noticing where understanding thins out, and helping make those gaps discussable — can change how the next steps unfold.
Often, simply noticing this moment is enough to shift what comes next.