Identify Stakeholders

Stakeholders/Initiating/Identify Stakeholders
Inputs Tools & Techniques Outputs

Inputs, tools & techniques, and outputs for this process.

The disciplined, iterative activity of discovering everyone who can affect or be affected by the work, understanding their interests and influence, and recording how to engage and communicate with them.

Purpose & When to Use

Identify Stakeholders ensures you know who matters, why they matter, and how to work with them. It builds a shared view of roles, expectations, and influence so the team can plan engagement and communications effectively.

  • Use at the very start of the initiative to seed the stakeholder register and shape early engagement and communication plans.
  • Refresh continuously at phase gates, major scope or strategy changes, team changes, new vendors, regulatory updates, or when new risks emerge.
  • Apply in all delivery approaches (predictive, agile, hybrid) to support ongoing discovery, feedback, and governance.

Mini Flow (How It’s Done)

  • Review sources: charter or vision, business case, contracts, backlog, org charts, compliance obligations, prior lessons learned.
  • Elicit names: interview sponsor and product owner, hold workshops, scan governance bodies, vendors, users, support teams, regulators, and communities affected.
  • Analyze and categorize: assess interest, influence, impact, and current attitude; use simple tools like power–interest grids, salience or onion models, and relationship maps.
  • Prioritize and profile: identify key stakeholders, define what each cares about, preferred channels, availability, and potential benefits or concerns.
  • Draft initial engagement approach: outline how to involve high-priority stakeholders in decisions, feedback cycles, and reviews; note quick wins and early risks.
  • Create the stakeholder register: record names, roles, contact details, influence level, interests, current and desired engagement levels, and any constraints or sensitivities.
  • Validate and socialize: confirm the list and priorities with the sponsor or product owner and core team; adjust based on feedback.
  • Set upkeep rules: define update cadence, triggers for adding or reclassifying stakeholders, and access controls for sensitive information.

Quality & Acceptance Checklist

  • Key stakeholder groups are identified across business, technical, users, operations, vendors, governance, and external parties.
  • Each critical stakeholder has documented interests, influence, and current versus desired engagement level.
  • Prioritization is clear and defensible using simple, agreed criteria.
  • Initial engagement actions for high-priority stakeholders are defined and feasible.
  • Stakeholder register fields are complete, current, and traceable to sources or interviews.
  • Privacy and confidentiality needs are respected with appropriate access controls.
  • Update cadence and triggers are documented and communicated to the team.
  • Alignment exists with early communication and engagement planning activities.

Common Mistakes & Exam Traps

  • Treating identification as a one-time task instead of an iterative activity.
  • Ignoring stakeholders who may oppose the work or underestimating informal influencers.
  • Focusing only on internal roles and missing external regulators, suppliers, or affected communities.
  • Equating formal authority with actual influence and overlooking network relationships.
  • Jumping straight to a detailed communication plan without first building and analyzing the stakeholder register.
  • Sending the same message to everyone instead of tailoring by interest and influence.
  • Failing to validate the list with the sponsor or product owner, leading to missed decision-makers.
  • Storing personal data without consent or access controls, creating compliance risk.

PMP Example Question

You are assigned to lead a hybrid initiative. The sponsor asks you to publish a communication plan by end of week. What should you do first?

  1. Draft and distribute a communication plan to all parties using the PMO template.
  2. Build the stakeholder register and analyze each stakeholder’s interest and influence.
  3. Schedule recurring sprint reviews to collect feedback from users and management.
  4. Escalate to the PMO to confirm which communication channels are mandatory.

Correct Answer: B — Build the stakeholder register and analyze each stakeholder’s interest and influence.

Explanation: You need to identify and understand stakeholders before tailoring communication and engagement. The register is the foundation for an effective communication approach.

AI for Project Managers — Build Plans Faster, Lead Better

Turn messy inputs into structured project plans in minutes. If you are a project manager tired of spending hours on documentation, this course shows you how to use AI to work faster while staying fully in control.

This is not a generic AI course. You will learn how to use AI as a practical co-pilot to build real project artifacts—charters, WBS, schedules, risk registers, and executive reports—using structured, reliable prompt frameworks.

You will also learn how to keep your project aligned across scope, schedule, cost, and risk, and how to interpret performance data like Earned Value Management to support better decisions and communication.

Everything is designed for immediate use. You get ready-to-use prompt templates and workflows you can apply right away in your projects. Watch the video to see how it works and start building your first AI-supported project plan.



Become an AI-First Agile Leader!

HK School of Management empowers you to master AI as your most powerful co-pilot—without the complexity. Transform your agile leadership with practical, prompt-based workflows and proven strategies designed for real-world scrum challenges. For the price of lunch, you get the tools to automate mundane tasks, refine backlogs with precision, and drive unprecedented efficiency in your team. Backed by our 30-day money-back guarantee—zero risk, real impact.

Learn More