𝐒𝐨𝐦𝐞𝐭𝐢𝐦𝐞𝐬, 𝐢𝐭’𝐬 𝐧𝐨𝐭 𝐭𝐡𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐭𝐡𝐚𝐭 𝐟𝐚𝐢𝐥𝐬; 𝐢𝐭’𝐬 𝐭𝐡𝐞 𝐩𝐞𝐨𝐩𝐥𝐞 𝐚𝐥𝐢𝐠𝐧𝐦𝐞𝐧𝐭 𝐛𝐞𝐡𝐢𝐧𝐝 𝐢𝐭.
When stakeholders aren’t clearly understood or managed, even the best ideas can fall flat.
I’ve been reading Kaosarat Ibrahim’s book for a few weeks now, and while many things have stood out, one concept I keep reflecting on is Stakeholder Analysis, not just as a tool, but as a mindset.
Whether it’s a product launch, a class project, or even opening a small café, there are always people who can influence the outcome and others who are deeply interested in the result.
And the tricky part? Those two groups aren’t always the same.
Get kehinde abdul-azeez’s stories in your inbox
Join Medium for free to get updates from this writer.
Imagine this 👇🏽
You’re building a new app, and the developer has high influence but low interest; they’ll build what you ask, but won’t use it.
The customer, on the other hand, has a high interest but little power to drive changes.
If you don’t balance both sides, you might end up with a polished product that no one actually connects with.
That’s why stakeholder mapping matters; not just for documentation, but for communication, empathy, and collaboration.
Because at the end of the day, projects succeed when people are understood, not just managed.
How do you typically identify and engage your stakeholders before a project starts?
