Journal · The AI Architect · 2026-08-30
Give a helper one clear, bounded job. "Handle everything" isn't a task — it's a shrug that produces a mess.
Give a helper one clear, bounded job. “Handle everything” isn’t a task — it’s a shrug that produces a mess.
The tension isn’t really about laziness or vagueness. It’s about control. When you hand someone — or something — an open-ended mandate, you get to feel like you’ve delegated without actually giving up the specifics. You’ve kept your hands clean of the details while still hoping the outcome matches what was in your head. That gap between what you imagined and what you said out loud is where the mess comes from.
Name the job, not the outcome
“Handle my inbox” sounds like a task. It isn’t. It’s a wish. Handling an inbox could mean archiving newsletters, drafting replies, flagging urgent items, unsubscribing from noise, or all four in some order you haven’t specified. A helper — human or otherwise — has to guess, and guessing at scale produces inconsistency. One day it archives things you wanted kept. The next day it drafts a reply in a tone you’d never use.
The fix is almost boring in its simplicity: separate the outcome you want from the job you’re assigning. The outcome is “my inbox feels manageable.” The job is something like “move anything from these three senders into a folder, and flag anything with ‘invoice’ in the subject.” The second version can actually be checked. You’ll know within a day whether it worked.
Try this: take one thing you’ve been meaning to delegate — to a person, a tool, an automation — and write the instruction twice. First, write it the way you’d normally say it out loud. Then rewrite it so a stranger with no context could do it correctly on the first try. Notice what disappears between version one and version two. That gap is usually where the vagueness was hiding.
Bounded doesn’t mean small
People sometimes hear “give a bounded job” and assume it means give a tiny, trivial job. That’s not the idea. Bounded means the edges are visible. A helper can be handed something genuinely large — reorganize a filing system, draft a first pass of a report, manage a whole category of scheduling — as long as the edges of that job are clear: what’s in scope, what’s out, what counts as done, and what to do when something doesn’t fit the plan.
Without edges, even a capable helper starts improvising in ways you didn’t authorize. It’s not because it’s careless. It’s because “everything” has no natural stopping point, so it invents one, and the one it invents is rarely the one you had in mind.
Try this: for any job you’re handing off, write one sentence that starts with “This does not include…” Naming the boundary is often more clarifying than describing the task itself. If you can’t finish that sentence, the job probably isn’t ready to hand off yet.
Build in a way to check
A clear job isn’t just easier to do — it’s easier to verify. This matters more than it sounds like it should. Vague assignments don’t just fail more often; they fail invisibly. Nobody catches the drift until it’s compounded for weeks. “Handle it” gives you no way to know if it’s being handled well, badly, or not at all, until something breaks in a way you notice.
A bounded task, by contrast, comes with its own report card. “Sort emails from these senders into this folder” is easy to spot-check. “Handle my inbox” is not. The clarity you put in up front is the same clarity you get to use later when you’re deciding whether the arrangement is working.
Try this: before handing off any task, decide in advance what “done well” looks like, in a form specific enough that you could check it in under a minute. If you can’t imagine that minute-long check, the task is still too loose.
None of this is about distrust. It’s about respect, actually — for the helper’s time and for your own. Vague instructions don’t feel generous; they feel like an unfair test with no visible rules. Clear, bounded jobs let a helper actually succeed, and let you actually notice when they have.
This is one small piece of a larger habit — thinking clearly about what you’re asking for before you ask for it — that I get into more fully in the book, with more examples of what bounded work looks like across different kinds of helpers. But the shift itself is small enough to try today, on the next thing you were about to hand off with a shrug.
Go deeper. The full method is in The AI Architect. New here? Start with the free companion pack, or explore the series.