Another ERP implementation struggle came from a client sharing their experiences with another 6-figure ERP system. Issues included excessive data entry, repeated data migration failures, and unskilled personnel.

Here's the full story:

ERP Project : Sharing Lessons Learned 🚨
Name : Precision Engineering Company ERP System
Case : TPERP-JRR-FTC

In details (TLDR)

1. Another 6-figure ERP system that cannot go live
2. Too many data entry for fast-turn around jobs
3. Lack of considerations for users, such as lower-skilled workers in system adoption
4. Data migration takes multiple times. Turns out that personnel was not experienced for data ETL processes.
5. Lack of key functional considerations and customization for company and industries.

The client insisted on engaging us as a "insurance" 😅
1. We can do process flow and complex flow mapping. Aka, works that client staff avoids
2. Walk around and understand worker's requirements. Aka, works that developers don't want to do
3. Perform Data ETL as early as project starts. Aka, works that developers shuns away from and clients don't really know how to do.
4. Workflows and Function testing. Aka, works that is repetitive for both client and developers. They dislikes it.
5. Walkthrough and UAT. Aka, works that is long, tiring and yet is important.

In summary, we do the works that clients and developers don't like to do and at a professional level. 🥹🥹

Jokes aside, honored to have a chance to work with them and hope they ended up like many of our happy clients.

#trustpro #managementconsulting #erpsystem

A recent ERP project review taught us some tough lessons. A listed company invested in a 6-figure ERP system, but after 3 years, it was still not live due to system errors, mismanagement, and lack of process flow documentation.

Here's what went wrong:

ERP Project : Sharing Lessons Learned🚨
Name: Listed Company-Wholesale Industry ERP System Went South
Case : TPERP-CNX-HUT

In details (TLDR)

In one case, a listed company came to TP and shared their 6-figure ERP dismal situation 😅
1. ERP system that is unable to go live after 3 years.
2. It went up for a few months but down again due to multiple system errors.
3. Training was conducted but in silos modules.

We went for a online meeting and reviewed the findings
1. There was no process flows
2. The client was managing the developers directly. The main-con's project team quitted.
3. There was no UAT sign off against process flows.
4. There was no punch listing of functions.
5. The phase 2 processes was not even discussed.
6. Whatever that cannot be done is "due to system limitations" or "shifted to Phase 2".
7. There was no assessment on whether it can go-live. Developer was urgent to push it through.
8. Ultimately, the client keep on saying " there was no consultant like yourself to manage the whole thing".

My comments to them is
1. Review the full system with the newly-documented process flows.
2. Walkthrough on workflows, not modules
3. Split staging site data against live. Both have to load in full live data. A good ETL process should be done.
4. Conduct full process flows studies first, then split into phases. Else it is easy to "dust-under-and-forget"
5. Proper documentations at all times. The purpose is traceability. Even simple ones will suffice.
6. Walk with better developers and consultants who can handle complex projects. The current system is quite painful to watch, given its high costs and dis-connected quirky flow.

Sigh. I also shared that
1. Consultants are not necessary for ERP/Digital system, or any projects.
2. Experienced COEX (consultant and executionist), however can be invaluable for complex project.

Sometimes there are reasons why ERP/Digital projects will not end with expected success.
We wish they have found us earlier and the project would have been a more pleasant journey with good results by now, instead of waited for 3 years. 😄😄

Hope to have a chance to work with them, like many of our happy clients.

AI-generated image. Cool.

#trustpro #digitalsystem #managementconsulting