When ERP works, but not well enough
Key Stone is relevant when ERP systems are operational, yet persistent inefficiencies, workarounds, and control gaps suggest deeper issues.
Transactions post. Processes run. Reports are produced. And yet, over time, exceptions multiply, manual interventions increase, and confidence in system discipline weakens. Leadership senses that something is off, but cannot clearly see where or why.
This situation is often dismissed as normal system ageing. In reality, it is usually the result of accumulated design compromises, governance gaps, and unexamined operational drift.
Who Key Stone is for
Key Stone applies when organisations observe patterns such as:
This problem definition appears most often in mature SAP landscapes that have evolved through multiple changes without periodic structural review.
What changes after Key Stone
Key Stone is not about reimplementing ERP.
It is about restoring clarity and control.
Organisations typically experience:
Clearer visibility into ERP health and operational risks
Better understanding of where controls are weak or inconsistent
Reduced dependence on informal workarounds
Greater confidence in audit outcomes
A stronger basis for deciding what to fix, tolerate, or redesign
The objective is not perfection, but intentional ERP behaviour.
What Key Stone actually does
At a high level, Key Stone focuses on:
The emphasis is on visibility and judgment, not on blame or disruption.
How Key Stone engagements typically begin
Key Stone engagements usually start with a structured discussion around:
If the concern is about ERP integrity rather than transformation, Key Stone provides the right entry point. If not, we help redirect the conversation.
Learn More
About Key Stone
Key Stone is a dedicated service with its own depth, principles, and engagement approach.
Related thinking
You may find it useful to explore Lydian’s writing on:
ERP governance and hygiene
Control drift in mature SAP systems
Audit readiness versus audit theatre
