Practice / ERP in Practice

ERP systems break at the architecture, not the implementation.

Every ERP failure has an official explanation: bad data, wrong vendor, rushed timeline, insufficient training. The structural explanation is usually different — and usually invisible until after the damage is done.

Series
B — ERP
Cases
—
Method
CDSA
—

This is relevant if

The situation looks like this
Go-live succeeded. Six months later, operations are running on shadow spreadsheets.
Inventory numbers are "accurate" in the system and unusable on the floor.
Each customization made sense. Together they make upgrades impossible.
Data quality issues keep returning after every cleanup effort.
The project ended. Nobody owns what happens to the data now.
Less relevant if
You are still selecting a vendor or comparing platforms.
The problem is clearly defined and the path forward is visible.
You need implementation guidance, training, or standard best practices.
The constraint is resources or timeline, not structure.
01

What this series is about

The diagnostic frame

ERP implementations produce a specific class of structural contradiction: a system designed to unify information sits on top of an organization with its own logic, timelines, and power structures.

The gap between system logic and organizational logic doesn't disappear at go-live. It gets encoded into the implementation — into customizations, workarounds, and data that no one owns. This series documents that gap: how it forms, where it hides, and what makes it structurally inevitable rather than merely avoidable.

02

What we look at

Three structural zones where ERP contradictions concentrate.

01
State alignment

The system holds one version of reality. The warehouse holds another. The contradiction is not a sync error — it is a missing layer: who owns reconciliation, and when.

02
Governance continuity

Projects end. Data doesn't. The structural gap between project lifecycle and operational lifecycle produces ownership vacuums that no one budgeted for.

03
Process transformation

Customization is where the unresolved contradiction goes. Each rational local decision leaves a residue. The residue accumulates. The trap closes slowly.

03

Cases

Each case is a documented structural contradiction — not a failure story, but an architectural analysis of what made the failure structurally predictable.

04

From cases to intervention

Each case points to a specific structural move — not a fix, but a layer that was missing.

State alignment
System state and physical state diverge continuously
→
The missing layer is reconciliation ownership. The intervention is to make it explicit: who owns it, at what frequency, and with what authority to halt operations when states diverge beyond threshold.
Governance continuity
Data quality degrades after go-live because no one owns it
→
The missing layer is data stewardship as an operational role. The intervention is to make it explicit before the project closes — not as a handoff document, but as a funded, named responsibility that survives go-live.
Process transformation
Customization accumulates until rollback becomes impossible
→
The missing layer is cumulative cost visibility. The intervention is to make it explicit: a customization register that tracks upgrade impact, so the accumulation is visible before it becomes irreversible — not after.
Pattern — across all three cases

The absent layer determines where the conflict goes.

In each case, the structural contradiction migrates to the next available layer — the one no one explicitly designed. In ERP-001 it is reconciliation. In ERP-002 it is stewardship. In ERP-003 it is organizational change. The layer is absent not by accident, but because the project architecture had no place for it. This is what makes the conflict structurally predictable and locally invisible at the same time.

Diagnostic rule: when a contradiction keeps returning after fixes, look for the layer that was never designed — not the fix that was applied wrong.

—

Across domains

The structural pattern
The same class of contradiction appears across different systems. ERP is where the cost is visible.
ERP
System logic vs organizational logic. The gap gets encoded into customizations, workarounds, and unowned data.
AI in Production →
Model capability vs operational context. Evaluation metrics optimize one thing while degrading another. The absent layer is usually evaluation architecture.
Decision systems
Speed vs completeness. Clarity vs accuracy. The contradiction is in the output layer — not in the decision logic itself.

If the situation looks familiar — and the same contradiction keeps returning after fixes — the next step is not another fix. It is finding the layer that was never designed.

Describe your situation →
Back to
Practice
→
Also in Practice
AI in Production
→
The method
Foundation
→