Method

From a tangle to a route map.

Five phases. Each ends with something you can read and approve.

1. Trace

We follow data from where it is created to where it is finally used, interviewing the people who touch it along the way. The hidden steps matter most: the column someone deletes before forwarding, the lookup someone does from memory.

You approve: a current-state map of the route.

2. Name the boundaries

Every change of owner, system or format is marked as a handoff. Some disappear once the route is drawn; others turn out to be the source of most problems.

You approve: a list of handoffs with an owner on each side.

3. Describe the steps

Transformations are written in plain sentences before they are built. "Combine first and last name with a single space." "Exclude orders with status Cancelled." Each sentence can be questioned by someone who knows the data.

You approve: transformation descriptions and handoff agreements.

4. Rehearse

The flow runs end to end on dummy or approved test data. Receivers look at the result in their own tools. Surprises at this point are cheap.

You approve: rehearsal output, checked by the receiver.

5. Run and record

The flow goes live on its schedule. Each run produces a record. After the first few runs we review together whether the agreements and checks are pitched right.

You receive: run records and a short review after the early runs.

Before any real data moves