Search
  • en
  • es
  • en
    Search
    Open menu Open menu

    Data product framework for domain teams

    Domains ship the data they own without queuing behind a central team, each product carrying a data contract, a named owner and a versioned lifecycle. We define the framework and build the first products.

      Why it matters

      Every dataset is somebody else’s problem

      Pipelines get built for a single request, handed over and then forgotten: no contract, no named owner, no schema versioning. Every consumer compensates with defensive joins and private copies, and the central team ends up arbitrating each breaking change, so it becomes the bottleneck for all data work.

      A data product framework changes the unit of work. Instead of a pipeline, the domain ships a product with a named owner, a documented contract, quality thresholds and a deprecation policy consumers can plan against. The question you answer first is not which pipelines to rebuild, but which domains are ready to own and publish their own data.

      1data contract per product, owned and versioned by the publishing domain
      Aigües Carglass Hermes Sage Telefónica Willbo Acciona Mediaset Microsoft Ferrovial Coca-Cola Iberdrola
      Anatomy of a data product

      What turns a dataset into a product

      Four elements. Miss one and it goes back to being a pipeline somebody maintains out of goodwill.

      OwnedThe data
      product

      Contract

      Schema, semantics and guarantees documented and versioned

      Owner

      A named domain owner accountable for it, not a ticket queue

      Quality

      Freshness, completeness and consistency validated automatically

      Lifecycle

      Versioning, deprecation and a roadmap consumers can plan around

      Why Plain Concepts

      What makes this different

      Products with an owner

      A named owner per data product, accountable for it beyond the first delivery.

      A documented contract

      Schema, semantics and guarantees versioned, so changes are deliberate and announced.

      Domains that ship

      A framework and golden paths that let each domain publish safely on its own.

      Deliverables

      What you take away

      The framework, the golden paths and the first data products the domains build with them. Not for organisations without named domain owners; if one team still owns every dataset, fix the operating model first.

      01

      Data product standard

      02

      Templates and tooling

      03

      Reference data products

      04

      Federated governance model

      Recommended next step

      Review your data product readiness

      A half-day session with your data and domain leads. You leave with the candidate domains ranked and the first data contract drafted.

      Book the readiness review