Identifying the most important essential skills for the workplace can be somewhat subjective. The most relevant skills may be impacted by a number of attributes such as company culture, the specific industry, and individual strengths. PMI (Project Management Institute) has cited communication, problem-solving, collaborative leadership, and strategic thinking as the most important skills in their 2023 Pulse of the Profession Report. A 2024 Forbes article cites innovation, resilience, and persuasion among others as being the most in demand leveraging data from an analysis of 17 million job listings on Indeed.com.
Through our experience, we’ve identified a core set of skills that consistently drive successful project outcomes: conflict resolution, communication, and creativity. These skills don’t just apply to one area of project management. They span all five focus areas and all seven performance domains (referencing the PMBOK 8th Edition), creating a strong foundation for delivery. Even better, as these skills mature, they naturally strengthen other essential skill capabilities like negotiation and decision-making, compounding their impact over time. Let’s take a closer look at conflict resolution in this article.
Conflict Resolution
Working with people inherently brings some kind of conflict to professional activities. The same variation in lived experiences that creates diversity can also create differences of opinion that unfortunately, may escalate into negative conflict. Unchecked, conflict will wreak havoc within projects and teams. Ignored, teams run the risk of missing the benefits.
Project leaders must be observant about teams so conflict thresholds can be effectively identified. A conflict threshold is the point where good conflict (healthy debate) transitions to unhealthy conflict (infighting and resentment). This transition is marked by changes in routine mannerisms such as: vocal people getting quiet, “we and us” becoming “you and I” in conversation, articulate team members starting to fumble words. The culture of each team will be different and even as a single team evolves with new activities or members, conflict thresholds will be different requiring heightened observation.
Beyond recognizing conflict when it arises, project leaders must be skilled at guiding teams through it. Healthy debate can be a powerful driver of better outcomes, but only when it’s managed effectively and kept from tipping into dysfunction. Different types of conflict tend to stem from different root causes and situational dynamics, and understanding those distinctions is essential to facilitating productive resolution. Conflict may occur within teams, between teams, between teams and stakeholders, or with vendors. Below are some common root causes in each of these scenarios that project leaders should be prepared to identify and address.
Intragroup Conflict (Within a Team)
- Lack of transparency in communications
- Misunderstandings stemming from unclear responsibilities
- Interpersonal issues (usually driven by past history or perceptions of being professionally challenged)
- Unbalanced workloads
Interteam Conflict (Between Teams)
- Misaligned goals
- Competing priorities
- Lack of ownership clarity
- Different philosophies or skill levels on approaching work
Stakeholder Conflict (External to Team)
- Misaligned interests
- Insufficient or lack of transparency in communications
- Unrealistic expectations
- Competing objectives
Vendor Conflict (External Partners or Suppliers)
- Different interpretations of scope or deliverables
- Project team having little influence on vendor performance or management
- Lack of transparency in communication
- Resistance to vendor solutions stemming from a “not invented here” mindset
Conflict is unavoidable in project work, but poor conflict management is not. As conflict resolution acumen increases, project leaders shift from damage control to value creation, using healthy tension to drive clarity, alignment, and better outcomes. Use this information to determine your conflict resolution skill maturity.
High Acumen
Conflict is actively leveraged to improve project outcomes.
Project leaders with high conflict-resolution acumen recognize conflict early and respond deliberately. They understand team dynamics well enough to identify conflict thresholds before healthy debate turns disruptive. These leaders create environments where differing perspectives are encouraged and managed constructively.
Medium Acumen
Conflict is managed reactively, with mixed results.
Project leaders at this level recognize conflict once it becomes visible but may struggle to intervene consistently or confidently. They can resolve straightforward issues but may avoid deeper or more complex tensions, especially those involving power dynamics or external stakeholders.
Low Acumen
Conflict is avoided, ignored, or allowed to escalate.
Project leaders with low conflict-resolution acumen often underestimate the impact of conflict or assume it will resolve itself. They may avoid difficult conversations, unintentionally allowing healthy debate to turn into disengagement or resentment.
Typical Outcomes
High
- Healthy debate leads to clearer requirements, stronger risk identification, and better decision quality
- Roles, responsibilities, and ownership are clarified proactively, reducing rework and delays
- Interteam dependencies are managed through alignment on shared objectives and delivery milestones
- Stakeholder and vendor conflicts are addressed through transparent communication, expectation management, and clear escalation paths
- Teams remain engaged and productive, even during high-pressure phases
Medium
- Some conflicts are resolved, while others resurface later in the project
- Misunderstandings around roles, scope, or priorities cause periodic friction
- Interteam or stakeholder conflicts are often escalated rather than facilitated
- Productivity dips temporarily during periods of conflict but eventually recovers
- Lessons learned are identified but not always applied consistently across projects
Low
- Unclear responsibilities and scope ambiguities persist throughout the project
- Teams disengage, communicate defensively, or work in silos
- Interteam conflicts lead to missed handoffs, duplicated effort, or delivery delays
- Stakeholder dissatisfaction increases due to unmanaged expectations
- Vendor issues escalate into contractual disputes or performance failures
- Projects experience higher risk, rework, and reduced team morale
You are likely at this level if you
High
- Intervene early when communication patterns shift or engagement drops
- Adjust facilitation techniques based on team culture and project phase
- Address root causes rather than symptoms of conflict
- Use conflict as input to improve scope clarity, schedules, or governance
Medium
- Notice conflict only after it begins to affect schedule, cost, or team morale
- Rely on escalation or authority rather than facilitation
- Address issues on a case-by-case basis without identifying broader patterns
- Feel less comfortable managing conflict involving vendors or senior stakeholders
Low
- Avoid addressing tension unless it becomes disruptive
- Focus on task execution while overlooking team dynamics
- Treat conflict as a personal or interpersonal issue rather than a project risk
- Frequently react to conflict after it has already impacted outcomes
Take a moment to reflect on how conflict shows up in your projects today. Where do you tend to intervene early, and where do issues linger longer than they should? Use the scenarios and root causes outlined above to assess your own conflict resolution maturity and identify one behavior you can apply in your current work.
