PMO Flashmob has published another post in its modern project management series, this one on conflict. The argument is blunt: if you are running a project, conflict is part of the job. New problems, new people, new expectations, friction. According to the post, the problem is not the conflict. The problem is what teams do with it.
That framing is correct, and it is also where most teams quietly fail.
The short version
- The post is part of a PMO Flashmob series on modern project management skills.
- It frames conflict as an expected and useful part of project work.
- It positions the PMO's role as helping teams handle conflict well.
- Full content sits behind a House of PMO paid membership.
Background: why project work is structurally conflict-heavy
Projects exist to deliver something the organization has not done before. New work means new ambiguity. New ambiguity means new disagreement. New disagreement means new conflict. This is not a personality problem. It is a feature of the work.
The mistake most teams make is reading the friction as a signal that something is wrong. It is not. It is a signal that the team is actually engaging with the problem. The job of the project lead is to make the conflict productive, which is a different skill from avoiding the conflict or winning it.
Our analysis
The useful question is not how to remove conflict from a project. It is how to make the conflict legible and cheap. Three moves do most of the work.
First, name the type. Disagreement about facts is technical. Disagreement about priorities is political. Disagreement about values is personal. Each needs a different handling, and most teams skip the classification and go straight to feelings.
Second, separate the decision from the relationship. A team that can disagree on Monday and eat lunch together on Tuesday is a healthy team. A team that avoids the disagreement and then snaps over a small thing on Friday is not.
Third, make the trade-off explicit. Most project conflict is a trade-off dispute dressed up as a fact dispute. Saying "we are choosing speed over quality here, and that is the conscious call" defuses half of all disagreements on the spot.
What to watch next: whether your retros surface the conflict, or only the action items. The former is a healthy team. The latter is a polite one.
A worked example
Say two senior engineers are arguing about which microservice to refactor first. Engineer A wants the auth service, because the security review is coming. Engineer B wants the reporting service, because the customer escalation is louder. The instinct, especially for a new PM, is to schedule a meeting and ask them to "align." That meeting will not end well.
A better move is to ask, in front of both of them, what the project is actually trying to do this quarter. If the answer is "pass the security review," the trade-off is clear. If the answer is "stop the bleeding on customer escalations," the trade-off is the other way. The conflict was never about code. It was about which fire the team was allowed to focus on. Naming the fire ends the argument.
What to watch next
Whether your project retros ask what the team disagreed about this week, and what that disagreement taught them. If they do not, the next conflict will be just as expensive as this one.
Bottom line
Conflict is the job. The PM's job is to keep it cheap, legible, and pointed at the actual trade-off.
Key takeaways
- Project conflict is structural, not personal, and should be read as engagement.
- Naming the type of conflict, and the trade-off behind it, defuses most of it.
- Healthy teams argue in meetings and eat lunch together. Unhealthy teams do the opposite.
Frequently asked questions
What is the post about?
It is part of a PMO Flashmob series on modern project management, with this installment focused on conflict management.
Why does the post say conflict is a good thing?
Because projects involve new problems and new people, and the friction that comes from working through them is what surfaces better answers.
Is the full article free?
No. The full text sits behind a House of PMO paid membership.
What is the single most useful move when conflict shows up?
Name the type of conflict, then name the trade-off. Most disagreements are trade-off disputes in disguise.