T01: Manage Conflict | Domain 1

📖 Lý thuyết / Theory

🇺🇸 English

Conflict is inevitable in projects. The PMP exam recognizes that some conflict can be healthy (constructive conflict drives innovation and better solutions), while unmanaged conflict is destructive.

Sources of conflict in projects: Schedules, priorities, resources, technical approaches, administration, personality, cost. (PMI research: schedule conflict is #1)

The PM's role is not to eliminate all conflict, but to manage it effectively — channeling healthy conflict and resolving destructive conflict.

Reference: PMI — Conflict Management Skills for PM

🇻🇳 Tiếng Việt

Xung đột là không thể tránh khỏi trong dự án. Kỳ thi PMP nhận ra rằng một số xung đột có thể lành mạnh (xung đột mang tính xây dựng thúc đẩy đổi mới), trong khi xung đột không được quản lý là phá hoại.

Nguyên nhân xung đột trong dự án: Lịch trình, ưu tiên, nguồn lực, phương pháp kỹ thuật, hành chính, tính cách, chi phí. (Nghiên cứu PMI: xung đột về lịch trình là #1)

Vai trò của PM không phải là loại bỏ mọi xung đột, mà là quản lý nó hiệu quả.

⚖️ Thomas-Kilmann Conflict Model

🇺🇸 English

Five conflict handling modes, plotted on two axes: Assertiveness (concern for self) vs Cooperativeness (concern for others).

Thomas-Kilmann official resource →

🇻🇳 Tiếng Việt

Năm chế độ xử lý xung đột, trên hai trục: Tính quyết đoán (quan tâm bản thân) vs Tính hợp tác (quan tâm người khác).

Mode	VI	Assertive	Cooperative	When to Use	PMP View
Withdraw/Avoid	Né tránh	Low	Low	Trivial issue; cool down; not your battle	⚠️ Least effective — postpones, doesn't resolve
Smooth/Accommodate	Nhường nhịn	Low	High	Preserve relationship; goodwill needed	⚠️ Temporary solution; may build resentment
Compromise	Thỏa hiệp	Medium	Medium	Equal power; time-constrained; acceptable loss	✅ Acceptable — "lose-lose" but balanced
Force/Direct	Cưỡng ép	High	Low	Safety issue; emergency; clear right/wrong	⚠️ Win-lose — damages relationships; last resort
Collaborate/Problem Solve	Cộng tác giải quyết	High	High	Important issue; time available; trust exists	⭐ PMI PREFERRED — win-win, addresses root cause

🎯

Exam Tips — Conflict

Đáp án đúng trong hầu hết câu hỏi về conflict = Collaborate/Problem Solve
Khi đề nói "FIRST" → thường là: lắng nghe, hiểu cả hai phía, tổ chức meeting
Avoid/Withdraw = đáp án sai trong hầu hết tình huống
Force/Direct chỉ đúng khi có safety concern hoặc deadline khẩn cấp không thể trì hoãn
Trong Agile: conflict trong retrospective là healthy — không nên suppress

🔧 Công cụ & Template / Tools & Templates

Conflict Resolution Process (Quy trình giải quyết xung đột)

Conflict Resolution Steps

── STEP 1: IDENTIFY ──────────────────────────────── Who: Identify parties involved What: Nature of conflict (technical, resource, personality, schedule) When: When did it start, when escalated Impact: Effect on team, project, delivery ── STEP 2: PREPARE ───────────────────────────────── Meet separately with each party first Listen without judgement Understand each person's perspective and interests (not just positions) ── STEP 3: FACILITATE ────────────────────────────── Joint meeting in neutral setting Ground rules: respectful communication, no interrupting Focus on interests, not positions Brainstorm options together Agree on resolution and next steps ── STEP 4: DOCUMENT ──────────────────────────────── Record agreed resolution in issue log Follow up to ensure resolution holds Update team norms if needed

Conflict Log Template

ID	Date	Parties	Type	Description	Resolution Mode	Action Taken	Status
CON-001	2026-05-01	Dev A, Dev B	Technical	Disagreement on API design pattern	Collaborate	Architecture review meeting held; ADR documented	Resolved
CON-002	2026-05-05	BE Team, QA Team	Priority	QA blocking BE tickets due to priority mismatch	Compromise	Sprint priority re-ordered with PO input	Monitoring

💼 Thực chiến / Real-World Scenario

🏢

FinTech Company X — Project Alpha (Lending Platform)

Tình huống:

Trong sprint 4 của Project Alpha, hai senior backend developers có xung đột nghiêm trọng về kiến trúc hệ thống. Developer A muốn dùng event-driven architecture với Kafka cho toàn bộ service communication. Developer B cho rằng synchronous REST APIs đơn giản hơn và đủ dùng cho giai đoạn đầu. Cả hai đều có lý lẽ kỹ thuật vững chắc, nhưng cuộc tranh luận kéo dài 3 ngày đang block sprint progress và ảnh hưởng đến tinh thần team.

Cách áp dụng Conflict Management:

1. Identify (Xác định): Đây là technical conflict, không phải personality conflict — đây là dấu hiệu tốt. Cả hai parties đều engaged và muốn dự án thành công.

2. Separate meetings (Gặp riêng): Gặp từng developer để hiểu: họ lo ngại gì? Cả hai đều lo về maintainability và scalability — đây là interests chung, dù positions khác nhau.

3. Facilitate (Tổ chức): Tổ chức Architecture Review Meeting với cả team (không chỉ 2 người). Đặt ra tiêu chí đánh giá: performance, maintainability, team skill level, time to implement. Invite tech lead như người có thẩm quyền kỹ thuật.

4. Outcome (Kết quả): Team quyết định hybrid approach: event-driven cho async flows (notifications, audit logs), REST cho sync operations. Cả hai developers đều contribute vào ADR (Architecture Decision Record). Conflict được chuyển thành better decision.

Bài học PMP:

Đây là ví dụ điển hình của Collaborate/Problem Solve. Key: PM không quyết định thay team về kỹ thuật. PM facilitate để team tự ra quyết định tốt hơn. Healthy technical conflict → Better architecture.

✏️ Câu hỏi luyện tập / Practice Questions

Question 1

A project team member tells the PM that there is an interpersonal conflict between two team members that is affecting their work. The PM should FIRST:

A. Separate the team members and assign them to different tasks
B. Meet with both team members together immediately to resolve the conflict
C. Meet with each team member separately to understand their perspective
D. Document the conflict in the project management plan and monitor

✅ Answer: C — Meeting separately FIRST to understand each perspective before bringing parties together is the collaborative approach. Meeting both together immediately (B) without preparation can escalate, not resolve. Separating them (A) avoids the issue. Just documenting (D) is passive.

Question 2

During a retrospective, two team members begin arguing loudly about the development process. As the Scrum Master/PM, what should you do?

A. Stop the retrospective and reschedule when people are calmer
B. Side with the team member who makes the stronger technical argument
C. Acknowledge the disagreement, establish ground rules, and guide the discussion toward finding a solution
D. Tell both team members their behavior is unacceptable and document it in their performance records

✅ Answer: C — In agile, retrospectives are specifically designed for open discussion and improvement. The Scrum Master/PM should facilitate, acknowledge emotions, set ground rules, and guide toward resolution. Stopping (A) wastes the opportunity. Taking sides (B) creates bias. Threatening documentation (D) creates fear, not psychological safety.

Question 3

The project is behind schedule, and the PM needs to make a quick decision about resource allocation despite two team leads disagreeing. Safety requirements are not at stake, but the deadline is tomorrow. Which conflict resolution mode should the PM use?

A. Collaborate — schedule a workshop to find a win-win solution
B. Smooth/Accommodate — let the more senior team lead decide
C. Force/Direct — make the decision using PM authority
D. Compromise — split the resources equally between both options

✅ Answer: C — When there's a real time constraint (deadline tomorrow) and the PM has authority, using Force/Direct is acceptable. Collaborate (A) takes too much time. This is one of the rare cases where Force is the right answer — note the time pressure context. D (compromise) could be viable but Force is more decisive given the deadline.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs prepare for difficult conversations, draft neutral communications, and analyze conflict patterns across stakeholder groups.

Sample Claude Prompts

Conflict root cause analysis You are a senior PM and organizational psychologist. I have a conflict between [Person A / Role] and [Person B / Role] on my project. Situation: [describe the conflict — what happened, when, what each party said/did] Project context: [team size, project phase, relationship history] Stakes: [what happens if this isn't resolved] Please help me: 1. Identify the likely root cause (Thomas-Kilmann lens: competing/avoiding/compromising/accommodating/collaborating?) 2. Assess whose interests are legitimate and where they clash 3. Suggest a structured 3-step resolution approach 4. Draft a neutral message I can send to bring both parties to a conversation

Difficult conversation prep I need to have a difficult conversation with [team member / stakeholder]. Issue: [what needs to be addressed — performance, behavior, missed commitment] My goal: [what outcome I want from the conversation] Risk: [what I'm worried about — defensiveness, escalation, relationship damage] Their likely reaction: [how I expect them to respond] Help me: 1. Structure the conversation using SBI (Situation-Behavior-Impact) framework 2. Anticipate their objections and prepare my responses 3. Draft an opening statement that is direct but not accusatory 4. Define what success looks like at the end of the conversation

Stakeholder conflict escalation decision I'm a PM deciding whether to escalate a conflict. Here's the situation: - Parties involved: [describe] - Duration of conflict: [how long] - Impact on project: [scope/schedule/team morale impact] - Steps already taken: [what I've tried] - Sponsor/leadership awareness: [do they know?] Analyze whether I should: (a) continue to mediate directly, (b) escalate to sponsor/PMO, or (c) involve HR. Provide a decision framework and draft an escalation message if needed.

Jira / Confluence Template

Confluence — Conflict Resolution Record

── CONFLUENCE: CONFLICT RESOLUTION RECORD ─────────────── Date: [YYYY-MM-DD] Parties Involved: [Name/Role] vs [Name/Role] Raised By: [PM / Stakeholder / Team Member] Conflict Type: [ ] Task [ ] Process [ ] Relationship [ ] Values ── SITUATION ───────────────────────────────────────────── Root Cause: [Summary of what triggered the conflict] Positions: Party A wants: [their stated position] Party B wants: [their stated position] Underlying Needs: [what each party actually needs] Project Impact: [ ] Low [ ] Medium [ ] High ── RESOLUTION ACTIONS ──────────────────────────────────── Approach Used: [Collaborating / Compromising / Smoothing / etc.] Actions Agreed: 1. [Action — Owner — Due date] 2. [Action — Owner — Due date] Follow-up Date: [YYYY-MM-DD] Status: [ ] Open [ ] Resolved [ ] Escalated