Published August 28, 2026 · Hoopi team
A prompt is a request. A brief is a contract.
When someone asks Hoopi for 'a report on last month', they get something reasonable and generic, and then spend twenty minutes explaining what they actually meant. When they ask for the same thing the way they would ask a new analyst — here is the audience, here is what decision it feeds, here is what good looked like last time, here is what to do if the numbers disagree — they get something usable on the first pass.
That is not a prompting technique. It is the same skill that makes someone good at running a team, and it transfers almost perfectly.
The four things a good brief contains
Purpose: what decision this feeds, and who makes it. Scope: what is in and, more usefully, what is deliberately out. Standard: an example of what good looks like — the last version somebody was happy with. Escalation: what to do when the inputs disagree or something is missing.
Managers who write all four get consistent output. Managers who write none of them get exactly what an under-briefed new hire would produce, which is to say: an attempt.
Where it differs from managing a person
Two things are genuinely different. First, the correction loop is much shorter — a fix you make once holds permanently and applies to everyone, rather than being relearned by each new person. Second, you can be far more explicit about the failure mode than would be polite with a colleague: say plainly what should stop the work and get escalated, and it will stop.
That second one is where most of the trust comes from. Teams that specify the stopping conditions end up delegating far more, not less.
Want to try this on your own worst task?