Collaborate with Stakeholders
Hợp tác với Các bên liên quan
Xây dựng văn hóa hợp tác giữa các bên trong và ngoài dự án. Hợp tác không phải là "làm việc cùng nhau" một cách thụ động — đó là chủ động tạo ra sự đồng thuận và shared ownership.
📖 Lý thuyết / Theory
🇺🇸 English
Collaboration means working jointly toward shared goals. It's different from coordination (ensuring activities don't conflict) and cooperation (agreeing to help when asked). Collaboration is proactive, synergistic, and creates outcomes greater than what individuals could achieve alone.
PM collaborates with: internal team, product owners, business stakeholders, partner organizations, vendors, functional managers, PMO, executive sponsors.
Reference: PMI — Collaboration Skills for PMs
🇻🇳 Tiếng Việt
Hợp tác có nghĩa là cùng nhau làm việc hướng tới mục tiêu chung. Khác với coordination (đảm bảo hoạt động không xung đột) và cooperation (đồng ý giúp khi được hỏi). Hợp tác là chủ động, cộng hưởng và tạo ra kết quả vượt trội hơn những gì cá nhân có thể đạt được.
🔧 Team Collaboration Agreement
Team Collaboration Agreement
── COMMUNICATION CHANNELS ──────────────────────────
Async: Slack for day-to-day async communication
Sync: Zoom for discussions requiring real-time decision-making
External: Email for communication with Bank Partner A and external stakeholders
── RESPONSE TIME EXPECTATIONS ──────────────────────
Slack: 4 hours during work hours (9am–6pm local time)
Email: 24 hours on working days
Urgent: Tag @here in #project-alpha-urgent or call directly
── MEETING NORMS ────────────────────────────────────
• Agenda required at least 2 hours before meeting
• Decisions documented in Confluence within 24 hours
• No phones / no multitasking during calls
• Meeting owner responsible for sending notes
── CODE COLLABORATION ───────────────────────────────
• PR review within 24 hours of submission
• Pair programming for complex or high-risk features
• Definition of Done agreed before sprint start
• No merging without at least one approval
── CROSS-TEAM COORDINATION ─────────────────────────
• Designated liaison per team for inter-team topics
• Weekly cross-team sync (30 min) every Monday
• Escalation path: Team Lead → PM → Sponsor
🔧 Collaboration Tools & Techniques
| Tool/Technique | Purpose | When to Use |
|---|---|---|
| RACI Matrix | Clarify who is Responsible, Accountable, Consulted, Informed | Project kickoff; when role confusion exists |
| Decision Matrix | Objective evaluation of options with team | Complex decisions with multiple stakeholders |
| Workshop Facilitation | Structured sessions to gather input and align | Requirements gathering, retrospectives, planning |
| Shared workspace (Confluence, Notion) | Single source of truth for all project artifacts | Always — especially for distributed teams |
| Regular cadence | Sprint reviews, demos, stakeholder updates | Agile ceremonies; monthly stakeholder reviews |
| Cross-functional pairing | Developers & QA working together on stories | Complex features needing multiple perspectives |
💼 Thực chiến / Scenario
FinTech Company X — Cross-team API Collaboration
Tình huống: Project Alpha cần integrate với Legacy EVO system (owned bởi team khác). Hai teams có priorities khác nhau, EVO team không có bandwidth trong Q2.
Collaboration approach: PM tổ chức joint planning session với cả hai PMs. Thay vì "fight for bandwidth", identify shared goals: cả hai muốn platform được modernize. Agree on minimal viable integration API mà EVO team có thể deliver in 2 weeks. Alpha team build facade layer để decouple từ EVO internals. Mutual agreement: EVO team có autonomy over timeline, Alpha team adapt. Document integration contract (API spec) jointly.
PMP Principle: Collaboration tạo ra better solution (facade pattern) mà không force hoặc frustrate either team. Đây là collaborative problem solving across organizational boundaries.
✏️ Practice Questions
Question 1
The PM's project requires a critical integration with a system owned by another department. The other department's manager says they're too busy to help. What is the BEST approach?
- A. Escalate to executive management to force the department to cooperate
- B. Find a workaround that avoids the integration altogether
- C. Schedule a collaborative meeting to understand the department's constraints, identify shared interests, and explore mutually beneficial options
- D. Hire an external consultant to handle the integration
✅ Answer: C — The PMI way is to collaborate first — understand the other party's constraints, find common ground, and create options that work for both. Escalating immediately (A) damages relationships. Workarounds (B) create technical debt. External hire (D) is costly and skips collaboration. If C fails after genuine effort, then escalation may be appropriate.
Question 2
A project requires two teams from different departments to co-develop an API. One team writes the backend, another the frontend. How should the PM facilitate collaboration?
- A. Have teams work independently and integrate at the end
- B. Create shared definition of done, regular joint ceremonies, and clear API contracts agreed upfront
- C. Assign one team to manage the other
- D. Have the PM act as the single communication point between teams
✅ Answer: B — Effective cross-team collaboration requires: a shared understanding of what "done" looks like, regular touchpoints (joint sprint reviews, API design sessions), and upfront contracts (API spec) so both teams can work in parallel without hidden misalignments. Integrating at the end (A) creates big-bang integration risk. One team managing the other (C) creates hierarchy friction. Funneling all communication through the PM (D) creates a bottleneck and prevents team ownership.
Question 3
During a cross-team collaboration, Team A and Team B have conflicting priorities — both need the shared infrastructure resource. What should the PM do FIRST?
- A. Escalate to senior management immediately
- B. Facilitate a joint prioritization meeting with both teams to understand the impact of each team's needs and find a schedule that serves both
- C. Assign the resource to whichever team asked first
- D. Hire a dedicated resource for each team
✅ Answer: B — Collaboration first: bring both teams together to surface the real priorities, understand the business impact of each claim, and negotiate a shared schedule or sequenced access. This is the PMI collaborative conflict resolution approach. Escalating immediately (A) bypasses the teams' ability to self-resolve and damages relationships. First-come-first-served (C) ignores relative business value. Hiring duplicates (D) is wasteful and may not be feasible.
🤖 AI Tools for PMs
How AI Augments This Process
AI helps PMs draft stakeholder collaboration plans, synthesize diverse inputs, create decision logs, and facilitate structured workshops with large groups.
Sample Claude Prompts
Stakeholder workshop facilitation plan
I'm facilitating a [requirements workshop / planning session / alignment meeting] with [N] stakeholders.
Goal: [what decisions or outputs need to come out of this]
Stakeholder mix: [executive / technical / business / external]
Duration: [2 hours / half day / full day]
Known tensions: [any conflicts of interest or competing priorities]
Remote / in-person: [format]
Design the workshop:
1. Pre-work (what to send in advance, 1 page max)
2. Opening (10 min) — align on purpose and ground rules
3. Structured activities with timing (use specific techniques: dot voting, affinity mapping, silent brainstorm, etc.)
4. Decision-making method for contentious items (consensus / consult-decide / sponsor decides)
5. Close (10 min) — capture decisions, actions, open items
6. Follow-up email template (send within 24h)
Decision log synthesis
We just completed a [meeting / workshop / review]. Help me capture the decisions.
Meeting summary: [paste notes or describe what was discussed]
Attendees: [list of roles]
Decisions made: [rough list]
Open items: [unresolved questions]
Actions assigned: [rough list]
Create a clean Decision Log with:
1. Each decision: what was decided, who decided, date, rationale (1 sentence), alternatives considered
2. Open items: question, owner, due date
3. Action items: action, owner, due date, dependencies
4. Parking lot: items deferred to future session
Format for Confluence page.
Cross-functional alignment email
I need to align multiple stakeholders on [decision / direction / change].
Context: [what happened, what needs to be aligned on]
Stakeholders: [list roles and their positions/concerns]
My recommended direction: [what I believe we should do]
Risks if not aligned: [what happens if people stay misaligned]
Draft an alignment communication that:
1. Acknowledges each group's perspective (don't steamroll)
2. Clearly states the direction and the rationale
3. Explains what's fixed vs. what's still open for input
4. Specifies the deadline for any remaining feedback
5. Has a clear call to action
Tone: collaborative, not directive. Under 250 words.
Jira / Confluence Template
Confluence — Decision Log
── CONFLUENCE: PROJECT DECISION LOG ─────────────────────
Project: [Project Alpha] | Owner: [PM] | Last updated: [YYYY-MM-DD]
── DECISION RECORD ───────────────────────────────────────
ID: DEC-[001]
Date: [YYYY-MM-DD]
Decision: [Clear statement of what was decided]
Made by: [Role / name who has authority]
Rationale: [Why this option was chosen — 1-2 sentences]
Alternatives:
Option A: [what was considered] — reason not chosen
Option B: [what was considered] — reason not chosen
Impact: [scope / schedule / cost / team]
Reversible? [Yes — how / No — why it's locked]
Review date: [when to revisit if assumptions change]
── OPEN QUESTIONS ────────────────────────────────────────
Q: [Unresolved question]
Owner: [name] | Due: [date] | Status: [ ] Open [ ] Resolved