Should you customize the ERP or change the process to fit it?

Neither by default. First measure where the system and the floor do not fit, and sort what the system lacks from what it imposes. Then weigh each customization against what it will add to maintenance for as long as the system runs. Measuring is not the same as agreeing: some requests should get a no.

How it works

A standard package is cut before anyone measures your floor: code, forms, a configuration made for a typical company. Where it does not fit, the floor wears it like armor made for someone else. It walks, but stiffly.

Ask the smith for a pocket and the answer is that the standard has none. The tailor’s risk is the opposite: sewing whatever the client orders. Every pocket has to be carried through every upgrade. The useful question is not whether a change can be made, but what the pocket will cost to carry.

Evidence

Following one enterprise-system rollout for three years, Diane Strong and Olga Volkoff sorted the misfits between system and company into six domains, data among them, and two kinds: what the system lacks and what it imposes.

Ben Light noted that most companies bend instead, reshaping their processes to fit the package and keep the vendor’s support. In his two cases, customizations could pay off, but each needed weighing against what it added to future maintenance.

What this does not prove

Sources

From the field notes The Smith and the Tailor · PDF, 10 pages