How Data Flow Map works
Data tracks what happens. Every analysis follows a repeatable pattern of motions —
source the data, focus on what matters, build the answer. A Data Flow Map documents
that path so it can be read, shared, and repeated.
The three motions
Source
Get raw data, mix it with other contexts, and fix it for analysis.
Focus
Select the columns, rows, and order that matter.
Build
Categorize and size the data into meaningful results, then ship them.
The nine symbols
| Symbol | Name | Meaning |
|---|
| O | Get | Source a single location of data |
| X | Fix | Format, reorder, or extract useful data |
| + | Mix | Incorporate other sources |
| v | Cut | Drop the unwanted data |
| ^ | Keep | Keep the data that matters |
| \ | Sort | Order most to least important |
| ] | Box | Summarize the data into buckets |
| # | Size | Measure the size of the buckets |
| = | Ship | Deliver final results |
Flows and tags
Steps group into flows — named sequences of motions. Each flow gets
an @tag so a map reads like a table of contents for the analysis.
A map, rendered
This is a real map, rendered by the same component the product uses: