How to Delegate When You Have ADHD: A Step-by-Step Guide for Bottlenecked Founders

You know you need to hand things off. You have known for months. And yet the same five tasks keep landing back on your desk, and the same thought keeps circling: "It will take longer to explain this than to just do it." So you do it. Again. Then you answer five more questions about it, fix what came back wrong, and finish the day with a to-do list longer than the one you started with. That is not a character flaw. It is what happens when a fast, pattern-matching, hyperfocus-capable brain tries to use a delegation system built for someone else's wiring. Learning how to delegate when you have ADHD is not about becoming more disciplined. It is about building handoffs that survive your energy swings, your working memory gaps, and your very real need to see progress. This guide gives you a specific process you can start using this week, with one hour of setup and small daily touches after that.

Why delegation fails for ADHD founders (and it is not effort)

Most delegation advice assumes three things: that you can hold the full task in working memory while you explain it, that you can remember to check in later, and that you get a small dopamine reward from watching someone else do the work. For many ADHD founders, all three assumptions break down.

Working memory is the first casualty. When you hand off a task verbally, you often leave out the one detail that makes the whole thing work, because you did not know you knew it until the output came back wrong. Then the correction costs more than the original task, and your brain files delegation under "expensive."

The second casualty is the reward loop. Closing a task yourself gives you a fast, satisfying click. Delegating gives you a slower, quieter reward: a thing you no longer have to think about. Your brain does not feel that. It feels the vague anxiety of an open loop and decides the open loop is the problem, so it takes the task back.

The third casualty is object permanence for tasks. Once something leaves your sight, it can genuinely fall out of your mental awareness. A handoff without a built-in reminder is not a handoff, it is a leak.

None of these are fixed by trying harder. They are fixed by designing the handoff differently.

The real bottleneck is not your workload, it is your transfer cost

Here is the framing I use with founders in one-on-one coaching, and it changes how they see the problem. Every task has two costs: the cost to do it and the cost to transfer it. You are not actually overloaded because you have too much to do. You are overloaded because your transfer cost is so high that doing it yourself still looks cheaper.

So the goal is not "delegate more." The goal is to get your transfer cost low enough that handing off becomes the obvious, low-friction choice. That means written specs, small pieces, and a check-in you cannot miss.

The task you keep taking back is rarely the task you cannot explain. It is the task you have never written down in a form that survives your own memory.

Consider an example. A founder I will call Maeve runs a six-person agency and personally writes every proposal because "no one else gets the tone." Every proposal takes her about 90 minutes, and she writes three to five a week. That is roughly 6 hours of her week. The alternative she tried once was briefing a team member verbally for 20 minutes, getting a draft back that missed the pricing logic, and spending 50 minutes rewriting it. Total: 70 minutes, plus irritation. Of course she took it back.

But notice what actually happened. The brief was verbal, it skipped the pricing logic, and there was no template. The transfer cost was high because the system was bad, not because delegation is impossible for her. Fix the system and the math changes. I am describing this as an illustrative scenario, not a client result.

Step 1: Separate the work into three buckets, not two

Most founders sort tasks into "mine" and "not mine." With ADHD, that binary fails because so much sits in a middle zone you cannot quite name. Use three buckets instead.

• Only you: Work that genuinely requires your judgment, relationships, or vision. Pricing decisions, key hires, final calls on strategy, the conversations only the founder can have.
• Transferable now: Work someone else could do with a written spec and one review. Editing, scheduling, invoicing, first drafts, follow-up emails, research, formatting, reporting.
• Transferable after you build the spec: Work you want to hand off but cannot yet explain cleanly. These are not "no" tasks. They are "not this month" tasks, and they become future handoffs.

Spend 20 minutes listing everything on your plate and dropping each item into one of the three buckets. Do not evaluate whether you have the right person yet. Do not reorganize your whole business. Just sort.

The value of the third bucket is psychological. Without it, every task you cannot explain feels like proof you are bad at delegating. With it, you have a queue, and a queue is calm.

Step 2: Write the spec that your own forgetting requires

Here is the core skill. A delegation spec is not documentation for the team. It is a memory prosthetic for you.

Write it in four lines:

1. Done looks like: one sentence describing the finished output. Not the process, the output.
2. The three things that matter: the quality bars, the constraints, and the thing that must never happen.
3. Where to look: the folder, template, or past example that shows the standard.
4. When to stop and ask: the specific decision the person should bring back to you rather than guess on.

For Maeve's proposal handoff, that would read: done looks like a complete draft in the proposal template with pricing built from the rate sheet; the three things that matter are the client's stated problem quoted in the opening, a scope section with three clearly priced tiers, and never a discount without my approval; where to look is the templates folder plus the last two approved proposals; when to stop is any scope that goes beyond what the discovery call covered.

That took four minutes to write and it removes the entire 20-minute verbal brief, forever. It also removes the "did I mention the pricing thing?" anxiety that makes founders rewrite drafts from scratch.

Keep specs in one place, one file per task, named the way you would actually search for them. If your spec lives inside a chat thread, it does not exist.

Step 3: Hand off one task, not a function

ADHD brains do well with bounded, visible units. Handing off "marketing" is unbounded and invisible. Handing off "the two-touch follow-up email sequence for inbound leads, first draft by Thursday" is bounded and visible.

For the first month, hand off single tasks. Once a person has done the same task three times to standard, bundle it into an ongoing responsibility. That sequencing matters because it gives you evidence before you give away ownership.

Notice the last column. Most founders delegate the doing and keep the briefing and the checking forever, which is why delegation never returns time. The column you should be watching is the one where you stop doing things, not the one where someone else starts.

Step 4: Build one check-in that you cannot miss

Your working memory is not the place to store commitments. Put check-ins somewhere that will interrupt you.

• One recurring slot, not many. A single 20-minute weekly handoff meeting where every delegated item gets reviewed beats five scattered check-ins you will forget.
• Written status, not verbal. Ask for a short written update before the meeting: green, amber, red, plus anything blocked. Writing removes the need to remember what was said.
• A visible board. Whatever tool you use, the delegated items must be on a screen you already look at. If it is in a second tool you check when you remember, it is invisible.
• An escalation rule. The person knows exactly which decision comes back to you and which does not. Without this rule, they will either guess badly or ask you everything.

One 20-minute slot per week plus 10 minutes of pre-reading is 30 minutes total. It can replace the hour of scattered corrections most founders do without noticing.

Use body doubling if follow-through is your weak spot

If the weekly check-in keeps sliding, run it with another person present. Sit in a call with an accountability partner, your operations lead, or me during a coaching session and do the review out loud. For many ADHD founders, the presence of another human is the difference between a meeting that happens and a meeting that quietly disappears. That is not a workaround. It is a legitimate accommodation.

Step 5: Close the loop so your brain lets go

Your brain will keep pinging you about a delegated task until it has evidence that it is handled. Give it that evidence on purpose.

When you hand something off, do three things in under a minute. Write the task on your visible board with the person's name and the due date. Delete or archive your own copy of the task so you are not looking at it twice. Say out loud, ideally to the person, what "handled" will look and sound like.

Then when it comes back done, close it visibly. Mark it done, say thank you in specific terms, and note the one thing that made it work so the next handoff is faster. That is the moment your brain learns delegation pays. You are training the reward loop, and it can be trained.

A 45-minute starting plan for this week

Total time: 45 minutes, split into three blocks.

1. 20 minutes: Sort your task list into the three buckets. Do not fix anything. Just sort.
2. 15 minutes: Pick one task from the transferable bucket and write the four-line spec. One task. Not the whole function.
3. 10 minutes: Choose the person, book the handoff conversation, and put the recurring 20-minute check-in on the calendar with a reminder that actually fires.

Then next week, review for 20 minutes and add one more task to the handoff list. Two tasks a month is a reasonable pace. Four is ambitious. Do not attempt eight.

What to do when the handoff comes back wrong

It will, at least once. When it does, resist the urge to fix it silently and take it back. Instead, ask one question: was this a spec gap, a skill gap, or a judgment gap?

• Spec gap: you did not write down the constraint. Add the line to the spec and run it again. This is the most common one, and it is cheap to fix.
• Skill gap: the person has not done this enough yet. Reduce the scope and review more closely for two more rounds.
• Judgment gap: this task needs a decision only you can make. Move it back to the "only you" bucket with no guilt, and hand off something else instead.

For ADHD founders, the first gap is almost always the culprit, because it is the one that involves memory. When you write the fix into the spec, you are not just improving the process. You are making sure you never have to remember that detail again.

What changes when the handoffs hold

The shift is not that your business suddenly runs without you. It is quieter and more useful than that. You stop losing the same hours every week to work that should belong to someone else. Your focus has somewhere to land. And the people around you get something better than your instructions: they get your standard, written down, so they can meet it without reading your mind.

That is how momentum actually builds. Not from a big heroic push to get organized, but from a small number of handoffs that hold, repeated until they become the way your business runs.

If you are staring at that first bucket and cannot see the 20 minutes to sort it, start smaller. Pick one task you resent doing. Write four lines about it. Hand it to one person. That is the whole first step, and it is enough to begin.