Data Flow Map

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

SymbolNameMeaning
OGetSource a single location of data
XFixFormat, reorder, or extract useful data
+MixIncorporate other sources
vCutDrop the unwanted data
^KeepKeep the data that matters
\SortOrder most to least important
]BoxSummarize the data into buckets
#SizeMeasure the size of the buckets
=ShipDeliver 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:

Load Sales Data

Monthly pipeline for the sales dashboard

@extract

O
Get
Pull CRM export
+
Mix
Join region table
X
Fix
Fix date formats

@report

v
Cut
Keep revenue columns
\
Sort
Rank by revenue
]
Box
Bucket by quarter
=
Ship
Publish dashboard