Build and maintain a Stakeholder Register per PMBOK 8 Stakeholder Performance Domain. Identify stakeholders, analyze using Power/Interest grid, plan engagement strategies, and define communication cadence. Use at project initiation and whenever stakeholder landscape changes.
Map each stakeholder on a 2×2 matrix:
| High Interest | Low Interest |
|---|
| High Power | Manage Closely | Keep Satisfied |
| Low Power | Keep Informed | Monitor |
For each stakeholder, also assess:
For each quadrant, define the engagement strategy:
| Quadrant | Strategy | Communication Frequency |
|---|---|---|
| Manage Closely | Proactive, face-to-face, co-create | Weekly or bi-weekly |
| Keep Satisfied | Regular updates, escalation channel | Bi-weekly or monthly |
| Keep Informed | Status reports, newsletters | Monthly |
| Monitor | Passive, available on request | Quarterly or ad-hoc |
Map key stakeholders to project deliverables using RACI:
| Input | Required | Format |
|---|---|---|
| Project charter or brief | Yes | Document or summary |
| Org chart | Recommended | Hierarchy diagram or list |
| Sponsor brief | Recommended | Key expectations and constraints |
## Stakeholder Register — [Project Name]
### Register
| # | Name | Role | Power | Interest | Quadrant | Current | Desired | Strategy |
|---|------|------|-------|----------|----------|---------|---------|----------|
| 1 | Jane Kim | VP Finance | High | High | Manage Closely | Neutral | Supportive | Weekly 1:1, co-design budget review |
| 2 | Mark Lee | IT Director | High | Low | Keep Satisfied | Supportive | Supportive | Monthly status email + escalation path |
| 3 | Sarah Chen | End User Lead | Low | High | Keep Informed | Resistant | Neutral | Include in demos, gather feedback |
| 4 | External Auditor | Regulator | High | Low | Keep Satisfied | Neutral | Neutral | Quarterly compliance report |
### Power/Interest Grid
High Power │ Keep Satisfied │ Manage Closely │
│ Mark Lee │ Jane Kim │
───────────┼────────────────┼─────────────────│
Low Power │ Monitor │ Keep Informed │
│ │ Sarah Chen │
└──Low Interest──┴──High Interest──┘
### Communication Plan
| Stakeholder | Channel | Frequency | Owner | Content |
|-------------|---------|-----------|-------|---------|
| Jane Kim | 1:1 meeting | Weekly | PM | Decisions, risks, budget |
| Mark Lee | Email report | Monthly | PM | Status, IT dependencies |
| Sarah Chen | Demo + survey | Bi-weekly | BA | Feature feedback |
### RACI — Key Deliverables
| Deliverable | Jane Kim | Mark Lee | Sarah Chen | PM |
|-------------|----------|----------|------------|-----|
| Requirements | C | C | R | A |
| Budget approval | A | I | I | R |
| User testing | I | C | R | A |
I am starting a new ERP implementation project.
Sponsor: CFO. Key departments: Finance, IT, Operations, HR.
External: ERP vendor (SAP), external auditor.
Build a complete stakeholder register with engagement strategies and communication plan.
| Check | Question |
|---|---|
| Correctness | Are all configurations, permissions, and dependencies accurate? |
| Completeness | Does the setup cover dev, staging, and prod environments as needed? |
| Context-fit | Is the solution proportional to the problem (not over/under-engineered)? |
| Consequence | If deployed as-is to production, what is the highest-risk failure mode? |