You can’t fix what you can’t trace. Here’s the 4-stage lineage maturity model.
After working with dozens of data teams, I see the same maturity curve. Four stages, and most teams are stuck at Stage 2.
Stage 1: Nothing. Nobody knows where data comes from. When something breaks, it’s detective work. Slack messages, git blame, asking the person who “probably built that.”
Stage 2: Documentation. Spreadsheets, Confluence pages, wiki articles. Looks good on paper. Outdated within a week. Nobody maintains it because nobody owns it.
Stage 3: Automated technical lineage. Tools like dbt’s lineage graphs or Airflow DAGs trace pipeline connections automatically. You can see what feeds what. This is where scale becomes possible.
Stage 4: Business context lineage. Column-level tracing plus business impact mapping. You don’t just know that Table A feeds Table B. You know that if Table A’s revenue column is wrong, the CFO’s quarterly report is wrong.
Most teams need Stage 3 minimum to scale. Getting there requires treating lineage as infrastructure, not documentation.
What stage is your lineage tracking at today?