How ERP Implementations Can Become Accepted Before Their Full Value Is Realized

When electricity first entered factories, it often arrived without disturbing the room. A large motor took the place of the engine that had powered the plant. Above the workers, the same shafts continued to turn. The same belts dropped from the ceiling to the same machines below.

To anyone standing on the factory floor, the change was obvious. The source of power was new. The arrangement of work was not.

That distinction mattered. Early manufacturers had bought a remarkable capability, yet many used it to reproduce a factory designed for an earlier age. The machines remained crowded around a central drive system. Production still followed the limits imposed by shafts and belts. The investment worked, but the expected leap in productivity was slow to appear.

It took years for businesses to understand what they had purchased. Electricity was not simply another way to turn the central shaft. Smaller motors could be placed beside individual machines. Once power no longer had to travel across the factory from a single source, the entire floor could be reconsidered. Equipment moved closer to the work. Material followed a more direct path. Maintenance became less disruptive. The technology became valuable when managers stopped asking it to preserve the old factory.

The Benefit Was Not Inside the Motor

The larger gains arrived only as manufacturers learned what electricity made possible. Smaller motors could drive individual machines. Equipment no longer had to gather around a central shaft. Factory floors could be redesigned around workflow, material movement, safety, maintenance, and output.

That learning took time. Existing buildings represented sunk investment. Managers knew how to operate the layouts they already had. Workers had developed routines around them. Capturing the full value of electricity required more than buying a motor; it required complementary investment, new skills, and a willingness to reorganize work. Historical research therefore identifies a lag between the adoption of electric power and the larger productivity improvements associated with it.

The motor was necessary, but the advantage came from redesigning the factory around its capability.

ERP Begins with the Same Unanswered Question

More than a century later, the same mistake is being made in quieter rooms.

A leadership team approves a new enterprise platform. The business case is persuasive. Finance will spend less time reconciling numbers. Operations will see what is happening sooner. Reports will arrive with fewer manual interventions. Decisions will be made from information that people can trust.

The program begins with unusual energy because almost everyone recognizes the problem. Systems do not speak to one another. The same data carries different meanings across the company. Important reports depend on people who know which spreadsheet to open and which adjustment to make. A common platform appears to offer a way out.

Then design begins, and the promise meets the organization as it actually exists.

The software offers a standard process. One business unit says the process cannot work in its market. A control team points to a regulatory requirement. Another group wants to keep a local report that has been used for years. Some objections protect real business value. Others protect familiarity. In a workshop, they can sound remarkably similar.

The project is soon caught between two convictions. One side believes the business must adopt the system as designed. The other believes the system must reflect the business as it operates today. Both positions contain some truth. Neither provides a reliable rule for the hundreds of decisions that follow.

So the program settles each question on its own. One process is standardized. Another is customized. A third remains outside the platform until a later phase. The choices may be reasonable when viewed separately. Together, they begin to create an operating model that nobody consciously chose.

Time changes the nature of the discussion. Early meetings ask what the business should become. Later meetings ask whether testing can finish before the launch date. A design decision that once seemed open now carries months of configuration behind it. Revisiting that decision could delay the program and increase the cost. It could also force leaders to acknowledge that the organization never resolved the underlying business question.

Under this pressure, ambition contracts. A report that was meant to disappear is retained for comfort. A manual control survives because redesign would take too long. Training shows employees how to complete a transaction but leaves little room to explain why the process has changed. Each compromise promises to protect the launch. Each one also moves the program a little farther from the case that won approval.

Eventually the date arrives. Orders move through the platform. Invoices are paid. The ledger closes. Problems appear, as they do after any large implementation, and teams work long hours to stabilize the system. When the backlog begins to fall, the organization feels an understandable sense of relief.

The implementation is declared a success.

 

That may be true in an important sense. The system is live. The company is operating. Yet the original promise was not simply to replace software. It was to improve the business.

This is where the more difficult part of the story begins.

A spreadsheet returns because the new report does not answer a question the business still needs to ask. A local tracker appears because managers cannot see an issue soon enough. Finance exports data for another reconciliation before presenting it to leadership. None of these actions is dramatic. Most begin as practical responses to immediate problems.

Some will disappear as employees learn the system. Others reveal gaps in training or discipline. A few expose something more fundamental. The platform may have changed, but the flow of information and authority around it has not.

By this stage, the company has spent heavily. The project team is moving on. Leaders are turning to the next priority. Reopening old design choices feels less responsible than learning to live with them. Workarounds become routine, and routine makes the extra effort harder to see.

The organization has entered an acceptance trap. Nothing appears broken enough to justify another major intervention. Transactions are processed. Audits are completed. Reports are issued. The system does what it was configured to do. Over time, that becomes the new definition of success.

What gets lost is the distance between a system that functions and a business that works better.

Research on enterprise systems has described this distance for decades. Installation is only the beginning of value creation. The larger gains depend on changes to processes, roles and organizational design. More recent research reaches the same conclusion. Results vary because organizational fit and the quality of process redesign vary.

Executives do not need another technology scorecard to see the difference. They can find it in the work that remains. How many reconciliations still take place outside the platform? How many reports must be repaired before they can be trusted? Has the close become easier, or has effort merely moved to another part of the process? Can a forecast respond quickly when assumptions change? Have old systems and spreadsheets actually been retired?

These questions return the conversation to the purpose of the investment. They do not assume that every workaround is a failure or that every standard process is superior. They ask where the business has a valid reason to differ, where old complexity has survived without one, and where both the software and the existing process fall short.

That judgment cannot be supplied by the technology. It belongs to leadership.

The manufacturers who eventually benefited most from electricity did not choose between preserving the factory and surrendering to the motor. They redesigned the relationship between the two. The technology changed what was possible. Management changed the work so the possibility could become productive.

A company with a stable platform can still make the same move. It does not need to reopen the entire implementation. It can begin where people still repair information, repeat work or wait too long for a decision. Those points of friction show where the promised value has not yet reached the business.

“A successful implementation proves that the system works. Value appears when the business works better because of it. “

At COGMERIX, we describe this as business ergonomics. The idea is straightforward. People, processes, information, controls and technology must fit the work the organization is trying to perform. When they do not, even capable systems create effort. When they do, the investment begins to create leverage.

The early electric motor was not a disappointing technology. It was a new capability confined inside an old design. Many modern systems are waiting for businesses to make the same discovery.

From Implementation Acceptance to Benefit Realization

“Which intended business benefits remain incomplete and what combination of learning, process, data, accountability, or design will realize them? “

What do you think?

What do you think?

1 Comment
July 24, 2023

This strategic reallocation of resources can help companies create a significant competitive advantage.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Insights