The ERP Fit Challenge: Bridging the Gap Between Theory and Reality

Contributed by: Ejaz Ahmed

One of the most important things to recognise in ERP transformation is that enterprise systems are not designed around one organisation’s exact way of working.

They are packaged applications, built to support common business processes across many organisations, industries, structures, and operating models. They bring standardisation and that is part of their strength. At the same time, this means they will almost always be an imperfect fit in some areas. That is not necessarily a failure of the system or the implementation but the nature of adopting an enterprise platform.

The real question is how well the organisation understands, manages, and responds to that misfit.

Research into enterprise-system implementations identifies several domains where misfit can appear. These include functionality, data, usability, roles, control, and organisational culture.

This is a helpful way to think about ERP change, because fit is not only about whether the system has a particular function available. It is also about whether the system enables the business to operate effectively.

In some cases, the misfit is functional. The system may support the core process, but not the specific variation or exception the business relies on.

In other cases, the issue sits in the data. ERP often exposes where master data is inconsistent, where ownership is unclear, or where the structure of legacy data is not strong enough for the new operating model.

Usability is another area that can be underestimated. A process may work from a technical point of view, while still feeling slow, complex, or unintuitive for the users who need to follow it every day.

Misfit can also appear in roles and responsibilities. An ERP implementation often changes who owns a process, who approves a transaction, who maintains data, and who is accountable when something goes wrong.

Control is another important area. The system may introduce stronger governance, segregation of duties, audit trails, approval workflows, and process discipline. These controls may be right for the business, but they can still feel restrictive if people are used to local flexibility.

Finally, culture is often the hardest area to address. An ERP system may expect standardisation, transparency, and shared ways of working, while the organisation is still used to local workarounds, informal decisions, and spreadsheet-led control. This is where ERP change management becomes critical.

These misfits are not only technical design issues. They affect people, behaviour, mindset, ownership, and culture.

Some misfits are deficiencies, where the system does not provide enough support for what the organisation needs. Others are impositions, where the system introduces new structures, controls, or ways of working that the organisation must adapt to.

Both matter.

If the system lacks coverage, the business may struggle to operate effectively. If the system imposes a new way of working without enough preparation, users may resist, avoid the process, or recreate the old way of working outside the system.

That is why ERP success should not be judged only by whether the solution is configured, tested, and deployed.

A solution can go live and still leave the business with poor adoption, manual workarounds, unclear ownership, weak data confidence, and processes that do not feel natural in daily operation.

For me, the key question is not simply: “Does the ERP meet the requirement?”

It is also: “Does the ERP enable the organisation to operate in the way it now needs to operate?”

That means looking beyond functionality and asking:

• Is the data model understood and owned?
• Are roles and responsibilities clear?
• Can users work effectively in the system?
• Are the controls accepted and embedded?
• Does the culture support standardised ways of working?
• Are people ready for the behavioural change the system introduces?

ERP transformation is ultimately about whether the new operating model can work in practice. The system has to support the process, but the process also needs to be understood by the people using it.

Data has to support decision-making, not just transaction processing. Controls need to strengthen accountability without creating unnecessary friction. Roles need to be clear enough for people to know what they own, what they approve, and what they are responsible for. Technology needs to be embedded into the culture of the organisation, not treated as something separate from how the business actually works.

The organisations that do this well are not necessarily the ones that customise everything to match the old world. They are the ones that understand where the system fits, where it does not fit, where the business should adapt, and where the solution genuinely needs to be shaped around business value.

That is where ERP delivery becomes more than implementation. It becomes real transformation.