Flow of Work

How work actually moves through a body — distinct from the network of promises that says it will.

Two different things are easy to confuse. A network of commitments is who has promised what to whom, by when: a structure of words. The flow of work is the physical reality underneath — where the work sits right now, what it is waiting on, how long it waits, how often it goes backwards for rework, and where it piles up. A body can have a perfect network of promises and a terrible flow (Networks of Commitments, The Life of a Commitment).

Seeing it requires walking the actual path of one piece of work from beginning to end and noting every step, every wait, and every handoff. What that exercise reliably reveals is that the great majority of a thing's life is spent waiting rather than being worked on — which means that speeding up the working changes almost nothing, and removing the waiting changes everything (Value Stream Mapping, Waste, Throughput).

It is load-bearing because it redirects effort to where the gain is. Bodies under pressure reflexively work harder at the steps they can see themselves performing, and the steps are rarely the problem. Flow points instead at the joins: the handoff that sits over a weekend, the approval that waits for one person, the piece that is started before it is ready and comes back (Bottleneck, Limiting Factor, Make-Ready Process, Buffer).

Its disciplines follow directly. Release work at the pace the narrow place can take it, rather than at the pace it arrives (Pull planning, Work In Progress). Let nothing enter a week that is not actually ready (Constraint, The look-ahead). And make the movement visible, so that a pile-up is seen by everyone rather than discovered at the end (The Board, Work Deck, Data Date).

Also called: how work moves Stands on: Flow · Throughput · Value Stream Mapping Opens onto: Bottleneck · Limiting Factor · Work In Progress · Pull planning · Make-Ready Process · The Board · Work Deck · Waste · Last Planner System · Networks of Commitments · Just in time In play: Home — walked once, then watched weekly Sources: the Concept Ledger v2, §K.3 birth list and §4 on the thin practice layer, which names it as an operational hinge that is red or stub while the cosmology is covered (draft) · Value Stream Mapping, Flow, Throughput (wiki) · Projects/the term pages/Bottleneck.md (draft) · lionsberg.wiki: Value Stream Mapping Open: Named in the canon's own birth list and nowhere written; an earlier grouping folds it into value-stream mapping as an alias, which loses the distinction from the network of promises that is the point of the term.