Skip to content
PMPCAPM

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Share:

Know it well enough for the exam? Questions on Power Interest Grid (Power/Influence Grid) are scenario-based, not definitional.

Practice it free

Explanation

The grid is used early, during stakeholder analysis, as soon as the main stakeholders have been identified (in predictive terms, the Identify Stakeholders process, typically once the charter exists). It is used again whenever the stakeholder landscape shifts: a reorganization, a new sponsor, a phase gate, an escalation. Its real output is not the picture but the decisions that follow from it: who sits on the steering group, who gets a one-page monthly summary, who is invited to demos and feedback sessions. Those decisions are recorded in the stakeholder register and the stakeholder engagement plan.

Its strength is simplicity. A team can build one in a short workshop and explain it to a sponsor in a minute. The weakness is the same simplicity: two axes, scores that are judgment calls, and a result that can be politically sensitive. Few executives enjoy seeing themselves plotted in the "monitor" corner, so many project managers keep the grid in their working files and share the communication approach derived from it instead.

The name varies. PMI material groups the power/interest, power/influence and impact/influence grids as variations of the same two-axis technique, and people searching for a "power influence grid" usually mean this 2x2 with influence as the second axis. The quadrant logic and the exam reasoning are the same; read which attributes the question gives you.

The power interest grid in plain language

You can't give every stakeholder the same amount of attention, and you shouldn't try. The power interest grid is a quick way to decide where your engagement effort goes. For each stakeholder you ask two questions: How much can this person change or stop the project? (power) and How much do they care about its outcome? (interest). Plot the answers on a 2×2 and each quadrant suggests a default strategy.

The model is usually credited to Aubrey Mendelow's stakeholder mapping work in the early 1990s and is now standard in PMI material. The PMBOK Guide 6th edition lists it alongside the power/influence and impact/influence grids as stakeholder mapping techniques used in Identify Stakeholders; the 7th edition covers the same activity in the Stakeholders performance domain.

The four quadrants

QuadrantPower / interestDefault strategyWhat it looks like in practice
Manage closelyHigh / highEngage fully and oftenInvolve in key decisions, regular one-to-ones, early warning on risks and changes
Keep satisfiedHigh / lowMeet their needs without overloading themConcise summaries, escalate only what needs their decision, watch for rising interest
Keep informedLow / highCommunicate regularly and listenDemos, newsletters, feedback sessions; often your best source of requirements and early problems
MonitorLow / lowMinimum effort, periodic checkGeneral updates; re-assess if their situation changes

Worked example: hospital electronic records upgrade

A hospital is replacing the nursing documentation module of its electronic health record. The project team scores seven stakeholders from 0 to 10 for power and interest:

StakeholderPowerInterestQuadrantWhy
Chief Medical Officer (sponsor)99.5Manage closelyOwns the business case and funds the project
Director of Nursing87Manage closelyCan delay go-live if wards are not ready
CFO83Keep satisfiedApproves budget changes; little day-to-day interest
Information security officer72Keep satisfiedMust sign off before go-live; otherwise uninvolved
Ward nurses39Keep informedUse the system every shift; little formal authority
Patient advisory council27Keep informedCares about privacy and bedside time
Facilities manager22MonitorNeeds to know about extra network points, little more
KEEP SATISFIEDMANAGE CLOSELYMONITORKEEP INFORMEDInterest →lowhighPower →Ward nurses after union grievanceChief Medical Officer (sponsor)Director of NursingCFOSecurity officerWard nursesPatient councilFacilities manager
The same seven stakeholders on the grid. The dashed arrow shows the ward nurses moving up after a union grievance about new charting time.

What the project manager does with it

  • CMO and Director of Nursing: fortnightly steering meeting, involvement in the go-live decision, personal heads-up before any bad news reaches them through other channels.
  • CFO and security officer: a one-page monthly status, plus a scheduled security review well before go-live so the sign-off is not a surprise gate in the last week.
  • Ward nurses: super-user champions on each ward, demos of each release, a feedback channel that gets visible answers. Low formal power doesn't mean low importance; they decide whether the system is actually adopted.
  • Patient council: a briefing on privacy safeguards and a chance to comment on bedside workflow.
  • Facilities: included in the general update; contacted directly when cabling work is scheduled.

The grid moves

Mid-project the nurses' union files a grievance that the new forms add charting time. The nurses now have real power to stop rollout, so they move from keep informed to manage closely. The right response is to update the stakeholder register and the engagement plan and change how you work with them (for example, a joint workflow review), not to keep the old plan because the grid was “done” in planning.

Common exam traps

  • Swapping "keep satisfied" and "keep informed".

    Satisfied goes with high power (you need them content, not flooded with detail). Informed goes with high interest (they want to know). Anchor on power: powerful people are kept satisfied.

  • Reading "monitor" as "ignore".

    Monitor means minimal, periodic effort. PMI answers never favour excluding a stakeholder; the grid only sets the level of effort.

  • Dismissing high-interest, low-power stakeholders.

    End users usually sit here. Scenario questions that end with resistance or poor adoption often trace back to treating this group as an afterthought. Engagement, not just broadcast, is the PMI-preferred answer.

  • Treating the grid as a one-time planning artifact.

    Stakeholder analysis is iterative. When a stakeholder’s power or interest changes, re-assess and update the stakeholder register and engagement plan.

  • Confusing classification with engagement level.

    The grid says how much attention someone needs. The stakeholder engagement assessment matrix records how engaged they are now (unaware, resistant, neutral, supportive, leading) versus where you need them. A question about current vs desired engagement wants the matrix, not the grid.

Power/interest vs power/influence and other models

Searchers often type “power influence grid” for this model. They are close relatives: PMI lists the power/interest, power/influence and impact/influence grids together as variations of the same two-axis idea. The difference is the second axis. Interest is how much a stakeholder cares about the outcome; influence is how actively they can sway decisions, often informally. A respected senior engineer may have little formal power, high influence and only moderate interest. The full comparison is on the power/influence grid page.

ModelDimensionsUse it when
Power/interest gridPower, interestDeciding how much engagement effort each stakeholder gets
Power/influence gridPower, influenceInformal influence matters, e.g. politically complex or matrix organizations
Impact/influence gridImpact, influenceStakeholders can change plans or execution without formal power
Salience modelPower, urgency, legitimacyLarge or complex stakeholder communities; prioritizing claims
Stakeholder cubeThree of the above as a 3D modelRefining a 2×2 when two axes oversimplify

Where it fits

Stakeholders are identified and analysed early, typically right after the charter, and the grid output feeds the stakeholder register and the stakeholder engagement plan. In agile teams the same thinking shapes who attends reviews and how the product owner gathers input, even if no one draws the grid.

Practice and related pages

Key Points

  • •Two axes: power (can they change or stop the project?) and interest (do they care about the outcome?)
  • •Manage closely = high power, high interest; keep satisfied = high power, low interest
  • •Keep informed = low power, high interest; monitor = low power, low interest
  • •Used in stakeholder analysis; feeds the stakeholder register and engagement plan
  • •Positions change over the project, so re-assess when power or interest shifts
  • •It sets the level of attention; current vs desired engagement is tracked in the stakeholder engagement assessment matrix

Exam Tip

Anchor on power: high-power stakeholders are kept satisfied or managed closely; high-interest, low-power stakeholders are kept informed and still engaged, never ignored. When a scenario says a stakeholder has gained influence, the expected action is to re-analyze them and update the stakeholder register and engagement plan.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Stakeholder Analysis

Stakeholder analysis is a technique for systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Part of

Stakeholder Management

Study full domain →

Practice Power Interest Grid (Power/Influence Grid)

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.