The questions behind the frustration

Across business and IT teams, we hear the same concerns:

• Why is our SAP implementation so slow and expensive?
• How do we simplify SAP in a regulated pharma environment?
• Is SAP S/4HANA actually worth it for life sciences?
• How do other pharma companies reduce SAP customisation?
• Why does every process change take months in SAP?

These are not just technical questions. They reflect a deeper unease about predictability, cost and control.

The real issue: complexity without clarity

ERP environments rarely become unmanageable in a single programme. They evolve. New requirements are added. Too many “what if we need to exceptions” are built in. Integrations multiply. Local variations are preserved. Over time, organisations lose a shared understanding of:

• Which systems support which processes
• Where integration boundaries begin and end
• How architectural decisions affect process design
• What the true impact of change will be

Without that clarity, even straightforward adjustments feel risky. Every change becomes a project.

Customisation is usually a symptom

Over-customisation is often blamed for ERP frustration, but it is usually the outcome of deeper issues:

• Unclear process ownership
• Lack of challenge of legacy ways of working
• Decisions made without a holistic architectural view
• Business requirements translated directly into system changes without simplification
• Lack of understanding of future business needs and scalability

When business teams do not fully understand why processes operate as they do, or how the system enables them, customisation becomes the default response.

The result is an ERP landscape that is technically functional, but strategically constrained.

When architecture becomes invisible

Few organisations maintain a clear, business-level understanding of their ERP architecture.

As a result:

• System scope becomes blurred
• Dependencies are poorly understood
• Risk is not translated in business terms
• Validation effort increases
• Delivery cycles lengthen
• And cost of change escalates

The issue is not that ERP is inherently slow. It’s that uncertainty increases risk  and risk increases caution.

Regaining control

Addressing ERP frustration does not necessarily mean replacing SAP or launching another large-scale transformation programme. It means restoring clarity. Organisations that regain control typically:

• Clarify system scope and integration boundaries
• Re-establish strong business ownership of core processes
• Align architectural decisions with operating model intent
• Reduce unnecessary variation before implementing new change

The objective is not simplification for its own sake. It is restoring transparency, predictability and confidence in how change is delivered.

The opportunity

ERP becomes a liability when the business doesn’t engage, complexity accumulates faster than understanding.

Life sciences organisations that step back to reassess architecture, ownership and design regain something far more valuable than system efficiency: control.

When the relationship between process, system and strategy is clear, ERP once again becomes what it was intended to be: a platform for scale, not a barrier to it.