Conflict management

Conflict management is the structured approach to identifying, addressing, and resolving disagreements among project stakeholders and team members. It protects delivery objectives while maintaining trust and a healthy team climate.

Key Points

  • Conflict is normal and can be constructive when managed well.
  • Address issues early using a fair, transparent process.
  • Focus on interests and facts, not personalities or positions.
  • Select an approach (collaborate, compromise, accommodate, avoid, compete) based on urgency, importance, and relationships.
  • Use the team charter and working agreements as ground rules.
  • Document agreements, owners, and follow-ups in project logs.

Purpose

Enable the team to handle disagreements in a way that supports project outcomes and preserves working relationships. Effective conflict management promotes psychological safety, faster decisions, and better solutions.

Facilitation Steps

  • Prepare: review context, working agreements, and escalation paths; choose a neutral setting; clarify your role and authority.
  • Frame the issue: state the problem objectively and agree on the goal and decision criteria.
  • Hear perspectives: allow each party to speak without interruption; use active listening and summarize to confirm understanding.
  • Explore interests and data: surface underlying needs, assumptions, and evidence; separate people from the problem.
  • Generate options: brainstorm alternatives; assess trade-offs against constraints and agreed criteria.
  • Choose the approach: decide whether to collaborate, compromise, accommodate, avoid, or compete based on context.
  • Agree actions: document the decision, owners, timelines, and any measures of success; update logs.
  • Follow up: check implementation, reinforce positive behaviors, and escalate only if impasse or risk persists.

Inputs Needed

  • Team charter and working agreements.
  • Stakeholder register and role definitions (e.g., RACI).
  • Issue log, risk register, and recent status or performance data.
  • Communication management plan and escalation paths.
  • Organizational policies, HR guidance, and code of conduct.

Outputs Produced

  • Resolved or escalated conflict with documented rationale.
  • Updated issue and decision logs with agreements and due dates.
  • Action items or change requests if scope, schedule, or resources are affected.
  • Updates to team charter, working agreements, or communication plan.
  • Lessons learned entries to reduce recurrence.

Tips

  • Stay neutral, manage your own emotions, and model respectful behavior.
  • Use time-outs or private caucuses when emotions run high.
  • Ask open questions to uncover interests, constraints, and assumptions.
  • Reframe blame into shared goals and objective criteria.
  • Protect psychological safety; encourage constructive dissent.
  • Match the technique to the situation; avoid overusing compromise.

Example

Two senior team members disagree on whether to build a custom component or buy an off-the-shelf option. The project manager facilitates a short workshop to define decision criteria from the team charter (cost, time to deliver, quality, supportability), hears each viewpoint, and gathers quick data. The group evaluates options against the criteria, agrees to buy with a minor customization, assigns actions to vendors and engineers, and records the decision and follow-ups in the decision log.

Pitfalls

  • Ignoring issues until they escalate into personal disputes.
  • Treating symptoms instead of addressing root causes.
  • Focusing on personalities or blame rather than behaviors and outcomes.
  • Using a forceful approach when long-term collaboration matters.
  • Making vague agreements without owners, dates, or verification.

PMP Example Question

A disagreement between two specialists is delaying a design decision. The milestone is two weeks away, both proposals have merit, and the team charter emphasizes collaboration and evidence-based choices. What should the project manager do first?

  1. Facilitate a collaborative session to define criteria and evaluate options against those criteria.
  2. Escalate to the sponsor to make the decision and unblock the team.
  3. Select one approach and direct the team to proceed to protect the schedule.
  4. Ask a team member to mediate informally without a structured process.

Correct Answer: A - Facilitate a collaborative session to define criteria and evaluate options against those criteria.

Explanation: This aligns with the team charter and allows an evidence-based, participative decision. Escalation or directing is reserved for urgent time pressure or impasse after facilitation.

ICS/OT Cybersecurity Fundamentals — Security Built for Industrial Systems

Industrial control systems cannot be secured like ordinary IT. A forced reboot, aggressive scan, or incompatible patch can interrupt production and create real safety consequences. Effective OT security begins with understanding the systems, constraints, and risks unique to industrial environments.

This course gives IT professionals, engineers, operators, and security practitioners a practical foundation in ICS threats, zone and conduit design, risk assessment, passive asset visibility, and vendor evaluation. You will learn how IEC 62443, NIST CSF, and MITRE ATT&CK for ICS apply where availability and safety come first.

Eight reconstructed incidents—including Stuxnet, Triton, Ukraine 2015, Colonial Pipeline, and PIPEDREAM—show how attackers move through OT environments, what they target, and which defenses could have changed the outcome.

Watch the course preview, then build the vocabulary, frameworks, and judgment needed to take credible first steps in ICS/OT cybersecurity.

Explore the Course


ICS/OT Cybersecurity Fundamentals course preview

Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course