How Founders Can Delegate: Five Levels of Autonomy

Every task you hand off sits at one of these levels. Name the level out loud when you delegate:

1. Do exactly as instructed. You give the steps, and they carry them out. Use this for new people or high-risk tasks.
2. Research and report. They gather facts and options and bring them to you. You decide.
3. Recommend, then wait. They investigate, choose an option, and explain why. You approve before anything happens.
4. Decide and inform. They act, then tell you what they did and why. You step in only if something looks wrong.
5. Own it fully. They decide and act, and you don't need updates unless a set limit is crossed.

Most founders default to level 5 when they feel overloaded and level 1 when they feel nervous, then swing between them. The framework gives you a middle ground, and it gives the other person a clear map of what's allowed.

Ask three questions:

• What does a mistake cost? If the worst outcome is a small, reversible error, go higher. If it's a lost customer, a legal problem or a big payment, go lower.
• How much has this person done it before? Someone doing a task for the first time starts at level 2 or 3, even if they're senior.
• How much context does the decision need? Decisions that rely on things only you know, such as a pending deal or a sensitive relationship, start lower until you've shared the context.

Then plan to move up. Say a new operations hire handles vendor reorders at level 3 for a month, and you approve each order. After they've sent ten orders you'd have approved anyway, you move to level 4 with a spending limit. That's a concrete rule for raising autonomy, and it beats a vague feeling of trust.

Write the handoff on one page so nothing lives only in a conversation:

1. Outcome. What result you need, in a sentence a stranger would understand.
2. Level. Which of the five levels applies right now.
3. Boundaries. Budget, deadlines, and things they must not do without asking, such as contacting a certain customer.
4. Context. Why it matters, what you've already tried, and where the background documents are.
5. Check-ins. When you'll review, in what form, and what will count as done.
6. Path to more autonomy. What you'd need to see to move the level up.

Keep the briefs in a shared spot so both of you can revisit them. A task tool like Asana works well for this, with the brief in the task description and the level as a field. If the work repeats, document it once in a tool such as Trainual so the next person doesn't start from zero, and see how to document processes when you're the bottleneck.

The check-in rhythm should match the level. At level 1 or 2, short daily or twice-weekly touchpoints are normal. At level 3, agree on a review point before the decision. At level 4, a weekly summary is enough. At level 5, review results monthly against the outcome, not the activity.

A few rules keep check-ins from becoming micromanagement. Ask about outcomes and obstacles, not methods. When they bring a problem, ask "what do you recommend?" before offering your own answer, which pushes decisions downward. And if they make a call you would have made differently but that's within their level, let it stand, then discuss it afterward.

These patterns show up again and again:

• Taking the task back. When something is late or done differently, you quietly redo it. The message is that delegation isn't real.
• Delegating tasks, not outcomes. "Send these emails" gives them a chore. "Get three customers to renew by month end" gives them ownership.
• Vague authority. If they don't know what they can approve, they'll ask about everything or nothing.
• No time budget for handoff. The first delegation takes longer than doing it yourself. Plan for that, and don't judge the process by the first week.
• Delegating without a decision map. If people don't know who decides what, tasks bounce back to you. A decision rights matrix clears this up.

If you're building the same habit across a leadership team, read the delegation framework for operational leaders, and track team-level results with a leadership team scorecard.