---
ref_id: TAILOR-STAKE
ref_type: FocusArea
ref_name: "Stakeholders Domain Tailoring Guidance"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1 & §2.2 · PMO Practice Guide §4"
file_path: "reference/tailoring/tailoring-stakeholders.md"
---

# Stakeholders Domain Tailoring Guidance

**Ref ID:** TAILOR-STAKE  
**Type:** FocusArea  
**PMBOK8 Source:** PMBOK 8 Stakeholder & Team Performance Domains  
**Version:** 1.0.0  
**Status:** Active  

---

## 1. Stakeholder Tailoring Factors

Stakeholder tailoring ensures that communication channels, engagement frequency, and team collaboration mechanisms are adjusted to match stakeholder diversity, location footprints, cultural backgrounds, and project complexity.

Key tailoring factors include:
* **Geographical Distribution:** Globally distributed teams require robust virtual whiteboard tools and scheduled handoff protocols.
* **Stakeholder Power & Diversity:** Projects involving government regulators, external clients, and multi-layered internal teams require a highly structured engagement strategy.
* **Team Maturity:** High-velocity agile teams require supportive/cooperative leadership; newer teams need directive coaching.
* **Language & Culture:** Multi-cultural teams require tailored, inclusive communication standards and holiday scheduling alignments.

---

## 2. Scaling Stakeholder Engagement Across T1–T4

Engagement and team communication tools are scaled to match project tiers:

| Stakeholder Element | T1 (Low Complexity) | T2 (Medium Complexity) | T3 (High Complexity) | T4 (Strategic/Enterprise) |
|---|---|---|---|---|
| **Stakeholder Register** | Simple spreadsheet | Standard Register (A07) | Register + Power-Interest Grid | Register + Dynamic matrix |
| **Communication Mode** | Direct ad-hoc calls | Weekly team emails | Cloud PMIS (Jira/Confluence) | Multi-channel newsletter + PMIS |
| **Collaboration Tool** | Direct messaging | Shared MS Teams workspace | Slack + Miro Boards | Multi-tier corporate workspace |
| **Feedback Loop** | Casual conversations | Bi-weekly retrospectives | Weekly sprint review panels | Formal steering committee audits |

---

## 3. Scenario Integration (Meridian CRM System Upgrade)

During the *Meridian CRM System Upgrade* project, stakeholder engagement was tailored to address two distinct user groups:
* **The Steering Committee (T3 High Power):** Scheduled monthly formal PMO presentations focusing on cost baselines (`PR16`) and milestone achievements.
* **The End Users (Medium Power / High Interest):** Conducted bi-weekly interactive product demos (`PR32`) and posted updates inside an internal corporate Slack channel to collect usability feedback.
* **Outcome:** Enabled rapid feedback loops, reducing project adoption friction and securing customer sign-off without delays.

---

## 4. Stakeholder Tailoring Checklist

When tailoring stakeholder and team engagement, answer these key questions:

- [ ] **How diverse is the stakeholder group?** Identify key decision-makers and separate them from general information recipients in your registry (`PR02`).
- [ ] **What is the optimal communication frequency?** Balance the team's productivity with stakeholder information needs; avoid meeting fatigue by utilizing asynchronous PMIS dashboards.
- [ ] **Are collaboration standards established?** Establish a **Team Charter** to set shared workspace rules, expected response times, and meeting core hours.
- [ ] **How is stakeholder satisfaction measured?** Run simple periodic surveys or review issue logs (`PR30`) to gauge stakeholder alignment.

---

*Authority: PMBOK8 Guide §2.1 & §2.2 · PMO Practice Guide §4*
