When Every Company Has Its Own System, Technology Becomes an Operating Problem

The differences went well beyond which software each company used. The businesses were operating at very different levels of technology maturity. Some employees had years of experience working within established systems, while others had never worked within the type of enterprise platforms that were going to be introduced.

There were also functions being managed by outside vendors, which meant that bringing work into an enterprise environment required more than implementing new technology. Existing processes and data had to be understood, transitioned and incorporated into a new way of operating.

Implementation was phased based on where the individual businesses were starting and what would be required to move them into the new environment.

For some companies, that meant transitioning data and processes from outside vendors. For others, it meant moving work that had been heavily manual into technology for the first time. Training and development became critical because employees were being asked not simply to learn a new system, but in many cases to work differently.

Manual processes and reliance on disconnected systems were reduced, core workflows became more consistent, and the organization developed technology infrastructure capable of supporting a larger and increasingly complex enterprise.

Enterprise technology implementation becomes much more complex when the businesses involved are starting from entirely different places.

The technology itself is only one part of the work. Leaders also have to understand the processes being replaced, the data being moved, the functions being brought in-house, the roles that will change and whether employees have the skills and training required to operate successfully in the new environment.

Scroll to Top