A leader announces the fourth major initiative in eighteen months. Around the room, people nod politely. A few write something down. No one objects, and no one seems convinced. The meeting ends, people return to their work, and the announcement settles into a familiar place: one more change to absorb.
That quiet response is worth noticing. It may be compliance without belief.
We can be tempted to call this change fatigue, then move on as if naming it explains it. But what are people tired of, exactly? The new system, the latest reorganization, another shifting priority? Or the experience of being asked to invest in a change before they know whether it will last?
I believe leaders should take that question seriously. Workplace culture is shaped not only by the changes we introduce, but also by the trust and responsibility we show while introducing them.
1. Is change fatigue really resistance?
Fatigue is not laziness, and it is not automatically resistance to change. People can adapt, learn, and contribute through difficult transitions. But, over time, they may run out of reason to believe that the next change will hold.
There is a difference between “we have been asked to change” and “we have been shown why it matters.” One asks people to comply. The other helps them understand the purpose, the process, and how their work connects to the outcome.
That distinction matters. When the purpose is unclear, or when priorities shift before people see what came of the last effort, employees may reasonably wonder whether this initiative deserves their confidence. Have leaders explained what this change is meant to improve? Have they shown what will remain steady? Have they acknowledged what the previous effort cost the team?
People have freedom to decide how much effort to give. Leaders, in turn, have responsibility for the conditions that make commitment reasonable. Let’s not mistake cautious questions for unwillingness, or polite silence for belief.
2. What does repeated change cost?
The cost is not just time spent learning another process. Repeated change can weaken the credibility of the next announcement. If people have heard “this is the priority” several times, without seeing a clear outcome or honest account of what happened, the next declaration may carry less weight.
It can also reduce people’s willingness to speak up before decisions are locked. Why raise a concern if input has been invited too late to affect the plan? Why point out a risk if previous concerns went unanswered? When people stop offering what they notice, leaders lose information that could help the organization make sounder decisions.
And then there is discretionary effort: the problem-solving, mutual support, and extra care people contribute without being asked. It may disappear gradually, without anyone resigning. People continue doing their jobs, but stop volunteering ideas or helping others navigate the change. That matters for employee retention strategies, because the daily experience of work can influence whether people still see a meaningful future with the organization. No one has to resign to leave.
Silence is not the same as commitment.
3. Do you announce the destination and skip the reasoning?
A destination without reasoning can feel like another demand. People need to understand why the change is happening, what problem it addresses, and how progress will be recognized. They also need clarity about their own role, including how their work connects to other people’s responsibilities.
This is not a call for leaders to explain every detail before a decision can be made. Sometimes a decision must be made under imperfect conditions. But a clear explanation is still a form of respect. If the reasoning is still developing, say so. If there are constraints, name them. Do not present uncertainty as certainty.
4. Do you ask for input after the decision is already made?
A request for input can build trust, but only when people have a real opportunity to influence something. If the outcome is already fixed, say plainly what is decided and where the team’s input can still shape the process.
People can accept limits more readily when those limits are honest. They may not agree with every choice, and participation does not mean every suggestion must be adopted. It does mean employees deserve to understand how their feedback was considered and what happened next. Let’s close the loop rather than leave people to guess.
5. Do you treat the last change as finished when people are still living in its consequences?
A launch date is not the same as resolution. A new system may be active while people are still dealing with unclear handoffs, added work, or problems the rollout did not address. A reorganization may be formally complete while roles and relationships remain unsettled.
What is your team still carrying from the last change? Before introducing the next initiative, check what is working, what is not, and what still needs attention. If a change did not work as intended, acknowledge that directly. Trust is more likely to be earned through an honest account than through pretending the effort had no shortcomings.
6. Do you ask the same people to absorb every change without asking how they are doing?
Some employees become the dependable ones who learn the new tool, explain the revised process, steady colleagues, and keep the work moving. Their competence can make it easy to overlook their strain. Have you asked how they are doing, and then made room for an honest answer?
A genuine check-in is not a way to extract reassurance. It is a chance to listen, notice workload, and determine whether support or priorities need to change. We need to recognize people not only for what they can carry, but also for the responsibility leaders have to make the load workable.

7. How do we help people believe again?
Engagement is not restored by insisting that people be more positive. It is earned through consistent actions that make purpose, truth, and participation more credible.
Start by explaining the process and why each role connects to it. People do not need every answer at once, but they need enough clarity to understand what is expected and where their contribution matters.
Say plainly what is not changing. In periods of uncertainty, a steady purpose, a dependable commitment, or a core responsibility can offer people something real to hold onto. Do not promise that nothing will change if that is not true. Instead, distinguish what is settled from what is still being worked through.
Be honest about what you learned from the last change that did not work. What would you do differently now? What has the organization adjusted? Acknowledging a misstep is not a loss of authority; it can be an act of integrity.
Then give people a real part in how the change happens, even when they cannot determine whether it happens. Invite them to identify risks, improve the sequence, clarify handoffs, or test how a process affects their work. Be specific about what they can influence, and follow up on what you hear.
This is where RUC, “Are You Curious?”, belongs: as a leadership discipline, not a slogan. Are we willing to ask what people are experiencing and listen without preparing a defense? Ron Cooper learned that discipline in the cockpit, where questions and candid observations were never treated as weakness; they were part of how a crew made sound decisions. The same holds in the boardroom. The Three R’s of workplace culture offer a companion idea here: unresolved frustration and resistance deserve curiosity and accountability, not quick labels.
Curiosity does not remove standards. It helps us understand what is happening before we decide how to respond. That is useful work for leadership development, for building company culture, and for leaders who want communication to become genuine connection. It also asks something of us: patience, follow-through, and the humility to adjust when the facts call for it.

Will the next announcement meet a different response?
Let’s return to that meeting room. A leader announces another major initiative. The team listens. What happens next depends, in part, on what leaders have done before the announcement: explained the reasoning, addressed what remains unfinished, and made space for real questions and honest answers.
We cannot expect belief to return in one meeting. It grows through consistency, clarity, and respect over time. Executive coaching and leadership development may help leaders examine their own habits, but the daily work belongs to all of us: communicate honestly, listen carefully, and take responsibility for the effects of our decisions.
When the next change is announced, will your team simply nod, or will they understand why it matters and see how their part connects?
Let’s make the next change more worthy of belief.
How has your team handled a season of constant change? What helped people stay engaged, or what do you wish leaders had done differently? Share your experience and what you would recommend to others.