Lineage
Lineage maps for event streams
When a dashboard number looks wrong, the investigation path should not depend on who happens to be online. A one-page lineage map — crude is fine — keeps Data Governance for App Analytics grounded in ownership instead of folklore.
Draw five columns only
Source surface (app screen or API), collector or SDK, transport or CDP, warehouse table, and consuming tile. Resist adding every microservice. The goal is a shared sketch, not a perfect CMDB. Annotate each column with a human owner and a backup.
Mark the dark edges
Reverse ETL, vendor overlays, and CSV side-loads create dark edges that bypass your carefully named events. Put them on the map in a different color. If an edge has no owner, it is a governance defect waiting for an incident.
Refresh on release, not on guilt
Tie map updates to release trains that touch analytics schemas. A quarterly archaeology session is better than nothing, yet change-driven updates keep the sketch honest. In Stewardship Studio, teams practice updating a map during a mock schema break.
Prefer guided practice? Open the Analytics Stewardship Studio syllabus.