# Resolve project team conflict without guessing at the cause Handle project team conflict with a practical conversation sequence, an original delivery example, and guidance on when facilitation or escalation is needed. Source: https://tirtle.com/blog/project-team-conflict-resolution Publisher: Tirtle | Updated: 2026-10-10 ## The short answer Resolve team conflict by understanding the disagreement, separating evidence from assumptions, and agreeing on a practical next step. Use facilitation when people can work through the issue within their authority. Follow the appropriate escalation route when the stakes, conduct, or decision exceed that authority. ## Find out what the conflict is about What looks like a personality problem may be a disagreement about requirements, workload, priorities, or who can make a decision. Before proposing a solution, ask each person to describe the situation and its effect on the work. Use a recent example rather than broad claims about someone's attitude. Suppose a tester says developers keep handing over unfinished work. A developer says testing adds requirements at the last minute. The useful question is what the team agreed to deliver and how each person recognizes completion. That gives you a shared issue to investigate. ## Prepare a conversation people can use Choose a setting that fits the sensitivity of the issue. A private conversation may help you understand the facts before bringing the parties together. Set a clear purpose: agree how a specific handoff will work, not decide who is a better team member. Invite people to explain observations, effects, and needs. Interrupt personal attacks and bring the discussion back to the work. If the matter involves harassment, discrimination, threats, or another serious conduct concern, use the designated process rather than treating it as an ordinary disagreement to negotiate. ## Work through a testing disagreement In an original scenario, a team must release a stock tracking screen. Developers believe a successful normal transaction is enough for testing. Testers expect a clear message when a barcode cannot be found. The requirement says invalid input must be handled, but it does not define the message. The project manager helps the team compare the requirement, the agreed quality criteria, and the current behavior. The team defines an understandable error message and adds the check to its handoff checklist. The person with product authority confirms the desired behavior. The disagreement leads to a clearer agreement instead of a forced apology. ## Choose a response that fits the situation Collaborative problem solving is useful when people have relevant knowledge and enough time to explore a durable solution. A compromise can be practical when an acceptable tradeoff is available. A temporary pause can reduce heat, but it needs a return point so the issue does not disappear unresolved. Some decisions need a clear direction from an authorized person, especially when there is immediate risk or a firm requirement. No single response is always best. Consider urgency, the relationship, the importance of the outcome, and whether the people involved have authority to settle it. ## Make the agreement observable Close the discussion with a specific action, owner, and review point. We will communicate better is too vague to test. We will include the agreed invalid-input check before the next testing handoff is much clearer. Use this quick follow-up checklist after the next handoff. It keeps the focus on whether the agreement helped the work. - Was the agreed action completed? - Did it resolve the original blockage or reveal another cause? - Do the people involved understand their responsibilities? - Is a decision or support outside the team still needed? - What should be adjusted before the next cycle? ## Your next step Focus on the actual disagreement and a testable agreement. Support respectful problem solving while keeping authority and serious conduct boundaries clear. - [Practice with Tirtle](https://tirtle.com/) - [How Tirtle practice works](https://tirtle.com/help/free-practice-and-plus) ## Sources - [PMI Lexicon of Project Management Terms (registration may be required)](https://www.pmi.org/standards/lexicon) | Project Management Institute - [Principles behind the Agile Manifesto](https://agilemanifesto.org/principles.html) | Agile Manifesto authors ## Watch next [Servant Leadership in Scrum](https://www.youtube.com/watch?v=_d1LpOPw9n8) | Scrum.org Examples of openness, respect and accountability in teamwork. This older lesson supports leadership principles; use the current Scrum Guide for framework terminology. ## Keep learning - [Servant leadership in project management: help the team succeed](https://tirtle.com/blog/servant-leadership-project-management) - [Build a stakeholder engagement plan people can use](https://tirtle.com/blog/stakeholder-engagement-plan) - [Lessons learned and retrospectives: turn insight into a change](https://tirtle.com/blog/lessons-learned-retrospective) Tirtle is an independent study companion, not endorsed by PMI. Our practice does not award qualifying education hours or PDUs or guarantee exam results.