Living Fieldbook · Field mission

Systems thinking · Up to 15 min · Works on any public product

Map one dependencywhose failure wouldbreak what comes next.

How to go about it

Pick a step in a public product, like payment or a confirmation email. Note what it depends on and what depends on it, from what you can see.

What counts as evidence

The step, what it depends on, and what waits on it.

A good observationThe order is not confirmed until the bank’s check page loads; when it timed out, the cart emptied anyway.
Take this mission

Opens Living Fieldbook in this browser. No account; your notes stay on your device.

One real observation at a time. What you saw is kept apart from what you think it means.