On most ERP projects, the sponsor is appointed on launch day, shows up at the kick-off meeting, then all but disappears until go-live. Nobody blames them: their calendar is full, the project team is competent, and the project is “moving along”. Until the day a decision only the sponsor could make sits unresolved for three weeks, and the schedule slips with no one able to say why.
This article is for CEOs, CFOs and executive committee members who sponsor an ERP, and for the CIOs who have to coach them. It does not cover rescuing a project that is already in trouble (see our 5-step ERP project rescue plan). It covers what to do before the project derails: which role to play, how much time to give it, and which decisions cannot be delegated.
Why an absent sponsor is a recurring cause of failure
The topic has been documented for years by the PMI. In its 2015 Pulse of the Profession study, reported by Raconteur, the PMI found that in organisations where actively engaged executive sponsors oversee more than 80% of projects, 77% of projects meet their original goals, against 46% elsewhere.
Those figures cover projects in general, not ERP projects alone. But the mechanism is the same, and it is even stronger with an ERP, because an ERP touches finance, procurement, production, sales and HR all at once. No project manager and no CIO has the authority to arbitrate between those functions. Only a member of the executive team can.
In practice, an absent sponsor produces three effects:
- Decisions stall. Every scope or priority conflict escalates, waits, then gets resolved by default (often by adding an exception instead of making a decision).
- The business does not feel involved. If leadership does not attend steering meetings, department heads release their best people last, or not at all.
- The integrator negotiates with the project manager rather than the decision-maker, which shifts the balance of power on change orders.
Sponsor, project manager, steering committee: who does what
The detailed split of responsibilities is in our RACI matrix for the ERP project team. We will not repeat it here. Just keep the dividing line in mind:
- The project manager runs execution: schedule, deliverables, operational risks, coordination with the integrator.
- The steering committee (see the weekly template, in French) is where decisions are prepared, recorded and made visible.
- The sponsor is accountable for business results to the board and holds the authority to settle what neither the project manager nor the committee can settle alone.
A simple rule checks that everyone stays in their lane: if a decision commits budget, organisation or the relationship between two departments, it goes up to the sponsor. Otherwise, it is handled lower down.
The 6 decisions a sponsor cannot delegate
For each one, here is a typical situation, the wrong reaction and the right one.
1. Scope and budget trade-offs
Typical situation. In a design workshop, the sales department asks for a complex discount-management module that is not in the contract. The integrator’s estimate: several dozen days.
Wrong reaction. “Talk to the project manager.” The request is accepted out of fatigue, the budget swells, and nothing is removed in return.
Right reaction. The sponsor sets the rule: any scope addition must come with an equivalent removal of value, or with an extra budget explicitly approved by them. They decide in committee, with the estimate in front of them, and the decision is recorded.
2. Standard versus custom development
Typical situation. A shop-floor manager wants to keep a legacy process for releasing production orders that standard ERP does not cover identically.
Wrong reaction. The sponsor lets the business and the integrator negotiate. Customisations pile up, and with them maintenance debt and the cost of every version upgrade.
Right reaction. The sponsor sets a starting principle: standard by default, custom by documented exception, with a business owner who accepts the maintenance cost. They personally rule on which processes are a genuine competitive advantage and which are merely habit.
3. Appointing and releasing key users
Typical situation. The key users chosen are the ones who “have a bit of time”, not the ones who know the processes best. Their managers pull them back as soon as activity picks up.
Wrong reaction. The sponsor treats it as an HR matter or an IT matter.
Right reaction. The sponsor appoints the key users personally, negotiates their availability with their managers (with a time percentage in writing), and has their workload backfilled if needed. It is the most underestimated decision: it determines the quality of user acceptance testing.
4. The go/no-go
Typical situation. Three weeks before cutover, testing reveals defects in the financial close and stock flows. The integrator claims everything will be fixed “in time”.
Wrong reaction. The sponsor sticks to the schedule because the date has been announced to the board and to the teams.
Right reaction. The sponsor defined go/no-go criteria in advance (zero blocking defects, critical flows validated by the business, fallback plan ready). On the day, they apply the criteria, not emotion. Delaying by a month costs less than a failed cutover during a period-end close.
5. Communicating to the teams
Typical situation. Rumours circulate: the ERP will eliminate jobs, impose data entry, replace the tools people have mastered.
Wrong reaction. Leaving communication to the project manager or IT, in the form of internal newsletters.
Right reaction. The sponsor speaks personally, at launch, at each major milestone and before go-live. They explain why the company is changing systems, what will change for each person and what will not. This message only carries weight if it comes from leadership. To go further, see our approach to change management in ERP projects.
6. Escalating cross-department conflicts
Typical situation. Procurement and finance cannot agree on the purchase order approval workflow: one wants flexibility, the other control. The issue returns at every committee.
Wrong reaction. The sponsor asks both parties to “find a compromise” and postpones.
Right reaction. The sponsor brings the two heads together, hears each, and decides within a short time, with a simple rule: a conflict that comes back twice in committee is arbitrated at the next session, by them.
How much time to actually commit, by phase
There is no sourced standard for sponsor time. The ranges below are rules of thumb from field experience, to be validated against company size, scope and the maturity of the project team.
| Phase | Order of magnitude (hours/month) | Nature of the investment |
|---|---|---|
| Scoping | 10 to 20 h | Objectives, scope, choice of vendor and integrator, key user appointments |
| Build (configuration, design) | 6 to 12 h | Committees, standard-versus-custom rulings, budget tracking |
| Testing | 8 to 15 h | Rulings on defects, attendance at key sessions, go/no-go preparation |
| Go-live | 15 to 25 h over the month | Cutover decision, communication, presence with the teams |
| Hypercare | 6 to 10 h | Incident follow-up, correction priorities, review |
A sponsor who cannot free up these hours should say so at scoping, and appoint a deputy sponsor with a written mandate, rather than remaining sponsor in name only.
5 warning signs that a sponsor is absent
- Steering committees meet without them, or with a representative who cannot decide anything.
- The same topics come back week after week with no decision.
- Key users are pulled back by their managers during workshops.
- The project manager rules on budget or scope issues beyond their mandate.
- Teams say they do not know why the project exists, or what it will change for them.
How to push back without conflict
The CIO or project manager has no need to reproach the sponsor. Three levers work:
- Present the cost of delay, not blame. “This pending decision blocks two work packages and costs X days of schedule.” A quantified fact is easier to discuss than a judgement.
- Prepare decisions ready to be made: context, two options, a recommendation, the impact. The sponsor decides in five minutes instead of deliberating for an hour.
- Ask for a fixed slot (30 minutes a week, before the committee) rather than broad availability. A short, regular appointment is easier to keep than a vague commitment.
The sponsor toolkit
Sample quarterly agenda
- Month 1 of the quarter: review of the project’s business objectives, validation of budget spent and remaining, key user check-in.
- Month 2: open rulings (scope, customisation), meetings with 2 or 3 business leads outside committee, communication to the teams.
- Month 3: risk review, decision on next quarter’s milestones, review with the integrator.
5 questions to ask in the steering committee
- What decision do you need from me today, and what happens if I do not make it this week?
- What have we removed from scope since the last committee, in exchange for what was added?
- Are the key users really available at the planned level?
- What are the three risks that could delay go-live, and who owns each?
- What was the last piece of end-user feedback we heard, and what did we do with it?
A minimal dashboard
Five indicators are enough:
- Budget spent and estimate to complete, compared with actual progress
- Schedule variance on the critical path
- Key user availability against plan
- Number of open blocking defects (from testing onwards)
- Decisions pending for more than seven days, with their owner
Going further
This topic takes sustained effort. Get our next practical guides on ERP project governance by subscribing to the newsletter, and download our ERP evaluation grid to put the decision-focused format described above in place this week.