ERP Scope Creep: When Every User Request Gets a Yes
ERP scope creep rarely comes from one big decision. It comes from small user requests nobody weighs against a KPI. How to control it, with a real example.
Most ERP steering committees hear status updates and approve nothing. How to set one up that takes decisions, guards the scope and tracks business KPIs.
Most ERP projects have a steering committee. It meets once a month, the project manager shows a slide with mostly green dots, the partner says testing is on track, and everyone goes back to work. An hour later, nothing has been decided that was not already decided before the meeting.
Then, three months before go-live, the dots turn red all at once. The problems were there all along. They just never reached a room where someone could take a decision about them.
A steering committee is not there to be informed. It is there to decide the things the project team cannot decide on its own.
A project team can configure, test and train. It cannot do everything, because some choices belong to the business, not to the project.
If none of those topics are on the agenda, the meeting is a status update with senior people in it.
Keep it small. Five or six people is enough.
The partner should not run your steering committee. They are a party in many of the decisions, especially scope and budget. You want their view at the table, not their agenda.
The most useful change is also the simplest: every meeting starts from a short decision list, not a status report.
For each open point, the project lead writes down the question, the options, what each option costs in time and money, and a recommendation. The steering committee picks one. Someone writes down who decided what, and when.
The status still matters, but it can go in a one-page report sent the day before. If people have read it, the meeting does not need to repeat it.
Project milestones tell you whether the project is moving. They do not tell you whether the business will be better off when it lands.
Before the project starts, agree three to five business KPIs the new system has to protect or improve. Think of orders shipped per day, invoices matched automatically, days to close the month, or the time it takes to answer a customer. Put them on every steering committee agenda, and check them again in the test phase with real volumes.
Ben Van Aken has seen an ERP upgrade where the warehouse ended up shipping fewer packages a day, with more people on the floor than before. Nobody planned that. It happened because user requests were approved one at a time, each reasonable on its own, and nobody kept asking what they did to the numbers the business actually runs on. A steering committee that looks at those numbers every month would have caught it long before go-live.
Scope creep rarely arrives as one big change. It arrives as twenty small ones that each sound fair. The steering committee is where the total becomes visible.
Ask the project lead to keep a running list of every change request with its status, effort and the business reason behind it. Review the total at every meeting. Saying "not in this phase" is a decision too, and it is much easier to say it in month two than in month eight.
Inside a company, it is hard to tell a director that their request does not make the cut, or that their department is the one holding up the project. An independent project lead or business analyst has no department to protect. They can ask why, question every step and hold everyone, including the partner, to what was agreed, without it becoming personal.
That is a large part of Ben's role as project lead: keeping the steering committee focused on decisions and on the KPIs that matter, so problems reach the table while they are still cheap to fix.
Before your next steering committee, check:
If the answer to most of these is no, the project is still running. It is just running without anyone steering it.
ERP Scope Creep: When Every User Request Gets a Yes
KEEP READING
ERP scope creep rarely comes from one big decision. It comes from small user requests nobody weighs against a KPI. How to control it, with a real example.
The licence and the partner quote are the easy part of an ERP project budget. What overruns is your own people’s time, the data, the testing and the months after go-live. Put them in the 2027 budget as named lines.
Most SMEs that start an ERP or CRM project ask whether to sign with an implementation partner or bring in an independent consultant. The two roles do different jobs, and the projects that struggle usually expected one of them to do both.
Book a free discovery call and we will look at your steering setup together.
Currently accepting new engagements, starting now and into 2027.
Comments
Loading comments…