Every project has people who can help it, hurt it, or be hurt by it, and most of them are not on the team. The sponsor who funds it, the department whose process it changes, the security team who must approve it, the union whose members' work it alters, the regulator, the customer, the finance director who signs the invoices: each has interests, and each can act on them. Stakeholder management is the deliberate version of what good managers do instinctively, which is to find these people early, understand what they need and fear, and talk to them in the way and at the frequency that keeps their support or at least their acquiescence.
| Power to affect the project | Interest in the outcome | How to engage |
|---|---|---|
| High | High | Manage closely: regular, personal, two-way. These are the people who decide whether it succeeds. |
| High | Low | Keep satisfied: brief them enough that they never feel surprised, and no more. |
| Low | High | Keep informed: they care and will talk; make sure what they say is accurate. |
| Low | Low | Monitor: check occasionally that neither axis has changed. |
The grid is a first sort, not a verdict, because positions move. A department head with low interest becomes highly interested the week the project changes their reporting line; a quiet compliance officer acquires power the day an auditor asks a question. The map is revisited at every stage boundary and whenever the project's scope or organisation changes, and the people on it are engaged according to where they now sit rather than where they were drawn in month one. The certification bodies treat this as a core competence: PMI's people domain is a third of its professional exam, PRINCE2 mandates a communication management approach, and IPMA assesses engagement as a behavioural competence rather than a document.
