18.7 What “more will be required” turned out to mean

Book 1 · Your Next Job TitleWhat More Will Be RequiredBook 3 · The Orchestrated OrganizationThe Purpose Put Into the Machine · section 7 of 9

The Introduction’s promise came with a second half: more may be achieved, and more will be required. I can now say what the requirement is for each of the three readers the book addressed.

For the individual, it is a system model you can trace by hand before anyone gives you authority over the system — Chapter 12 follows Marcus, a mid-career engineer the book uses to show what that trace looks like when someone does it for the first time; Chapter 2’s register, kept so a colleague can take the work over; and the willingness to be less necessary. The concrete version, this week: pick one recurring task you already do with AI assistance and write down what evidence you would need before you let it act without you. That list is your first delegation contract, and no one has to grant you a title to write it.

For the manager, it is staffing the review queue as the production system it is, before it turns into a rubber stamp, as Chapter 10 warned; writing the approval map before the first proposal crosses a boundary rather than during the first incident; and treating cost as Chapter 15 does, as a constraint designed in advance. The concrete version: take the next proposal on your desk that touches an agent or a model, and write down who reviews its output, on what cadence, funded from which budget. If no one is named, the review is fiction and the proposal is not done.

For the organization, it is building the path before removing the rung, in Chapter 12’s phrase, and funding Chapter 11’s ninety days rather than announcing a transformation; Chapter 16’s infrastructure, which records the conversation as well as the code so the evidence chain exists at all; and Chapter 14’s security, owned as a discipline. The first organizational step is smaller than a transformation: choose one workflow that crosses a department boundary, delegate it deliberately, write the approval map down, and let the ninety days produce the evidence the rest of the company will actually believe. None of that is a slogan’s second half anymore. It is a budget line, a staffing decision, and a policy someone has to sign.