Delegating a Task Without Abdicating It
The posture is easy to agree with and hard to execute. This is the part that is actually procedural: five steps you run once, before a task starts running unattended, so that autonomy is real and responsibility is still locatable afterwards.
Most setup advice stops at the posture: keep a human in the loop, stay accountable, do not just hand it over. All true, and none of it tells you what to do on the morning you actually turn something on.
The steps below are the procedural half. They assume you have already accepted the underlying position — that real autonomy inside a narrow, stated boundary is the thing worth building, and that responsibility does not transfer to the system doing the work. What follows is how you set one task up so both halves survive contact with a working week.
Run them in order. Steps two and three are where arrangements usually fail, and they fail quietly: the boundary gets written as a list of permissions with no edge, and the escalation cases get written as a category rather than as named people.
What this does not claim
- This does not claim following the steps makes an outcome correct. A well-bounded system can still be wrong; the point is that you can tell, and you know who answers.
- This does not claim all work is suitable for delegation. Some tasks fail step one and should not proceed.
- This does not claim responsibility can be transferred to a system.
- This is not legal or compliance guidance.
Steps
Pick a task shaped like watch this, remember this, or notice if this changes — not find opportunities, generate leads, or go look around.
You know it is done when: You can state the trigger and describe what a normal report looks like, without using the word maybe.
Write the box: what the system may do, and explicitly what it may not do inside that same domain.
You know it is done when: You can name at least one action the system is capable of, adjacent to its job, that it is forbidden to take.
List the cases that must come back to a person — anything needing constant clarification, a creative leap, a taste judgment, or reading how someone will feel.
You know it is done when: Each listed case has a named person attached to it, not a team and not an inbox.
Name who answers for the outcome, in writing, before anything runs.
You know it is done when: One person by name would be asked why did this happen, and they already know it.
Decide how you will find out the system has drifted, and make that a thing you receive rather than a thing you remember to check.
You know it is done when: There is a report you would still read on a week when nothing went wrong.
When not to use this
Do not run this for an action that is both irreversible and unsupervised — that is a different and larger decision than task setup. Do not run it for work whose value comes from judgment you cannot state out loud; if you cannot write the criteria, the system cannot hold them either.
FAQ
- What kind of task is actually safe to hand over first?
- The ones shaped like watch this so I do not have to, remember this so I do not carry it, and notice this if it changes. They have a stated trigger, a narrow domain, and an output you can recognise as normal or not. Open-ended tasks — find opportunities, go look around — have no boundary to state, which means there is nothing to hold the system to.
- Why does the boundary have to say what the system may NOT do?
- Because a boundary stated only as permissions has no edge. A system with genuine autonomy will meet cases the permission list never addressed, and without a stated prohibition the honest default is unclear. Naming one adjacent action it is forbidden to take is the cheapest way to find out whether the boundary is real or decorative.
- Doesn't naming a responsible person just create a scapegoat?
- It creates a locatable owner, which is the opposite. The failure this prevents is diffusion — an arrangement where something goes wrong and the honest answer to who owns this is nobody in particular. Responsibility does not transfer to a process, so if no person is named it has not moved anywhere; it has only become harder to find.