The AI Delegation Cycle

The Delegation Cycle, five steps around a Drucker × principal-agent core: define the work, choose the right worker, set the autonomy level, check in mid-stream, own the outcome.

​

Step one: define the work. State the task, the outcome wanted, the constraints, and the standard of done. Give the context AI cannot infer: who the audience is, what good output looks like, what the red lines are. Thin briefs produce thin work, regardless of the worker.

​

Step two: choose the right worker. AI is not one worker. The model, the persona, the tools, and the documents in working context are choices about which worker is being asked. A coding model differs from a strategy model; a general assistant with no documents differs from one given the board pack and the last three minutes. Match the worker to the brief.

​

Step three: set the autonomy level. A capable worker on a familiar task gets latitude; a new worker on an unfamiliar task gets close supervision. The same calibration applies to AI. On a known task with predictable failure modes, AI produces and the leader checks the result. On a new or sensitive task, the leader stays in the loop at intermediate steps.

Step four: check in mid-stream. After the first pass, ask the model what it understood the brief to be, what assumptions it has made, and where it is least sure. The check-in is twenty seconds of additional prompting and the cheapest correction available. It is also the move most often skipped.

​

Step five: own the outcome. Whatever AI produces, when it leaves the leader’s hands, is the leader’s. The agent did the work; the principal owns the standard. AI does not absorb accountability; it only moves the labour.

​

Genesis

Two older frames sit underneath the cycle. Peter Drucker (1967, The Effective Executive) draws the line between specifiable work, whose result, constraint and standard of done can be stated at hand-over, and unspecifiable judgement-heavy work, which has to run through dialogue. Specifiable work is the proper subject of delegation. Principal-agent dynamics (Jensen and Meckling, 1976) names what goes wrong once the work is handed over: information asymmetry, goal divergence, monitoring cost. The classical fix is to design the relationship through clear result, calibrated autonomy, deliberate check-in, and accountable ownership. Both frames apply, unchanged, when the worker is AI. Monitoring cost becomes the most expensive of the three, because skipping the check-in feels free in the moment and is paid for downstream.

​

How ChangeSchool applies it with executives

We run senior teams through the Delegation Audit in three-hour cohort sessions. Bring a week’s worth of AI working sessions. Walk each one through the five steps; mark which were run, which were skipped. Most leaders find brief and check-in are the two regularly missing.

​

The discipline

Three habits embed the cycle. A weekly delegation audit, five minutes on a Friday, asks three questions of each AI working session: was a brief written, was a check-in run, was the output owned. A delegation template per recurring task: for any AI-assisted task done more than once a fortnight, write the brief once, save it, reuse it. A weekly twenty-minute session on a delegation skipped: identify one piece of work that could have been delegated to AI but was not, and run the cycle on it as practice.

​

The discipline is to make AI working sessions look, in the leader’s hands, the way good delegation to a capable colleague already looks.

​

​

​

‘AI is a worker, not a vending machine; delegate to it the way you delegate to people.’

​

​

Viren Lall, Managing Director,

ChangeSchool LDN (2026).

virenlall.com/ai-delegation-cycle

​

​

​