Conflict management in project management is how a project manager spots, frames and settles disagreements so they improve decisions instead of stalling the work. The advice online tends to start with personalities and listening skills. The classic research points somewhere else. When Thamhain and Wilemon asked 100 project managers what caused the most conflict, schedules ranked first and personality clashes ranked at the bottom.
That finding changes the job. Many project fights are arguments about time, priorities and people’s availability, and those are problems you can put numbers on. This guide ranks the sources of conflict in project management, reviews what the evidence says about “healthy conflict”, and compares the five resolution techniques with a clear rule for choosing one. It also walks through a typical dispute settled with time data and covers what to do when the conflict is not yours to solve.
- What is conflict management in project management?
- What project teams fight about: 7 ranked sources
- Is conflict good for a project? What the evidence says
- 5 conflict resolution techniques in project management
- How to choose a technique
- How to resolve a project conflict in 6 steps
- Example: a blame dispute settled with hours
- Conflict changes with who is involved
- How to prevent conflict in project management
- Using actiTIME data in a dispute
- FAQ
What is conflict management in project management?
Conflict management in project management covers everything you do before, during and after a disagreement: setting rules that prevent it, noticing it early, choosing a response, and following up. Conflict resolution in project management is the narrower part, the act of settling one specific dispute.
Projects produce conflict by design. They borrow people from other teams, run against fixed dates, and put specialists with different priorities in one room. The Association for Project Management, the UK professional body, calls conflict in projects inevitable. So the useful goal of project conflict management is not zero conflict. It is cheap, fast conflict that ends in a decision.
Two estimates are cited most often, and both need labels. CPP’s global survey found US employees spending 2.8 hours a week dealing with conflict, which it valued at about $359 billion in paid hours in 2008. In the UK, Acas estimated in 2021 that workplace conflict costs organizations about £28.5 billion a year, or more than £1,000 per employee. Both cover whole workforces, not project teams, and CPP’s figure rests on what employees reported.
What project teams fight about: 7 ranked sources
The best known ranking comes from Thamhain and Wilemon, whose 1974 study of 100 project managers is summarized in a Project Management Institute (PMI) review. The table keeps their order and adds a typical trigger and the evidence that helps. Those last two columns are our reading, not part of the study.
| Rank | Source of conflict | Typical trigger | Evidence that helps |
|---|---|---|---|
| 1 | Schedules | A date set without the people doing the work | Estimates compared with hours on similar tasks |
| 2 | Project priorities | Two managers want the same person this week | A ranked project list from the sponsor |
| 3 | Manpower resources | Functional managers pull people back | Hours booked per person across projects |
| 4 | Technical conflicts | Competing solutions or quality standards | Agreed criteria, a test or a small prototype |
| 5 | Administrative procedures | Unclear authority or reporting lines | A written roles and decisions list |
| 6 | Cost objectives | Disputed estimates from support teams | Budget against actual cost by task |
| 7 | Personality conflicts | Clashing styles or old grudges | A private conversation, since data rarely helps here |
Three cautions apply. The study is more than 50 years old and drew on one sample, although Vijay Verma’s comparison shows a later study by Posner also placing schedules first. Verma’s table puts personality sixth rather than last, so read it as near the bottom. Next, people outside projects see things differently: in CPP’s nine country survey, employees in Ireland, the US and the UK were the most likely to name personality clashes as the prime source of workplace conflict.
The last caution is the practical one. Managers in the original study felt that personality conflicts were often disguised as technical or staffing disagreements. So when an argument about a schedule refuses to die after the facts are clear, look for the feeling underneath it.
Is conflict good for a project? What the evidence says
Many articles on conflict in project management say that conflict is healthy and drives innovation. The research is less cheerful. It helps to separate three types: relationship conflict over people and values, task conflict over the content of the work, and process conflict over how the work gets done.
| Study | Finding |
|---|---|
| De Dreu and Weingart, 2003 | Both relationship and task conflict were strongly and negatively linked to team performance and satisfaction, and the link was stronger on complex work, including projects |
| De Wit, Greer and Jehn, 2012 (116 studies, 8,880 groups) | Relationship and process conflict had stable negative links with group outcomes, while task conflict showed no strong negative link with performance |
The later review adds a detail. Task conflict was more positively related to performance when it stayed separate from relationship conflict, and when performance meant decision quality or financial results. In plain terms, arguing about the work can help, but only if nobody takes it personally. These are correlations, so they cannot prove what caused what. So keep disputes about the work, and fix arguments about process quickly instead of treating them as healthy debate.
5 conflict resolution techniques in project management
The five techniques from PMI’s PMBOK tradition match the five modes of the Thomas and Kilmann model almost exactly, so you will see both sets of names. The Thomas and Kilmann model sorts them by how assertive and how cooperative each one is.
| Technique | What you do | Use it when | The risk |
|---|---|---|---|
| Collaborate / problem solve | Work through the causes together until a solution meets both needs | The issue matters, the relationship matters, and there is time | It takes the most time and needs goodwill |
| Compromise / reconcile | Each side gives up something | Positions are fixed and a partial win beats a delay | Nobody is fully satisfied, so the issue may return |
| Smooth / accommodate | Stress agreement and give way on the difference | The issue matters more to the other side, or time is very short | The real problem stays hidden |
| Force / direct | Make the decision and require it | Safety, law or an emergency leaves no room for debate | Resentment, especially among people you do not manage |
| Withdraw / avoid | Postpone or step away from the issue | Tempers are high, you lack facts, or the issue will resolve itself | Avoided conflict grows if nobody returns to it |
Examples make these conflict resolution techniques in project management easier to tell apart. On a one week deliverable, two team members disagree about a minor formatting standard, and you smooth it over because the deadline matters more. A lead developer asks for a three week course that would wreck the schedule, so you compromise on a shorter option later on. A worker on a construction site arrives without protective gear, and you direct them to put it on, because safety is not up for discussion.
Thamhain and Wilemon also measured what project managers do. The problem solving or confrontation mode was the most frequently used, at 70%, followed by compromise and smoothing, while forcing and withdrawal came fourth and fifth. Forcing and withdrawal were often linked to more conflict with people assigned from functional departments, so treat them as exceptions.
How to choose a technique
Ask four questions in order. The first answer that applies usually decides it.
-
Is someone at risk, or is a legal line involved?
Direct. If it involves harassment or discrimination, go to HR rather than resolving it yourself.
-
Are tempers too high, or are the facts missing?
Withdraw, and set a time to come back within a day or two.
-
Is the issue small compared with the deadline?
Smooth it over or compromise, then note it for later if it could come back.
-
Does the issue affect the outcome or how people will work together?
Collaborate, even though it costs an hour now.
How to resolve a project conflict in 6 steps
For anything bigger than a passing disagreement, this project management conflict resolution sequence keeps the discussion on the work:
-
Talk to each person alone first.
Ask what happened and what they need. You learn the real issue before anyone has to defend a position in public.
-
Name the problem as a project problem.
“The release depends on two people on one week” works better than “you two are not getting along”.
-
Bring facts.
Dates, hours, task status and written requirements turn opinions into something both sides can look at.
-
Separate positions from needs.
“I need this person on Monday” is a position. “The client review needs one person who knows the module” is a need, and it may have several solutions.
-
Decide and write it down.
Record who does what by when. If they cannot agree, you decide, and you say why.
-
Check back within a week.
Ask whether the agreement is holding. Many conflicts return because nobody looks again.
Language matters in steps 1 to 3. Describe behavior and its effect rather than character: “the last two handoffs arrived after the test window” lands better than “you are always late”. Our guide to giving feedback covers this in more depth.
Example: a blame dispute settled with hours
This case is illustrative, and the numbers are invented. A feature estimated at 120 hours took 165. The development lead blames late test results, and the QA lead blames slow development. Each has a story and a grievance. Time logged by type of work tells a third story.
| Work | Estimated hours | Actual hours | Difference |
|---|---|---|---|
| Development | 80 | 90 | +10 |
| Testing | 40 | 30 | −10 |
| Rework after a requirement change | 0 | 45 | +45 |
| Total | 120 | 165 | +45 |
Development and testing cancel out, and the whole overrun is rework. Neither lead caused it. A requirement changed mid sprint without an impact check, and at $60 an hour that change cost $2,700. The fight about people becomes a five minute agreement on a rule: no requirement change without an estimate, as we explain in our guide to scope creep.
Delay also has a price. Applying CPP’s US average of 2.8 hours a week to a team of 8 gives 22.4 hours a week. At $45 an hour that is $1,008 a week, or $12,096 over a 12 week project. Treat it as a rough scale. A survey average will not describe your team.
Conflict changes with who is involved
In project conflict management, the same technique can work with one group and backfire with another, mostly because your authority differs.
| Who | Usual issue | What tends to work |
|---|---|---|
| Two team members | Handoffs, standards, workload | Let them try first, then facilitate with facts |
| You and a functional manager | Who gets a person and when | Avoid forcing, bring hours by person, and ask the sponsor to rank work if you stall |
| You and a client | Scope and expected dates | Return to the signed scope, price the change, and offer options |
| Two stakeholders | Competing goals | Make the trade off visible and let the sponsor decide |
| Remote or cross country teams | Tone in writing, cultural norms | Move to a call early, and do not assume silence means agreement |
Some cases are not project conflicts at all. Harassment, discrimination, threats or suspected fraud belong with HR or legal, and rules on them differ by country. Do not mediate those yourself. For a colleague whose behavior damages the whole team, see our guide on toxic employees.
How to prevent conflict in project management
The ranking above suggests where conflict management in project management pays off most, and that is prevention. Most of it is ordinary project discipline done early:
- Build the schedule with the people doing the work. This addresses the top source directly.
- Get one ranked list of projects. Then two managers cannot both claim priority.
- Agree on roles and decisions. Write down who decides, who is consulted and who is informed. Our project team guide covers structure and roles.
- Set an escalation path at kickoff. Team members try first, then the project manager, then the sponsor, each with a time limit.
- Agree on working norms. Cover response times, meeting habits and how people raise a concern.
- Make workload visible. People argue less about fairness when everyone can see who is on what.
- Watch for early signs. APM lists defensiveness, unwillingness to collaborate, direct challenges to decisions and sudden changes in how someone communicates.
For a wider view of team trouble, see our list of common project team problems.
Using actiTIME data in a dispute
No software resolves a conflict, and actiTIME does not try to. It gives you a shared record for the disputes that rank highest, the ones about time and people. Task estimates and the Estimated vs. Actual Time Report show where hours went, and custom types of work let you separate rework from new work, as in the example above.
For resource arguments, the Staff Performance Report and Time-Track Report show who logged what across projects, so two managers can look at the same numbers. Work assignments make it clear who is on which task, while comments on tasks keep the context next to the work.
actiTIME enables us to balance workload better
I found in actiTIME all the requirements I was looking for. We are getting a lot of benefits – the tool enables us to better balance workload, have a constant view of what people are doing. I really recommend it, I evaluated a lot of tools, also had an in-house development before which demanded a lot of maintenance, and actiTIME solved all problems with no hassle.
The Online version starts from $5 per user per month, and a permanent free version covers teams of up to 3 users with limited features. Task estimates need the paid version or the 30 day trial, which is full featured. Start a free trial and run your next schedule discussion from real hours.
FAQ
What are the stages of conflict management?
The classic model comes from Louis Pondy’s 1967 paper, which describes five stages of a conflict episode: latent, perceived, felt, manifest and aftermath. For project managers, the point is to act at the perceived stage, before emotions harden. The aftermath stage matters too, because an unresolved episode feeds the next one.
What are the 5 C’s of conflict management?
There is no standard list. One version names clarity, communication, collaboration, compromise and control, while others use a different set. The same goes for the “four R’s”. Treat these lists as memory aids. For project work, the five techniques above have a much firmer basis.
How do you handle conflict in a group project with no manager?
Agree on who does what, and by when, in writing at the start, so a dispute can point to something concrete. When a problem appears, raise it early and privately, and describe the effect on the shared deadline rather than the person. If it does not improve, take it to whoever set the project with the facts in hand. This applies to peer teams at work as well as to students.
Keep the argument about the work
Good conflict management in project management looks unremarkable from the outside. Schedules get built with the team, priorities come from one list, disputes get facts early, and someone follows up. When a fight does break out, check the ranking first. It is probably about time, and you can probably measure it.
