Many companies stop at department projects: sales has CRM, plant has reporting, finance has its ledger. Each accepts; company problems still translate in Excel. Middle platform talk means build shared capability then bloom. Pragmatic version reverses: win one scenario, extract what scenario two needs into shared layer. What cannot extract is delivery, not capability.
Department project to enterprise capability is measured by reuse count—not architecture layer count.
Why Department Systems Do Not Become Capability
Customer codes, org, permissions each built once. Scenario two maps again. Unowned mapping means capability never grows. Departments allow private fields for speed—private fields become debt at copy time.
Middle platform before scenarios becomes an expensive empty shell. Expensive—and the floor still bypasses.
Pragmatic Extraction Order
- Unify identity and org first—all apps share login and scope.
- Customers, materials, document status from one source—department differences in extension attributes.
- Scenario two must reuse layer one—no parallel system purchase.
- Score middle platform by "how many scenarios call"—not module checklist.
The XYN digital intelligence system uses a unified framework for org and master data and configurable apps for scenarios. Pragmatic middle platform grows in being called. When calls happen, department projects upgrade to enterprise capability.
