How everyday moments determine whether change becomes real
Many leaders assume that once the strategy is clear and the plan is well structured, change will follow. They invest in defining direction, aligning leadership teams, and communicating the roadmap across the organization.
Yet when you observe how change unfolds in practice, a different pattern appears. Kickoff meetings generate initial clarity, but not sustained movement. Decisions return to familiar logic under pressure. Conflicts are avoided rather than used to resolve tension. People listen carefully, but they do not fully engage. The issue is rarely clarity.
It is that the moments where change should be experienced are not designed to move people.
Leaders often respond by increasing communication. More updates, more presentations, more explanation. But engagement does not increase proportionally.Because engagement is not driven by communication alone.
It is shaped through experience.
People do not adopt change because they understand it. They adopt it when key moments in the system begin to work differently.
The misunderstanding: we treat engagement as communication instead of design
In many transformation efforts, one assumption quietly shapes leadership behavior.
- Myth: If we communicate clearly and consistently, people will engage with the change.
- Reality: People engage when the environment invites participation and makes new behavior feel natural.
- When the two conflict: Participation overrides communication.
Leaders often increase clarity when engagement feels low. The logic is understandable. If people are not moving, the assumption is that they do not yet understand. But most organizations do not lack understanding. They lack moments where people can act differently.
Employees do not experience change through strategy decks. They experience it through decisions, interactions, tensions, and consequences. When those moments remain unchanged, behavior remains unchanged.
Change moments as a design lever
Change does not spread through explanation. It spreads through experience.
Every organization operates through recurring moments — kickoff sessions, decision forums, escalation discussions, cross-functional tensions, review meetings. These moments are where people interpret how the system actually works.
A “change moment” is not a soft concept. It is a behavioral mechanism. It carries consequences. It signals what is safe, what is rewarded, and what is expected. Because these moments repeat, they create patterns. Patterns create expectations. Expectations shape behavior.
If these moments reinforce the old system, the change remains conceptual.
If they are redesigned to reinforce the new system, change begins to feel normal.
Change moments that determine whether people move
1) The Kickoff Experience Trigger
The kickoff is often treated as a communication event. In practice, it is the first moment where people infer their role in the change. It signals whether they are expected to align, contribute, or take ownership.
A familiar case: A global organization launches a transformation program to simplify its operating model. The kickoff brings together senior leaders and key managers. The CEO presents the rationale clearly, supported by a structured deck outlining the future state.
There is a short Q&A. Most questions focus on clarification. The session ends on time.
Participants leave aligned in language, but not in action. In the following weeks, each function interprets the change differently. Some move cautiously. Others wait.
The kickoff created understanding, but not ownership.
What this teaches
When kickoff moments are designed as one-way communication, people learn that their role is to absorb, not to shape. Engagement becomes passive. Ownership remains limited.
A small practice that shifts it (3 minutes): At the end of a kickoff, shift the moment: “Before we close, take one minute: what is one decision you will make differently next week because of this change?”Invite a few responses.
This moves the moment from explanation to commitment.
Boundary: Participation must be structured. Without direction, it can diffuse rather than focus energy.
2) The Decision Moment Trigger
Decisions are where strategy becomes operational reality. Every decision either reinforces the change or quietly restores the previous system. People learn quickly which logic actually governs outcomes.
A familiar case: In a weekly leadership meeting, a trade-off emerges between speed and risk control. The organization is attempting to move toward faster experimentation. After brief discussion, the senior leader concludes: “We’ll go with the safer option for now.”
The decision closes the topic. No explicit link is made to the transformation.
Over time, similar decisions accumulate. People begin to understand that the new direction is conditional. The old logic still governs under pressure.
What this teaches
People do not follow strategy statements. They follow decision patterns. If decisions consistently revert to the old logic, the change loses credibility.
A small practice that shifts it (60 seconds): Before closing, make the trade-off explicit: “Which option reinforces the direction we said we’re moving toward — and what risk are we willing to accept?”.
This makes the decision intentional rather than habitual.
Boundary: The goal is not to prolong decisions, but to clarify the logic behind them.
3) The Conflict Utilization Trigger
Conflict is not a disruption to change; it is one of the few moments where assumptions become visible. How leaders handle tension determines whether clarity increases or is postponed.
A familiar case: During a transformation, two functions disagree on resource allocation. The discussion becomes tense. A senior leader intervenes: “Let’s take this offline so we don’t slow the meeting.” The topic is deferred.
In later meetings, similar tensions resurface. Alignment appears, but execution slows. Decisions lack clarity because underlying disagreements remain unresolved.
What this teaches
When conflict is avoided, people learn that maintaining harmony is more important than resolving reality. Misalignment becomes structural.
A small practice that shifts it (2 minutes): When tension appears, name it: “It sounds like we have two competing priorities. Let’s surface both clearly before deciding.”
This reframes conflict as input rather than disruption.
Boundary: Not all conflicts need immediate resolution. The shift is about visibility, not forced closure.
4) The Participation Design Trigger
Participation is often left to personality. In reality, it is shaped by how the moment is structured. The design of interaction determines whose thinking enters the system.
A familiar case: A transformation program includes workshops to support adoption. Leaders present frameworks and invite discussion. A few voices dominate. Others remain silent. After the sessions, participants report that they understand the change. But behavior remains uneven.
The moment allowed contribution, but did not structure participation.
What this teaches
Participation without structure creates imbalance. Some engage deeply. Others disengage quietly. The change spreads unevenly.
A small practice that shifts it (3 minutes): Introduce simple structure: “Take one minute individually: what would need to change in your daily work for this to become real?” Then collect responses systematically.
Structure expands participation.
Boundary: Over-structuring can reduce spontaneity. The aim is to enable contribution, not control it.
5) The Reinforcement Moment Trigger
Recognition is not neutral. It signals what the organization values in practice. It shapes what people choose to repeat.
A familiar case: In a leadership review, one team presents strong short-term results achieved through familiar methods. Another team shares how they experimented with a new approach, learned from early setbacks, and adapted. The first team receives more recognition because the results are more visible.
Over time, teams draw a clear conclusion: traditional execution remains the safer path.
What this teaches
Recognition directs behavior. If the system rewards outcomes achieved through old patterns, the change remains secondary.
A small practice that shifts it (60 seconds): When recognizing performance, include the behavior: “I want to highlight not just the result, but how this team adapted their approach in line with the new direction.”This aligns reinforcement with transformation.
Boundary: Recognition must remain credible. It should connect behavior to meaningful outcomes.
How these moments shape engagement
These moments do not operate independently.
- The kickoff defines initial ownership.
- Decisions reinforce priorities.
- Conflict determines clarity.
- Participation shapes involvement.
- Recognition reinforces direction.
Together, they form the lived experience of change.
People do not evaluate transformation based on messaging. They evaluate whether these moments feel different.
If they do not, the system remains unchanged.
If they do, behavior begins to shift.
Leaders cannot avoid shaping these moments. Every interaction carries a design — whether intentional or not.
The takeaway
Change leadership is often framed as alignment and execution.
In practice, it is design. Not large-scale design, but micro-design — how key moments are structured.
A useful question is: “Where in our system does the old behavior still feel easier than the new one?”
That question reveals where the experience of change still contradicts the intention. And those moments can be redesigned. Not through programs. Through repetition. Because engagement is not created by communication.It is created by experience.
Mini-Exercise: Your Change Moment Scan (7 minutes)
Think about the past few weeks.
- Where did kickoff create clarity but not ownership?
- Which decisions reinforced old logic?
- Where was conflict avoided instead of used?
- Who participated — and who stayed silent?
- What behavior was most visibly recognized?
One of these moments is shaping how people experience the change.
That is your leverage point.
Executive Reflection (for the week ahead)
Before your next leadership interaction, pause.
- Consider what people will experience in that moment — not what they will hear.
- Think about how your structure shapes participation, clarity, and ownership.
- Ask yourself what behavior will feel safer after the interaction.
- Then shift one moment deliberately.
Because change does not move through explanation.
It moves through experience.
References
- Schein, E. H. Organizational Culture and Leadership.
- Edmondson, A. C. The Fearless Organization.
- Heath, C. & Heath, D. Switch: How to Change Things When Change Is Hard.
- Coyle, D. The Culture Code.
- Weick, K. Sensemaking in Organizations.
