Understanding Your Stakeholders

Before you can improve a process, you need to understand who cares about it. Stakeholder analysis helps you identify everyone involved in or affected by your process—and figure out how to work with them effectively.


Who is a Stakeholder?

A stakeholder is anyone involved in or affected by your process, across its entire life cycle. This includes:

  • Those who do the work - The people actually performing process steps
  • Those who receive the output - Internal or external customers
  • Those who provide inputs - Suppliers, data sources, upstream processes
  • Those who manage it - Supervisors, executives, governance bodies
  • Those affected by it - Even indirectly, like neighbors of a factory

The key insight is that stakeholders extend far beyond the obvious participants. A shipping process affects warehouse workers, but also customers waiting for packages, finance teams tracking costs, and IT staff maintaining the systems.


Why Stakeholder Analysis Matters

Practical Benefits

Benefit What It Means
Complete requirements You won't miss what different groups need
Reduced resistance People support changes they helped shape
Better solutions Diverse perspectives catch blind spots
Smoother implementation You know who needs to be trained, informed, or consulted

The Cost of Skipping It

Organizations that skip stakeholder analysis often face:

  • Surprise objections late in the project
  • Missing requirements discovered after implementation
  • Adoption failures because users weren't consulted
  • Political resistance from groups who felt ignored

Stakeholder Identification Techniques

1. The Stakeholder List

Start with the basics: make a list of everyone who touches the process.

Categories to consider:

Example: Insurance Claims Process

Category Stakeholders
Performers Claims adjusters, Investigators, Customer service reps
Managers Claims supervisors, Department heads
Support IT support, Training team, Quality assurance
External Policyholders, Healthcare providers, Repair shops
Governance Compliance officers, State regulators

2. The Stakeholder Matrix

Once you've identified stakeholders, understand their influence and interest.

How to use the matrix:

  • High influence, High interest (Manage closely) - Key players who need regular engagement
  • High influence, Low interest (Keep satisfied) - Powerful but distant; don't bore them with details
  • Low influence, High interest (Keep informed) - Engaged supporters; good sources of insight
  • Low influence, Low interest (Monitor) - Minimal effort, but don't ignore completely

3. The Onion Diagram

Visualize stakeholders by their proximity to the core process.

Layers typically include:

  1. Core - Those directly performing the process
  2. Direct support - Those enabling the core performers
  3. Organizational - Management, governance, adjacent departments
  4. External - Customers, suppliers, regulators, community

4. RACI Analysis

For each process step or project activity, clarify who is:

Role Definition Key Question
Responsible Does the work Who performs this task?
Accountable Owns the outcome Who has final authority?
Consulted Provides input Whose expertise is needed?
Informed Needs to know Who should be updated?

Example: New Employee Onboarding

Activity HR Manager IT Employee
Offer letter R, A C I I
Equipment setup I C R, A I
Orientation R, A C C R
Training plan C R, A I R

Rule: Each row should have exactly one "A" (Accountable). Multiple people can be Responsible, but one person owns the outcome.


Building Stakeholder Personas

For key stakeholder groups, develop detailed personas that capture:

What to Include

  • Role and responsibilities - What do they do day-to-day?
  • Goals and motivations - What are they trying to achieve?
  • Pain points - What frustrates them about the current process?
  • Information needs - What do they need to know to do their job?
  • Interaction patterns - How and when do they engage with the process?

Example Persona

Maria - Claims Adjuster

Role: Reviews and approves insurance claims under $10,000

Goals: Process claims accurately and quickly; maintain quality scores

Pain points: Incomplete documentation from claimants; system slowdowns during peak times; unclear guidelines for edge cases

Needs: Fast access to policy details; clear decision criteria; easy communication with claimants

Interaction: Uses claims system 6-8 hours daily; handles 20-30 claims per day; peaks on Mondays


Engaging Stakeholders Effectively

Identification is just the start. You need to actually engage stakeholders throughout your improvement effort.

Engagement Strategies by Quadrant

Communication Planning

Stakeholder Group Format Frequency Owner
Steering committee Presentation Bi-weekly Project lead
Process performers Team meeting Weekly Supervisor
IT support Email update As needed Tech lead
External customers Newsletter Monthly Communications

Common Pitfalls

Forgetting the "Invisible" Stakeholders

Some stakeholders don't have obvious presence but matter greatly:

  • Future employees who will inherit the process
  • Auditors who will examine it later
  • Customers' customers affected downstream
  • Community members affected by externalities

Treating All Stakeholders the Same

A one-size-fits-all approach wastes effort and annoys people. Executives don't want the same level of detail as process performers. External customers don't need internal project updates.

Identifying but Not Engaging

A stakeholder list that sits in a drawer helps no one. Use your analysis to drive actual engagement throughout the project.


Practical Exercise

For your target process, complete this stakeholder identification:

  1. List all stakeholders you can identify (aim for at least 15-20)
  2. Categorize them as internal/external and by role type
  3. Place them on the influence/interest matrix
  4. Create personas for the 3-5 most important groups
  5. Draft a communication plan for key stakeholders

Key Takeaways

  • Stakeholders include everyone involved in or affected by your process
  • Use multiple techniques: lists, matrices, onion diagrams, RACI
  • Develop detailed personas for key stakeholder groups
  • Tailor your engagement approach to each group's needs
  • Revisit your stakeholder analysis as the project evolves