The Stakeholder Map

Every project has more people involved than the people doing the work. The people who care about the outcome are called stakeholders, and pretending they do not exist is the fastest way to get a perfectly executed project that nobody is happy with. The mehndi can be flawless, and chacha can still be furious because nobody told him the timing changed. The fix is to draw a stakeholder map before you start, not after he stops talking to you.

A stakeholder map has two columns. Column one: their name. Column two: what they want from this project, in their own words, not yours. Ammi might want, no embarrassment in front of relatives. Chacha might want, his side of the family seated in the front row. Your friend might want, to actually have fun for once. Your school principal might want, no complaints reaching her on Monday. Each is a different goal. None of them is wrong.

Now sort them. Put a small mark next to two kinds of people. The ones with high power, who can stop the project if they get upset. And the ones with high interest, who care a lot even if they cannot stop you. Principal is high power, low interest. The captains are low power, high interest. Ammi at home is medium power, very high interest. The matrix matters because it tells you who you owe a phone call to versus who you owe a quick text.

Today's habit. For your next real project, before you do any work, draw the map. Write 6 to 10 names. Next to each, one line on what they actually want. Star the high power ones. Underline the high interest ones. Now you know who needs a phone call before launch, who needs a WhatsApp during, and who just needs a thank you after. Most project failures are not skill failures. They are stakeholder failures with skill clothes on.