Leadership, Conflict Resolution and Negotiation Skills for IT Project Managers

A project manager rarely has formal authority over the people who do the work. Developers, testers, analysts and vendors report to other managers, yet the project manager is held responsible for results. That gap is closed by leadership, conflict resolution and negotiation: the ability to influence without commanding, to resolve disagreements before they become delays and to reach agreements that both sides can live with. These skills are often described as “soft”, but they decide more projects than any scheduling technique.

Leadership vs Management

Management is about planning, organising and controlling. Leadership is about setting direction, aligning people and motivating them to follow it. A project manager needs both. A useful way to see the difference: management makes sure the schedule is right, leadership makes sure people care whether it is met.

Management behaviourLeadership behaviour
Assigns tasks and tracks completionExplains why the work matters and invites ideas
Enforces processShapes a culture where people raise problems early
Solves problems for the teamHelps the team develop its own solutions
Reports statusBuilds trust that the status is honest

Adapt Your Style to the Situation

There is no single best style. The situational leadership idea suggests matching your approach to the team member’s skill and motivation for the task at hand:

  • Directing: clear instructions and close supervision for someone new to a task.
  • Coaching: explanation and encouragement for someone learning but keen.
  • Supporting: listening and facilitating for a capable person who needs confidence.
  • Delegating: handing over ownership to an experienced, motivated person.

The same person may need different styles on different tasks. A senior engineer may be ready to be delegated a design decision yet need direction on a new compliance process. Pair this with team development stages from Resource Management and Team Building.

Everyday Leadership Behaviours That Work

  • Be clear about goals and priorities and repeat them when pressure rises.
  • Protect the team from interruptions, shifting requests and unproductive meetings.
  • Give specific feedback promptly, praise in public and correct in private.
  • Admit mistakes and share what you learned. It makes it safe for others to do the same.
  • Recognise contributions in ways people value, not just in the status report.
  • Keep promises to the team about information, support and decisions.

Where Project Conflict Comes From

Conflict is normal on projects because people with different goals share limited time and money. Common sources include:

  • Competing priorities between business units or between delivery and operations.
  • Scarce resources: the same specialist wanted on two projects.
  • Schedule pressure and disagreements about estimates.
  • Technical disagreements about design choices.
  • Unclear roles, so two people think they own the same decision.
  • Personality and communication-style clashes.

Task conflict about ideas can improve decisions if handled respectfully. Relationship conflict, where it becomes personal, damages trust and should be addressed early.

Five Ways to Handle Conflict

The Thomas-Kilmann model, widely used in project management training, describes five modes:

ModeDescriptionBest used when
Collaborate (problem-solve)Work together to find a solution that satisfies everyone’s real needsThe issue is important and there is time and trust
CompromiseEach side gives something up for a middle positionA quick, acceptable solution is needed
Accommodate (smooth)Emphasise agreement and give wayThe issue matters more to the other party, or to preserve a relationship
Compete (force)Use authority to impose a decisionAn emergency or an unpopular but necessary decision
Avoid (withdraw)Postpone or sidestep the issueThe issue is trivial or emotions need to cool first

Collaboration is usually the most durable, but it is not always practical. The skill is choosing the mode deliberately instead of defaulting to the one you are most comfortable with.

A Simple Process for a Team Conflict

  1. Talk to each person separately and listen for facts, interests and feelings.
  2. Bring them together in a calm setting with a clear purpose: solve the problem, not assign blame.
  3. Restate the problem in neutral language and agree on the shared goal.
  4. Generate options and evaluate them against project objectives.
  5. Agree an action, an owner and a review date, and write it down.
  6. Escalate to the sponsor or functional manager if the conflict cannot be settled at team level, giving a balanced summary.

Negotiation Basics

Project managers negotiate constantly: with sponsors about deadlines, with functional managers about people, with vendors about contracts and with the team about scope. Four principles carry most of the value:

  • Focus on interests, not positions. A position is “I need the engineer full time”. The interest might be “my release must not slip”. Interests often have more than one solution.
  • Know your alternative. Your BATNA (best alternative to a negotiated agreement) tells you when to walk away and how firm to be.
  • Prepare the zone of agreement. Think about what each side wants, what each can give and where they overlap.
  • Use objective criteria, such as data, benchmarks and contract terms, to move away from a contest of wills.

Worked Example: Two Projects, One Engineer

Project A and Project B both need the only integration specialist during March. Both managers insist on a full-time allocation. The project manager of Project A asks what Project B actually needs and discovers that B only needs design review in the first week and testing support in the last. She proposes: specialist to B for two short windows, to A for the rest, with a documented handover. She backs her case with schedule data showing the critical path runs through A’s integration work. B’s manager agrees because the plan protects his key dates. The solution emerged from interests and data, not from a test of seniority.

Managing Up and Across

Leadership extends beyond the team. With sponsors, bring options and recommendations rather than only problems, and give early warning of bad news with the facts and a plan. With peers and functional managers, build relationships before you need favours, and be clear about what you need and by when. See Project Communication Management for how to structure these conversations.

Common Mistakes

  • Avoiding a conflict until it explodes in a status meeting.
  • Using authority you do not formally have, instead of influence.
  • Negotiating positions instead of interests.
  • Giving feedback only in annual reviews, not when it is useful.
  • Hiding bad news from sponsors until it cannot be fixed.
Key takeaways
  • Project managers lead through influence, since they rarely have formal authority.
  • Match your leadership style to the person and the task.
  • Choose a conflict-handling mode deliberately; collaboration is usually best but not always possible.
  • Negotiate on interests and objective criteria, and know your alternative.

Related Lessons