methodatlas
RunsheetFacilitation

Power Interest Grid

ComplexityLow
Time30-60 min
Participants2-8
FormatWorkshop
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstStakeholder Mapping

A stakeholder list with names, roles and rough relationship to the initiative is available (at least 5-10 stakeholders).

Without: Without a stakeholder list, the grid becomes a brainstorming session and positioning lacks a basis.
02

Preparation

What needs to be ready before start

Materials

Whiteboard or Miro board with 2x2 matrix (X: Interest, Y: Power); stakeholder cards with name and role; definition banner for Power and Interest; pens; confidential storage for the artifact.

People / roles

One facilitator who keeps definitions present and protects confidentiality; project lead or sponsor; 2-6 additional participants with stakeholder context; scribe for strategy notes.

Pre-read

Stakeholder list with roles and mandates; known history (past conflicts, alliances); current distribution lists; project charter with stakeholder reference.

Time needed

30-60 min

Setup

Set up matrix with 4 quadrants: Manage Closely (high P, high I), Keep Satisfied (high P, low I), Keep Informed (low P, high I), Monitor (low P, low I). Keep definitions visible. Mark artifact confidential.

03

Core question

The one question this method answers

Which stakeholders need which communication and relationship strategy, based on their power and interest in the initiative?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Define Power and Interest
10 minPower: influence on project success (budget, veto, resources). Interest: affectedness or engagement. Give examples from the initiative for each definition.Power and Interest are not the same as hierarchy. A sponsor can be high or low in Interest. Clarify definitions before plotting.
2Phase 2: Position stakeholders
15-25 minPlace stakeholders individually in quadrants. When there is discussion, note the rationale. Use hidden voting if politically sensitive.Positions are a snapshot. Nobody sees the grid except workshop participants. Confidentiality is a prerequisite for honesty.
3Phase 3: Discuss clusters
10-15 minCheck each quadrant: does the distribution fit? Discuss outliers. Nobody should sit alone in a quadrant without rationale.The Manage Closely quadrant should not be overcrowded (max 5-7). Too many there paralyze the project. If it is full, check the Power definition.
4Phase 4: Strategy per quadrant
10-15 minDerive communication strategy per quadrant: Manage Closely (1:1 meetings, early involvement), Keep Satisfied (status reports, ad-hoc briefings), Keep Informed (email updates, newsletter), Monitor (public updates).Strategy without concrete action is empty wording. Define at least one concrete cadence per quadrant, for example weekly status email or bi-weekly 1:1.
05

Artifact

What comes out at the end

Form

Grid diagram as board export or photo, plus table list of stakeholders with quadrant, strategy, communication cadence and owner. Confidential storage with access for sponsor and project lead.

Versioning / ownership

Recreate quarterly or when mandates change. Archive previous version with date and rationale for change. Confidential. Update immediately after personnel changes.

Tool alternatives
  • Miro or FigJam with Power-Interest template
  • Lucidchart with matrix template
  • Notion database with quadrant property
  • Confluence page with restricted table
  • Excel or Google Sheet sorted by quadrant

power-interest-grid-working-template.md

Compact working template for Power Interest Grid with context, input, output artifacts, and next step.

Power Interest Grid Working Template

Goal

Sorts stakeholders into four quadrants by influence and interest.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Power Interest Grid:
  • Stakeholder strategy:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

power-interest-grid-beispiel.md

Concrete filled scenario, fictional example

Power Interest Grid - Multi-Tenant Migration Q3/2026, 2026-05-18 (CONFIDENTIAL)

Manage Closely (high P, high I)

  • CTO @julia: strong veto right, drives multi-tenant as strategy. Strategy: weekly 1:1, architecture review before every milestone.
  • CFO @michael: budget owner, high attention because of cost impact. Strategy: monthly status with forecast, escalation on budget deviation.
  • Compliance Lead @sandra: veto on audit trail, critical interest. Strategy: bi-weekly 1:1, early involvement on compliance topics.

Keep Satisfied (high P, low I)

  • Sales Lead @thomas: can trigger escalation, interest is situational. Strategy: monthly 30-min briefing, ad-hoc for customer topics.
  • IT Director @marcus: can pull resources, interest currently low. Strategy: quarterly update, involve on infrastructure topics.

Keep Informed (low P, high I)

  • Customer Success Team: highly affected by migration. Strategy: bi-weekly update email, FAQ wiki, migration webinar.
  • Engineering Team B (frontend): direct stakeholder. Strategy: Slack channel, sprint review participation.

Monitor (low P, low I)

  • HR Lead: only tangential. Strategy: quarterly newsletter.
  • Marketing Team: launch-date information is sufficient. Strategy: briefing 4 weeks before launch.

Escalation trigger: On budget deviation >10% or compliance findings: inform CFO and Compliance Lead within 24h.

07

Pitfalls

Recognize symptoms and steer against them

Trap

Power equals hierarchy

Symptom

Senior managers automatically land high in Power, while actual veto people are missed.

What to do

Define Power as actual influence, not org-chart position. Examples: domain experts without formal power can have high veto power (compliance, security).

Trap

Interest treated as static

Symptom

Stakeholders are positioned once, and Interest changes across project phases are ignored.

What to do

Treat the grid as a snapshot. Re-evaluate quarterly. Expect Interest shifts at phase changes, for example from planning to launch.

Trap

Manage Closely quadrant overcrowded

Symptom

More than 7 people are in Manage Closely, and the project lead has no capacity for 1:1 cadence.

What to do

Sharpen the Power definition. Someone with Power 4 instead of 5 may belong in Keep Satisfied. Manage Closely is scarce attention.

Trap

Communication without cadence

Symptom

Strategy per quadrant is abstract ("communicate closely"), with no concrete dates.

What to do

Define concrete cadence per stakeholder: weekly 1:1, monthly status report, ad-hoc on topics. Without cadence, strategy decays within 4 weeks.

Trap

Artifact leaks

Symptom

A stakeholder learns their quadrant position and feels misclassified or offended.

What to do

Enforce confidentiality centrally. Restrict access to sponsor and project lead. If a leak happens, communicate transparently and discuss the position again.

08

Stop criteria

Done signals checkable in under a minute

Fewer than 5 stakeholders, so the grid would be overhead.
Power and Interest definitions cannot be made clear, so assessment would be gut feeling.
Project is very small and internal; all stakeholders use the same cadence.
Confidentiality cannot be guaranteed (for example public tool), and stakeholder harm is likely.
Sponsor or project lead is absent, so strategy derivation would be non-binding.
An established stakeholder strategy already exists, so the grid would create a parallel structure.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.