How can I delegate a task when the outcome matters more than the exact method?

Separate the brief into four parts: the outcome, the constraints, the choices the person owns, and how you’ll stay aligned. “Use your judgment” by itself can sound freeing but leave someone unsure what counts as success.

Start with an observable result: what should be ready, for whom, and by when? Add a way to tell whether it meets the need. Avoid prescribing steps unless a step is genuinely required. For example, “Prepare a one-page decision summary for the team’s Tuesday meeting, with the options and trade-offs clear enough for us to choose” describes a result. “Make a slide deck in the format I usually use” specifies a method and may not be necessary.

Then distinguish what must stay fixed from what can change. That distinction lets the person choose an approach while still knowing where the boundaries are.

Include only boundaries that would make a reasonable approach unacceptable or create a problem if overlooked. These might be a deadline, an agreed scope, a required audience or format, a budget limit, or a review that must happen before sharing the work. Don’t add preferences just because they’re familiar; label them as preferences if they’re useful but not mandatory.

Make each boundary concrete. Instead of “keep it appropriate,” say what that means for this task: for instance, “Use the approved project figures, and don’t send the summary outside our team before I review it.” Treat that as a hypothetical example and replace it with the actual requirements for your work.

If you’re unsure whether a detail is essential, ask yourself: would I reject a good result just because this detail was handled differently? If not, it probably belongs among the person’s choices, not the constraints.

Name the decisions the person can make, the decisions you need to make, and the circumstances that call for a conversation. For example: “Choose the research approach and layout. You can adjust the order of sections. Check with me before changing the audience, due date, or agreed scope.” Tailor those examples to the actual task; don’t imply authority you haven’t been given.

Set a check-in around a useful decision point rather than asking for constant updates. You might agree to review an outline before the person spends time polishing the final version. Also name an escalation trigger, such as a key input arriving late or a constraint seeming impossible to meet. The goal is to hear early about changes that affect the result, not to supervise every move.

Here’s a reusable delegation brief. Fill in the placeholders together, and revise anything that doesn’t fit:

Task: [name the task]

Outcome: By [date], deliver [specific result] for [audience or use]. It will be ready when [observable completion criteria].

Fixed constraints: [deadline, scope, required inputs, format, review, or other true requirements].

Your choices: You may decide [methods, tools, order, or other choices within your authority].

Check with me before: [decisions outside your authority or changes that affect the agreed result].

Check-in: We’ll review [draft or milestone] on [date or decision point]. Contact me sooner if [specific issue or trigger].

Before you start, ask the person to summarize the outcome and the main boundary in their own words. That’s a quick way to notice different interpretations while there’s still time to adjust the brief. Agree on the brief, not just the task label.