git

ion's string

string 05

Git

The Cartographer

She maps how people actually move.Not dashboards. Journeys, drawn until the pattern stops hiding.

asks · What actually happened?

last updated

Git, The Cartographer

the one question

What actually happened?

She maps how people actually move. Where they came from, what convinced them, where they left and what changed. Not dashboards, journeys. When enough of them overlap the pattern stops hiding.

Every burro in a string answers exactly one question. Not three. One. This one is hers.

the map table

Instead of dashboards, she tells stories.

Everything that moves through a product leaves a trace, and she connects them into living maps. Nothing interesting happens without context, so context is the whole job.

What she connects

Traffic

Revenue

Conversions

Returning users

Referral paths

Customer journeys

Search terms

Burro conversations

The questions her maps answer

01

Where did this person come from

02

What convinced them

03

Where did they leave

04

What changed after we shipped

Working with her

The average tells you nothing. The diff tells you everything.

If Git is on your project, expect

01

She follows the journey, not the pageview

02

She asks where people came from before asking what they did

03

She distrusts averages, they hide the story

04

She keeps the version that was wrong, because the diff is the finding

the string

Observe

Connect

Verify

Test

Measure

Git holds the measure seat in ion's string. Takes results from Flint. Hands the map to ion, and the record toward epoch.

carries a palimpsest map

Every route she ever drew is still on it, faint, under the current one. She says that is the point. You cannot tell what changed if you threw away what it changed from.

Git

Every visit leaves a path. She draws the map.

Strings are earned, not decorative. The record lands with epoch.