You will be able to brief a task by stating the result you need, the limits that apply and the deadline.
Pick a task you plan to hand to someone in the next few weeks, and write down in two or three lines how you would explain it to them. Then look at what you wrote. If it reads as a sequence of actions, such as "export this, copy that, send it to me", you are asking that person to act as your hands.
Someone can follow a list of steps without understanding why each step exists, so they don't learn why. If anything changes, for example the CRM export looks different from the one the list describes, they get stuck, because the list was all they understood. They come back to you as soon as a step doesn't match what they see. When the work is finished, they have learned nothing and they own nothing.
When you describe the result you need and why you need it, you hand over the thinking along with the work. Working out how to reach the result is how the person builds the skill, and they may find a better way than yours. They may also make mistakes you would have avoided, which is part of the price of having someone other than you able to do the work.
Wei Ling is a team lead in an example company. Every quarter her team surveys 40 business clients on satisfaction and writes up the results for Daniel, the head of operations. She has run the survey herself for two years, and this quarter she is handing it to Farid.
Her first draft of the handover message was a numbered list of fourteen steps. It began with exporting the client list from the CRM, filtering out inactive accounts, copying last quarter's survey form and changing the date in question 2, and it ended with sending the summary to her for checking. If the screen stopped matching the list at step 9, Farid's only option would be to message her and wait for an answer. She rewrote the message as a brief.
A brief is a handover that describes the result you need and why it's needed, and leaves the person to work out the method. A brief written this way usually covers five things. Each part below is followed by what Wei Ling wrote for Farid.
What done looks like. Describe the finished result specifically enough that you would both recognise it. Wei Ling asked for a one-page summary with response rate, average scores, the three most common complaints and two suggested actions, ready for the head of operations. Why it matters. Say what the work is for and who uses it. Daniel uses the survey to decide which client accounts need attention next quarter, so the complaints matter more than the averages. Constraints. These are the limits the person must work within. Farid has to use the same questions as last quarter so the results can be compared, chase clients no more than twice, and raise any comment naming a staff member with Wei Ling before it goes into a summary. Deadline, plus any earlier dates that matter. The summary goes to Wei Ling by the 20th, which gives her two days before it goes upward. Who to ask. Name the people who can help and what each of them knows. Hui Min knows the CRM export, Wei Ling can explain any client history, and Daniel's assistant handles the distribution list.
A good brief leaves out the detailed steps. Wei Ling mentioned that last quarter's file was on the shared drive if Farid wanted to see an example of the finished work. She offered it as something to look at, and he was free to reach the result his own way.
Before the person starts, ask them to play the brief back in their own words. Present it as a check on how well you explained the task, so it doesn't feel like a test of their listening. You might say something like "just so I'm sure I explained it well, what are you aiming for?" A play-back takes about two minutes and catches most misunderstandings before they cost a week. If anything is off, correct it straight away.
When Farid played the brief back, he described the summary as "the average scores for each client". He had missed the complaints and suggested actions entirely, and those were the parts Daniel cared about. Wei Ling corrected him in thirty seconds at the start, which saved him from redoing the whole summary at the end.
If you have done lesson 4.3, "Clarify the task before you start", in the course "Communicate at work", you have seen the same check from the receiving side, when you are the one given the work. As the person delegating, your part is to invite that check.
Where you can, delegate a whole piece of work, meaning something complete the person can point to when it's done. "Run the client survey" is a whole piece. "Pull the client list for my survey" is a slice, where the person does one part of a task and you keep the rest.
Slices are sometimes necessary, especially with someone very new. A person who only ever does slices never sees the full picture, never makes the judgement calls and never gets credit for a result. They also stay dependent on you to stitch the pieces together, so you never get your time back. Whole pieces build ownership. Farid's summary goes to the head of operations with his name on it, which gives him something to talk about at review time and a reason to care about doing it well next quarter.
Detailed step lists are right for safety procedures, regulatory processes, and anything where order matters and a mistake is costly. In those cases the person should follow the steps as written. Explain why each step exists even then, because someone who knows the reason for a step is far less likely to skip it under pressure.
For most delegated work, the five-part brief does more than a step list. Take a task you are about to delegate and write it the same way Wei Ling rewrote hers.
Pick one task you are about to hand over and rewrite it 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).