What hands over, and the cutover it belongs to

What this studio does

A process map holds two states. Where an activity is performed by a person today and by a machine in the future, something has to hand over — and that handover has to be rehearsed, reconciled and reversible. This studio reads those handovers off the map, and then asks the two questions a transition plan has to answer for each: which cutover does it go live in, and who takes it back if it does not work.

It refuses the shortcuts that would make it look more decisive than it is. Whether a cutover touches the close, cash or tax is declared, because nothing in the map records it and a plausible correspondence is not a stated one. A changeover that writes data is told apart from one that only reads it, because that is observable. A design that hands nothing over is reported as unstarted rather than as safe.