How clarity, capacity, operational reality, Acceptance, and Ownership shape employee responses across concurrent initiatives
“The team is resisting the new process” sounds like a diagnosis. Usually, it is a description that requires further investigation.
Employee resistance to change can appear as continued use of an old system, missed training, objections in meetings, workarounds, delayed decisions, limited participation, or declining enthusiasm. These behaviors matter, but they do not explain themselves.
Employees may not understand the purpose of the change. They may lack the capability or time to meet new expectations. They may be concerned about their role, status, workload, or professional identity. They may distrust the decision because of earlier experiences. They may also have discovered that the proposed process does not work in ordinary operating or customer situations.
The possibility of deliberate noncompliance should not be excluded. It should be considered after leaders have established what is happening, whether expectations are clear, whether the work is feasible, and whether appropriate support has been provided.
Managing resistance to change begins with diagnosis. Leaders need to understand the behavior, its context, and its likely causes before selecting a response.
Describe the Behavior Before Assigning a Cause
Broad labels hide important differences.
Instead of saying that employees are resistant, describe what can be observed:
- Are employees continuing to use an old system?
- Are they missing or postponing training?
- Are they questioning instructions?
- Are they creating workarounds?
- Are they raising the same concern in several meetings?
- Are they completing required activities without using the new approach?
- Are service, quality, or productivity beginning to fluctuate?
Ask when the behavior began, where it occurs, and what employees say they are trying to accomplish. Compare the formal process with how the work is actually performed.
An employee who continues using an old procedure may be avoiding change. The employee may also be compensating for a system defect, protecting a customer commitment, responding to conflicting instructions, or trying to maintain service while several initiatives compete for attention.
Employee explanations are important evidence, but they are not the only evidence. Review the workflow, operating data, customer effects, system performance, workload, leadership expectations, and relevant dependencies. Test interpretations rather than assuming that either management or employees automatically have the complete picture.
Recent research on responses to organizational change emphasizes that employee responses are more varied than simple support or opposition. Timing, ambivalence, leadership, and organizational conditions all influence how people respond.
Five Causes of Employee Resistance to Change
Employee resistance to change rarely has one universal cause. Several conditions may be operating at the same time.
1. Insufficient Clarity and Information
Employees need to understand why the change is necessary, what has been decided, what remains open, how their work will be affected, and what the organization expects from them.
A high volume of communication does not guarantee clarity. Long presentations, broad statements about transformation, and repeated slogans may still leave practical questions unanswered.
Employees may ask:
- What does this mean for my role?
- Which priorities have changed?
- What should I stop doing?
- Which decisions can I make?
- What happens when the new process does not work?
- Where can I raise an unresolved issue?
When leaders cannot answer these questions, resistance to change may reflect uncertainty rather than opposition.
2. Limited Capability or Support
Understanding an expectation does not establish the ability to meet it.
Employees may need knowledge, practice, coaching, technical assistance, revised procedures, clearer escalation routes, or access to experienced colleagues. Managers may also require support to interpret the change, guide their teams, and handle exceptions.
Training is appropriate when a capability gap exists. It is less useful when the actual problem is unclear authority, an unworkable process, inadequate staffing, or mistrust.
Before prescribing more training, ask what people are currently unable to do and why.
3. An Unworkable Process or System
A technically completed change may still fail under real operating conditions.
Employees often encounter exceptions that were not visible during design. A system may not support a critical customer scenario. A new approval process may create delays. Revised performance expectations may conflict with compliance or service requirements.
In these situations, workarounds and objections can reveal a design or integration problem. Treating them only as employee resistance can protect the process from scrutiny while placing the burden on the people expected to use it.
Operational evidence should therefore influence the change itself, not merely the communication surrounding it.
4. Excessive or Conflicting Change Demand
Employees rarely experience initiatives as separate project plans. They experience their combined effect in daily work.
A team may be implementing a new customer relationship management system while learning revised pricing rules, adopting additional quality controls, and maintaining normal service levels. Each initiative may make a reasonable request when assessed independently. Together, they may exceed the team’s effective capacity.
Research on asynchronous multiple overlapping change has examined how cumulative and conflicting organizational changes can contribute to workplace stress and resistance to change.
Ask:
- Which changes are reaching the same team?
- Which roles are required by several projects?
- Do implementation and training peaks overlap?
- What operational work is being displaced?
- How much stabilization work remains from earlier changes?
- Which commitments will be adjusted if capacity is insufficient?
More communication cannot create additional capacity or resolve conflicting priorities.
5. Trust, Loss, Identity, and Organizational Culture
A change can be technically feasible and still alter something employees value.
People may be concerned about status, professional identity, autonomy, relationships, competence, job security, or the meaning they attach to their work. Previous changes may also have taught employees that leadership announcements are inconsistent, feedback is ignored, or promised support does not arrive.
Organizational culture influences how employees interpret uncertainty. In a low-trust environment, missing information may be filled with rumors and defensive assumptions. In a culture where concerns are punished, silence may conceal significant resistance.
Leaders should acknowledge real consequences honestly. Transparency does not mean that every decision is negotiable. It means communicating clearly about what is known, what remains uncertain, what has been decided, and what people can still influence.
Prosci’s discussion of why people resist change also identifies awareness, role impacts, trust, leadership support, and exclusion from decisions as recurring sources of resistance.
A Practical Example: When Incomplete Adoption Protects the Customer
Consider a service company introducing a new CRM, revising its pricing rules, and adding new quality checks.
Employees continue recording some information in the old system. The CRM project interprets this as incomplete adoption and proposes another communication and training campaign.
The employees describe a different problem. The new CRM does not yet support an exception required under the revised pricing process. If they use only the new system, they cannot complete certain customer requests correctly. Their supervisor is also trying to maintain response times while releasing employees for training and addressing quality-control requirements.
Several issues are interacting:
- The new CRM has an operational gap.
- Pricing and CRM requirements are not fully connected.
- The team is carrying demands from several initiatives.
- Employees lack a clear exception process.
- The supervisor has limited coordination capacity.
- The project and the operation are using different definitions of success.
The observed behavior is real, but “resistance” does not explain it. Another adoption campaign would leave the process defect, conflicting requirements, and capacity problem unresolved.
The appropriate response begins with investigating the operational gap and deciding which project, policy, or timeline must change.
Match the Response to the Cause
The purpose of diagnosis is to select a response that addresses the underlying condition.
- If the direction is unclear: Explain the business reason, intended outcome, practical implications, and relationship to organizational priorities.
- If information is incomplete: State what has been decided, what remains open, what is uncertain, and when further information will be available.
- If capability is insufficient: Provide relevant practice, coaching, tools, technical support, and time to learn.
- If expectations conflict: Clarify priorities, responsibilities, decision rights, and escalation routes.
- If the process is defective: Correct the design, workflow, system, policy, or exception process.
- If workload exceeds capacity: Resequence work, narrow scope, protect operational periods, add targeted support, or stop lower-priority activity.
- If trust has been damaged: Acknowledge previous experience, communicate honestly, follow through on commitments, and make the response to feedback visible.
- If consequences involve loss or identity: Discuss them seriously and avoid pretending that every negative effect can be removed.
- If expectations are reasonable and support is sufficient: Apply normal performance and accountability processes consistently.
Several responses may be required together. Employee resistance to change can arise from a combination of unclear direction, limited capability, operational defects, cumulative demand, and mistrust.
From Resistance to Acceptance and Ownership
The immediate objective of managing resistance to change should not be silence or superficial compliance. Leaders need conditions in which people can understand the change, engage with it constructively, and assume appropriate responsibility.
Within the GRIFFOX Layered Cake Model™, Acceptance describes a willingness to acknowledge the change and engage constructively with the new direction, expectations, or working conditions.
Acceptance does not require agreement with every decision. Employees may accept that a change will proceed while continuing to raise valid concerns about its design, timing, consequences, or operational feasibility.
Ownership goes further. It means actively assuming responsibility for making the change work within a defined role and set of decision boundaries.
Ownership requires practical answers to questions such as:
- What is my responsibility?
- What must I do differently?
- Which decisions can I make?
- How should I handle exceptions?
- How can I contribute to improvement?
- Where should I escalate an issue I cannot resolve?
- What evidence will show that the new approach is working?
People cannot take meaningful ownership of expectations they do not understand. They also cannot carry responsibility effectively when they lack authority, capacity, information, or support.
Clarity, transparency, and timely information help create the conditions for Acceptance. Participation, practical authority, support, and accountability help translate Acceptance into Ownership.
The progression is therefore not simply from resistance to agreement. It moves from interpretation and uncertainty toward clarity, Acceptance, defined responsibility, and active Ownership.
Invite Input While It Can Still Affect the Work
Participation is more credible when leaders explain what is open for discussion.
The decision to introduce a new system may already be fixed. The rollout sequence, training arrangements, exception handling, local workflows, and support structures may remain adjustable.
Employees should know which type of participation is being requested:
- Are leaders gathering information?
- Are employees helping design an approach?
- Are teams testing a proposed solution?
- Is the organization consulting people before making a decision?
- Is the purpose to explain a decision that has already been made?
Invite contributions early enough to use them. Afterward, explain what changed, what did not change, and why.
This does not make every decision a vote. It makes participation transparent and helps prevent employees from concluding that their involvement was symbolic.
It also creates an opportunity to identify operational problems before they become repeated workarounds, delays, or escalations.
Make Operational Experience Part of the Decision
The GLCM begins with the Foundation and Experience the organization already carries. This includes earlier change experiences, operational conditions, culture, capability, trust, constraints, and lessons learned.
Within a change initiative, the model connects the work with the operational units where the change must be interpreted, implemented, and sustained. Operational Integration makes dependencies, capacity pressures, and interactions across units and concurrent initiatives visible and manageable.
Observed resistance may initially be information. It becomes a useful signal when leaders interpret it against a management question, operating context, baseline, objective, or risk.
A useful account of employee resistance should identify:
- The behavior that was observed
- The work or stakeholder group affected
- When and where the behavior occurs
- What employees are trying to accomplish
- The likely operational consequence
- Related system, process, leadership, or capacity conditions
- Evidence that supports or challenges the interpretation
- What remains uncertain
- Which decision may be required
The GLCM’s Theme-Centered Diagnostics, an author-developed adaptation inspired by Theme-Centered Interaction, can help examine whether the strain is emerging through Systems, Behavior, Culture, or their interaction.
Where an issue crosses initiative boundaries, a Change Office function can combine related signals, identify patterns and contradictions, and prepare decision options. Enterprise Governance then decides matters within its authority, including priorities, sequencing, resources, policy, scope, or changes in direction.
The affected employees and operational units should hear what was decided, why it was decided, and what happens next. This feedback is part of transparency and helps protect leadership credibility.
Use Reflection Cycles to Understand What Resistance Is Revealing
Organizations need a recurring way to examine employee responses while change is taking place. In the GLCM, Reflection Cycles create structured opportunities for teams to compare the intended change with their operational experience.
A Reflection Cycle can explore:
- What is working as intended?
- Where are employees encountering confusion, overload, or operational friction?
- Which concerns reflect a local issue, and which appear across teams or initiatives?
- What has changed since the previous review?
- What can be adjusted locally?
- Which dependencies, capacity constraints, or unresolved decisions require escalation?
The purpose is not simply to collect opinions. Observations must be interpreted in relation to the change objective, operational context, available capacity, and expected outcomes. Repeated concerns, connected observations, or significant local exceptions may then become signals that contribute to a broader signal picture.
This makes resistance part of a learning process. Teams can test adjustments and observe their effects. When patterns cannot be resolved locally, they can be routed to the Change Office for integration and, where an enterprise decision is required, to Enterprise Governance. Reflection Cycles therefore support both employee involvement and management accountability.
Check for Workable Adoption
Reduced complaints do not prove successful adoption.
After responding to employee resistance to change, ask:
- Can people perform the revised work reliably?
- Are important exceptions handled appropriately?
- Has hidden rework decreased?
- Are employees using the new process without unsupported workarounds?
- Is service or quality becoming more stable?
- Are managers able to support the change within available capacity?
- Are responsibilities and decision rights functioning as intended?
- Can the organization sustain the new routine?
Continued questions may indicate engagement and learning. Silence may reflect confidence, resignation, fear, or a lack of opportunity to speak. Each requires interpretation in context.
The GLCM’s Recalibration layer provides a deliberate point for evaluating emerging evidence and deciding whether to maintain the course, adjust the implementation, wait, or revisit an earlier assumption.
The way leaders respond to employee concerns also becomes part of the organization’s Foundation and Experience for the next change. Employees remember whether leaders listened, whether operational evidence mattered, and whether commitments were honored.
Resistance Is Information About the Change System
Employee resistance to change should neither be romanticized nor dismissed.
Some concerns reveal real problems. Others arise from uncertainty, incomplete information, perceived loss, mistrust, or limited capability. Some behaviors may eventually require clear accountability. Leaders need to distinguish among these conditions rather than applying one standard response.
The most useful questions are:
- What behavior are we observing?
- What are employees trying to accomplish or protect?
- Which system, process, cultural, leadership, or capacity conditions may be contributing?
- What evidence supports our interpretation?
- What response would address the actual cause?
- What would help employees move toward Acceptance?
- What responsibilities and decision boundaries would support Ownership?
- Which problems can be resolved locally, and which require an enterprise decision?
When “resistance” becomes the default explanation for stalled initiatives, leaders may overlook the information the organization is providing.
A more effective response combines listening with accountability, transparency with decision clarity, and participation with defined responsibility. This creates a stronger path from employee resistance to workable adoption and sustainable change.
Reflection Cycles provide the recurring learning mechanism through which operational experience, employee concerns, and emerging adoption problems can be examined, interpreted, and connected to appropriate management decisions.
Explore the GRIFFOX Enterprise Change Architecture to learn how operational evidence, concurrent initiatives, Change Office support, and Enterprise Governance can be connected.
By Harald Lavric | Founder, GRIFFOX Consulting | Creator, GRIFFOX Layered Cake Model™
About Harald Lavric
Harald Lavric is the founder of GRIFFOX Consulting and creator of the GRIFFOX Layered Cake Model™. His work focuses on the connections among leadership, strategy, organizational change, operational responsibility, and enterprise decision-making. Drawing on more than three decades of experience in the German health-insurance system and work across public- and private-sector environments, he helps leaders make overlapping change more coherent and workable.