FIELD GUIDEVENDOR-NEUTRALEDITION 2026
The ERP Pitfalls Guide
Seven ways ERP programmes quietly go wrong in East Africa — what each one looks like from the inside, what it costs, and the antidote we apply before a single licence is signed.
HOW TO USE THIS GUIDE
ERP rarely fails at the software layer.
It fails at sponsorship, data, scope and change — long before anyone blames the product. Read each pitfall against your own programme and mark it green, amber or red. Anything amber or red is a decision you still have time to make cheaply.
Read it honestlyScore your own programme green, amber or red. Optimism is the most expensive input in ERP.
Act while it's cheapEvery pitfall costs least before contracts are signed and data is migrated.
Keep it vendor-neutralOur advice is not tied to any vendor's licence sale, so the recommendation follows the evidence.
Seven pitfalls.
Symptom · what it costs · the antidote.
01HIGH RISK
Weak executive sponsorship
SYMPTOMThe programme is delegated to IT or finance. Steering meetings slip, decisions wait for a monthly slot.
WHAT IT COSTSCross-departmental decisions stall; the implementer bills for waiting.
THE ANTIDOTEName one accountable executive sponsor with authority to settle process disputes, and hold a fortnightly steering committee with a live risk register.
02HIGH RISK
Dirty data going in
SYMPTOMCustomer, supplier and stock masters live in several spreadsheets with different codes and duplicates.
WHAT IT COSTSMessy data migrates faster than clean data — and reappears as distrust in every report after go-live.
THE ANTIDOTECleanse and de-duplicate masters before migration, with named data owners per domain and a signed-off cut-off.
03COMMON
Scope creep
SYMPTOMEvery department asks for “just one more report”, and each is individually reasonable.
WHAT IT COSTSTimelines stretch, change requests multiply, and the original business case quietly disappears.
THE ANTIDOTEFreeze a phase-one scope tied to the business case; everything else goes to a phase-two backlog with its own approval.
04HIGH RISK
Vendor finger-pointing
SYMPTOMSoftware vendor, implementer and internal team each explain why the delay belongs to someone else.
WHAT IT COSTSNobody owns the outcome, and the client absorbs both the delay and the rework.
THE ANTIDOTEA vendor-neutral governance layer: one accountability matrix, contractual milestones, and an advisor with no licence revenue at stake.
05COMMON
Unrealistic timelines
SYMPTOMA go-live date is chosen for a board meeting or a financial year, then work is compressed to fit it.
WHAT IT COSTSCompressed delivery multiplies every other risk — testing, training and data all get cut first.
THE ANTIDOTEPlan backwards from a tested cut-over, not forwards from a wish, and protect UAT and training as non-negotiable.
06HIGH RISK
Insufficient change management
SYMPTOMTraining happens the week before go-live; workarounds and parallel spreadsheets appear the week after.
WHAT IT COSTSThe system goes live, but the people do not — adoption stalls and benefits never land.
THE ANTIDOTERole-based training, super-users per department, and adoption measured as a KPI for 90 days after go-live.
07SILENT
No post-go-live audit
SYMPTOMThe project closes at go-live. Nobody revisits whether the promised benefits actually arrived.
WHAT IT COSTSLicences and support renew for years on a business case nobody ever validated.
THE ANTIDOTEAudit benefits realisation at three and six months against the original case, and act on the gap.
TWO-MINUTE SELF-CHECK
Score it with a consultant→
Eight statements. Count the ones you can say honestly.
Six or more and you are ready to talk to vendors. Four or five and you need a scoping exercise first. Three or fewer and choosing software now is the most expensive thing you could do.
0/ 8
YOUR SCORE✓One named executive sponsor owns this programme, not a committee.
✓We can state the business case in numbers, not adjectives.
✓Our customer, supplier and stock masters have named owners.
✓We know which processes we will change and which we will keep.
✓Phase-one scope is written down and frozen.
✓The go-live date came from a plan, not from a board calendar.
✓Budget includes data cleansing, training and post-go-live support.
✓We have agreed how we will measure benefits after go-live.
Six stages that remove the pitfalls.
Our ERP consulting sequence exists because every stage closes one of the seven pitfalls above before it can cost money.
STAGE 01Audit firstWe audit current systems, processes, data and risks before discussing vendors.Closes: dirty data
STAGE 02Readiness assessmentWe score people, process, data, sponsorship, budget and governance honestly.Closes: weak sponsorship
STAGE 03Gap analysisWe separate what the business truly needs from what is merely nice to have.Closes: scope creep
STAGE 04Vendor selectionStructured RFP, demo scoring, reference checks and contract review.Closes: finger-pointing
STAGE 05Implementation governanceSteering committee, risk register, implementer accountability and change control.Closes: unrealistic timelines
STAGE 06Post-go-live auditThree and six months after go-live, we review benefits realisation against the business case.Closes: no audit
Have a look at your own programme against these seven. Then let's talk about the amber ones.
A scoping session is vendor-neutral, evidence-first and costs you nothing but an honest hour.