When delegated work comes back wrong, the usual explanation offered is a skill or effort gap, the person did not try hard enough or was not capable of the task. In practice, a large share of these failures trace back to something far more mundane: the person delegating never actually stated what "done well" looked like, and the person doing the work had to guess, using their own default assumptions, which frequently do not match the delegator's unstated picture.
The Assumptions You Are Not Saying Out Loud
Every delegated task carries invisible assumptions in the mind of the person assigning it: how polished the output needs to be, how much independent judgment is welcome versus how much should be checked first, what the real deadline is versus the stated one, and what "good" actually looks like in a concrete sense rather than a general one. None of these are obvious to the person receiving the task unless they are said explicitly, and most delegators do not realize how much they are leaving unsaid because the picture is so clear in their own head that they forget it is not automatically shared.
The fix is naming these dimensions directly, even briefly: "this can be rough, I mainly need the structure right, not the polish" or "check with me before you finalize anything customer-facing" removes an entire category of guesswork that would otherwise get filled in, often incorrectly, by the person doing the work.
Describe the Outcome, Not Just the Task
Instructions that describe only the task, "put together a summary of the meeting," leave the actual purpose of the output unstated, and purpose is what should shape most of the decisions the person doing the work will have to make: how long, how formal, for whom, emphasizing what. Describing the outcome instead, "I need a summary I can forward to the client that reassures them we're on track," gives the person doing the work a target to make judgment calls against, rather than a bare instruction they have to interpret from scratch.
Confirm Understanding, Don't Just Ask If There Are Questions
Asking "does that make sense" after giving instructions reliably produces a yes, regardless of whether the person actually has a clear picture, because admitting confusion in the moment feels awkward and most people default to nodding along. A more reliable check is asking the person to reflect the task back in their own words, "what's your plan for tackling this," which surfaces gaps in understanding immediately, while there is still time to correct them, rather than after the work is complete.
This connects to the broader discipline of giving feedback people can actually act on: expectations set clearly at the start of a task reduce the volume and severity of corrective feedback needed at the end of it, because fewer things go wrong that were never actually specified in the first place.
Revisit Expectations When the Task Changes
Expectations set at the start of a project often stop matching reality once new information emerges partway through, and failing to explicitly update them leaves both parties operating on an outdated shared understanding. A short check-in, "given what we've learned, does the original scope still make sense," prevents a slow drift where the delegator's expectations quietly shift while the instructions the other person is working from stay frozen at the original conversation.
Guidance on performance expectations published by the U.S. Office of Personnel Management at opm.gov consistently emphasizes that clearly communicated, specific performance expectations, set and revisited proactively, are a stronger predictor of successful outcomes than skill level alone, a finding that applies as much to a one-off delegated task as to a formal annual review.
Written Expectations Survive Better Than Spoken Ones
A verbal handoff of expectations feels efficient in the moment but is the first thing to get fuzzy once both people are a few days removed from the original conversation, especially if either side is juggling several other tasks in the meantime. A short written note summarizing what was agreed, even three or four lines sent right after the conversation, gives both parties something concrete to check back against later, rather than relying on two potentially divergent memories of a conversation that happened once and was never written down.