Data products, not data projects
An operating model for governed data products with accountable owners, consumer contracts, quality, access, service levels, adoption and platform enablement.
An operating model for governed data products with accountable owners, consumer contracts, quality, access, service levels, adoption and platform enablement.
On this page
Overview
On this page
Enterprise data becomes reusable when a named owner serves defined consumers under a governed contract. A platform alone cannot turn an unowned dataset into a dependable product.
Data programmes often organize around ingestion, storage and project delivery. The platform fills while business teams continue waiting for definitions, access, quality decisions and trustworthy context. The missing layer is product ownership.
A data product serves a defined group of consumers and decisions. It has an accountable owner, documented meaning, an access route, quality expectations, service behaviour and a lifecycle. Its value is demonstrated through adoption and decision use, not through data volume.
Start with a consequential decision and a committed consumer. Build the smallest governed data product that serves that decision, then improve it through measured use.
The first products should solve visible decision problems while proving shared governance and platform patterns. A broad “customer 360” or enterprise-wide canonical model is rarely a useful starting scope. Select a bounded decision such as service demand, inventory availability, revenue recognition, workforce capacity or operational risk.
A committed consumer participates in definition and acceptance. The accountable owner can resolve semantic disputes. Source-system owners agree access and correction routes. The platform team provides paved paths for ingestion, contracts, quality, lineage and publishing.
A decision or workflow changes when the product is available and trusted.
- Catalog and ownership
- Business meaning
- Quality and freshness
- Consumer examples
- Ingestion patterns
- Schema and contract tests
- Transformation standards
- Versioned delivery
- Classification and policy
- Lineage and audit
- Purpose-aware access
- Exception workflow
- Quality and service telemetry
- Incident ownership
- Usage and cost
- Deprecation and retirement
- Every priority data product has a named product owner with decision rights.
- A defined consumer and decision justify the product.
- Meaning, quality, access and service expectations form one product contract.
- Source and correction ownership are explicit.
A dataset becomes a product when someone is accountable for its use
Data programmes often organize around ingestion, storage and project delivery. The platform fills while business teams continue waiting for definitions, access, quality decisions and trustworthy context. The missing layer is product ownership.
A data product serves a defined group of consumers and decisions. It has an accountable owner, documented meaning, an access route, quality expectations, service behaviour and a lifecycle. Its value is demonstrated through adoption and decision use, not through data volume.
Start with a consequential decision and a committed consumer. Build the smallest governed data product that serves that decision, then improve it through measured use.
Select first products by consumer commitment and reusable value
The first products should solve visible decision problems while proving shared governance and platform patterns. A broad “customer 360” or enterprise-wide canonical model is rarely a useful starting scope. Select a bounded decision such as service demand, inventory availability, revenue recognition, workforce capacity or operational risk.
A committed consumer participates in definition and acceptance. The accountable owner can resolve semantic disputes. Source-system owners agree access and correction routes. The platform team provides paved paths for ingestion, contracts, quality, lineage and publishing.
A decision or workflow changes when the product is available and trusted.
Named users will adopt it, test it and retire a current workaround.
A business-aligned owner can decide definitions, priority and acceptable quality.
The product proves reusable platform, governance or operating-model capabilities.
Join domain ownership with federated governance
Domain ownership puts meaning and quality decisions near the teams that understand the data. Federated governance keeps products interoperable and controlled across the enterprise. Centralization of every decision creates queues; complete decentralization creates incompatible definitions and uneven controls.
MENTARA applies the domain ownership, data-as-product, self-service platform and federated governance foundations described in Data Mesh Principles and Logical Architecture.
Use the platform to make governed behaviour repeatable
Platform capabilities should reduce cognitive load for product teams and encode required controls. They should not remove accountability from the data-product owner or force every product into one physical architecture.
- Catalog and ownership
- Business meaning
- Quality and freshness
- Consumer examples
- Ingestion patterns
- Schema and contract tests
- Transformation standards
- Versioned delivery
- Classification and policy
- Lineage and audit
- Purpose-aware access
- Exception workflow
- Quality and service telemetry
- Incident ownership
- Usage and cost
- Deprecation and retirement
A phased product path
Name the decision, users, accountable owner and current workaround; agree the evidence of adoption.
Agree meaning, sources, quality, access, service expectations, interfaces and change policy.
Build through governed platform paths, test with consumers and establish operational ownership.
Monitor adoption, quality, service, cost and support; prioritize changes with consumers.
Reuse platform and governance capabilities while preserving domain ownership and explicit product boundaries.
Executive decision checklist
- Every priority data product has a named product owner with decision rights.
- A defined consumer and decision justify the product.
- Meaning, quality, access and service expectations form one product contract.
- Source and correction ownership are explicit.
- Platform capabilities encode common controls without centralizing every product decision.
- Governance defines standards, exceptions and interoperability.
- Adoption and retired workarounds are measured alongside technical service.
- Products have version, deprecation and retirement paths.
Turn priority data into an owned enterprise product.
A named MENTARA lead can help frame consumers, product contracts, governance, platform dependencies and the capability model required to operate them.
Continue with the decision in front of you.
Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.
Submit your requirement