Open the editor

Data flow diagram

How data moves through pipeline steps and who owns each one.

1 data flow diagram example

Data platform roles flow

How data moves from admins through engineers and scientists to consumers, step by step.

Each lane is a role and each column a pipeline step, so the diagram answers who does what at each stage. The role chip on every node repeats the lane, and the accented arrow is the anonymised hand-off into analysis.

Open in the editor

What is a data flow diagram?

A data flow diagram (DFD) shows how data moves through a system: from sources, through processing steps, into stores and out to consumers. Classic DFD notation comes in two styles, Yourdon-DeMarco and Gane-Sarson, and modern data teams use the same idea for pipelines.

Read it along the arrows. Each arrow is data in motion labeled with what it carries, each process transforms it, and stores hold it at rest. Ownership labels show who is responsible at each step.

When to use a data flow diagram

  • Use it to document a data pipeline and which role owns each stage, from ingestion to reporting.
  • Use it in privacy or security reviews to trace where personal data travels.
  • If you need the order of events between services, a sequence diagram shows timing that a DFD omits.

How to make a good data flow diagram

  1. Label every arrow with the data it carries, not with a verb.
  2. Make sure every process has at least one input and one output.
  3. Show owners for each stage so accountability is visible.
  4. Start with a context-level diagram and break it down only where needed.