← All articles
ControlStakeholder management and communication

Trust is built in the ordinary weeks

Stakeholder management sounds formal. For me it comes down to four habits: frequent syncs, trust, clear communication and everything written down.

Ionut Ilasi3 min read

Stakeholder management sounds like a formal discipline. In practice it comes down to four habits: talking often, building trust, speaking clearly and writing everything down.

Frequent syncs

I prefer short, frequent syncs to long, rare ones. A short call every week costs little, and it means that nothing the client or the team hears from me is new. Problems come up while they are small, and the people involved already know me when a difficult conversation arrives.

Frequent syncs are also for listening. I try to ask what worries the other person before I give my own update, because the first minutes of a call often show what the next risk will be.

Trust comes before the difficult news

Trust is built in ordinary weeks, by doing what I said I would do and by telling the truth about small things. It is what lets me bring bad news, such as a red status or a late delivery, and have it discussed as a problem to solve rather than a case to defend. I cannot build that trust at the moment I need it.

Clear, articulate, documented

I try to say things in a way that cannot be read two ways: what happened, what it means, what I propose and what I need from the listener. Then I write it down.

Everything goes into Confluence: decisions, assumptions, meeting notes and status. I do this for transparency, not for self-protection. Anyone who joins later, on either side, can read how we got here without asking me.

Writing also forces me to be clear. If I cannot put a decision in three lines, I have not understood it well enough to ask anyone to agree to it. Clear writing is a form of respect for the reader.

Different stakeholders need different things from me. A sponsor wants the decision and its cost, a business owner wants to know what changes for their own side, and a technical lead wants the detail. I adjust the level of detail, never the facts: everyone gets the same truth.

Nobody should have to ask me what was decided.

One roadmap across three countries

I led a multi-country programme through a change of ownership in one of the countries, and through the handover of programme leadership to the central team. Through both, the business owners in three countries still had to move on one roadmap, and my job was to keep them aligned.

A change of ownership or of leadership raises questions for everyone around it. In my experience the first thing people need is clarity on what stays the same and what changes, said plainly and early, before they start guessing.

What held it together was the same four habits at a larger scale: regular contact with each business owner, trust built before the hard decisions, a roadmap each country could read in its own terms, and a shared written record. When people changed, the record and the relationships stayed.

Previous articleA risk needs an owner and a trigger Next articleRun the first UAT sessions with the client

Working on something complex?

If this is how you want your next programme to be run, let's talk.