Issue No. 12 · October 28, 2026

TL;DR

You can't scale what only you can do. Delegate the high-frequency, low-judgment work first, and hand it off with a doc, an owner, and a check, so it doesn't boomerang straight back to you.

Hey there, Ops Connectors... how's everybody connecting the dots this week?

Most owners aren't bad at delegating because they can't let go. They're bad at it because they delegate the wrong things in the wrong way, the work comes back broken, and they conclude "it's faster to just do it myself." So they stay buried.

Make it stay gone: a woman hands a checklist to a man, with document, owner, and checkmark symbols and a blocked boomerang above them.

A clear handoff gives someone the instructions, authority, and checkpoint to own the work.

The problem usually isn't delegation. It's how the handoff is done, and what gets handed off first.

What to delegate first

Don't start with the scary, high-stakes work. Start where the math is easiest:

  • High-frequency, low-judgment. The tasks you do over and over that don't need your specific brain. This is pure time you buy back.

  • The work only you do but shouldn't. The stuff that's below your role but still sits on your plate because "it's easier." That's capacity you're quietly burning.

  • Not yet: the things that are genuinely your unique value. Delegate around those so you have more room for them, not less.

A simple rule: if you can describe exactly how to do it, you can delegate it. If you can't, that's a documentation problem, not a reason to keep it. (Yes, that's what SOPs were for.)

Why delegation boomerangs (and how to stop it)

Work comes back when the handoff was a toss, not a pass. Three things make it stay gone:

  1. A doc, not a vague verbal. Give them the SOP so they aren't reverse-engineering your method from memory.

  2. An owner with authority. They own the outcome, not just the task, and they can make the small calls without you. Delegating the task but keeping every decision just builds a new thing that waits on you.

  3. A check, then trust. Agree on how you'll know it's working, one metric or a quick review, use it for a few cycles, then stop hovering. Checking is not the same as doing it yourself.

Make the handoff stick: three connected circles show a checklist labeled A Doc, a person labeled An Owner, and a checkmark labeled A Check.

Three essentials for a useful handoff: a document, an owner with authority, and an agreed check.

The real test: does it stay gone?

You've delegated well when you stop thinking about it. If a task keeps pulling your attention back, something in the handoff is missing: the doc, the authority, or the trust. Fix that, not the person. Most "bad delegation" is really an incomplete handoff.

The Business Operating System Starter Kit includes delegation and handoff tools, so you can document the task and hand it off cleanly instead of from memory.

This week's AI prompt

The Delegation Prompt

“Help me choose one recurring task to delegate. Here’s my list: [TASKS]. For each task, I’ve included how often it happens, how long it takes, and what could go wrong if it’s done incorrectly.

Here’s who could take it on, their experience, and their available capacity: [DETAILS].

Recommend one task to start with and explain why. Outline the instructions they’ll need, which decisions they can make independently, when to bring a question back to me, and a checkpoint. Ask me for missing information instead of guessing.”

Before assigning anything, check that the person has the time, skills, and access to do it. Review the suggested instructions and decision limits with them. AI can help you plan the handoff; you still need to agree on what’s realistic.

Regina's Ops Lesson

The hardest thing I ever delegated was the work I was good at, because being needed felt like being valuable. If I was the one everyone relied on, I mattered, right?

What actually changed my business or my role as a VP of Operations was realizing that every task I kept "because I'm faster" was a task my business or my team couldn't grow past. I was the ceiling. The day I started handing things off with a real doc and real authority, instead of a rushed verbal and a hope, the work stopped coming back. And the room it freed up went to the things only I could do.

Delegation isn't losing control. It's trading the illusion of control over everything for actual leverage on the few things that matter.

Not sure what to let go of (free)

If you can't tell which tasks are safe to hand off first, the free Business Operations Quick Check highlights where your business is most dependent on you specifically, which is exactly the work to document and delegate.

Your challenge this week

Pick one high-frequency, low-judgment task you still do. Write or grab the SOP, hand it to one owner with the authority to run it, and agree on a single check. Then let it go. Reply and tell me what you delegated.

Quick Answers

What should I delegate first in my business? Start with high-frequency, low-judgment tasks and the work that sits below your role but still lands on your plate. They buy back the most time for the least risk.

Why does delegated work keep coming back to me? Because the handoff was incomplete. Work stays gone only when the person has the documented steps, the authority to make small decisions, and an agreed way to confirm it's working.

How do I delegate without losing control? Give a clear doc, assign one owner with real authority, and agree on a single check you review for a few cycles. Checking is control. Doing it yourself is just being the bottleneck.

Know a business owner who is drowning because they do everything themselves? Forward this. The first clean handoff is the one that changes everything.

Until next time, keep connecting the dots.

Regina Morgan
aka The Dot Connector™

Founder, Break Into Ops™
Founder, The Ops Connector™

Helping professionals and businesses connect the dots through better operations, smarter systems, and AI.

Next Wednesday: The "Hit by a Bus" Test. Is your business documented, or does it only exist in your head? A quick, slightly scary audit.

In partnership with

Nobody's coming to approve your idea

People assume that real businesses get built by other people with more resources. It's how great ideas get stuck in notes apps and conversations.

But you don't need six months and a developer's salary to validate your concept. You just need a weekend. Describe what you want to exist and Lovable builds it: a real site, a real product, ready to accept real payments from real customers. Not a mockup to show people. An actual thing they can use.

You don't need anyone's sign-off to get started. Take $5 off your first month.

Discount of $5 applies to first month of any paid plan. You need to sign up via this webpage in order to claim the discount. The discount applies to new and returning users without an active paid plan. Terms apply.