A key reason for this design ritual is to ensure corporate memory of why the data product was developed in the first place, and what challenges were faced and overcome in the past.
What is the #Learning ritual for?
The purpose of this design ritual is to evaluate the performance of a data product. The primary “wave” that this ritual is concerned with are the outcomes that can be related to a #DataProduct.
What is the #DataReadiness ritual for?
The purpose of this design ritual is to validate whether data exists in a form that will support the analytics objectives. The primary “wave” that this ritual is concerned with are the resources that capture or record data.
Before a data product can be built, the feasibility of fulfilling stakeholder expectations needs to be validated. Based on the information design and hypothesis design, sources of data need to be identified and tested for its completeness and utility.
What is the #HypothesisDesign ritual for?
This ritual aims to define the levers and constraints of a particular business issue, identifying the needs to support data-driven intervention, often associated with the practice of statistical analysis & machine learning.
What is the #InformationDesign ritual for?
It's about defining a common language for describing what a business does and what you want to measure. This language lays a foundation for a #DataLake, #Hub or #DataWarehouse.
With ADML, data products are developed with the outcome and context of the problem firmly in mind. Equally, by starting from the outcome desired, data products can be developed to ensure the outcome is achieved.
✔️ Developing a reusable library of assets to improve the speed and reduce the cost of development;
✔️Capturing the expected contribution of a #dataproduct to business value to help with managing resources and giving priority to the right data investments;
✔️ Linking #datalineage to context (i.e., problems, imperatives and business value contribution) so that change processes can be managed in line with their value.