Index
When an indicator changes unexpectedly, the team needs to locate the source of the difference. Data lineage connects source, transformation, and reporting to support this investigation.
How to evaluate this decision
Map the route at the level required for use: table, field or rule. Record filters, joins, and transformations that change meaning. An arrow between systems does not explain how a value was calculated. Documentation must track versions and allow you to evaluate the impact of a change before implementing it.
Criteria for comparing proposals
- Origin: identify relevant source, field and moment of extraction.
- Transformation: document rules and dependencies that affect the calculation.
- Consumption: relate indicators and reports that use the result.
A scenario to discuss with the supplier
Hypothetical example: a change in order classification changes the billing shown to management. Lineage should point out the affected rule and reports, rather than requiring manual investigation of the entire platform.
What to validate upon delivery
Choose a bookmark and scroll down to source records. Then, simulate a field change and check if the impacted consumers are identified.
Prepare the conversation about the project
Quantum9 can map and instrument the lineage of a priority stream. Enter critical indicators, tools, and frequency of changes to choose a sustainable level of detail.
Data engineering · Map the company's priority