Project Management for System Implementations: Avoiding the Scope Trap
System projects grow one reasonable request at a time. A clear structure makes it possible to say "not now" without starting an argument.

Every system implementation starts with a scope, and very few finish with it. Requests arrive one at a time, each sounds reasonable, and each is agreed in a meeting without anyone adding up the cost. Six months later the project is late, over budget and still missing the basics it was meant to deliver.
How scope creep actually happens
Scope usually grows through small, polite additions that nobody wants to refuse, one meeting at a time. The usual sources are familiar:
- Requirements that were never written down. If the original scope said “inventory module” without listing what it must do, every department fills the gap with its own expectations.
- Recreating the old system. Users ask for every report and screen they had before, including the ones they opened twice a year.
- Senior requests in corridors. A director mentions a nice-to-have to the developer directly, and it gets built without passing through anyone.
- Customisation instead of process change. Rather than adjusting a local habit, the team asks the vendor to change the software to match it.
- Discoveries during testing. Real data reveals cases nobody mentioned, such as a customer with three billing addresses or a product sold in two units of measure.
Some of these additions are genuinely needed. The trouble starts when changes are accepted without a decision about time, cost and priority.
A scenario: a new system at a factory in Sahab
Consider a mid-sized plastics manufacturer in Sahab replacing an old accounting package and a set of production spreadsheets with an enterprise resource planning (ERP) system. The agreed first phase covers purchasing, inventory, sales and finance. Go-live is planned for the start of the financial year.
In month two, the production manager asks for machine scheduling. In month three, the sales director wants a customer portal. Quality asks for batch traceability reports in a specific format. Each request is accepted by the project coordinator, who does not feel senior enough to refuse. The vendor builds, the timeline slides, and go-live moves twice.
When the system finally launches, the core inventory setup has been rushed, stock balances are wrong in the first week, and users lose trust in the whole thing. Scheduling, a portal and traceability were all valid ideas. They simply belonged in a second phase, decided by someone with the authority to say “not now”.
Set up the project so that “not now” is possible
Most scope problems are solved before the first configuration session, through structure rather than willpower.
- Write a scope statement with exclusions. List what is in, and just as clearly what is out. “Machine scheduling is out of scope for phase one” prevents a lot of later argument.
- Appoint a sponsor with real authority. The sponsor is a senior person, often the general manager or COO (chief operating officer), who decides on priorities when departments disagree. A coordinator without authority cannot protect scope.
- Rank requirements before the build. Sort them into must-have, should-have and later. Go-live depends only on the must-haves.
- Define a single entry point for requests. Every new idea goes into one change log, whoever it comes from. The vendor agrees not to build anything that is not on it.
- Keep a phase-two list. Good ideas that are not urgent need a visible home. People accept “later” far more easily when they can see their request written down.
A simple change control routine
Change control does not need a heavy committee. For a mid-sized implementation, a short weekly review is usually enough. Each request is assessed against the same questions:
| Question | Why it matters |
|---|---|
| What problem does this solve, and for whom? | Separates real operational needs from preferences |
| Can we change the process instead of the system? | Standard features are cheaper to maintain and upgrade |
| What does it cost in days and money? | Makes the trade-off visible to the sponsor |
| Does it affect go-live? | Anything that moves the date needs a sponsor decision |
| What happens if we defer it? | Often the honest answer is “very little” |
The sponsor decides on anything that changes the date or the budget. The project manager decides on the rest. Record each decision with a line of reasoning, because in three months nobody will remember why something was approved.
Watch the signals before the timeline slips
Scope trouble shows up early if you know where to look. The change log grows faster than items are closed. Configuration workshops keep reopening decisions that were already made. Testing is shortened to protect the date. Key users from operations stop attending because they assume the IT (information technology) team is handling it. Any one of these is a reason to pause and reset priorities with the sponsor, rather than pushing on and hoping.
It also helps to separate your project manager from the vendor’s. A vendor’s project manager manages the vendor’s delivery. Someone on your side needs to manage your decisions, your data, your users and your priorities. In smaller organisations this can be a part-time internal lead supported by an independent adviser.
Finally, make the change log visible to the key users and department heads, not just the project team. When the head of sales can see that his portal request sits on the phase-two list next to the production manager’s scheduling request, the conversation becomes about priorities across the business rather than about whose voice is loudest.
Delivering the system you actually agreed to build
In a well-run implementation things still change, but every change is a decision, made by the right person, with the cost in view. That discipline starts with clear requirements and an honest picture of how the business works today, which is where our Enterprise Systems work begins. When scope is protected, phase one goes live on a stable base, users trust the data, and the phase-two list becomes a roadmap rather than a pile of disappointments.



