Tag Archives: Gap

Solution overview: hablamos tutti die gleiche language?

One of the biggest obstacles of the ERP projects is the language. Not the spoken language, such as Spanish or German, but the lingo of the business, of the branch, of the company. The consultants speak their lingo. The customer speaks theirs. Especially in the early stages, the projects can fall apart on understanding each other.

If there is one profound risk that all ERP projects share, it’s that during requirement analysis and early stages of design the consultant won’t understand the customer’s need, and that the customer won’t really understand what consultant is proposing. A bad choice, and there goes another failed project.

Luckily, there is a tool in Sure Step which is used specifically to eliminate this risk of misunderstanding: the Solution Overview.

Continue reading Solution overview: hablamos tutti die gleiche language?

4th rule of agile ERP: avoid heavy customizations

You can’t avoid customizations. Vanilla ERP is a great first step, and a valuable tool for establishing common language between the customer and the consultant. But in the long run? Probably not. Pristine uncustomized ERP won’t be sufficient, because of the gaps between your way and ERP’s way. Sooner or later, gaps will have to go.

Two most common ways of closing functionality gaps are customizing the software, and changing the processes. You can almost always touch general processes, optimize them, twist them, bend them, make them more efficient or even eliminate them. But when it is about industry specifics that add true value or contribute to company’s competitive edge, customization is the answer.

Continue reading 4th rule of agile ERP: avoid heavy customizations