How to delegate without redoing the work yourself

Delegation fails at the briefing, not the doing. To hand off work without redoing it, your brief needs five parts: the outcome you want, one example of good, a deadline, a check-in point, and a clear definition of done. When work comes back wrong, one of those five was missing from your handoff. It is almost never that the person could not do the job. It is that you did not tell them what the job was.

This is the single most expensive habit in a growing business. You delegate, the result disappoints, you fix it yourself, and you conclude that delegation does not work for you. The real lesson is narrower: that brief was incomplete. Fix the brief and the redos stop.

Why does delegated work keep coming back wrong?

Because most handoffs are missing information the owner assumed was obvious. You know what "good" looks like, you know the deadline, you know the one edge case that matters, so you forget to say any of it. The person doing the work is not in your head. They fill the gaps with guesses, and their guesses do not match yours. The result feels like a performance problem. It started as a communication gap.

The proof is simple. When you redo the work, notice what you are fixing. Nine times out of ten it is not effort or skill. It is a detail you never specified, a format, a tone, a threshold, an example you had in mind and never shared.

The complete handoff

Every clean delegation contains five parts. Miss one and you invite a redo. This is the framework I give owners who tell me delegation "does not work" for them.

Read it as a diagnostic, not just a recipe. When a task comes back wrong, walk the five parts backward and find the one you skipped. That is your fix, and it is usually the same one every time for a given person, which tells you exactly what your handoffs are missing.

Outcome, not activity

Weak briefs describe activity: "clean up the spreadsheet." Strong briefs describe the outcome: "I need one sheet where every client has a status, a next action, and an owner, so I can scan it in thirty seconds on Monday." The second version tells the person what success is, so they can make a hundred small choices in the right direction without asking you about each one.

Show one example

An example does more than a paragraph of description. Link a past deliverable you loved, or a template, or even a competitor's version you admire. People match patterns fast. Showing "good" once removes an entire category of back-and-forth. If you do not have an example yet, this is where writing it down as an SOP that sticks pays off, because the first good result becomes the example for every handoff after.

A real deadline and a check-in

"When you get a chance" gives no deadline and leaves both of you anxious. Give a date and time. Then set a check-in partway through, especially for anything new or high-stakes. A five-minute review at the halfway mark catches a wrong turn while it is still cheap to correct. Skipping it is how a small misunderstanding becomes a finished deliverable you have to throw out.

Define done

Say the standard out loud. Format, length, tone, the must-nots, the threshold for "good enough." This is the part owners find awkward because it feels like micromanaging. It is the opposite. A clear definition of done is what lets you stop hovering, because the person knows exactly when they are finished and whether they hit the mark.

A worked example: one missing part, one redo

A composite, not a market claim. A founder I'll call Renata asked her assistant to "put together a recap of last month's sales." She got back a dense spreadsheet of every transaction. Useless to her. She almost redid it herself and almost decided her assistant was not detail-oriented.

Instead she walked the five parts. Outcome, example, deadline, check-in, done. She found the gap immediately.

The redo was not a skill gap. It was three missing parts. Renata rewrote the same request as a complete handoff: "I want a one-paragraph summary plus three numbers, total revenue, top product, and month-over-month change, so I can drop it into my investor update. Here is last quarter's version as the format. Draft by Thursday, show me a rough version Wednesday." Same assistant. Right result, first try.

She tracked her redos for a month afterward and the pattern was stark.

Five hours a week of rework, mostly gone, from changing the brief and nothing else. The WorkSmart OS includes handoff and brief templates built on these five parts, so a complete handoff becomes a fill-in-the-blank habit instead of something you remember only after the work comes back wrong.

If the work came back wrong, read your own brief. The missing part is right there.

Where owners get delegation wrong

Two failures sit on either side of good delegation. On one side, handing someone a task with no brief and hoping for the best, which is really just gambling. On the other, doing the work through someone else, narrating every keystroke. The complete handoff sits between them. You define the outcome and the standard clearly, then you let go of the how. Getting this right is the same skill that lets a business run without you, which is the whole point of basic business systems in the first place.

Do this next

Take the last task that came back wrong and rewrite the brief using all five parts, outcome, example, deadline, check-in, and done. Send it again. Notice which part you had skipped the first time, because that is the part you skip by default. The WorkSmart OS includes handoff templates built on these five parts, so your briefs are complete before the work starts instead of corrected after.