One short assignment can create a great deal of unnecessary work. “Please look at this report,” “Please handle it quickly,” or “Please prepare a proposal” may sound clear when two people are standing beside each other. Yet the recipient must guess what needs changing in the report, whether “quickly” means today or this week, and whether the proposal is for internal feedback or a customer presentation. When the work returns below expectations, both often say they understood it differently. In fact, the work started with a gap no one named.
Clear delegation does not mean that a manager writes every step for someone else. Its purpose is to agree the result to achieve, the boundaries to respect, and the time to speak again, so the person doing the work has room to choose the method. A good request helps them decide most of the work without repeatedly asking, while helping the delegator know when to review rather than intervening too late after the work has drifted.
Separate an outcome from an activity
An activity describes what someone should be busy doing: reading documents, contacting customers, building a table, or organising a meeting. An outcome describes something that can later be checked: a three-page summary with three options and a recommendation, a verified customer list using stated criteria, or a meeting plan with an owner and objective for each session. When only activity is assigned, a recipient can do a great deal and still fail to create what the manager needs for a decision.
A good outcome is specific enough without locking the method. Instead of saying “research competitors,” say: “By Thursday, prepare a comparison of five direct competitors by segment, price, message, and evidence of distribution channels; identify three implications for our choice.” The recipient knows the standard of completion, while the way they find evidence, present it, and sequence their work remains within their control.
| Element to agree | Short question | Value |
|---|---|---|
| Required result | What is the final product, and which decision will use it? | Prevents work that is correct in activity but wrong in purpose. |
| Good-enough standard | What is essential, and what is not needed yet? | Avoids both superficial work and overwork. |
| Boundaries | Which budget, data source, audience, or risk must be respected? | Helps the recipient choose an appropriate route independently. |
| Check-in point | When should they flag an issue or seek a decision? | Finds drift while it is still easy to correct. |
Set a “good enough” standard instead of demanding perfection
Many tasks run late not because the recipient lacks ability, but because they do not know where to stop. If an analysis will be used to select three potential partners, it must be reliable on the deciding criteria; it does not need to become a full market report. If a draft will be used to obtain internal feedback, its argument structure and open questions matter more than finished wording. Stating the desired level of completion helps a team place its time where it matters.
The standard should also connect to evidence. “Make it more convincing” is hard to act on unless it says for whom and on what basis. “Include two figures with clear sources, one customer example, and one recommendation with conditions for implementation” can be checked. This does not make work mechanical; it lets creativity go into the part that needs creativity rather than into guessing intent.
Example: assigning preparation for a customer meeting
A team lead tells an employee, “Prepare carefully for the meeting with Customer A.” The employee may spend a full day making slides yet miss what the manager needs. A clearer request is: “Before 4 p.m. today, send a one-page brief covering the meeting objective, three customer issues supported by interaction history, two proposed options, and the question that requires the director’s decision. No slide design is needed; prioritise checking the usage data and attendance.” The recipient now knows the outcome, boundary, and point to flag; the meeting is also more likely to reach a concrete next step.
Create a check-in point, not another layer of permission
A check-in point is not a meeting to report every piece of progress. It is the moment when both parties need to speak because the work has met an important assumption, risk, or choice beyond the recipient’s authority. For example, an owner may contact customers on an approved list independently but must flag a request for terms that differ from policy. When this boundary is clear, the recipient does not seek approval for every detail and the manager is not surprised at the end.
For work that lasts more than a few days, agree a short early draft or mid-point update. Its content should be tied to what must be decided: has the hypothesis changed, is the evidence sufficient, or does the scope need adjustment? Asking “how far along are you?” normally produces a description of activity. Asking “does the expected outcome still meet the original purpose?” produces a more useful conversation.
Build a habit of feedback on the request, not only the result
A mature team should allow the recipient to respond as soon as work is assigned: “My understanding is that the outcome is…, the standard is…, and I will flag it if…; is that correct?” This brief response is not bureaucracy. It finds differences before time has been spent. The delegator also learns to see gaps in their own request, rather than assuming that others share the same context.
Good delegation creates the capacity to work independently, not dependency. When outcome, standard, boundary, and check-in point are clear, the recipient can use their expertise to find a route. The manager can focus on the choices that genuinely require their accountability. The result is not only fewer revision loops, but a team that knows how to turn a request into work that can be completed and verified.
