What is the first task a founder should delegate?

Calendar coordination. It has the highest frequency, lowest reversibility risk, and clearest success conditions of any founder task. Most founders reclaim 3 to 5 hours per week within 2 weeks of delegating calendar to an EA with authority.

How long does it take to delegate effectively?

Meaningful delegation takes about 30 to 60 days for the first phase. Full operational delegation (where the founder is no longer the routing layer for routine decisions) typically takes 90 days. Founders who try to compress this timeline usually end up with rework, missed briefings, and a damaged EA relationship.

Should I delegate inbox management in the first month?

Delegate inbox triage in the first month. Do not delegate inbox response until at least month 3. Triage means someone else reads, tags, and prioritises your inbox. Response means someone else writes on your behalf. Triage is safe from day 1. Response requires context the EA does not have yet.

Can I delegate strategic tasks to my EA?

Not in the first 60 days. Strategic tasks require deep business context, decision-making judgment, and often external relationships. These come after operational tasks are handled reliably. A typical timeline: operational delegation months 1-3, coordination delegation months 3-6, strategic delegation months 6+.

What tasks should I never delegate?

Hiring final decisions, direct investor communication, cash position review, and any client conversation where relationship reshape happens. These require founder judgment that cannot be reliably outsourced to an EA. A chief of staff can take on some of these, but only after 12+ months of context.

How do I know if I am delegating too fast?

Three signals. First, the EA asks the same questions repeatedly (context gap). Second, you are correcting more than 20% of her work (briefing gap). Third, you find yourself redoing things after she completes them (trust gap). Any of these three means slow down. Add scope only when the current scope is running clean.

What is the difference between task delegation and decision delegation?

Task delegation means someone else does the work. Decision delegation means someone else chooses what work to do. Most founders start with task delegation and never move to decision delegation. This is why they still feel overwhelmed after hiring an EA. Real capacity comes from decision delegation, which requires an authority document.

What to Delegate First as a Founder: The 5-Task Sequence

Most delegation advice is written backwards

Every article about what to delegate first tells you to make a list of everything you do and rank it by hourly value. The problem with this advice is that it treats delegation as a math exercise.

It is not a math exercise. It is a trust exercise.

The things you should delegate first are not the things that consume the most time. They are the things that meet three criteria: high frequency, low reversibility risk, and clear success conditions.

High frequency means the work happens weekly or daily. That gives your delegate enough repetitions to get good at it.

Low reversibility risk means if the task is done wrong, you can fix it the next day without lasting damage.

Clear success conditions means you can describe what "done well" looks like in writing, without having to be there.

Use these three tests. Everything that passes all three should be delegated within the first 60 days. Everything that fails one should wait.

The 5 tasks every founder should delegate first

1. Calendar coordination

Especially across time zones. This is the highest-frequency operational work a founder does, and it has almost zero reversibility risk. If the EA books a meeting badly, you can move it.

The rule to give: any calendar conflict under 4 hours of impact is the EA's decision. Above 4 hours, she flags it to you with a recommended resolution.

Most founders reclaim 3 to 5 hours per week by delegating calendar within the first 2 weeks.

2. Inbox triage

Note: not full inbox management. Triage only.

A good triage system uses three buckets. Urgent means needs founder today. Waiting means founder needed but not today. FYI means founder never needs to see this.

Your EA reads every email that comes in, tags it into a bucket, drafts responses for anything obvious, and gives you back an inbox that is already prioritised when you open it.

Do not delegate full inbox response in the first 30 days. Delegate only triage. Response comes later, when the EA has enough context to represent your voice.

Typical time reclaimed: 5 to 8 hours per week by end of month 1.

3. Document chasing

Contracts. NDAs. Onboarding paperwork. Signed proposals. Vendor forms. The founder should never be the person chasing a signature. This is pure follow-through work with no strategic component.

Give the EA a shared folder or Notion board where every open document lives with a status: awaiting signature, awaiting review, closed. She checks it daily. She chases whoever is holding it up. The founder sees the status board weekly.

This is the delegation that generates the biggest "how did I not do this earlier" reaction from founders. It also delivers about 2 to 3 hours per week back.

4. Expense approvals under $500

This is the most contested item on the list. Founders resist it because it feels like losing control.

Run the numbers first. In a typical week, how many expense approvals under $500 come through you? Most founders find 8 to 15 per week. How many of those have you ever said no to? For most founders, the answer is under 5%.

If you approve 95% of these requests, the requests do not need you. They need a written rule.

Give your ops lead or finance person authority up to $500. Set the escalation rule: any single expense over $500, any monthly total for a category over $3,000, or anything to a new vendor comes to you.

Time reclaimed: 1 to 2 hours per week, plus the elimination of context-switching cost which is usually larger than the raw time saved.

5. Travel logistics

Booking flights, hotels, ground transport, meeting logistics on the road.

The rule that works: give the EA your travel constraints, not the steps.

Instead of: "Book me a flight to Dubai for Tuesday."

Say: "I need to be in Dubai for a client meeting on Wednesday morning. Direct flights only. Land by 6 PM Tuesday. Hotel within 15 minutes of the office. Budget up to $1,800 for flight, $400 for hotel."

Now she decides. You see the calendar invite.

This single reframe (constraints, not steps) applies to most delegation and is worth training your team to use across every role.

The 5 tasks founders often try to delegate first, but should not

Equal to knowing what to delegate is knowing what to hold onto in the first 60 days.

1. Direct client communication

Not in the first 30 days. The EA does not have enough context yet to represent your voice, tone, or business relationships. Hand off client scheduling and prep, keep the direct written communication yourself. This changes by month 3, when the EA has the context.

2. Hiring decisions

The EA can schedule interviews. She can source candidates. She can format offer letters. She cannot decide who to hire. Hiring is one of the highest-consequence decisions a founder makes, and it does not meet the low-reversibility test.

3. Strategic email responses

Investor updates. Partnership discussions. Any email where the response reshapes a relationship. Keep these until at least month 6.

4. Financial oversight

Monthly reconciliation, cash position review, forecasting. This work needs the founder's judgement about what to worry about. Delegate the operational admin (invoice submission, expense categorisation) but not the review.

5. Anything client-facing on paid accounts

Customer success touchpoints. Renewal conversations. Escalation resolution. These decisions have long reversibility windows (a bad renewal call can cost a customer 6 months later). Keep them until you have a specific customer success function.

The 30-day delegation sequence

A concrete order that has worked for most founders we work with.

Week 1. Delegate calendar coordination and inbox triage. Nothing else. Give the EA time to learn your patterns before adding scope.

Week 2. Add document chasing and expense approvals under $500. These are low-risk additions that produce visible relief.

Week 3. Add travel logistics with constraint-based briefs.

Week 4. Review what has been working. Add one more scope item based on what feels most painful now. Common week 4 additions: vendor coordination, meeting prep, weekly reporting.

By end of month 1, most founders have reclaimed 8 to 12 hours per week and delegated approximately 30% of their operational load.

Do not try to delegate everything at once. Every scope expansion is a trust conversation. Rushing it creates rework, which teaches the EA that she cannot be trusted, which reduces future scope.

The single biggest mistake

Delegating what you dislike, instead of what you should not be doing.

Most founders start delegation by handing off the tasks they personally dislike. This is intuitive but wrong.

The right question is not "what do I hate doing." The right question is "what have I been doing that anyone with reasonable judgment could do?"

These are often the tasks you enjoy, because they feel productive and give you a sense of control. Approving vendor invoices under $500. Reviewing calendar conflicts. Chasing signed contracts.

Delegating tasks you enjoy is harder than delegating tasks you hate. It is also more valuable. The tasks you enjoy but should not be doing are typically the ones eating the most of your strategic capacity, because you have been unconsciously prioritising them.

What Tasks Should a Founder Delegate First? (2026 Guide)