Stakeholder identification

A stakeholder is anyone who can affect or be affected by the project. This includes people you'd expect (sponsor, team, customers) and people you might not (the compliance officer who needs to approve the final product, the facilities manager who needs to allocate desk space for the implementation team, the IT security team that will audit whatever you build).

The most dangerous stakeholder is the one you didn't identify. They don't show up to meetings because they weren't invited. They don't raise concerns because they don't know the project exists. And then one day, three weeks before go-live, they say 'I need to review this before it launches, and the review window is six weeks.' That conversation is not their fault - it's yours, for not finding them earlier.

A practical exercise: look at your project scope and ask 'who would be affected if this project succeeded or failed dramatically?' Then ask 'who could stop this project if they wanted to?' Then ask 'who would complain they weren't consulted if they saw the finished product?' The answers to these three questions form the core of your stakeholder list.

Some stakeholders are hidden by design - they don't need to engage until a specific trigger point. The legal team doesn't need to be in your weekly standup, but they need to be on your radar for when the contract review phase hits. The procurement team doesn't care about your project until you need to buy something that exceeds their threshold.

Others are hidden because they don't know they're stakeholders. The operations team that will inherit your system after launch. The training team that will need to build onboarding materials. The support desk that will field calls when users can't figure out the new interface. Find them early, brief them early, and they'll be allies. Find them on launch day and they'll be obstacles.

Technique: the stakeholder snowball. Start with the obvious stakeholders and ask each one 'who else should I be talking to?' Each conversation adds names. After three rounds, you'll have a list that's 80% complete. The remaining 20% will introduce themselves - usually by email, usually with a tone that suggests they should have been consulted earlier.

Stakeholders are anyone who can affect or be affected by your project. The ones you miss are the ones who will cause the most problems. Use the snowball technique - ask every stakeholder 'who else?' - to build your list. Document everything in a stakeholder register, not a mental list that gets emptier as the project gets more stressful.

Next: the power/interest grid - a tool for deciding which stakeholders get your attention and which ones can survive on email updates without you feeling guilty about it.