How to Delegate to an Executive Assistant (Without Losing Control)

Most leaders who say "my assistant didn't work out" actually mean "I never really delegated." Delegation is a skill, and it fails in predictable ways: handing off too little, handing off without context, or taking work back at the first mistake. Here's a practical framework that works whether your EA sits next to you or 8,000 miles away.

Step 1: Audit a real week

Don't start from a job description. Start from your calendar and inbox.

For one week, keep a running list of every task you do that isn't core to your role. At the end of the week, sort each task into one of four buckets, a version of the approach described in Harvard Business Review by Julian Birkinshaw and Jordan Cohen (HBR):

1. Drop — it doesn't need doing.
2. Delegate — someone else can do it with instructions.
3. Redesign — it's needed but could be done differently (a template, an automation).
4. Keep — it genuinely requires you.

Most leaders find their "delegate" bucket is bigger than expected.

Step 2: Rank by frequency and pain

Delegate recurring tasks first. A weekly task you hand off saves you time every week forever; a one-off saves you time once.

Score each delegable task on:

• Frequency (daily, weekly, monthly)
• Time per occurrence
• Risk if done wrong (low, medium, high)

Start with high-frequency, low-risk tasks. Common first wins: scheduling, inbox triage, expense reports, meeting prep packs, CRM updates after calls.

Step 3: Define "done" before you hand off

The most common delegation failure is ambiguity. "Can you handle my calendar?" means nothing. "Book external meetings only Tuesday to Thursday, 10–4 Central, never back-to-back, with 15 minutes' buffer and a Zoom link" means something.

For each task, write down:

• The outcome: what good looks like.
• The rules: constraints and preferences.
• The decision rights: what they can decide alone, what they should propose, what they must escalate.
• The deadline or cadence.

Step 4: Use levels of authority

A useful model is to give each task an explicit authority level:

Start most tasks at level 2 or 3. Move them up as trust builds. This also makes feedback cleaner: if something goes wrong at level 3, the fix is usually a rule, not a reprimand.

Step 5: Record the process once

Instead of writing long documents, record a short screen video doing the task while narrating your choices. Your assistant then turns it into a written checklist, which you review. You get documentation without writing it. See how to write an SOP for your assistant.

Step 6: Build a daily and weekly rhythm

Delegation runs on rhythm:

• Daily: a short end-of-day summary from your assistant — what's done, what's pending, what needs you.
• Weekly: a 30-minute review of priorities for next week and feedback on the past week.
• Monthly: decide which tasks move up an authority level and what new work to hand off.

Step 7: Give feedback that improves the system

When something goes wrong, ask: was it a missing rule, a misunderstood rule, or a judgment call? Fix the rule or the checklist, not just the instance. Assistants learn fastest when feedback is specific, immediate and tied to the process.

What not to delegate (yet)

• Relationship-defining communication: a difficult conversation with a key client or employee.
• Decisions only you can make: hiring, firing, strategy, pricing exceptions.
• Tasks you can't yet describe: if you can't explain what "good" looks like, you're not ready to hand it off.

Common delegation mistakes

1. Delegating tasks, not outcomes. "Answer emails" vs. "Keep my inbox to under 20 items needing my attention."
2. Withholding context. Your assistant can't prioritize if they don't know your goals this quarter.
3. Reclaiming work after one mistake. Every new teammate makes mistakes. Fix the rule.
4. No single source of truth. Keep preferences, contacts and SOPs in one shared document.
5. Inconsistent availability. Block 15 minutes a day for your assistant's questions in the first month.

A starter delegation list for executives

• Inbox triage with agreed folders and flags
• Calendar scheduling and rescheduling
• Meeting briefs: attendees, context, last touchpoint, open items
• Travel booking to your rules
• Expense reports
• CRM updates after calls (for sales leaders)
• Weekly reports compiled from your tools
• Follow-up tracking after meetings

A worked example: from audit to handoff

Here's an illustrative result from step 1 (audit a real week) for a COO, with the decisions that followed:

About 12 of 16 hours were delegated within a month, recovering a meaningful slice of the week.

Checklist: a good handoff message

• What the task is and why it matters
• What "done" looks like, with an example if possible
• The deadline
• The authority level: do it, draft it, or recommend it
• Where to find what's needed
• Who to ask if stuck, other than you

The two-week test for any delegated task

After handing off a task, check it at two weeks with three questions:

1. Is it getting done without reminders? If not, the trigger or deadline is unclear.
2. Is the quality where it needs to be? If not, the "done" definition or the example needs work. Fix the instructions before blaming the person.
3. Have I stopped thinking about it? This is the real goal. If you still check every instance, either the authority level is too low or trust hasn't been built yet. Move from "draft" to "do and tell me" once quality is consistent.

Tasks that pass all three become permanent parts of the assistant's role. Tasks that fail twice usually need a better SOP, or they belong with someone else.

The bottom line

Delegation is a system: audit, prioritize, define done, set authority levels, document once, review on a rhythm. Leaders who treat it that way usually find they can delegate far more than they expected within the first few months.

If you'd like a dedicated assistant who's trained to work this way, see our Executive Assistant service or read onboarding a remote EA.

Sources

• Julian Birkinshaw and Jordan Cohen, Make Time for the Work That Matters, Harvard Business Review, 2013.