You will be able to brief a task by the result you need, the limits that apply and the deadline.
Every quarter, Wei Ling's team sends a short satisfaction survey to its 40 business clients and writes up the results for the head of operations. Wei Ling has done it herself for two years. This quarter she has decided Farid will do it. Her first draft of the handover message is a numbered list of fourteen steps: export the client list from the CRM, filter out inactive accounts, copy last quarter's survey form, change the date in question 2, and so on down to "send the summary to me for checking".
It is a thorough list. It is also a good way to make sure Farid learns nothing, owns nothing, and comes back to her the moment step 9 doesn't match what he sees on screen.
When you hand someone a list of steps, you are asking them to be your hands. They follow the list, and if the list is right, the work gets done. They don't need to understand why any step exists, so they don't. If something changes, say the CRM export looks different this quarter, they are stuck, because the list was the whole of their understanding.
When you describe the result you need and why, you hand over the thinking along with the work. The person has to work out how to get there, which is exactly how they build the skill. They might find a better way than yours. They might also make mistakes you would have avoided, and that is part of the price of anyone other than you ever being able to do it.
A brief that hands over a result rather than a recipe usually covers five things.
The first is what done looks like. Describe the finished result specifically enough that you would both recognise it. For the survey, that means a one-page summary with response rate, average scores, the three most common complaints and two suggested actions, ready for the head of operations.
The second is why it matters. Tell them what the work is for and who uses it. The head of operations uses the survey to decide which client accounts need attention next quarter. Knowing that, Farid will understand that the complaints matter more than the averages.
The third is the constraints: the limits they must work within. Use the same survey questions as last quarter so results compare. Clients are not to be chased more than twice. Any comment that names a staff member is to be raised with Wei Ling before it appears in a summary.
The fourth is the deadline, plus any earlier dates that matter. Summary to Wei Ling by the 20th, so she has two days before it goes upward.
The fifth is who to ask. Name the people who can help and what they know. Hui Min knows the CRM export. Wei Ling can explain any client history. Daniel's assistant handles the distribution list.
Notice what isn't there: the fourteen steps. If Farid wants to see how Wei Ling did it last time, last quarter's file is on the shared drive. He can use it as an example rather than a script.
Before the person starts, ask them to play the brief back to you in their own words. "Just so I'm sure I explained it well, can you tell me what you're aiming for?" Framing it as a check on your explanation, not their listening, keeps it from feeling like a test.
This takes two minutes and catches most misunderstandings before they cost a week. When Farid played the survey brief back, he described the summary as "the average scores for each client". He had missed the complaints and the suggested actions entirely, which were the parts Daniel cared about. A thirty-second correction at the start saved him from reworking the whole summary at the end.
If you have done Communicate at work, lesson 4.3, Clarify the task before you start, taught the same check from the other side, when you are the one receiving the work. Now you are on the side that should invite it.
Where you can, delegate a complete piece of work that the person can point to when it's done, rather than a slice of a task you keep the rest of. "Run the client survey" is a whole piece. "Pull the client list for my survey" is a slice.
Slices are sometimes necessary, especially with someone very new. But a person who only ever does slices never sees the full picture, never has to make the judgement calls, and never gets credit for a result. They also stay dependent on you to stitch the slices together, which means you never get the time back.
Whole pieces build ownership. When the survey summary goes to the head of operations with Farid's name on it, he has done something he can talk about at review time, and he will care about doing it well next quarter.
There are cases for detailed steps. Safety procedures, regulatory processes and anything where the order matters and a mistake is costly should be written down step by step, and the person should follow them. Even then, explain why the steps exist. A person who knows why a step is there is far less likely to skip it under pressure.
For most of the work you hand over, though, the five-part brief does more. Take a task you are about to delegate and write it the same way Wei Ling rewrote hers.
Rewrite one task you are about to hand over as a five-part brief: outcome, reason, constraints, deadline and contacts.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).