Did you delegate it, or loan it out?

Hand over the decision, then check whether you took it back

To delegate as a founder, you hand over a decision, not a task, and then you test whether it stayed handed over. The test is simple: look at the last 30 days and count every time you made, reversed, or approved a call that the new owner could have made. If the count is above zero, you did not delegate it. You loaned it out and kept the keys.

Most founders believe they have delegated more than they have. The gap between the two is where a lot of hidden risk sits, and your personality has a lot to do with how wide it is.

The 30-day override check

Pick one function you believe someone else now owns. Sales follow-up, hiring for a role, supplier payments, anything. Then go back through the last 30 days of messages, meetings, and approvals and count the times you stepped in.

Count three kinds of step-in:

• You made the call. They carried it out, but the decision was yours.
• You reversed their call. They decided, you overruled.
• You answered a permission question. They asked what to do, and you told them.

Zero means the function is delegated. Any other number means you still own it and have stopped watching closely. That second state is worse than never delegating at all, and we will get to why.

We borrowed this check from our operating partner. The fuller operator playbook is on Advisor Avi, including how it fits into a wider seat diagnostic.

Each step-in teaches something different

If you made the call, you handed over a task. That can be fine, as long as you call it a task. It is not ownership, and nobody will act like an owner of something they only execute.

If you reversed their call, you took the outcome back. You cannot ask someone to own a result and then overrule how they got there. After one or two reversals, they own the function in title only, and they know it.

If you answered a permission question, you confirmed the decision is still yours. They asked because they believed it was your call, and your answer proved them right. Every answer is another small lesson in checking with you first.

Delegation theater hides the risk

When you have not delegated, at least you know it. Delegation theater is worse because it feels like progress. You have told people the function is handled, you have stopped thinking about it, and it still runs through you. If you went away for two weeks, it would stall, and you would be surprised.

That surprise is exactly what you thought you had bought your way out of. If you want to see how exposed you are across the whole business, run the two-week test.

Why letting go is harder for some wiring

Some founders find the override check easy to pass. Others fail it every month and cannot see why. The difference is often personality. These are tendencies, not verdicts, but they are worth checking against yourself.

• High conscientiousness. This Big Five trait (validated) drives the standards that built your business. It also makes a worse result feel unacceptable, so you reverse the call to protect the bar. The reversal feels like quality control. From the other side, it looks like the job was never theirs.
• A strong D in DISC. DISC is a framework for self-reflection, not a validated measure, but its D factor describes something real: a pull toward speed and control. Making the call yourself is faster this week. It makes you slower every week after.
• Low trust. Trust is one of the facets under agreeableness in the Big Five. If yours is low, you expect the hand-off to fail, so you check in, and checking in becomes steering.
• High neuroticism. A sensitive stress alarm makes an unwatched function feel dangerous. The step-ins are less about control and more about calming the worry.
• High agreeableness. This one fails the check differently. You hand things over, but you answer every permission question because sending it back feels cold, and you avoid the conversation when a standard slips.

If two or three of these fit, delegation will cost you more effort than it costs other founders. That is not a reason to skip it. It is a reason to build more structure around it, because willpower alone will lose to your wiring on a bad week.

What real ownership looks like

Ownership is the right to be wrong without you stepping in. The owner makes the call, sometimes worse than you would have, and you let it stand. You coach afterward instead of catching it in the moment.

If a person never gets to make a decision you would not have made, they do not own anything. They are running your decisions with extra steps.

How to make the hand-off stick

1. Name the decisions that are theirs. Say out loud, and write down, which calls they own and any limits on them (a spending cap, a scope). Anything ambiguous drifts back to you.
2. Stop answering permission questions. When they ask what to do, ask what they think. It is slower once and it is how ownership transfers. Better still, train them to bring you decisions instead of problems.
3. Let the first worse call stand. Do not reverse it. Let it play out, then review it together. That one act of restraint teaches more than any speech about ownership.
4. Judge the function, not your involvement. Give the owner an outcome they are measured on. If the number is good and you were not in it, that is the win.
5. Run the check again in 30 days. Same function, same count. You want the number going down.

Know what you are fighting before you start

If the override count keeps coming back above zero, the problem is rarely the person you handed it to. It is usually the specific way you are wired to take things back. Founder OS names that pattern in its "How you lead" section, covering your delegation style, your decision-making, and the people-management blind spot to watch, and pairs it with a "how to work with you" manual you can give the person taking over.

Founder OS is $9, one-time, and takes about an hour. Get your Founder OS and find out which of these patterns is yours.