The Delegation Flywheel

Author

Aaron Hayslip

Published

Jul 10, 2026

Read

7 min

Practices

Delegate, Architect

Think about the last time something got completely off your plate. Not “I delegated it and now I'm following up on it.” Gone. Someone else took it, owned it, and closed it - and the next time you heard about it, it was already done.

Now imagine your whole week feeling like that.

You mention offhand that you should reconnect with an old client. By Thursday he's on your calendar, and there's a note reminding you his daughter just left for college.

A vendor tries to nickel-and-dime you - you never even see it; it's resolved before it reaches you, in your favor.

You land from a red-eye and there's a car waiting, a room booked, and dinner set with the one person in that city worth your time.

Your anniversary doesn't sneak up on you, because someone who knows you made sure it wouldn't.

Here's the part most people miss about a great assistant: it's not about tasks.

It's about handing another person your standards, your judgment, and your relationships - and watching them guard all three the way you would. They don't wait to be told. They see it coming, and they've already moved.

That's the goal. Not an assistant who does your tasks - an assistant who runs your world.

Most founders never get there. They think delegation means handing off tasks: make a list, explain each one, check the work. That's not delegation - that's your job with an extra step.

Real delegation is a system. We call it the Delegation Flywheel, and it's how we get the founders we work with to what I call delegation equilibrium.

Delegation Equilibrium

Here's the goal: within the first 90 days of working with an assistant, 80% of their time is spent running processes you've already reviewed and signed off on. They're your person. You trust how they work because you've watched it and shaped it.

Sometimes we hit it in a month. Sometimes it takes six. Ninety days is the target.

And notice what the goal is not: it's not for you to spend your time delegating. If you're sitting around deciding what to hand off and writing instructions, you've just traded one kind of work for another.

The whole point is to get the assistant to lead the charge - asking the questions, driving the conversation, pressing you for feedback. Here's the system that makes that happen.

Step 1: Map the First Three Responsibilities

Weeks 1–4

Don't try to hand off everything at once. In the first four weeks, we pick the top three responsibilities to transfer first. For most founders, that's:

• Triaging and drafting email
• Scheduling and calendar
• One more that's specific to you - updating the CRM, client follow-ups, expense tracking, whatever quietly eats your time

Then we deep-dive the preferences on each one.

How often should email be checked? Who always gets a fast response? What context matters? We turn each responsibility into an SOP in a standard format.

One nuance that matters: an SOP isn't just a how-to. It represents the responsibility itself. Some SOPs are detailed because the process is specific. Others are basically one line - they just name the thing your assistant now owns. Both count.

The Board: Not Started → Implementing → Rolling

Every SOP lives on a simple Kanban board with three columns:

• Not Started - responsibilities we haven't picked up yet
• Implementing - being actively run and refined
• Rolling - adopted; your assistant owns it and you don't think about it

This board is the single source of truth for what your assistant is responsible for. It's also the agenda for the one meeting that powers the whole thing.

The Keystone Habit: Your Weekly Meeting

The flywheel runs on one recurring meeting a week. That's it.

During it:

1. You pull up the board and look at everything in Implementing.
2. For each SOP, you think back over the week: how did this go? You give feedback on the actual work. Example: “I noticed that call got scheduled with no buffer - going forward, always leave 15 minutes.”
3. Your assistant takes notes - ideally recording with an AI notetaker so nothing gets lost.

Simple. But there's a mindset shift buried in here that most executives get wrong.

Stop Trying to Download Your Brain

The instinct is to sit your assistant down for a marathon call and unload every preference you have. Founders do this - even sharp ones - and call it “training.”

It doesn't work, for two reasons.

First, you're not teaching, you're just talking. Information with no action attached to it doesn't stick. They can't apply a preference they have no context for yet, so they'll make the mistake anyway.

Second - and this is the big one - you don't actually know all your preferences. A huge number of them live in your head subconsciously, because you've never had to ask another human to do this for you. What's subconscious only becomes conscious when you watch someone do it differently and it bugs you.

So flip the whole thing.

Give them the process. Let them start. Let them make mistakes.

The mistakes are the curriculum - each one surfaces a preference you didn't know you had, and now you can name it.

Then the SOP Gets Sharper

After the meeting, your assistant's first job is to go through the feedback and update the SOP. If there's an AI skill attached to the process, they update that too. The process gets a little better every single week.

Eventually, you'll review an SOP and have nothing to add.

That SOP moves from Implementing to Rolling. It's adopted - off your mind for good.

Then you ask the only question that keeps the wheel turning:

Pull one from Not Started, and go again.

Why This Compounds

This is a flywheel, not a checklist, because every turn makes the next one easier:

• Every process gets ~10% better each week, because your assistant is always working out of the SOP - executing from the documented process and improving it as they go.
• Responsibilities stack up. Equilibrium gets closer.
• It's all documented. The day you need to hand a responsibility to someone new, the SOP is already written. No knowledge trapped in one person's head.

Two Things People Miss

1. Start with the small stuff on purpose

The first responsibilities you hand off - email, calendar, the routine follow-ups - can feel like the least valuable things to give away. They're not. That everyday work is how your assistant absorbs your world: who your people are, what actually matters to you, how you'd want things handled, where the landmines are. It's context you could never sit down and fully explain - they pick it up just by being in the flow of it every day.

And that context is what eventually lets them take on the things you can't write into an SOP: the judgment calls. My assistant can read a client's note, know instantly it's a problem, and get it to the right person without me saying a word - because she's been living in that relationship since day one. The routine work isn't the prize. It's the on-ramp to everything you actually want off your plate.

2. One-off tasks

You'll still hand off plenty of one-offs.

Ask your assistant to watch for patterns: when the same “one-off” keeps coming back, it's a responsibility in disguise. Flag it in the weekly meeting, write an SOP, and it joins the flywheel.

The Takeaway

Delegation isn't an event you power through. It's a wheel you build once and keep turning.

You don't get free by working harder at handing things off - you get free by installing a system that hands things off for you, and an assistant who drives it.

Give it 90 days.

This is exactly what we install for the founders we work with at FreedUp - a trained executive assistant plus the system that makes them effective from week one.