When agents do part of the work, the work of whoever directs changes in nature: it stops being doing and becomes choosing what gets done, explaining it well, reviewing what comes back and deciding. It is, in essence, the work of someone who leads a team.
Addy Osmani, a software engineer, summed it up in November 2026 in an article titled «Your coding agents made you a manager»: whoever spends the day working with agents is already managing, and the skills for directing agents are nearly the same as those for directing people. His piece is about agents that write code; what follows carries the idea over to a business, and it applies equally to an independent professional working with a team of agents: in that case, the person who directs and the person who does the underlying work are the same, and what changes is how much of that work can be delegated without losing judgment.
A clear request
A well-built business factory that receives a poorly explained request quickly produces a wrong result. The quality of what comes back depends, to a large extent, on the quality of what was asked. A good request states:
- what is to be achieved, not just what to do;
- what the role cannot know on its own: the context, why now, what has been tried before;
- what is left out;
- how it will be known that it is right: the signal for «done».
Example. «Improve contact lens sales» is a loose idea. A clear request would be: that inquiries about contact lenses get answered in under an hour during store hours; today they take half a day because nobody checks messages in the afternoon; prices are not to be touched; it is right when the following month's response time drops below one hour.
The rule from chapter 11 helps with the last point: before starting something large, whoever receives the request states what they understood and when they will consider it done. If they understood it wrong, it is corrected in one line.
Delegating the task, not the judgment
Not everything is delegated the same way:
| Delegated entirely | Delegated with checkpoints | Stays in a person's hands |
|---|---|---|
| repetitive work with clear rules: follow-ups, reminders, reconciliations | what touches other areas or important customers | what the business sells, at what price, whom it hires, what gets published |
| drafts that someone will review | what changes data others use | what cannot be undone |
The business factory already comes with part of this (roles ask before doing what their rules tell them to ask about, and they flag what cannot be undone), but where each line of that table falls is decided by whoever directs, who writes it into each role's instructions and rules.
Asking for proof, not promises
A role that says «done» has to be able to show why: the number, the document, the message sent. It is worth always asking how it is known, and, over time, it is worth having the roles answer that without being asked. It ends up as a business instruction: every «done» comes with its evidence.
Reviewing what is worth reviewing
The attention of whoever directs is the scarcest thing in the business, and the measure from chapter 11 (attention per task finished right) also applies to one's own work. Some reading is the work itself and is not cut: a text that will go out signed, a strategy, a fine-grained decision. And some reading serves only to check, and that is cut, with better requests, with evidence in every delivery and with rules the role already follows on its own.
Fewer open fronts
That an agent can start many things at once does not mean it should. Each open front is one more thing to review and decide. It is better to have few pieces of work in progress, finished well, than many half done, and to decide before starting something large when it would be stopped if it does not work.
Closing the loop
Each time something went wrong because of a confusing request or a missing rule, it is worth not just fixing that one case but changing the instruction, the skill or the rule so it does not happen again. A correction made twice is a sign that structure is missing. That way the business factory learns from the corrections of whoever directs it, and each month it asks for a little less attention.
In short, directing a business factory means asking clearly, delegating the task while keeping the judgment, demanding evidence, guarding one's own attention, limiting open fronts and turning every correction into structure. The next chapter looks at what a business factory costs and how its quality is maintained.