Name the person who could cancel this program next Tuesday without asking anyone. If the name takes more than three seconds, you do not have a sponsor.
An electricity distribution business is eighteen months into a grid modernisation program. The steering committee meets monthly and is well attended. The program has an executive sponsor: the Chief Operating Officer, whose name appears on the charter, who opens the annual program update, and who is unfailingly supportive.
In month nineteen the program needs a decision. A core assumption about metering interoperability has failed, and the sensible response is to stop two of five workstreams and redirect the funding. The question goes to the sponsor. He agrees it looks right, and says he will raise it with the Chief Executive and the investment committee, since a change of that size is not his to make.
At that moment everyone in the room learns something they should have known on day one. The program has an endorser. It does not have a sponsor.
The Strategic Context
Sponsorship is the most under-specified role in enterprise governance. Organisations that would never leave a financial delegation ambiguous — who may approve what, to what limit, under what conditions — routinely appoint programme sponsors with no statement of what the appointee is actually empowered to do.
The teaching literature on project management is, on this point, more precise than most corporate practice. One formulation defines the sponsor as the lowest level in the organisation with the authority to start and stop the project, explicitly aligned to the organisation's delegated authorities policy, and as the first point of escalation. Read carefully, that definition is doing two things at once. It ties sponsorship to a delegation instrument rather than to seniority. And it identifies the defining power as the power to stop.
A second strand, from the practitioner literature, adds the other half. Manage Projects Successfully (Bloomsbury Business Library, 2007) describes the sponsor as the individual or organisation for whom the project is undertaken — the primary risk-taker, and usually the party financing it. Not the most interested stakeholder. The one carrying the exposure. That distinction — between parties who hold attention and parties who hold consequence — runs through the whole of stakeholder analysis, and is developed in [Related article: Your Stakeholder Map Measures Attention, Not Exposure].
Put together, sponsorship is an office defined by two properties: delegated authority sufficient to start and stop, and ownership of the risk if it goes wrong. Everything else attached to the role — chairing the steering committee, opening the town hall, championing the change — is decoration on those two.
What Leaders Commonly Misread
The first misreading is that sponsorship is a level. Most organisations appoint the most senior person plausibly connected to the work, on the theory that seniority confers weight. But seniority and delegation are different instruments. A director with a $50 million approval limit is a better sponsor for a $30 million program than an executive with a $10 million limit and a bigger office, because the director can actually decide. Appointing upward for symbolic weight produces exactly the failure in the opening example: an appointee whose authority does not encompass the decisions the program will need.
The teaching formulation's phrase — the lowest level with authority to start and stop — is counterintuitive and correct. Sponsorship should be positioned as close to the work as the delegation allows, not as far up as the org chart permits.
The second misreading is that enthusiasm is a qualification. Sponsors are frequently chosen because they want the program to succeed. This is nearly the opposite of the requirement. The office exists to make continuation decisions, and a sponsor who cannot conceive of stopping is structurally unable to perform its central function. The right disposition is ownership, not advocacy — someone who will carry the consequence either way.
The third misreading is that sponsorship is a relationship. A great deal of published advice treats the sponsor as a stakeholder to be managed: consulted early, kept informed, brought on side. That advice is not wrong, but it describes the delivery leader's tactics rather than the organisation's design. An office is not a relationship. It has a holder, a delegation, a set of obligations and a record.
There is a related and genuinely serious problem — that delivery roles routinely carry accountability without commensurate authority — which is a different argument with a different remedy, and is treated in [Related article: Accountability Without Authority: How Organisations Design Delivery Leadership to Fail]. The question here is narrower: whether the sponsoring office is filled at all, and at what level.
Reframing the Issue
The reframing is to treat sponsorship as a delegation decision rather than an appointment.
That change alone resolves most of the ambiguity. A delegation decision has a defined form: this person may commit up to this amount, may approve changes within these bounds, may cease the activity, and is answerable for the outcome. Organisations already know how to write this; they do it for procurement, for capital expenditure, for treasury. They simply do not do it for programs.
The consequence of not doing it is that the authority to stop diffuses upward into a committee, and a committee is an unreliable place to keep a stop decision. Committees can withhold approval, which is not the same thing. Stopping requires someone willing to own having stopped — to absorb the sunk cost, tell the affected teams, and defend the decision afterwards. That is an individual act, and it needs an individual office.
Strategic Analysis
What the office actually obliges
The practitioner literature sets out a specific and demanding list. The sponsor approves the project proposal; assists in creating and then signs off the brief and preliminary plan; ensures that key business resources are available in accordance with the plan; supports the manager in resolving risks and issues; reviews the project regularly; formally accepts the deliverables; approves all changes to scope, schedule and budget; and ensures the organisation recognises what the project achieved.
Three of these are worth pausing on, because they are the ones most often unmet in practice.
Ensures key business resources are available in accordance with the plan. This is not encouragement. It is a commitment that the operational parts of the business will release named people at named times, and it is the obligation that most frequently fails, because the sponsor rarely controls the functions being drawn from. A sponsor who cannot make this commitment stick has not been given the office.
Formally accepts the deliverables. Acceptance is the moment the organisation takes ownership of what was built and, with it, ownership of whether the benefits arrive. Where acceptance is a signature collected at the end, benefit ownership is nobody's — a structural problem examined in [Related article: The Hidden Cost of Putting Work Into Project Form].
Ensures achievements are recognised. This looks like the softest item on the list and is among the more consequential. Recognition is how an organisation signals what it values, and a sponsor who does not deliver it teaches the next cohort of delivery leaders exactly how much the work is worth.
Note what the list also contains: authority over changes to scope, schedule and budget. Who may redefine what a program is for is a distinct governance question with its own logic, and is treated in [Related article: Drivers, Supporters and Observers: Who Is Allowed to Change What Your Program Is For]. Here it is recorded simply as one obligation of the office.
The disagreement protocol, and why it matters
The practitioner guidance on sponsor disagreement is unusually specific: if the sponsor's direction seems wrong, say so honestly and without confrontation — and if the sponsor holds their position, follow it and work to make the outcome succeed.
This deserves examination rather than automatic endorsement. As a norm it is defensible, and it is how decision rights are supposed to work: someone must be able to decide, and an organisation in which every direction can be relitigated cannot execute. But it carries a load-bearing condition — that the disagreement was genuinely heard and is recorded. Without the record, the protocol converts into something else entirely: a mechanism by which a delivery leader's accurate warning disappears, and the failure is later attributed to delivery.
The workable version is that dissent is stated, minuted, and the sponsor's decision is minuted as the sponsor's. That is not a challenge to authority. It is what makes authority accountable.
The empty office
The most common condition is not a bad sponsor. It is a vacant office with a name attached — an appointee who supports the program, attends the committee, and does not hold the delegation to stop it.
This is diagnosable in about ten minutes. Ask three questions of any program: what is the named sponsor's approval limit; does it exceed the program's remaining spend; and has the sponsor ever stopped anything. If the limit is lower than the exposure, the office is empty and the real authority sits elsewhere, unnamed and unaccountable. The governance chart is describing a structure the organisation does not have.
Decision Framework
A five-part test for any program above a material threshold.
1. The name test. One person, named, in three seconds. Not a committee, not a role, not two people jointly. If the answer is a committee, the organisation has distributed the stop decision to a body that will find it very difficult to make.
2. The delegation test. Does that person's existing financial and decision delegation encompass the program's remaining commitment? Note that what the office will actually be asked to decide is set by what binds the work, not by its budget — a reading developed in [Related article: Read the Constraints, Not the Deliverables]. If not, either raise the delegation explicitly for this program or appoint someone whose delegation already covers it.
3. The exposure test. If this program fails, whose result, budget or reputation carries the consequence? Where the answer is not the sponsor, the office has been separated from the risk, and the sponsor is adjudicating something they will not pay for.
4. The resource test. Can the sponsor commit the operational capacity the plan requires — not request it, commit it? This is the most common point of failure and the easiest to test in advance.
5. The awareness test. Does the appointee know all of the above? Ask them directly what they believe they are empowered to decide. The gap between the charter and their answer is the real governance position.
Where a program fails two or more of these, the practical remedy is rarely to find a more senior sponsor. It is to write the delegation down.
From Strategy to Execution
Immediate. Run the five tests across the current program portfolio. This is a half-day exercise and it produces a specific, actionable list: programs with no effective sponsor, programs whose sponsor lacks the delegation, and programs where the sponsor does not know what they hold. In most organisations the third category is the largest.
Medium term. Add a sponsorship schedule to the standard program charter: named individual, delegation limit, the specific decisions reserved to them, the decisions escalated above them, and their signature confirming they accept the office. This is a one-page instrument and it removes almost all of the ambiguity described in this article.
Long term. Build sponsorship as a recognised capability rather than an incidental duty. The office requires a particular skill — the willingness to stop something one has publicly supported — and organisations that never develop it end up with portfolios full of investments nobody is empowered to end. What a gate should decide once that authority exists is a related question, addressed in [Related article: What a Stage Gate Is Actually For].
Signals to Monitor
- Decisions travelling above the sponsor. Track how often a program decision is referred upward. A rising rate means the delegation is set below the decisions the program actually generates.
- Sponsor attendance and substitution. Persistent delegation of steering attendance to a nominee indicates the office is not being held, whatever the charter says.
- Time from problem identification to sponsor decision. Lengthening intervals usually mean the sponsor is consulting upward before deciding, which is the opening example in slow motion.
- Programs that have never had a stop discussion. A portfolio in which no sponsor has ever seriously considered stopping is not a portfolio of well-chosen investments. It is a portfolio without functioning sponsorship.
- Resource commitments that do not materialise. Where named people are not released as agreed, the sponsor's authority over the operational functions is nominal, and the plan rests on a commitment nobody can honour.
Questions for the Leadership Team
- For each of our five largest programs, can we name the individual who could stop it, and does their delegation actually cover the remaining spend?
- When did a sponsor in this organisation last stop a program — and what happened to that person afterwards?
- Where a sponsor cannot commit the operational resources their program requires, who can, and why are they not the sponsor?
- Do our sponsors know what they are empowered to decide, or would their answer differ from the charter?
- Is a delivery leader's recorded disagreement with a sponsor visible anywhere in our governance record, or does it disappear at the point of decision?
- If we applied the five tests today, how many of our programs would fail two or more?
Closing Perspective
Governance failures are usually described as failures of process — a gate that was not held, a report that was not read, a risk that was not escalated. Many of them are simpler than that. They are failures of office: a decision that needed an owner, and did not have one, because the person named as owner had been given the title and not the authority.
Sponsorship is the clearest case. It is not a mark of executive interest, not a reward for seniority, and not a relationship the delivery leader is expected to cultivate. It is a delegated authority to commit and to stop, held by a named individual who carries the consequence either way, and it is either present or it is not.
Most organisations could establish which of those two conditions they are in before lunch. Rather fewer would like the answer.
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.