The sponsor who showed up and the one who didn't.

Programme sponsorship is one of those roles that almost everyone agrees is critical and almost no one defines clearly enough to hold anyone accountable to.

Ask ten senior leaders what a programme sponsor is responsible for and you will get ten broadly similar answers. Oversight. Strategic alignment. Removing blockers. Stakeholder engagement. The answers are not wrong. They are just abstract enough to accommodate almost any level of actual involvement -- including very little.

What I have observed, across programmes of varying scale and complexity, is that the difference between a programme that delivers its intended outcomes and one that doesn't often comes down to a single variable: whether the sponsor was genuinely active or quietly passive.

What passive sponsorship looks like

Passive sponsorship rarely looks like disengagement. That is what makes it difficult to name.

The passive sponsor attends steering committees. They read the weekly report. They are available if needed. They approved the business case and they expect to be told if something goes seriously wrong.

What they don't do is initiate. They don't ask the uncomfortable questions. They don't proactively engage their peers to maintain organisational support for the programme. They don't treat unblocking as a personal responsibility. And they don't maintain a living connection between the programme's progress and the strategic outcome it was designed to produce.

From the outside, this can look like appropriate delegation. From inside the programme, it looks like something else entirely -- a figurehead rather than a force.

The cost of the comfort blanket

When sponsorship is passive, the programme team compensates. They manage upward carefully, presenting progress in terms designed to maintain confidence rather than surface difficulty. The weekly report becomes a comfort blanket -- for the sponsor as much as the team.

Problems that need senior intervention sit in the risk register longer than they should. Escalations that would benefit from executive visibility don't get made because the channel for making them doesn't feel genuinely open. Decisions that require cross-functional authority get delayed because the sponsor isn't actively present enough to convene the right people quickly.

None of this is dramatic. It accumulates quietly, in slipped timelines, in unresolved dependencies and in a delivery team that learns to work around the absence of active sponsorship rather than through it.

What the sponsor who showed up actually did

The most effective programme sponsors I have observed share a set of behaviours that are specific and learnable.

They treated their role as active, not reactive. They didn't wait to be told about problems -- they asked about them directly and created the conditions in which the programme team felt safe to surface them early.

They maintained peer relationships across the organisation throughout the programme, not just at mobilisation. When organisational resistance emerged -- and it always does -- they addressed it personally rather than leaving it to the programme team to manage upward.

They understood the difference between the programme's delivery status and its outcome trajectory, and they asked about both. A green RAG status did not satisfy them if the outcome question remained unanswered.

And they treated unblocking as one of their primary contributions. Not a favour to the programme team. A core part of the job.

The question of accountability

There is a structural issue underneath all of this. Programme sponsorship is rarely a role with formal accountability attached to it. Sponsors are not typically measured on programme outcomes. They are not performance-reviewed against delivery success. The role sits alongside their other responsibilities, which are many, and it tends to get the attention that's left over rather than the attention it requires.

This will not change overnight. But senior leaders who understand this dynamic can choose to hold themselves to a higher standard than the role formally requires -- because they understand that the programme's outcome is, in the most direct sense, their outcome too.

The system will do what it is designed to do. Whether the organisation gets there depends significantly on whether the person at the top of the programme is genuinely in the room or merely present in it.

If this is a challenge your organisation is facing, I may be able to help. hello@medasi.com