Skip to main content

Technical Reference — Diagram Options

Three diagram options for the Data Pipeline Technical Reference. Team colors: team.platform (#3F51B5), team.domain (#C2185B), team.business (#00695C), team.quality (#689F38). More: https://ohpen.stephenadei.nl

Bucket names in diagrams are example names; the same patterns apply for any deploying organization.

Option 1: Top-down “Pipeline Strip” (flow + teams)​

Use when: You want a single top-to-bottom flow that matches the “Architecture Overview” row, with team ownership on each layer. Fits on one slide or above/below the table.

Team colors: Subgraph borders use team.platform (#3F51B5), team.business (#00695C), mixed-owner group (#757575).

Pros: Top-down structure, teams on each subgraph, easy to read.
Cons: CI/CD and alerting not shown; add a one-line caption if needed.

Option 2: Layered “Full Stack” (all six components + teams)​

Use when: You want one top-down diagram that maps to all six rows of the technical reference (Architecture + 1–5) with team ownership. Same idea as the presentation “Canonical Baseline” but tightened for the reference table.

Team colors: team.platform (#3F51B5), team.business (#00695C), mixed (#757575).

Pros: One diagram covers the full technical reference (ingestion, transform, storage, schema, CI/CD, monitoring) with teams.
Cons: Denser; may need smaller font or wider layout for clarity.

Option 3: “Poster” — Top-down pipeline + callouts (with teams)​

Use when: You want a top-down pipeline in the centre and the table’s key facts plus team ownership in callouts.

Team colors: Callouts neutral (#757575); pipeline infra (#7B2CBF). Node fills use state/func tokens; team names in labels.

Pros: One view: top-down flow + buckets, validation, schema, CI/CD, alerts, and teams.
Cons: Callouts subgraph may wrap; use Option 2 if layout is tight.

Recommendation​

  • For the PDF with table: Use Option 1 (top-down strip + teams) above or below the table so the PDF stays clean.
  • For a single “big picture” slide or poster: Use Option 2 (full stack + teams) so one diagram covers all six components and ownership.
  • For a “cheat sheet” with flow + bullets + teams: Use Option 3 (poster) if your tool renders it well; otherwise Option 2.

All options use top-down (TB) layout and include teams (Data Platform Team, Domain Teams, Finance, Data Quality Team, Analysts / Finance). Export to PDF with the diagram filter so the diagram appears in the PDF. More: https://ohpen.stephenadei.nl

© 2026 Stephen Adei•CC BY 4.0