Codexkit Pmbok8 Stakeholder Register

For each stakeholder, also assess:

• Current attitude: Supportive / Neutral / Resistant
• Desired attitude: Where you need them to be
• Influence direction: Upward / Downward / Lateral / External

Step 3 — Plan Engagement

For each quadrant, define the engagement strategy:

Step 4 — Define RACI Alignment

Map key stakeholders to project deliverables using RACI:

• Responsible — does the work
• Accountable — owns the outcome
• Consulted — provides input
• Informed — receives updates

Inputs

Output

## 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 |

Definition of Done

• All stakeholders identified with role and org position
• Power/Interest grid completed for each stakeholder
• Engagement strategy defined per quadrant
• Communication plan with frequency, channel, and owner
• Current vs desired attitude gap identified
• At least one RACI matrix for key deliverables

Examples

Prompt

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.

Quality Criteria

• All dependencies and prerequisites are documented
• Changes are reversible or include a rollback plan
• Security implications are assessed for each configuration change
• Monitoring and alerting are defined for post-deployment validation

Verification (4C)

Edge Cases

• Target environment has pre-existing configuration — Scan for conflicts before applying changes. Document what to preserve.
• Permissions differ between environments — Test in staging first. Document the minimum permissions required.
• Third-party service is unavailable or deprecated — Document fallback or alternative. Include health-check endpoints.

Changelog

• v1.0.0 — Initial release