Skip to content

project-stakeholder

Formal PM artifact — stakeholder register, SVG power-interest grid, and engagement plan for a specific project. Use when the user mentions 'stakeholder register', 'power interest grid', 'identify stakeholders', 'project stakeholder document', or 'stakeholder methodology'. For ongoing relationship management and feedback briefs, see stakeholder-craft. For political navigation and buy-in, see influence-craft.

  • Area: Project Delivery
  • Category: project management
  • Level: beginner
  • Input: conversation
  • Output: document
  • Setup: none
  • Roles:

Formal PM artifact — stakeholder register, SVG power-interest grid, and engagement plan for a specific project.

How you ask

  • “Create a stakeholder register for our project”
  • “Build a power-interest grid for stakeholder analysis”
  • “Develop a stakeholder engagement plan”
  • “Identify and classify all project stakeholders”

Inputs

  • project_charter — Approved charter — scope, objectives, constraints (from project-charter) — read to ground stakeholder identification in the project's stated purpose.
  • request — The stakeholder-analysis task to produce — a fresh register, an update, or a specific quadrant or communication question.
  • scope — company, or a client-id under {company.clients}/ — a string with one reserved value, not a closed set
  • profile — Company or client profile — delivery standards and project context behind the stakeholder set. For client scope, resolves to the client profile instead (client.profile).
  • project_charter — Approved charter, where one exists, used to infer stakeholders the caller did not name directly.
  • request — The stakeholder-analysis task to produce, plus whatever partial stakeholder detail the caller can supply directly since the full roster is not available.
  • project_charter — Approved charter, where one exists, used to ground the stakeholder analysis since the grid cannot be plotted.
  • request — The stakeholder-analysis task to produce, given that quadrant placement will be reasoned manually rather than plotted.

Outputs

  • Portfolio-visibility mirror of the completed register for company or client management review.
  • Power (Y) x Interest (X) scatter plot with labeled quadrants and attitude color-coding, generated by stakeholder_grid.py.
  • Power-interest scatter plot generated from the assumption-filled stakeholder set.
  • Stakeholder directory and engagement plan built from the available detail, with every assumed power, interest, or attitude value stated explicitly.
  • Stakeholder directory, quadrant analysis, engagement assessment, and communication plan reasoned by hand, with the script error reported and the grid explicitly marked unavailable.
  • Stakeholder directory, quadrant analysis, engagement assessment, and communication plan, with the power-interest grid embedded.
  • {company.project-management}/project-stakeholder-{{YYYY-MM-DD}}.md
  • {project-folder}/stakeholder_grid.svg
  • {project-folder}/stakeholder_register.md