Stakeholder Analysis identifies who is affected by a change, what they need, how much influence they have, and how to involve them effectively.
Definition
Stakeholder Analysis is the structured review of people and groups who can affect, are affected by, or must support a project or change. It examines interest, influence, impact, current support, likely concerns, communication needs, and involvement strategy.
It helps improvement teams design adoption, not just technical solutions.
History
Stakeholder analysis comes from project management, change management, systems thinking, and organizational development. Lean Six Sigma teams use it because many process changes fail when affected people are identified too late.
When to Use
Use Stakeholder Analysis during project chartering, change planning, Kaizen preparation, system rollout, policy change, reorganization, and any improvement that changes roles, measures, workload, authority, or routines.
Step-by-Step
- List affected individuals, roles, teams, customers, suppliers, and leaders.
- Assess influence, impact, interest, and current support.
- Identify likely concerns, losses, and adoption barriers.
- Decide who must be consulted, informed, involved, or actively sponsored.
- Create communication and involvement actions.
- Assign owners for stakeholder follow-up.
- Monitor support and resistance during implementation.
- Update the analysis as the project changes.
Examples
- Layout change: Operators, maintenance, safety, material handlers, and supervisors all have different concerns.
- Software rollout: Users, IT, compliance, managers, and customers require different communication.
- DMAIC: Finance and process owners must validate benefits and sustain controls.
Common Pitfalls
- Only listing senior leaders.
- Assuming silence means support.
- No plan for informal influencers.
- Communicating after decisions are already locked.
- Ignoring groups that lose convenience, status, or control.
- No feedback loop during implementation.