Delegation Briefs: Task Instructions vs Outcome Briefs
Rowan & Pike closes 46 client books in the first nine days of every month with a staff of nine, and in September two associates rebuilt the same bank reconciliation three times because the brief they were handed said only “tidy up the bank recs.” That one vague phrase cost roughly eleven hours across three people. The partner did not have a motivation problem on the team; she had a brief problem, and it was written the same way for a mechanical task and an investigative one.
A delegation brief has a style, and the style should match the work. The table below maps a delegation scenario to a brief style, then a copy-paste prompt follows for each, then the cost of choosing the wrong one. Where the work must be repeatable across months, the writing discipline in our AI SOP workflow keeps the brief and the procedure in the same place.
Brief Style Decision Table
| Delegation scenario | Brief style | When it pays off | Risk if misused |
|---|---|---|---|
| A repeatable month-end task with one correct method | Task instructions | A new associate needs the exact sequence in order | Teaches steps, not judgement, and breaks when the client changes |
| A reconciliation with three possible causes | Outcome brief | The associate must investigate and report a finding | Drifts without a sharp definition of done |
| First time an associate owns a whole client book | Task instructions plus a worked sample | Removes guesswork on a live client file | Slow to write, and the sample must be current |
| A reviewer who knows the standard but not the path | Outcome brief | Saves the partner time and builds ownership | Needs trust and a fast review loop to be safe |
| An urgent filing with a hard external deadline | Task instructions | No interpretation is possible under time pressure | The associate learns nothing and stays dependent |
One question separates the rows: is there a single correct method, or is there a result with several valid routes to it? If a client’s VAT treatment has one approved procedure, write instructions. If the question is “why is this ledger out by 2,400 dollars,” write an outcome and name the evidence you want back.
Choosing Between Instructions and Outcomes
Task instructions suit work where the method is fixed and the associate is new. Closing the depreciation schedule at Rowan & Pike is a fixed sequence, and a first-timer who improvises it creates rework the partner has to unpick. Instructions also protect you when the deadline is hard. On the third of the month, nobody has time for a discovery journey.
Outcome briefs suit work where the method is the interesting part. “Find out why the Bank of Fennimore reconciliation is out by 2,400 dollars and tell me what you changed” is a real piece of thinking, and the associate will learn more from solving it than from following steps. The price is that you must define the finish line precisely, or the brief becomes an invitation to wander.
Instructions and outcomes also age differently. A step list goes stale the moment a client changes software or a rule changes, and a stale list is worse than no list because it produces confident errors. An outcome brief survives process changes, because it names a result. If you rewrite the same instructions every quarter, that is a signal to convert them into an outcome plus a short definition of done. For the boundary between a brief and a job description, the structure in our job description prompt keeps the two from drifting apart.
Mixing styles inside one brief is where most of the damage happens. A brief that lists four ordered steps and then adds “and generally make the account better” sends two signals at once: follow the method, then use your judgement. The associate picks one, usually the safer steps, and the vague clause is quietly ignored. Keep each brief to a single style. If a task genuinely needs both, split it into two documents: a short instruction block for the mechanical part, and a separate outcome for the investigative part.
Prompts for Each Brief Style
Task instructions. A numbered sequence with owners and stop points.
You are a partner at a nine-person accounting firm writing a task brief for an associate. Task: close the bank reconciliation for client "Harbrook Joinery" for month end. Produce a numbered list of steps in the exact order to perform them, naming the file or screen for each step. Mark every point where the associate must STOP and ask you rather than guess. Add a 3-line definition of done at the end. Write for someone doing this for the first time.Outcome brief. A result to reach, the evidence to bring back, and the limits.
Write an outcome brief for an accounting associate. The result: explain why the Bank of Fennimore reconciliation is out by 2,400 dollars and correct it. Specify: the evidence to bring back (the transaction rows, the cause, the fix), the deadline (end of day Thursday), and the two constraints (do not post an adjustment over 500 dollars without approval, do not contact the client directly). Do not describe how to investigate. Define what "done" looks like in two sentences.Hybrid for a first-time owner. An outcome with a worked sample attached.
Draft a brief for an associate taking ownership of client "Calla & Sons" for the first time. State the outcome: a clean month-end close by day nine. Attach a short worked example from a previous month showing one completed reconciliation, labelled "this is the standard". Then list three checkpoints where the associate reports back. Keep the outcome clear and the example clearly marked as a reference, not a template to copy blindly.The Real Cost of the Wrong Brief
Give task instructions for investigative work and you get compliance without thought. The associate follows the steps, reaches the end, and reports nothing useful, because the brief asked for activity rather than an answer. This is the “tidy up the bank recs” failure: three rebuilds, no diagnosis, eleven lost hours.
Give an outcome brief for mechanical work and you get variation. Two associates close the same schedule in two different ways, the partner reviews both, and the firm slowly accumulates five versions of one procedure. On a nine-person team, that is how quality drifts.
The hidden cost is the review loop. A good outcome brief is only as safe as the speed at which the partner reads the result back. If review takes four days, the associate has already moved on and the learning is lost. On a small team, pair every outcome brief with a same-day or next-morning review slot, or the brief quietly turns back into instructions.
Measure the fix the same way you measured the problem. Count rebuilds per close and questions that arrive after the deadline. At Rowan & Pike the September baseline was three rebuilds on one reconciliation. A clearer brief should hold that at zero while keeping the associate’s own judgement in the loop.
Then change one thing at a time. Rewrite a single brief, keep the rest as they are, and watch the questions that come back in the next close. If an outcome brief produces three “what do you mean by” emails, the definition of done was too soft, not the style. If an instruction brief produces a correct-but-thin result, the task was probably investigative all along and should have been an outcome. On a team of nine, that two-week loop of small rewrites is the cheapest training any associate will get.
Sources & Notes
These prompts describe a small accounting practice delegating month-end close work, but the instructions-versus-outcome split applies to any delegation where some tasks have one method and others do not. Rowan & Pike, the associates, Harbrook Joinery, Calla & Sons, the Bank of Fennimore, and the 2,400 dollar variance are illustrative examples, not real firms or figures. Re-check any brief that cites a specific filing rule, because accounting standards and tools change.
