---
title: "Enterprise Stakeholder Analysis Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2025-08-05"
primary_principles: ["stakeholder-engagement", "systems-thinking"]
secondary_principles: ["collaborative-leadership"]
principle_rationale: "Maps enterprise influence networks and affected groups to engagement strategies, communication responsibilities and escalation routes."
---

# Enterprise Stakeholder Analysis Template

## When to Use

- At initiation of a complex program with many affected groups and decision authorities.
- When influence networks, external parties, and conflicting needs require an engagement strategy.

## When NOT to Use

- For a small initiative where a concise stakeholder register already supports the decisions.
- Do not represent attendance, distribution, or silence as stakeholder agreement. See [Stakeholder broadcast](../../../../../docs/principles/anti-patterns.md#stakeholder-broadcast).

## Pairs Well With

- [Stakeholder Register Template](../../../../../domains/stakeholder/project-lifecycle/01-initiation/stakeholder-analysis/stakeholder-register-template.md).
- [Communication Plan Template](../../../../../domains/delivery/templates/traditional/Traditional/Templates/communication_plan_template.md).

Selection context: Stakeholder domain; universal methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Project Information
- **Project/Program Name**: [Name]
- **Project Manager**: [Name]
- **Date**: [Date]
- **Scope**: [Enterprise/Portfolio/Program level]
- **Duration**: [Project timeline]

## Executive Summary
[Brief overview of the stakeholder landscape, key challenges, and strategic importance of stakeholder management for this enterprise initiative]

## Stakeholder Ecosystem Mapping

### Executive Level
| Stakeholder | Role | Organization | Influence | Interest | Power Level |
|-------------|------|--------------|-----------|----------|-------------|
| [Name] | CEO/President | [Organization] | Very High | [Level] | Strategic |
| [Name] | COO | [Organization] | Very High | [Level] | Strategic |
| [Name] | CTO/CIO | [Organization] | High | [Level] | Strategic |
| [Name] | CFO | [Organization] | High | [Level] | Strategic |

### Senior Management
| Stakeholder | Role | Organization | Influence | Interest | Power Level |
|-------------|------|--------------|-----------|----------|-------------|
| [Name] | VP Engineering | [Organization] | High | [Level] | Operational |
| [Name] | VP Sales | [Organization] | High | [Level] | Operational |
| [Name] | VP Marketing | [Organization] | Medium | [Level] | Operational |

### Middle Management
| Stakeholder | Role | Department | Influence | Interest | Impact Area |
|-------------|------|------------|-----------|----------|-------------|
| [Name] | Director | [Department] | Medium | [Level] | [Area] |
| [Name] | Manager | [Department] | Medium | [Level] | [Area] |

### Operational Level
| Stakeholder | Role | Team | Influence | Interest | Involvement Type |
|-------------|------|------|-----------|----------|------------------|
| [Name] | Team Lead | [Team] | Low-Medium | [Level] | [Type] |
| [Name] | Subject Matter Expert | [Team] | Medium | [Level] | [Type] |

## External Stakeholders

### Customers and Partners
| Stakeholder | Organization | Relationship | Influence | Interest | Engagement Strategy |
|-------------|--------------|--------------|-----------|----------|-------------------|
| [Name] | [Company] | Key Customer | High | [Level] | [Strategy] |
| [Name] | [Company] | Strategic Partner | Medium | [Level] | [Strategy] |

### Vendors and Suppliers
| Stakeholder | Company | Service/Product | Influence | Interest | Management Approach |
|-------------|---------|-----------------|-----------|----------|-------------------|
| [Name] | [Company] | [Service] | Medium | [Level] | [Approach] |

### Regulatory and Compliance
| Stakeholder | Organization | Jurisdiction | Influence | Interest | Compliance Requirements |
|-------------|--------------|--------------|-----------|----------|----------------------|
| [Name] | [Agency] | [Region] | High | [Level] | [Requirements] |

## Stakeholder Analysis Matrix

### Power/Interest Grid

#### High Power, High Interest (Manage Closely)
**Key Players - Require Active Management**
- **[Stakeholder 1]**: [Name, Role]
  - **Engagement Strategy**: Weekly updates, direct involvement in decisions
  - **Communication Method**: Face-to-face meetings, executive reports
  - **Key Concerns**: [Primary concerns and motivations]
  - **Success Criteria**: [What they need to see to support the project]

- **[Stakeholder 2]**: [Name, Role]
  - **Engagement Strategy**: [Strategy]
  - **Communication Method**: [Method]
  - **Key Concerns**: [Concerns]
  - **Success Criteria**: [Criteria]

#### High Power, Low Interest (Keep Satisfied)
**Context Setters - Need Periodic Updates**
- **[Stakeholder 1]**: [Name, Role]
  - **Engagement Strategy**: Monthly summaries, escalate only critical issues
  - **Communication Method**: Executive dashboards, formal reports
  - **Monitoring Approach**: [How to track their satisfaction]

#### Low Power, High Interest (Keep Informed)
**Subjects - Provide Regular Information**
- **[Stakeholder 1]**: [Name, Role]
  - **Engagement Strategy**: Regular communication, involvement in relevant activities
  - **Communication Method**: Newsletters, team meetings, updates
  - **Value Contribution**: [How they can contribute to project success]

#### Low Power, Low Interest (Monitor)
**Crowd - Minimal Effort Required**
- **[Stakeholder 1]**: [Name, Role]
  - **Monitoring Approach**: Periodic check-ins, watch for changes in interest/power
  - **Communication Method**: General announcements, broadcast updates

## Stakeholder Influence Network

### Influence Relationships
| Stakeholder | Influences | Influenced By | Influence Type |
|-------------|------------|---------------|----------------|
| [Name] | [Names] | [Names] | Formal/Informal |
| [Name] | [Names] | [Names] | Formal/Informal |

### Coalition Building Opportunities
- **Pro-Project Coalition**: [Stakeholders who strongly support the project]
- **Neutral Stakeholders**: [Stakeholders who could be influenced either way]
- **Potential Opposition**: [Stakeholders who might resist the project]

### Key Influencers
1. **[Name]**: [Role and why they're influential]
2. **[Name]**: [Role and why they're influential]
3. **[Name]**: [Role and why they're influential]

## Communication Strategy

### Communication Matrix
| Stakeholder Group | Information Needs | Method | Frequency | Owner | Format |
|------------------|-------------------|--------|-----------|-------|--------|
| Executive Team | Strategic progress, ROI, risks | Face-to-face, Executive reports | Monthly | PM | Dashboard |
| Senior Management | Operational impact, resource needs | Meetings, Status reports | Bi-weekly | PM | Detailed reports |
| Middle Management | Team impact, process changes | Presentations, Email | Weekly | PM/Team Leads | Summaries |
| Project Teams | Task assignments, dependencies | Daily standups, Tools | Daily | Team Leads | Operational |

### Escalation Matrix
| Issue Level | Stakeholder | Escalation Path | Timeline | Method |
|-------------|-------------|-----------------|----------|--------|
| Operational | Team Lead | Project Manager | 24 hours | Email/Call |
| Tactical | Project Manager | Program Manager | 48 hours | Meeting |
| Strategic | Program Manager | Executive Sponsor | 72 hours | Formal presentation |
| Critical | Executive Sponsor | CEO/Board | Immediate | Emergency meeting |

## Risk Assessment

### Stakeholder-Related Risks
| Risk | Stakeholder | Impact | Probability | Mitigation Strategy | Owner |
|------|-------------|--------|-------------|-------------------|-------|
| Loss of executive support | [Executive] | High | Medium | Regular engagement, quick wins | PM |
| Resource reallocation | [Manager] | Medium | High | Clear business case, alternatives | PM |
| Scope creep pressure | [User Group] | Medium | High | Change control process | PO |

### Resistance Analysis
| Stakeholder | Resistance Level | Reasons | Mitigation Approach |
|-------------|------------------|---------|-------------------|
| [Name] | High | [Reasons] | [Approach] |
| [Name] | Medium | [Reasons] | [Approach] |

## Engagement Plan

### Phase-Based Engagement
#### Initiation Phase
- **Key Activities**: Stakeholder identification, initial buy-in
- **Primary Stakeholders**: Executive sponsors, key influencers
- **Success Criteria**: Project approval, resource allocation

#### Planning Phase
- **Key Activities**: Detailed planning, resource commitments
- **Primary Stakeholders**: Operational managers, technical leads
- **Success Criteria**: Approved plans, committed resources

#### Execution Phase
- **Key Activities**: Regular updates, issue resolution
- **Primary Stakeholders**: All active stakeholders
- **Success Criteria**: Maintained support, issue resolution

#### Closure Phase
- **Key Activities**: Benefit realization, lessons learned
- **Primary Stakeholders**: Sponsors, end users
- **Success Criteria**: Achieved benefits, stakeholder satisfaction

### Stakeholder Events Calendar
| Event | Stakeholders | Frequency | Objective |
|-------|-------------|-----------|-----------|
| Executive Review | Executive team | Monthly | Strategic alignment |
| Steering Committee | Senior management | Bi-weekly | Operational oversight |
| User Group Meetings | End users | Weekly | Feedback and buy-in |
| Vendor Reviews | External partners | Quarterly | Performance management |

## Success Metrics

### Stakeholder Satisfaction Metrics
| Metric | Target | Measurement Method | Frequency |
|--------|--------|--------------------|-----------|
| Executive Satisfaction | >4.0/5.0 | Survey | Quarterly |
| User Adoption Rate | >80% | Usage analytics | Monthly |
| Support Level | >85% | Stakeholder survey | Bi-annually |

### Engagement Effectiveness
- **Communication Response Rate**: Target >90%
- **Meeting Attendance**: Target >85% for key stakeholders
- **Issue Resolution Time**: Target <48 hours for critical stakeholder issues
- **Feedback Quality**: Measured through structured feedback forms

## Action Plans

### Immediate Actions (Next 30 Days)
| Action | Stakeholder | Owner | Due Date | Success Criteria |
|--------|-------------|-------|----------|------------------|
| [Action 1] | [Stakeholder] | [Owner] | [Date] | [Criteria] |
| [Action 2] | [Stakeholder] | [Owner] | [Date] | [Criteria] |

### Relationship Building Initiatives
- **[Initiative 1]**: [Description, stakeholders involved, timeline]
- **[Initiative 2]**: [Description, stakeholders involved, timeline]

### Conflict Resolution Plans
- **[Potential Conflict 1]**: [Description, stakeholders, resolution approach]
- **[Potential Conflict 2]**: [Description, stakeholders, resolution approach]

## Governance and Decision Making

### Decision Authority Matrix (RACI)
| Decision Type | Executive | Senior Mgmt | Project Team | External |
|---------------|-----------|-------------|--------------|----------|
| Strategic Direction | A | R | C | I |
| Resource Allocation | A | R | C | I |
| Scope Changes | A | R | R | C |
| Technical Decisions | I | C | A/R | C |

### Governance Bodies
- **Executive Steering Committee**: [Members, frequency, authority]
- **Project Management Office**: [Role, reporting, authority]
- **Change Control Board**: [Members, frequency, authority]

## Review and Updates

### Regular Review Schedule
- **Weekly**: Operational stakeholder status
- **Monthly**: Management stakeholder review
- **Quarterly**: Complete stakeholder analysis update
- **Semi-annually**: Stakeholder strategy review

### Update Triggers
- Major project milestones
- Significant organizational changes
- New stakeholder identification
- Changes in stakeholder power/interest
- Project scope or timeline changes

### Continuous Improvement
- **Stakeholder Feedback Integration**: Process for incorporating feedback
- **Engagement Strategy Optimization**: Regular assessment and improvement
- **Best Practice Documentation**: Capturing and sharing lessons learned

---

**Prepared by**: [Project Manager Name]  
**Reviewed by**: [Sponsor Name]  
**Last Updated**: [Date]  
**Next Review**: [Date]

*Comprehensive stakeholder management for enterprise success*