The Orchestrator

Some routine roles will shrink, and the organization should say so plainly rather than promising that every person will become an orchestrator. Some people will need time and training, some will move into evaluation, operations, customer exceptions, domain work, or specialist roles, some will leave, and some simply will not want the new work.

The right response is neither to deny the change nor to treat displacement as an individual failure. It is to assess the work honestly, provide training tied to real systems, give people a path to new responsibilities, and make staffing decisions in the open. The failure modes of doing this badly — headcount theater, Solo Sovereign executives, replacement dressed as modernization — are covered in Chapter 9.

Expect the longer-term work to get more complex even as routine tasks get cheaper, because a business objective typically combines customer effort, revenue, reliability, privacy, regulatory requirements, and operational cost. Somebody has to set those goals, negotiate the tradeoffs among them, and decide how much authority the system should hold.

HQ 6 — Assembled. The human and AI each wrote portions of this chapter. I assembled, reviewed, and take responsibility for the whole; the voice and arguments are mine, and I know which parts are which.