Delegate the outcome, not the process

Micromanagement comes from a bad assignment, not from bad people. When a manager hands off a task with no context — just “do this” — there's nothing left to do but keep asking how it's going, checking progress step by step, and stepping into the details, because the person doing the task doesn't have enough information to make good decisions on their own. The fix isn't stricter oversight — it's a better assignment up front.

A typical scenario

A manager tells a colleague to “put together materials for the client meeting” and moves on. The colleague has no idea whether to prepare a slide deck or just an email summary, whether the meeting is about a new project or settling an old one, or when it's actually due. Result: an hour spent on something the manager ends up redoing, because it wasn't what they had in mind — and the assignment has to be handed off again, this time in more detail, costing both sides time.

With an assignment that has four clear parts from the start, this situation almost never happens. The colleague knows exactly what needs to exist, why the manager needs it, when it's due, and how they'll know it's done and correct — and they choose their own path to get there.

How to do it

1. What: describe precisely what output needs to exist — a specific document, decision, working solution, or finished presentation, not a vague phrase like “put together materials.”
2. Why: explain the context and purpose — what the output will be used for, who will use it next, what decision depends on it. Context lets the person make the right smaller decisions along the way without constantly having to check back.
3. By when: set a specific deadline, not “as soon as possible” — a vague deadline either leads to procrastination or gets the wrong priority relative to other work.
4. What “done” looks like: describe measurably how you'll know the output is right — what points it should cover, what form it should take, who it needs to be understandable to. Not “just do it somehow,” but concrete criteria.
5. Leave the process to the person: once these four points are clear, don't step into how they get there — micromanaging the process is exactly what a good assignment is meant to replace.
6. Set up one check-in roughly halfway to the deadline, not only at the very end — that way you can adjust direction in time if the output is heading somewhere different than you expected, without having to check every individual step.

The best tools

• An assignment template (in a document, notes, or a task tool) — four fixed fields, what / why / by when / what done looks like, that you fill in every time you delegate, so none gets skipped.
• Task management tools (Asana, Trello, Linear) — let you write the assignment once, attach a deadline and check-in point, and keep a history of what was agreed.
• A shared goals document (OKRs, goal-tracking sheets) — for delegating bigger, multi-week tasks that need to connect to the team's overall goal.
• A short extra conversation at handoff — even without a tool, five minutes explaining context out loud helps, especially for assignments that don't summarize well in writing.

What you get out of it

• Time: fewer follow-up questions while the task is underway, and less redoing of output that missed unstated expectations.
• Less micromanagement: with clear context, the person makes their own decisions and the manager doesn't have to check every step.
• Better output: the colleague understands the purpose, so they make better smaller decisions in the parts the assignment doesn't spell out in detail.
• Growing your people: delegating the outcome instead of the process teaches the team to solve problems on their own, not just follow precise instructions.

Pro tip

If you're not sure yourself what exactly “done” should look like while handing off the assignment, that's a sign you haven't thought it through enough yet — a few extra minutes clarifying criteria up front saves much more time at the end, when the output would otherwise need redoing.