Many companies treat the data warehouse as the graduation project of informatization: connect every system, model every table, promise that anything can be analyzed later. Two years later the warehouse is huge, management meetings still argue over definitions, and business still asks IT for ad-hoc extracts. The warehouse is built; no one owns the questions.
Subject areas should not follow systems (ERP domain, OA domain) but business questions (delivery domain, quality domain, collections domain). Systems are sources; questions are destinations.
Benefits of Slicing by Question
A delivery domain naturally pulls orders, plans, inventory, and shipments; a quality domain pulls inspections, defects, and suppliers; a collections domain pulls contracts, invoicing, and bank receipts. Ownership is clear, field trade-offs have rationale, and garbage is not ingested "just in case."
Build Only Two or Three Domains in Phase One
- Pick questions the boss asks every week, not what tech finds most interesting.
- Land official metrics and detail permissions per domain before self-service analytics.
- Source systems keep evolving; subject areas expose stable definitions outward so the warehouse does not flip daily with table changes.
The XYN Technology digital platform grows business apps and definitions together, with the data layer serving scenarios. A warehouse is fine—but it is the back office for business questions, not the finish line of enterprise digitalization. A well-built warehouse stays small yet gets used every week.