Inform stakeholders before they ask, not after they complain

I’s are one-way — they receive information; the cost of surprising them is always higher than the cost of telling them.

Why it works

Stakeholders who are Informed but surprised feel disrespected and excluded, even when they have no formal input rights. The psychological mechanism is expectation violation: they knew they were affected but weren’t told. Proactive, regular information updates prevent the stakeholder management crisis that comes from a well-intentioned but silent project team.

How to do it

1. For each I, agree upfront on format and cadence: email digest, dashboard link, or meeting agenda item.
2. Send updates on the agreed schedule, even when there’s nothing new — "no change" is information.
3. Never ask an I for approval; that’s a C. If they keep trying to weigh in, either promote them to C or have the authority conversation.

Evidence

Stakeholder communication research in project management consistently identifies inadequate communication as a top cause of project failure. Proactive information flow prevents stakeholder interference and builds the trust needed to let the project team execute. (observational)

The PMI report is an industry survey, not a controlled study. The directional finding — that poor communication drives project failure — is consistent across multiple sources.

Sources

• PMI (2021). Pulse of the Profession: Beyond Agility (Project Management Institute). Reports communication failure as a top driver of project underperformance.

Common mistake

Treating I as "optional" and only informing people when asked — which means the first communication happens when a stakeholder is already frustrated.