Stakeholder Identification and Analysis for IT Projects: Register, Power-Interest Grid and Engagement
Projects succeed or fail through people. A technically excellent system can still be judged a failure if the sponsor loses interest, a key department is never consulted or users resist the change. Stakeholder management is the discipline of identifying everyone with an interest in the project and deliberately managing their expectations and involvement. It starts in initiation and continues until closure.
Who Are Stakeholders?
A stakeholder is any person, group or organisation that can affect, be affected by, or perceives itself to be affected by the project. On an IT project this typically includes:
- Sponsor: funds the project and holds ultimate accountability for benefits.
- Customers and end users: use the result day to day.
- Project team: developers, testers, analysts, designers and infrastructure engineers.
- Functional managers: own the people and processes the project depends on.
- Operations and support: run the solution after go-live.
- Vendors and partners: supply products or services.
- Governance and compliance: security, legal, audit and regulators.
- Other project teams: whose work shares dependencies.
- Executives and steering committee: make major decisions and remove obstacles.
Be careful with the “silent” stakeholders: the help desk that will receive the calls, the finance team that will reconcile new data, the security team whose approval is mandatory. They are often forgotten until late.
Step 1: Identify Stakeholders
Use several sources: the charter and business case, organisation charts, process maps, previous project documents and interviews with the sponsor. Ask each person you meet, “Who else should I speak to?” and “Who might be unhappy about this?” Brainstorming with the team often surfaces names that documents miss.
Step 2: Analyse Them
Capture what you know in a stakeholder register: a table recording identity and role, contact details, requirements and expectations, influence, interest, attitude to the project and engagement strategy. Treat the register as sensitive; it often contains frank assessments.
The Power-Interest Grid
The most common analysis tool plots stakeholders by their power (ability to affect the project) and interest (degree of concern about the outcome).
| Quadrant | Power | Interest | Strategy | Example |
|---|---|---|---|---|
| Manage closely | High | High | Engage fully, consult on key decisions | Sponsor, head of the business unit |
| Keep satisfied | High | Low | Brief concisely, avoid surprises | CFO, chief information security officer |
| Keep informed | Low | High | Regular updates, listen to feedback | End users, help desk |
| Monitor | Low | Low | Minimal effort, watch for changes | Peripheral departments |
Other models include the power-influence grid, the influence-impact grid and the salience model, which weighs power, legitimacy and urgency. Pick the one your audience understands.
Engagement Assessment
Compare each key stakeholder’s current engagement level with the desired level on a scale such as unaware, resistant, neutral, supportive and leading. The gap tells you where to invest effort. A powerful stakeholder who is resistant when you need them supportive deserves a conversation soon.
Step 3: Plan Engagement
For each important stakeholder, decide what they need to know, how often, through which channel and who will own the relationship. Tailor the approach:
- Executives want brief, outcome-focused updates and clear decisions to make.
- Users want to see how the change affects their daily work, and to influence the design.
- Technical leads want detail and early involvement in architecture choices.
- Resistant stakeholders need listening first, and an understanding of what they stand to lose.
Feed these decisions into the communication plan; see Project Communication Management.
Step 4: Engage and Monitor
Stakeholder positions change. A supporter may become a critic after a reorganisation or a missed milestone. Review the register regularly, for example at each phase gate or monthly, and update it. Watch for warning signs: declining attendance at demos, escalations that bypass you, delayed approvals and vague answers to direct questions.
Worked Example: HR System Rollout
A company introduces a new HR platform. The register lists the HR director (high power, high interest, supportive), the CFO (high power, low interest, neutral), line managers (medium power, high interest, resistant because they fear extra admin), employees (low power, high interest, neutral) and the payroll team (medium power, high interest, concerned about accuracy). The project manager plans weekly sessions with the HR director, a short monthly briefing with the CFO, hands-on workshops for line managers to design their approval screens and early parallel payroll runs with the payroll team. Because the resistant managers were invited to shape the design, adoption was far smoother than a mandated rollout would have been.
Dealing With Difficult Stakeholders
- Understand the concern behind the behaviour: fear, lack of information, competing priorities.
- Meet privately rather than confronting in a group.
- Find shared goals and acknowledge valid points.
- Agree specific actions and follow up.
- Escalate through the sponsor only after direct efforts have failed.
Also see Stakeholder Management for Scrum for an Agile perspective.
Common Mistakes
- Doing the analysis once at kick-off and never updating it.
- Treating all stakeholders the same, drowning some in detail and starving others.
- Ignoring low-power, high-interest groups such as end users, then facing resistance at go-live.
- Recording the register but never acting on it.
- Stakeholders include anyone affected by, or able to affect, the project.
- A register plus a power-interest grid gives a practical starting point.
- Compare current and desired engagement to focus effort.
- Review stakeholders regularly; their positions change.