Enterprise software is supposed to remove friction. Yet many organizations quietly reorganize perfectly sensible operations around the limitations of the software they bought. A field team adds three administrative steps because the ERP requires them. Project managers maintain a second spreadsheet because the official system cannot represent the information they actually manage. Employees copy data between platforms because an integration was considered “out of scope.” Leadership then sees low adoption and concludes that people are resistant to change.
Sometimes the process really does need to change. But sometimes the software is simply a poor fit. The important consulting work is knowing which is which.
The first diagnostic: find the shadow workflow
Ask people to show you how work is actually completed, not how the process diagram says it is completed. Look for spreadsheets maintained beside enterprise systems, email approvals, copied-and-pasted identifiers, local databases, Teams channels used as ticket queues, and people whose unofficial job is translating between systems.
These are not merely bad habits. They are evidence. A shadow workflow usually exists because the formal workflow is missing information, sequence, flexibility, or visibility that the operation requires. Before eliminating the workaround, determine what business function it is performing.
Standardization is valuable, but only when it standardizes the right thing
A global organization should absolutely standardize master data, financial controls, security, audit requirements, and common processes where variation adds no value. The mistake is assuming that every operational difference is waste.
For example, a service organization may need one financial system of record while different business units legitimately require different intake, engineering, or fulfillment workflows. The correct architecture may be a standardized core with purpose-built workflow layers around it, rather than forcing every user to live directly inside the ERP.
Use the “one-touch” test
Take a common transaction and count how many times the same information is touched by a human. A project number arrives by email, is entered into a spreadsheet, copied into a ticket, re-entered into the ERP, pasted into a status report, and finally copied into an invoice note. Six touches of the same fact is not six pieces of work. It is one piece of work multiplied by system boundaries.
The target state should be that information is captured once, validated at the appropriate point, and then moved through APIs, integrations, workflow automation, or shared data services. This is often a better transformation investment than replacing an entire platform.
When custom software is the sensible answer
Custom software is not automatically expensive, dangerous, or anti-standard. A narrow application can be the cleanest solution when the workflow is strategically important, highly specific, and poorly served by generic software.
The discipline is to build narrowly: keep identity, security, master data, finance, and other enterprise capabilities in established platforms; build only the workflow or user experience that is genuinely differentiated; use supported APIs; define ownership; instrument the application; and design an exit path. The goal is not to recreate Salesforce or SAP. It may be to replace a 14-column spreadsheet and 30 emails with a three-screen application that employees can actually use.
Measure transformation in operational terms
Do not measure success by licenses deployed or training completion. Measure cycle time, handoffs, touches per transaction, error rate, rework, time-to-information, backlog, user effort, and support demand.
If the new platform is technically live but a project coordinator now spends two additional hours per week maintaining it, that cost is real. Multiply it across hundreds of employees and the “standard” solution may be one of the most expensive processes in the organization.
The practical objective is not more technology. It is a better-performing operation with clearer ownership, less friction, and technology that can be supported over its full lifecycle.