Conflict Management During Organizational Change: From Concerns to Coordinated Decisions

How leaders protect valid arguments, diagnose structural tension, and turn enterprise-wide awareness into accountable action

Sales has promised a launch date. The project team has delivered the agreed functionality. Operations says the new process is not ready. Customer service expects to handle the exceptions that nobody has fully defined.

During the steering meeting, the discussion becomes personal. Sales accuses operations of resisting progress. Operations argues that the project is transferring unmanaged risk into daily work. The project manager points to completed milestones. Customer service asks who will own the problems after launch.

It is tempting to describe this as a communication problem among difficult colleagues. Communication and behavior may indeed be part of the issue. The conflict may also reveal incompatible commitments, insufficient capacity, unclear operational ownership, competing measures of success, or an enterprise decision that has never been made.

Effective conflict management during organizational change must address both the conversation and the conditions producing it.

Improving the tone of the meeting will not resolve two priorities that require the same unavailable resources. Escalating every disagreement will not develop local responsibility. Forcing a compromise will not help when the people in the room lack authority to change the underlying commitments.

Leaders need a disciplined way to determine what the conflict represents, what evidence matters, which response is appropriate, and where the necessary decision belongs.

From Concern to Conflict: Understand What Is Happening

Organizations often use words such as concern, issue, resistance, conflict, and complaint interchangeably. That makes it difficult to choose an appropriate response.

These conditions are related, but they are not identical.

Observation

An observation describes something that has happened:

Customer-service employees required an average of twelve additional minutes to resolve the exceptions found during testing.

An observation becomes more useful when it includes context, frequency, and consequences.

Concern

A concern expresses a possible problem, risk, or consequence:

The current launch plan may create a volume of customer exceptions that the service team cannot manage.

The concern may prove accurate, partially accurate, or unsupported. It needs examination rather than immediate acceptance or rejection.

Issue

An issue is a condition that requires attention:

Testing has identified recurring exceptions, but no team has accepted responsibility for handling them after launch.

The response may involve clarification, expertise, resources, redesign, or a management decision.

Disagreement

A disagreement exists when people interpret the evidence differently or prefer different responses:

Sales believes the commercial cost of postponement exceeds the operational risk. Customer service reaches the opposite conclusion.

Disagreement can improve a decision when the different perspectives are examined constructively.

Conflict

Conflict emerges when people or groups experience incompatible interests, commitments, responsibilities, values, or expected consequences.

Sales may be accountable for revenue and market timing. Operations may be accountable for reliability. Customer service may be responsible for customer outcomes without controlling the process that creates additional work.

The participants can share the same corporate objective while still experiencing a real conflict over how to achieve it.

Impasse

An impasse occurs when the participants cannot move forward within their authority, information, or current relationship.

An impasse does not necessarily indicate failure. It may show that the decision belongs at another level.

Misconduct or a protected complaint

Threats, harassment, discrimination, retaliation, or other serious misconduct require the organization’s appropriate reporting, investigation, and formal processes. These matters should not be reduced to an ordinary disagreement that colleagues are expected to resolve between themselves.

The first task is therefore diagnosis. Leaders should understand what is happening before selecting a conflict-resolution method.

Protect Valid Arguments While Addressing Harmful Behavior

A difficult message and the way it is delivered are separate matters.

An operational manager may communicate defensively while identifying a serious capacity problem. A project sponsor may communicate respectfully while defending an unrealistic deadline. A technically valid argument does not excuse personal attacks, and professional behavior does not make an unsupported claim correct.

Leaders should examine two questions independently:

1. What is the validity and significance of the concern?
2. Is the person’s behavior appropriate?

This produces four possible situations.

This distinction prevents leaders from punishing a valid argument because they dislike its delivery. It also prevents “speaking truth” from becoming an excuse for disrespectful behavior.

Employees watch how leaders respond to unwelcome information. If raising a risk harms the person who reports it, future concerns may remain hidden.

Amy Edmondson and Tijs Besieux describe voice and silence as more complex than simply speaking or withholding. Conversations can contribute to organizational goals or disrupt them, while silence can sometimes support reflection and sometimes conceal critical information. Their paper on voice and silence in workplace conversations provides a useful foundation for this distinction.

The related GRIFFOX article on employee voice during organizational change explains how operational observations should enter the decision process. Conflict management addresses what happens when those observations encounter competing interpretations, interests, or commitments.

Why Organizational Change Creates Competing Commitments

Organizational change does not always create conflict from nothing. It frequently exposes tensions that were already present.

Several conditions make conflict more likely.

Different responsibilities

Project leaders may be responsible for scope, schedule, and delivery. Operational managers may be responsible for service continuity, quality, safety, and employee workload.

Both can act responsibly while protecting different outcomes.

Different time horizons

A project team may concentrate on the next milestone. Operations may consider what happens after the project closes. Executive leadership may focus on strategic results over several years.

Each perspective can be valid but incomplete.

Limited resources

Several initiatives may require the same people, systems, funding, or management attention. A request for greater collaboration cannot create capacity that does not exist.

OpenStax’s educational overview of resolving conflict in organizations identifies scarce resources, incompatible objectives, and organizational conditions as common sources of conflict.

Conflicting measures of success

A function may be rewarded for speed while another is held accountable for accuracy. A project may report completion while operational teams continue managing unresolved consequences.

Unclear decision rights

People may disagree repeatedly because nobody knows who has authority to accept the trade-off.

Unequal consequences

One function may receive most of the benefit while another carries the implementation burden. Employees may be asked to own outcomes they had little opportunity to influence.

Loss, identity, and uncertainty

Changes to roles, status, relationships, professional identity, or future opportunities can intensify disagreement. These concerns should be understood without assuming that every objection invalidates the change.

The article on employee resistance to change examines these responses in greater detail.

Multiple simultaneous initiatives

A commitment that appears reasonable within one project may become unworkable when combined with everything else affecting the same team.

This is where conflict management connects with change capacity and Operational Integration.

Diagnose Conflict Through the Five GLCM Layers

The GRIFFOX Layered Cake Model™ provides a useful structure for diagnosing conflict during change.

A conflict may originate primarily within one layer, or it may connect several layers. The purpose of the diagnosis is not to classify people. It is to identify the conditions that require attention.

Foundation and Experience: What Is the Conflict Carrying?

The Foundation and Experience Layer includes organizational context, culture, behavior, readiness, and previous experience.

Questions include:

• What previous events influence the current conflict?
• Were earlier commitments fulfilled?
• How has the organization responded to disagreement in the past?
• Do employees believe that raising concerns is safe and useful?
• Are functions carrying unresolved history?
• How do professional identities shape the different positions?
• Are power differences affecting who can speak?
• Is change fatigue increasing the intensity of the response?
• Which informal practices currently keep the work functioning?
• What assumptions do the participants hold about one another?

A disagreement about a new process may be intensified by a previous implementation in which operations received inadequate support. A debate over evidence may reflect a culture in which admitting uncertainty has traditionally been treated as weakness.

Understanding the foundation does not mean allowing history to control the decision. It reveals what the organization must address if it wants a sustainable agreement.

Framework: Are Roles, Rules, and Responsibilities Producing Conflict?

The Framework Layer includes principles, methods, roles, responsibilities, governance, data, and decision rights.

Examine:

• Is the intended outcome clear?
• Are responsibilities defined across project and operational teams?
• Who owns implementation exceptions?
• Who can change scope, timing, or resources?
• Which policies or guardrails apply?
• Do performance measures create conflicting incentives?
• Are escalation routes understood?
• What evidence is required for a decision?
• Are customer and operational acceptance criteria defined?
• Does the governance structure include the people accountable for the consequences?

Many apparent relationship problems originate in an incomplete framework.

If two managers repeatedly argue about the same handoff because ownership has never been assigned, another conversation about collaboration will not resolve the underlying issue.

Implementation: What Is Happening in Daily Work?

The Implementation Layer is where the change meets operational reality.

Ask:

• What was expected to happen?
• What is happening instead?
• Which exceptions are appearing?
• Where are handoffs failing?
• Which teams are absorbing additional work?
• Are employees receiving contradictory instructions?
• Which skills or resources are missing?
• What other initiatives affect the same people?
• What are customers experiencing?
• Which consequences were not anticipated?
• What is working and should be protected?

This layer requires evidence from the people closest to the work as well as operational measures, customer information, project data, and leadership judgment.

A conflict may become personal because no shared operational picture exists. Making the work visible can reduce speculation and clarify the real trade-off.

Recalibration: What Should Happen Next?

The Recalibration Layer combines evidence and determines the next responsible action.

Four broad choices are available:

1. Keep the course when progress remains appropriate.
2. Adjust within the current layer when tactics, timing, resources, or implementation methods need to change.
3. Wait consciously when capacity, information, readiness, or an essential decision is missing.
4. Return to an earlier layer when evidence challenges a foundational assumption or the framework is incomplete.

Conflict often persists because participants are debating options without recognizing that they are making different judgments about these four choices.

Sales may support continuing. Operations may request an implementation adjustment. Customer service may argue for conscious waiting. The project team may believe returning to the framework would threaten the launch.

The role of leadership is to make these positions and consequences explicit.

Goal: Are Participants Protecting Different Outcomes?

The Goal Layer concerns intended outcomes, integration, benefits, and sustainability.

Ask:

• What outcome is each participant protecting?
• Are the outcomes genuinely incompatible?
• Which outcome has enterprise priority?
• Are project completion and operational success being confused?
• Who owns benefits realization?
• What would sustainable implementation require?
• Which customer, employee, financial, or operational consequences matter?
• Is the original goal still appropriate?
• What decision best supports corporate strategy?

Conflict may continue because people are optimizing different definitions of success.

The organization must determine how local, functional, project, and enterprise objectives relate to one another.

Use Reflection Cycles Before Positions Become Entrenched

Reflection should occur within every GLCM layer, not only after a conflict has escalated.

Regular reflection can identify weak signals before participants become committed to opposing positions.

Useful questions include:

• What are we noticing?
• What has changed since the last review?
• Is this an isolated event or a recurring pattern?
• Which facts are confirmed?
• Which claims remain assumptions?
• What is each person or function responsible for protecting?
• Where do interpretations differ?
• Which consequences occur outside the project?
• What do customers and employees experience?
• What can we resolve within our authority?
• What decision is missing?
• What will happen if no action is taken?
• What should we continue, adjust, pause, or reconsider?

Retrospectives, operational reviews, workshops, and structured conversations can all support reflection. The method should fit the question and the people involved.

Reflection should lead somewhere. Endless discussion without ownership can become another form of avoidance.

Choose the Response That Fits the Conflict

No single intervention is appropriate for every conflict.

The purpose is to resolve the real condition rather than selecting a familiar intervention and hoping it fits.

Facilitation, Coaching, Mediation, or Management Action?

These approaches serve different purposes.

Facilitation

Facilitation helps a group conduct a structured discussion, examine evidence, clarify options, and reach an appropriate output.

It is useful when participants can work together but need support managing the process.

A facilitator does not supply authority that the group does not possess.

Team coaching

Team coaching helps a team recognize recurring patterns in how it communicates, decides, coordinates, and learns.

It is appropriate when the team’s interaction contributes to repeated difficulty. The GRIFFOX article on team coaching during organizational change connects team learning with customer, departmental, and enterprise performance.

Coaching cannot correct an incentive system or resolve an enterprise priority conflict by itself.

Mediation

Mediation can help people address a damaged working relationship through a voluntary and confidential process.

Acas describes workplace mediation as a way of improving communication and rebuilding working relationships. It may be appropriate when interpersonal conflict prevents people from working through their differences directly.

Mediation should not be used to avoid a required formal process or to transfer organizational accountability to the individuals involved.

Training

Training is appropriate when people need defined skills, such as constructive dialogue, negotiation, facilitation, conflict management, or change leadership.

A lack of skill may contribute to conflict, but training will not resolve incompatible commitments.

Consulting or specialist advice

Specialist support may be needed to analyze a process, assess risk, interpret data, redesign governance, or provide legal, technical, or organizational expertise.

Management action

Leaders must act when the issue involves priorities, authority, workload, resources, performance, incentives, or organizational design.

A request that people “work it out” becomes irresponsible when only management can change the condition creating the conflict.

Move Unresolved Trade-Offs to the Correct Decision Level

Conflict should be resolved as close to the work as practical, but within the authority needed to make the decision.

Individual or team level

People may clarify an expectation, correct a misunderstanding, redesign a working practice, or agree on a better handoff.

Change Unit level

A team, department, business unit, or other Change Unit may adjust its local implementation, responsibilities, or resources.

Cross-unit level

Two or more Change Units may need to coordinate dependencies, sequencing, shared capacity, or customer consequences.

This is where Operational Integration in Change Management becomes important.

Project or program level

A sponsor or program leader may adjust scope, milestones, resources, or delivery expectations.

Enterprise level

Executive leadership or enterprise governance may need to decide between corporate priorities, accept a risk, allocate scarce capacity, or change strategic direction.

Escalation should not consist of forwarding competing complaints. The issue should be prepared so that leaders can understand:

• The decision required
• The relevant evidence
• The affected Change Units
• The available options
• The consequences of each option
• The recommendation, if appropriate
• The authority required
• The timing of the decision
• The consequences of waiting

This turns escalation into decision support.

Create Enterprise-Wide Change Awareness Through the Change Office

A project can be aware of its own conflict and still lack visibility into the larger pattern.

Enterprise-wide change awareness asks:

• Is the same capacity conflict appearing across several initiatives?
• Are multiple Change Units receiving contradictory priorities?
• Do recurring disagreements reveal unclear decision rights?
• Is one department repeatedly expected to absorb unmanaged work?
• Are several projects dependent on the same specialists?
• Are local compromises creating cumulative customer consequences?
• Do incentives encourage project progress at the expense of operational integration?
• Which concerns remain invisible because employees no longer expect a response?

A Change Office can connect signals from projects, Change Units, operational measures, employee experience, and customer information.

Its role is to:

• Identify patterns
• Clarify dependencies
• Distinguish local issues from enterprise conflicts
• Prepare management questions
• Develop decision options
• Recommend appropriate action
• Follow up on decisions
• Support the affected units

The Change Office should not become an informal court or a workaround around leadership. It should connect operational evidence with the people who hold the relevant authority.

Organizations may place this function within a project management office, transformation office, portfolio function, organizational-development unit, change-management function, or enterprise-architecture capability. The name matters less than the quality of the connection.

Where appropriate, management representatives and Change Office members can participate in a shared decision group. This reduces the separation between preparing a decision and understanding its operational consequences while preserving explicit decision rights.

Connect Enterprise Governance With Operational Reality

Enterprise governance should receive a connected picture rather than isolated project reports.

Leaders may need to decide:

• Which initiative has priority?
• What should begin, continue, slow down, or stop?
• Where should capacity be added or reassigned?
• Which risk is acceptable?
• Who owns a cross-unit dependency?
• Which policy or guardrail requires adjustment?
• Does the evidence challenge the original strategy?
• How should the decision be sequenced?
• Which operational consequences require monitoring?

The GLCM Enterprise Change Architecture connects local implementation, Operational Integration, decision support, and enterprise direction.

This relationship matters because conflict can contain information that no single project or function can interpret completely.

Enterprise governance should not reward the most forceful argument. It should assess strategic relevance, evidence, operational consequences, risk, capacity, customer effects, and organizational sustainability.

Move From Awareness to Acceptance and Ownership

Resolving the decision does not automatically create acceptance or ownership.

Awareness

People understand what is changing, what has been decided, and how the decision affects their work.

Acceptance

People recognize the decision and can work with it, even if it was not their preferred option.

Acceptance does not require enthusiasm or complete agreement.

Ownership

Responsibilities, authority, resources, expectations, and follow-up are sufficiently clear for people to act responsibly.

Ownership cannot be created simply by telling a team to “own the outcome.” The team must have a workable responsibility and the support required to carry it.

After a conflict-related decision, communicate:

• What issue was examined
• Which evidence was considered
• What was decided
• Why that option was selected
• Which alternatives were not chosen
• Who is responsible for what
• What resources or changes accompany the decision
• Which risks remain
• What will be monitored
• When the decision will be reviewed

This closes the feedback loop and reduces the likelihood that rejected arguments continue beneath an apparent agreement.

Check Whether the Decision Changes Daily Work

A meeting agreement is not yet an operational result.

Follow-up should ask:

• Are people acting according to the decision?
• Have contradictory instructions stopped?
• Is ownership visible in daily work?
• Did the expected resources become available?
• Are unresolved exceptions still moving to the same team?
• Has customer experience improved?
• Are risks decreasing or merely being reported less often?
• Are concerns being raised earlier?
• Has one function quietly resumed absorbing the burden?
• Does the decision need recalibration?

Silence is not reliable evidence that conflict has been resolved. People may be satisfied, uncertain, exhausted, or convinced that further voice is pointless.

Combine employee experience with behavior, operational measures, customer information, and leadership observation.

This is also where an organizational assessment during change can help leaders understand momentum, strain, and critical next steps.

Learn From Recurring Patterns

A recurring conflict is organizational evidence.

Repeated disputes over specialist access may reveal an enterprise capacity problem. Repeated arguments before launch may indicate missing operational-acceptance criteria. Repeated confusion about ownership may show that the framework is incomplete.

Recurring pressure to suppress negative information may reveal a culture that values reported progress over useful evidence.

Leaders should ask:

• Where else does this conflict appear?
• Which GLCM layer contains the recurring weakness?
• What conditions repeatedly produce it?
• Which teams or customers carry the consequences?
• Does the organization need a local correction or an enterprise response?
• What should become part of the foundation for future initiatives?

When the organization learns from conflict, the experience becomes part of its next Foundation and Experience Layer. The goal is not to eliminate every disagreement. It is to improve the organization’s ability to recognize tension, interpret it responsibly, make decisions, and adapt.

A Practical Conflict Management Checklist

When conflict emerges during organizational change, ask:

Clarify

• What happened?
• What is the specific concern or issue?
• Which facts are confirmed?
• Which statements are interpretations?
• Who is affected?

Diagnose

• Is the conflict relational, structural, operational, strategic, or mixed?
• Which GLCM layers are involved?
• What is each party responsible for protecting?
• Are incentives or success measures incompatible?
• Does the conflict involve several initiatives or Change Units?

Protect responsible voice

• Has a valid concern been separated from the way it was communicated?
• Can people challenge assumptions without retaliation?
• Are quieter or less powerful perspectives represented?
• Does the matter require a protected reporting route?

Select the response

• Is clarification sufficient?
• Would facilitation help?
• Is coaching appropriate?
• Has the relationship deteriorated enough to consider mediation?
• Is expertise or training required?
• Does management need to act?

Decide at the right level

• What can be resolved locally?
• Which dependencies require Operational Integration?
• Should the Change Office connect related signals?
• Who holds the necessary authority?
• What happens if the decision is delayed?

Implement and learn

• Is the decision clearly documented and communicated?
• Are responsibilities and resources aligned?
• Has the reasoning been explained?
• What evidence will show whether the decision works?
• When will reflection and recalibration occur?
• What should the organization learn for the next initiative?

Conflict Should Improve the Organization’s Understanding

Conflict management during organizational change is not primarily about making disagreement disappear.

Conflict may reveal that leadership intent and operational reality have become disconnected. It may expose unclear responsibilities, incompatible incentives, limited capacity, hidden customer consequences, or enterprise priorities that cannot all be maintained.

Employees and operational leaders must be able to raise these concerns without being punished for delivering unwelcome information. They must also remain accountable for how they conduct the conversation and carry authorized decisions.

The GLCM provides a way to examine where the conflict originates:

• Foundation and Experience reveal history, culture, trust, and inherited assumptions.
• Framework reveals roles, incentives, decision rights, and governance.
• Implementation reveals what is happening in daily work.
• Recalibration turns evidence into a decision about the next step.
• Goal clarifies which outcomes the organization is trying to protect.

Reflection cycles identify tension early. Facilitation, coaching, mediation, training, consulting, and management action address different needs. Operational Integration connects consequences across Change Units. The Change Office builds enterprise-wide change awareness, and enterprise governance makes decisions that individual projects or teams cannot make alone.

Handled responsibly, conflict becomes more than a disruption. It becomes a source of evidence about how the organization is functioning and what leadership must do next.

If your organization repeatedly encounters conflicts between projects, functions, and operational teams, contact GRIFFOX Consulting to discuss the responsibilities, dependencies, decision structures, and working relationships behind them.

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.