What should I include when delegating a task someone has never done before?

Start with the result and the boundaries, not a script of every action. A first-timer needs to know what the work is for, what a good result includes, when it is due, and which choices they can make themselves. Then provide a useful starting point—such as an example, a template, or a short list of things to consider—and agree on a check-in while there is still time to adjust.

A practical rule is: be specific about outcomes and constraints; be open about the method. If there is one required process, explain why it matters. If several approaches could work, say so explicitly. Avoid presenting your preferred method as mandatory unless it really is.

Cover five points in plain language:

1. Purpose: Who needs the result, and what will it help them do?
2. Deliverable: What should the person hand back? Describe its contents and format if those matter.
3. Success criteria: What must be true for you to consider it ready? Separate essential requirements from preferences.
4. Boundaries: What is in scope, what is not, and which decisions need your approval?
5. Timing and support: When is the final deadline, when should you review progress, and where can they find examples or help?

Ask them to summarize their understanding in their own words. That is a quick way to catch different assumptions before they spend time on the wrong result.

Here is a copyable example. The details are placeholders, so replace them with your actual expectations:

Task: Prepare a summary of the [team meeting] for [intended readers].

Purpose: Help colleagues who were not there understand the decisions and follow-up work.

Deliverable: A [one-page document or agreed format] with the main topics, decisions, action items, owners, and due dates where they were stated.

Ready when: The summary is easy to scan, distinguishes decisions from discussion, and does not present an uncertain point as settled. Mark anything unclear for confirmation rather than guessing.

Boundaries: Use the meeting notes and materials in [agreed location]. Do not add new recommendations or circulate the draft beyond [agreed audience] without checking first.

Timing and support: Send me a rough draft by [check-in time] and the final version by [deadline]. I can answer questions or review the outline. You can choose the headings and wording.

This sets a clear destination while leaving room for the colleague to organize and write the summary in their own way.

Agree on a small, useful check-in rather than asking for constant updates. For a task with an unfamiliar format, an early outline or sample section may be enough to confirm that they have interpreted the brief correctly. Ask what they have decided, what remains uncertain, and whether they need a decision or resource from you. Give feedback against the success criteria, with a clear distinction between required changes and optional suggestions.

If the work is off track, identify the gap and ask the person to propose a next step before you take over. You might say, “The draft needs clearer action owners to meet the brief. What approach would you use to revise it?” If a decision is yours to make, make it promptly; if it is theirs to make, let them own it. Afterward, discuss what guidance helped and what would make a future assignment easier.