"Just handle the inbox" is not a brief. It's a hope. And hope is why most delegation quietly fails — not because the person you handed it to wasn't capable, but because what landed in their head was never quite what was in yours.
A good brief isn't longer. It's more specific about the three or four things that actually cause mistakes, and silent on everything else.
Start with the outcome, not the steps
"Reply to customer emails" describes an activity. "Every customer hears back within four hours, in a tone that sounds like us, with refunds handled per policy" describes a result. Steps change constantly. The outcome is what you're actually delegating — lead with it, and let the person figure out the steps, checking in only if theirs don't match yours.
Name the judgment calls, not just the tasks
The instructions are rarely where delegation breaks. It breaks on the edge cases nobody wrote down — the angry customer, the vendor asking for a discount, the email that's technically urgent but not really. Spend your brief-writing time on these, not on the routine 80% that's usually self-explanatory.
Give one example of done right, and one of done wrong
Descriptions of quality are abstract. Examples aren't. A real sample reply you're happy with, next to one you'd have rewritten, teaches more in thirty seconds than a paragraph of adjectives — "professional," "friendly," "concise" all mean something slightly different to everyone who reads them.
Say what should never happen
Most briefs describe what to do and skip what not to do, which is often the more expensive gap. "Never issue a refund over $200 without checking with me" prevents more damage than ten paragraphs of positive instruction. A short list of hard lines does more work than people expect.
Put it somewhere that outlives the conversation
A brief given once, verbally, in a rush, gets remembered imperfectly and then not at all. The same brief written down — even messily — becomes something to check instead of guess from, and something the next person can read too. It doesn't need to be polished. It needs to survive longer than the meeting where you said it.
None of this replaces the ongoing back-and-forth of working with someone well. But a brief that names the outcome, the judgment calls, and the hard lines up front means that back-and-forth starts from a much better place — and that's exactly what a trial period is for: testing the brief on real work before anything's locked in.
