You’ve tried delegating. The work came back wrong, or it came back with questions, or it slowly drifted back onto your plate until you were doing it yourself again.

That usually has very little to do with the person you handed it to. It comes down to how the work was handed off. Most founders delegate tasks: respond to this, schedule that, update this sheet. Every task needs a new instruction, every result needs your review, and every edge case lands back on your desk. Your workload stays about where it started, with a management layer added on top.

Delegation that sticks works differently, and it follows the same five steps every time.

Step 1: Find what to hand off

Start with a delegation audit. For one real week, track how your time is spent. Write down what you did, not what you planned to do.

At the end of the week, go through every item and ask one question: did this require me specifically, my judgment, my relationships, my expertise? Or did it require a capable person with the right context and a clear brief?

For most founders, far more of the week falls into the second category than they expect. The specifics vary by business, but the categories are consistent:

  • Administrative operations (inbox management, calendar coordination, scheduling, expense tracking, vendor communication) almost never require the founder.
  • Client operations (proposals, contracts, CRM updates, onboarding logistics, follow-up) often don’t either.
  • Marketing execution (social posting, newsletter scheduling, website updates, content distribution) rarely needs the founder’s time, even when the ideas are theirs or they’re the face of the content.

For most of this work, the only reason it’s still on your plate is that nobody has built the setup to move it somewhere else.

Step 2: Match the work to the right level of support

Before you write a single brief, decide who the work belongs with. A great handoff to the wrong hire still fails, and mismatched support is one of the most common reasons founders give up on delegating.

The question that decides it is what level of judgment the work requires. Budget and hours come after that.

Executive assistant support keeps the business running day to day. An EA manages your time, your access, and the operational details: inbox triage, calendar management, scheduling, CRM updates, client logistics and follow-up. The work is high-trust and calls for good judgment about priorities and communication, but it doesn’t call for deep functional expertise. For most founders, this is the first hire and the one with the most immediate return.

Specialist support brings deep skill in one area, such as marketing, content, design, systems and automation, or financial admin. The work needs more than a generalist can offer but doesn’t need a full-time hire. A marketing specialist building your content calendar and running your social strategy. An operations specialist setting up your CRM and automating intake. A financial specialist handling your bookkeeping and reporting.

Fractional executive support brings senior judgment. A fractional COO, CMO, CFO, CHRO or other chief-level leader brings the strategic thinking of someone who has run that function for years, without the full-time salary. This is where you stop working in the business and start working on it: operational audits, financial strategy, marketing leadership and team infrastructure.

Step 3: Write the outcome down

This is the step that separates delegation from task distribution. Instead of handing over the motions, hand over what needs to be true when the work is done.

A founder on one of our recent discovery calls had 1,500 unread emails. Going through them wasn’t really what they needed. They needed to know which three mattered and deserved a reply.

That’s the difference in practice:

  • The task: Go through my inbox.
  • The outcome: Each day, I see the few emails that need me, and everything else gets dealt with without me.

Handed over as a task, an inbox like that gets sorted once and fills right back up. Handed over as an outcome, your EA knows what they’re looking for every single day, and you stop opening your inbox to find out what’s urgent.

The same shift works anywhere. “Follow up with leads” becomes “every lead who books a call hears back within one business day, and no warm lead goes two weeks without contact.” The task version needs you every time something unexpected happens. The outcome version gives your support a way to measure their own progress and make calls without checking in.

Write the outcome down, even when it feels obvious. This matters most when your support is remote. In an office, people pick up context by overhearing calls and catching you between meetings. A remote EA gets none of that, so the written outcome is how they learn what matters to you.

Step 4: Set the standard

Most founders have a quality bar in their heads (they know good work when they see it) but have never spelled it out. Someone who knows the standard can correct course before the work reaches you. Someone who doesn’t is guessing every time.

Answer these questions in your handoff doc:

  • If this came back wrong, what would you change?
  • What should never happen? (The guardrails.)
  • What decisions can they make alone, and which ones come to you?
  • What would make you uncomfortable, even if it’s technically correct?
  • What does an example of “great” look like? Link one if you have it.

Step 5: Let it go, and keep visibility

This is the step that breaks the most delegation relationships. Once the outcome and standard are set, you have to get out of the way. That means no hovering, no reviewing everything before it goes out, and no redoing work that came back slightly different from how you’d have done it. Different and wrong are not the same thing.

Letting go works best in stages:

  • Week one: review the work before it goes out, and give feedback against the standard you wrote.
  • Weeks two and three: spot-check. Look at a sample, not everything.
  • After that: step back and rely on regular reporting.

Most hovering comes from not being able to see what’s happening, so give yourself visibility instead of control. Every Nacho client gets a weekly report on work completed and budget used, plus a client portal showing hours logged and budget remaining. You know where things stand without stepping back in.

The release feels uncomfortable the first few times. It gets easier once you’ve seen work come back right without your fingerprints on every step.

Start with the 83 tasks

If you’re not sure where to begin step 1, Nacho’s Delegation Planning Guide is the fastest way in. It covers 83 specific tasks, organized by support level (EA, Specialist and Fractional Executive).

It also includes a framework for spotting your highest-leverage opportunities at your stage of business, and a planning worksheet that walks you through the audit: what’s draining your time right now, where the biggest opportunities are, which level of support makes sense first, and what your delegation priorities look like quarter by quarter.

Most founders who go through it find more than they expected. Tasks that have been on their plate so long they stopped registering as tasks. Functions that technically belong to someone else but default to the founder in practice.

The guide is free, and the worksheet alone is worth the thirty minutes.

Get the free guide Book a discovery call