How to Delegate Tasks as a Founder

You already delegated the easy stuff, and you still can't take a Friday off.

To delegate tasks as a founder, hand off decisions before chores. Start with calls where a mistake is cheap and reversible. Give each person a written dollar limit. Then stop taking the work back.

That's the whole method. It runs opposite to most delegation advice.

What should a founder delegate first?

A founder should delegate decisions first, starting with the ones where a wrong call costs little and can be undone. Tasks come second. Handing someone a to-do list while keeping the authority to answer their questions turns your team into a waiting room.

Most advice says the opposite. Delegate Solutions tells founders to start with tasks that "don't require your specific judgment," like calendar management, email triage, status reporting and travel booking. Prialto opens its list of the first five tasks founders should delegate with scheduling and calendar management.

Those lists save hours.

Hours were never the problem.

Look at what actually follows you into Saturday afternoon. It's rarely a calendar invite. It's a question:

• "Can we refund this customer?"
• "Is this invoice okay to pay?"
• "The client wants a discount. What do I tell them?"

Your team asks because you're the only person allowed to answer. That's the bottleneck. The number of tasks you've handed off doesn't touch it.

I've been building on the internet since 2011. I've hired, delegated and paid for the lessons. The pattern is easy to spot once you look for it: the founder becomes the answer key for every question the business asks.

A founder who delegates tasks but keeps every decision hasn't delegated. They've hired people to wait.

Your team hands decisions back because you let them

Your team follows the incentives you built. Handing the problem back is the safest move on the board, and you reward it every time you accept it.

In 1974, William Oncken Jr. and Donald Wass asked Harvard Business Review readers a question:

"Why is it that managers are typically running out of time while their subordinates are typically running out of work?"

HBR reprinted the article in 1999 and noted it was one of the magazine's two best-selling reprints ever.

Their answer was a monkey.

Every open problem has a next move. Someone has to own that move. That's the monkey.

Say your operations lead asks whether to refund a $400 order. You answer, "Let me think about it and get back to you."

The monkey just jumped. Your ops lead is now waiting on you, and you're the one with homework.

Three habits feed this:

• You answer instantly because it's faster than explaining.
• You say "let me think about it" because you want to get it right.
• You quietly fix the work after it ships.

Each one is a take-back. Each one teaches your team the same lesson: bring it to me.

It feels like helping. It works like a tax.

How to delegate tasks with a wrong-call budget

A wrong-call budget is the largest mistake you've agreed, in writing, to let one specific person make without asking you first. It's a dollar figure, set per person and per type of decision.

Most founders dodge the real question here: how wrong am I willing to let you be?

They answer an easier one instead. Do I trust you?

Trust is a feeling, and feelings swing with your mood. A budget is a number.

Think of a valet key. It starts the car and gets it to the lot. It doesn't open the glove box.

Most founders do one of two things. They hold the full keyring, or they hand it over and panic. The budget is the valet key.

Build one in four steps.

1. Log every decision that reaches you for one week

Keep a running note. Each time someone asks a question or waits on your approval, write down the question. Don't answer differently yet. Just log it.

Expect the same questions to repeat. Repeats are your best candidates.

2. Price each wrong call

Ask two questions about every item. What's the worst realistic cost if this goes wrong? Can we undo it within a week?

Then sort:

• Cheap and reversible: hand it off today.
• Costly but reversible: hand it off with a check-in.
• Costly and permanent: keep it, for now.

3. Write the limit down, per person

Write one sentence for each person: "You can decide this, up to this amount, without asking me. Tell me after."

Written matters. A spoken limit dissolves the first time something goes wrong. A written one survives the bad week.

One rule makes it real. Don't reverse a decision that stayed inside the limit.

4. Raise the limit on a schedule

Put a date on your calendar once a month. If someone stayed inside their limit and the calls held up, raise it.

Authority grows by evidence. A monthly date makes sure it grows at all.

Here's what a filled-in version looks like. These limits are examples only. Set yours against your own margins.

Decision	Worst realistic cost	Reversible?	Owner and limit
Refund a customer	$200	Yes	Support lead, up to $200
Pay a contractor invoice	$1,000	Mostly	Operations lead, up to $1,000
Offer a discount to close a deal	10% of the deal	Yes	Sales lead, up to 10%
Change your pricing	Months of revenue	Hard	You
Hire or fire a leader	Months of momentum	No	You

The founder rows stay short on purpose. Keep what's costly and permanent. Hand off the rest.

Don't roll this out to everyone at once. Open your log from step one and count questions by name. Whoever tops the list gets the first budget.

That person already has the context. You've been answering their questions for months. The budget just makes your answer permanent.

Run one person for 30 days. Add a second only after the first month holds.

How do you stop taking the work back?

Change what you say when someone brings you a problem. "Let me think about it" moves the problem to your desk. "What would you do?" keeps it on theirs.

Oncken and Wass suggested clarifying how much ownership you expect. The employee can recommend and implement a solution. They can act, then brief you immediately. Or they can act and report the outcome at a regular update.

Three rules keep you honest:

1. Ask for a recommendation first. Say "What would you do, and why?" before you offer an opinion.
2. Let calls inside the limit stand. If you'd have chosen differently, say so afterward. Reverse nothing.
3. Review after, not before. A fifteen-minute weekly look at what was decided beats a daily queue of what's waiting.

You'll want to take something back. That urge is data. It tells you the limit sits too high, or your team doesn't know what good looks like.

Adjust the number. Keep the rule.

Plan for the day someone blows the budget

Someone will. Say your sales lead gives a 20% discount when the limit was 10%.

Treat it as data, not a verdict. Make three moves, in order:

1. Fix the damage together. Repair first, discuss second.
2. Find the missing information. Look for what they didn't know before you question their judgment.
3. Change the system. Add a rule, adjust the limit, or fill the gap in what they know.

Never pull the budget back in front of the team. A public reversal teaches everyone to ask permission again.

The first blown budget is your real test. Pass it, and your team learns the limit is real. Fail it, and you've built an expensive suggestion box.

Keep a short list on purpose

Keep the decisions that are costly, permanent, or define the business. The list is short:

• What you sell and who you sell it to
• Pricing changes
• Hiring and firing leaders
• Anything you can't undo within a week at a cost you can't absorb

Everything else is a candidate for a budget.

If your keep list runs long, you're not keeping decisions. You're keeping control.

Write the keep list on the same page as the budgets. Your team should see what stays with you and why.

A closed door nobody explains reads as distrust. A closed door with a label reads as a decision.

What is the 70% rule of delegation?

The 70% rule says to delegate a task when someone can do it at least 70% as well as you can. Jim Schleckser of the Inc. CEO Project laid it out in 2018, and it works well for tasks.

It breaks for decisions.

Quality isn't the risk with a decision. Cost is. Someone at 70% of your judgment is fine on a $200 refund. The same person is a risk on a $20,000 contract.

Use the 70% rule to choose the person. Use the budget to choose the limit.

What the growth data says about delegation

Gallup's research points the same direction. In 2014, Gallup studied 143 CEOs on the Inc. 500 list. Those with high "delegator talent" posted an average three-year growth rate of 1,751%. That's 112 percentage points higher than CEOs with limited or low delegator talent.

Inc. reported that the same group generated 33 percent more revenue.

Gallup measured a talent, and a survey finds correlation. It didn't run an experiment. The direction still matches what you already feel: a business that waits on one person grows at that person's speed.

Growth also arrives on its own schedule. One podcast interview took Magai from $40K to $100K a month in a matter of weeks.

Growth like that lands on whoever is waiting to answer questions. If every decision sits in your inbox, you're the part that has to hold.

You don't need software, but AI helps

You can run all of this from a one-page note per person. List the decisions they own, the dollar limit and the date you'll review it. Keep it where they can find it without asking you.

AI speeds up the hardest part, which is getting your judgment out of your head. It can't hold authority. People do.

Record yourself answering ten questions from your log, out loud, with your reasons. Transcribe the recording. Ask an AI model to draft a decision guide: when this happens, do that, up to this amount, escalate if this.

Edit it until it sounds like you.

For the decisions you keep, I've written about how I built an AI board of directors. The guide trains judgment. The budget grants authority. Your team needs both.

Where this goes next

I run Keel, a small live room for founders between $500K and low seven figures whose business still runs through them. Delegation is one of the three things it covers. You can read how it works on the Keel page. I write about the operating side of building a company in Business.

Nobody earns freedom from a better calendar assistant. You earn it by putting a number on how wrong your team is allowed to be.

Set the budget. Then let them spend it.