Engagement Isn’t a Communication Problem. It’s an Exchange Problem.
Every technology program has the same complaint eventually: business stakeholders won’t engage. Steering committees where the sponsor skims their phone. Status meetings attended by a deputy who wasn’t in the room when the decision was made. Sign-offs that take three weeks to chase down what should take three days. The usual response is to treat this as a communication failure — tighten the cadence, simplify the update, chase harder. It rarely works, because engagement was never a communication problem. It’s an exchange problem.
People engage when there’s something in it for them. Not money, not necessarily even recognition in the way we usually mean it — a stake. Something that’s theirs to hold, defend, or be accountable for. A project that only asks for a stakeholder’s time and attention, without ever handing them anything back, is asking them to invest in something they don’t own. Most people, quite reasonably, decline to invest deeply in things they don’t own.
So the real question isn’t how to get stakeholders to show up. It’s what you’re actually offering them in exchange for showing up. Naming someone publicly as a key stakeholder or product owner is one currency — it converts a passive attendee into someone whose name is attached to the outcome in a room full of peers. A formal role, System Owner rather than “consulted party,” is another — a title carries weight even before the person has done anything to earn it, because it signals the organisation has already decided they matter. Authority to sign off on deliverables is a third, and probably the sharpest one — nothing manufactures ownership faster than being the person whose signature is genuinely required before work proceeds. Visibility is a fourth: making someone the face of the project, not just a name on a RACI chart buried in an appendix. And a public voice — being the one who speaks in the steering committee or the project forum instead of being spoken about — is a fifth.
None of these cost the project anything it wasn’t already going to spend. The role exists whether or not anyone is named to it. The sign-off happens whether or not it’s framed as authority. The difference is entirely in whether the stakeholder experiences these as things done to them or things given to them.
This is why engagement plans that read like communication plans keep failing. A communication plan asks: how do we get information to them, and how often. An exchange asks: what do they walk away holding that they didn’t have before. The first produces attendance. The second produces partnership — formal enough to survive when the project gets hard, and authentic enough that nobody’s pretending it’s something it isn’t.
So before the next steering committee gets rescheduled because “engagement is low,” it might be worth asking a sharper question: what, exactly, have we given this stakeholder that’s theirs to hold — and if the honest answer is nothing, whose problem is the disengagement really?
