The uncomfortable truth about ERP

Enterprise Resource Planning promises efficiency, visibility and control. But across Zimbabwe and Southern Africa, ERP projects stall, overrun budgets and fail to deliver. The reason is almost never the software.

The five reasons ERP implementations fail

1. Starting without clear objectives

“Implement ERP” is not an objective. “Reduce stock take time from 3 days to half a day” is. Without specific, measurable goals, success becomes impossible to define.

2. Skipping process mapping

Before choosing software, map your current processes. Where do bottlenecks exist? Where does data get lost? If you automate a broken process, you just get a faster broken process.

3. Underestimating data migration

Moving data from spreadsheets, legacy systems and paper records into a new ERP is time-consuming and tedious. Budget 30% more time than you think you need.

4. Insufficient training

If your team does not understand the new system, they will revert to old habits. Training is not a one-time event — plan for ongoing support during the first 3 months.

5. Trying to do everything at once

Phase your implementation. Start with core modules — inventory, accounting, sales — and add complexity after the foundation is stable.

How to succeed

Define clear success metrics before starting. Invest in process mapping. Choose a partner who understands your business, not just the software. And give your team the training and support they need to adopt the change.

A realistic timeline

For a typical Zimbabwe SME:

  • Weeks 1–4: Process mapping and requirements. Document how work actually happens — including the workarounds everyone pretends are official process.
  • Weeks 5–8: System selection and configuration. Choose against your documented requirements, not a vendor’s demo script.
  • Weeks 9–16: Data migration and testing. Migrate clean master data — customers, products, suppliers — then test with real transactions, including the odd ones: part-payments, returns, USD and local currency mixes.
  • Weeks 17–20: Parallel run and go-live. Run old and new systems side by side for at least two weeks before cutting over.

Six months is normal. Anyone promising three weeks is selling you the demo, not the system.

Budget realities

Beyond licence costs, plan for implementation services, training hours, data cleanup and a contingency of at least 20%. If your budget only covers software licences, you are not ready to start. Decide upfront how foreign vendor payments will be handled too — payment friction has derailed more than one project midway.

One rule above all

Appoint an internal champion. Not the most senior person — the most respected operational person. When they adopt the system, the team follows. Without a champion, even perfect software fails.

Planning an ERP project?

Blacklemur Innovations helps Zimbabwe businesses plan and implement ERP systems — from process mapping through to go-live and ongoing support.