Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Project Management for System Implementations: Avoiding the Scope Trap - Kemlat Insights
Kemlat2026-10-21T16:52:41+03:00
All insightsاقرأ بالعربية
Enterprise Systems

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.

10 November 20265 min read
Share
Project Management for System Implementations: Avoiding the Scope Trap - Kemlat Insights

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.

  1. 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.
  2. 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.
  3. Rank requirements before the build. Sort them into must-have, should-have and later. Go-live depends only on the must-haves.
  4. 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.
  5. 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:

QuestionWhy 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.

Practical tip: ask the vendor to price every change request in writing before approval, even small ones. Seeing that five “small” changes add up to three extra weeks changes the conversation quickly.

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.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Operations Transformation

Explore our services

Related insights

Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights
Enterprise Systems

Budgeting for an ERP Project: The Costs People Forget

ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add…

14 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.