Stakeholder Management

Almost no growth project succeeds without help from another team. Without that help it stalls in predictable ways. Product never schedules the integration. A budget owner cuts spend nobody explained. A client finds out about a delay from someone else. Updates sent before a problem escalates turn people into allies. Turning up only when something is needed feels transactional.

Mapping stakeholders early also brings disagreement into the open while it is still cheap to settle, before a campaign has been built on a shaky assumption.

• List who needs to hear from you and set a rhythm: weekly for a manager, monthly for an executive, as needed for people whose work depends on yours.
• Hold the rhythm. A note that slips once teaches people to stop expecting it.
• Start each update with a one-line headline and the key number, then link to detail for anyone who wants it.
• Use a short recorded walkthrough when something is easier to show than to write.
• Keep the leadership version to a page: trends, main risks and the decision being asked for.
• Answer every question within a day, even if the full answer takes longer.

A stakeholder is anyone with a stake in the outcome: the manager who approves the budget, the product team whose time a project needs, the finance lead who watches costs, the client who pays. Stakeholder management is the routine of finding out who these people are, what each one cares about and how often each wants to hear from you.

It is not politics or flattery. It is regular, honest communication, planned in advance.

• Only communicating when you need something. People treat a request from someone who has been silent for months as a favour to repay, not as part of a shared project.
• Treating everyone the same. The CEO, a peer team and a client need different detail at different rhythms. Sending everyone everything means your updates get skipped.
• Hiding bad news. A problem reported late looks like a cover-up. Report it early with a proposed next step.
• Updates with no ask. If a stakeholder has to decide something, say so clearly and give a date, otherwise the update is read and nothing happens.
• Mapping once and never again. People change roles and priorities. Review the list each quarter.