Who should lead an ERP implementation? A programme manager employed by the client, accountable to a named executive sponsor, with a design authority owning the solution and the system integrator leading delivery of the work it was contracted for. The integrator should not lead the whole programme, however good it is.
That answer surprises some executives. They are paying a large firm that has done this many times, so why not let it run the show? I have run programmes from the client side, and I have watched both models. When the integrator leads everything, the programme quietly starts to serve the contract rather than the business. Nobody intends it. It is simply where the incentives point.
Who should lead an ERP implementation: four roles, not one
Leadership on an ERP programme is shared, but each role must be clear. Confusion between them is where decisions stall.
- Executive sponsor. Owns the business case and the money. Makes the calls that cross departments, and removes blockers the programme cannot remove itself.
- Client-side programme manager. Runs the whole programme day to day: plan, budget, risks, people, vendors and reporting. Accountable to the sponsor.
- Design authority. A small group, usually led by a solution architect, that approves design decisions and protects the standard solution from drift.
- System integrator lead. Delivers the integrator's scope, manages its consultants and raises risks early. Accountable to the client programme manager.
The sponsor usually chairs the steering committee. If you are setting one up, read steering committee roles and decisions for what it should and should not decide.
Client-side programme manager vs the system integrator
The integrator brings method, product knowledge and people who have configured the system before. That is valuable. But the integrator also has a commercial interest in the scope, the timeline and the change requests. The client programme manager has only one interest: the business outcome.
Client-side programme manager
- Owns the whole plan, including business and data work
- Answers to the sponsor and the business case
- Manages every vendor, not just one
- Decides when a change request is justified
- Stays after go-live and lives with the result
System integrator lead
- Owns delivery of the contracted scope
- Answers to the client and to its own firm
- Manages its own consultants
- Raises change requests when scope moves
- Leaves when the contract ends
Much of the work that sinks ERP programmes sits outside the integrator's contract anyway. Data clean-up, business readiness, testing by key users and decisions on process change are client work. Someone on the client side has to own them, and that person needs authority across all of them.
The design authority: who says yes to the solution
Every ERP programme faces hundreds of design choices. Should we keep this approval step? Do we need this custom report? Without a design authority, those choices get made in workshops by whoever argues hardest, and the solution drifts away from the standard product.
A good design authority meets weekly, records every decision with its reason, and escalates only the choices that change cost, scope or timeline. It keeps the programme manager free to run the programme rather than referee design debates. It also needs a firm link to change control: a decision that adds scope becomes a change request, with its cost, before anyone builds it.
Which is better: program manager or project manager?
Neither is better. They are different jobs. A project manager delivers a defined piece of work to time, cost and quality. A programme manager coordinates several related projects, such as finance, supply chain, data, integration and change, so that together they deliver the benefit the business paid for.
An ERP implementation is almost always a programme. It needs a programme manager at the top, with project or workstream leads underneath. Putting a single project manager in charge of a multi-workstream ERP rollout usually means the joins between workstreams go unmanaged, and that is where cutover and data problems hide.
What makes a program manager successful?
In my experience the best client-side programme managers are not the most technical people in the room. They are the people others trust to tell the truth early.
Signs of a strong ERP programme manager
- Reports bad news to the sponsor the week it is known
- Holds every vendor to the same plan and the same standard
- Knows the business processes well enough to challenge a design
- Keeps one integrated plan, not a pile of vendor plans
- Makes decisions visible: who decided, when and why
- Protects the budget and knows the forecast at completion
- Builds trust with the business users who must adopt the system
None of these depend on having configured the software. They depend on judgement, honesty and authority. Give the programme manager real authority, a direct line to the sponsor, and enough time on the programme to use both.
How to set up ERP leadership in the first month
- Name the sponsor
One senior person who owns the business case and the budget, not a committee.
- Appoint the client programme manager
Full time, with authority over all vendors and workstreams.
- Form the design authority
A lead architect plus process owners, with a written rule for what they decide and what they escalate.
- Fix the integrator's role in the contract
Delivery of its scope, reporting into the client's integrated plan.
- Start the steering committee
Monthly, chaired by the sponsor, with decisions and actions recorded.
Getting this right early also protects your timeline. For realistic durations by phase, see how long an ERP implementation takes.
How ProjectCAPEX supports the client-side lead
ProjectCAPEX is built for the client-side programme manager. You keep one plan, the RAID log, change requests, quality gates, meetings and a decisions register in one place, alongside budget versus actual and the forecast at completion. Sponsors approve from their own approvals inbox, so decisions do not wait for the next meeting. Its AI agents can draft updates for you, but they only propose; a person approves. Explore the demo or create your workspace.