I have strong opinions about a debate that will probably never be settled (and it’s not about whether Ross and Rachel were on a break). It’s about whether companies should get their advanced supply chain planning solution customized to meet their specialized needs or instead adopt a standard template. In my view, it’s generally a much better idea to stick to the standard. Let me explain why.
Business leaders tell me there are a lot of good reasons why they have their advanced planning solution tailored to their needs. One I hear a lot is that software developers don’t involve all the potential stakeholders when they’re developing the standard templates. On a more fundamental level, they say, none of the standard software solutions on the market perfectly reflects a business as it actually is.
And if the standard solution doesn’t support current business processes and practices, it seems like it’s much easier to adapt the software than to overhaul the processes. Which is why change requests have become a common ingredient of most implementation projects.
So here’s what happens next. For a while, it can look like everybody’s happy with the customized solution as demonstrated in the pilot. The solution is then rolled out across the entire network of plants or divisions. And every time a plant goes live, short-term KPIs get a boost.
A comprehensive user engagement program comes next so that users fully embrace this made-to-measure solution. But (and here’s the killer) the solution is only tailored to the initial pilot, and it’s not yet tuned to the rest of the network, which means the struggle begins.
Not only that, advisory support stops because it’s only budgeted for in the initial project stages. Meanwhile, organizations are changing all the time. People leave or get promotions. New recruits arrive, with fresh ideas and all the right experience. And acquisitions take place. After that, new production lines are developed and put into operation, while business processes are redesigned to take into account new insights or in response to events. And all these things can happen even during the implementation project.
While companies change dramatically over the years, your tailored solution still operates just as it was initially designed and implemented.
Upgrading to newer versions is difficult because customized software add-ons may need to be reintegrated. So, the company is stuck with the original version until somebody sufficiently high in the hierarchy says it’s time for a solution make-over.
It’s much better to adopt a standard template and use the built-in parametrization tool to configure the solution to individual company needs. Local versions are to be avoided, let alone modifications with proprietary code. I see three fundamental reasons for this:
You may argue that adopting an available standard product is a rather conservative choice that doesn’t allow you to innovate. That might be a valid argument if it’s innovation that’s at stake. Innovative concepts should be developed as part of a co-creation effort, not in a customization project. But that’s a story for another time.
So, my advice is to standardize where possible and challenge stakeholder customization requests. Feel free to contact me to learn more about how we at OMP speed up implementation and rollout with smart templates and industry-specific advice.
Supporting implementation in the OMP alliance network around the world, Maarten focuses particularly on standardization, scalability, and rapid deployment in the consumer goods industry.