Chapter 13 · Learn to Work With the Machine

Steer or
dispatch.

An extract from Eat. Shift. Or Die. by Phil Gray

Some work needs steering, because the purpose is still forming. Good is difficult to describe, and the task contains taste, politics, trade-offs or a question you do not yet understand. So you stay close. You talk, inspect, redirect and discover the problem alongside the system. Writing a chapter like this sits in that category, and so does deciding what a weak signal means for your organisation, or whether a technically good answer is the wrong answer for the person who will receive it.

Other work can be dispatched. The outcome has edges, the sources are known, and the process is stable enough to describe. The result can be tested, reconciled or checked against evidence, so you assign the job, let the system work and inspect what returns. Searching a large transcript collection for every discussion of apprenticeship can be dispatched. Deciding what apprenticeship should mean in this book cannot.

The mistake is to dispatch ambiguity and steer routine forever. If you send away work whose purpose and quality bar remain unclear, the system will make decisions you didn't realise you had delegated. If you stay in a microscopic conversation after the job has become repeatable, you turn leverage back into supervision. The choice isn't a personality type. It changes with ambiguity, consequence and verifiability. Stay close when meaning is moving, step back when the work can show its paper trail.