Resources
What to delegate first: a founder’s guide
Most founders don’t struggle because they have too much to do. They struggle because they keep doing everything themselves — including the work someone else could easily own.
By Oliver Bite, virtual and executive assistant
The short version
Start with recurring, low-risk work that eats time but doesn’t need your judgment. Once that runs smoothly, hand over the work that needs more context and trust.
Good delegation isn’t about offloading tasks. It’s about handing over outcomes — so the other person can use judgment, spot problems, and improve the process over time.
Why delegation often fails
People usually delegate tasks, not outcomes. They say “sort my inbox” or “book my travel” and then wonder why the result still doesn’t feel right.
Good delegation answers a different question: what result do I want, and who owns getting there? When you delegate an outcome — “keep my inbox under control” or “make sure I’m prepared for every meeting” — you give the other person room to think, not just execute.
A simple filter: what to hand over first
Before delegating anything, run it through three questions:
- Is it repetitive? If you do it the same way every week, it’s a strong candidate.
- Is it time-sensitive but not strategic? Things that must happen on time but don’t need your unique judgment.
- Does it free up your highest-value time? If handing it off gives you back hours for sales, strategy, or deep work, it’s worth delegating.
If a task hits two or more of these, it belongs on your “hand over first” list.
The first 5–10 tasks to delegate
For most founders and small teams, these are the highest-return places to start:
- Inbox triage — sorting, flagging, drafting replies, keeping the inbox under control
- Calendar management — scheduling, rescheduling, reminders, protecting focus time
- Travel logistics — bookings, itineraries, changes, confirmations
- Meeting prep and follow-ups — agendas, briefs, notes, action items
- Research briefs — vendors, options, comparisons, background reading
- Customer support tickets — first-line responses, routing, escalation
- Content scheduling — social posts, newsletters, basic publishing
- Expense and receipt tracking — collecting, categorising, flagging anomalies
- CRM updates — data entry, pipeline hygiene, follow-up reminders
- Vendor and supplier coordination — quotes, orders, renewals, chasing updates
What not to delegate yet
Some things are better kept close in the early stages — not because they can’t be delegated eventually, but because they need more trust and context first:
- Final hiring decisions
- Sensitive financial approvals
- Core strategy and positioning
- Anything requiring your unique judgment or relationships
Once trust is built and processes are documented, many of these can shift over time too.
How to hand over a task properly
A clean handover saves weeks of back-and-forth. Use this simple template for each task you delegate:
- Outcome: What does “done well” look like?
- Deadline or cadence: When does it need to happen, and how often?
- Tools and access: Which accounts, logins, or systems are needed?
- Decision rights: What can they decide alone, and what needs your sign-off?
- Check-in cadence: A short daily or weekly update, not constant supervision.
Writing this down once — even as a short shared doc — prevents most misunderstandings later.
Your first 30 days
| Week | Focus |
|---|---|
| Week 1 | Observe and learn — they shadow, ask questions, and document how you work |
| Week 2 | Own with oversight — they run the task, you review and give feedback |
| Weeks 3–4 | Own independently — they run it end to end, reporting on a set cadence |
This ramp-up builds trust gradually and surfaces issues early, before they become expensive.
Common questions
What if I don’t know what to delegate?
Track your time for one week. Anything you do repeatedly that doesn’t need your unique judgment is a candidate. Start with the item that annoys you most — momentum matters.
How do I avoid micromanaging?
Delegate outcomes, not steps. Agree on the result and the check-in cadence, then step back. If you find yourself checking daily, revisit the handover doc rather than hovering.
What if it goes wrong?
It will, sometimes. Treat early mistakes as part of the ramp-up, not a reason to pull everything back. Fix the process, clarify the expectation, and keep going.
When should I move from a virtual assistant to an executive assistant?
When the work shifts from “do this task” to “manage this part of my week.” That’s usually a trust and context milestone, not a job-title change. You can read more about that shift in Virtual or Executive Assistant: Which Do You Need?
Where I fit
I work on both sides of this line — taking recurring work off your plate as a virtual assistant, and stepping into calendar, travel, briefing, and follow-through as an executive assistant once trust is built. If you’re not sure what to hand over first, a 30-minute call is usually enough to map it out together.