Enterprise Business Software and the Mixed-Up Chameleon Problem

Summary

Traditional ERP practice prioritizes a standardized, stable core, but the post argues that forcing every process into it can erode an organization’s identity and differentiated ways of creating value. It proposes keeping the ERP as the system of record while placing an interoperability layer above it. This layer uses a shared ontology to reconcile concepts across systems and supports workflows, automation, user experiences, agentic AI, and human engineering under shared security and governance. Because these capabilities remain outside the core, organizations can preserve distinctive processes during ERP upgrades and treat migration as a continuous software- and ontology-driven activity rather than a one-time manual exercise. The intended model is structured adaptability: standardized ERP functions retain discipline, auditability, and financial integrity while operational software adapts to the business.

Takeaways

1. 1

   Standard ERP processes provide discipline, consistency, auditability, and financial integrity, but the post says processes that create an organization’s unique advantage should not be forced into conformity merely because the ERP cannot adapt.

2. 2

   A shared ontology maps different system terms, such as “material,” “item,” and “stock number,” to the same enterprise concept while allowing the ERP to remain the system of record without being the sole source of meaning.

3. 3

   The post says ERP program budgets were at least 60% labor under the traditional systems-integrator model, while modern agentic systems can automate data alignment, discrepancy reconciliation, transaction testing, and validation.