.avif)
.avif)
How to Train Your Executive Assistant: A Practical 30-Day Plan
You hired the right person. Now comes the part most executives skip: training them to work with you specifically.
This is where EA relationships succeed or fail. An executive assistant who is objectively talented can underperform if they don't understand your priorities, your communication style, your decision thresholds, and your working rhythms. The first 30 days aren't just about getting up to speed—they're about encoding the context that turns a skilled professional into a genuine force multiplier.
What makes training an EA different from training most roles is that you're not just teaching processes—you're teaching yourself. Your inbox, your calendar, your stakeholder relationships, your voice. An EA can't read your mind. The first 30 days are the process of externalizing what's in your head so they can eventually operate without it.
This guide gives you the framework: week by week, with specific actions, conversations, and checkpoints.
Before Day 1: Clarify What You're Actually Delegating
The biggest mistake executives make before an EA starts is assuming the EA will figure out what to do. They won't—not quickly, and not well, unless you do this prep work first.
Before your EA's first day, complete three things:
1. Write a delegation inventory. List every recurring task that currently lives in your brain: inbox triaging, calendar management, travel booking, research requests, document prep, stakeholder follow-up. Be specific. "Handle email" is not a task. "Clear promotional and newsletter emails by 8am, flag emails from [specific names] as priority-one, and draft responses for anything from partners requiring same-day reply" is a task.
2. Define your decision threshold. What decisions should your EA make autonomously? What should they flag? What should they escalate immediately? Most EAs default to asking permission for everything because no one has told them where the line is. Write it down before day one.
3. Give them access. Calendar, email inbox (with whatever permissions match your model), travel booking tools, task management software, communication channels. Don't let day one be spent on IT tickets.
Week 1: Foundations
Week 1 is not about productivity. It's about orientation.
The Day 1 Briefing
Spend 60–90 minutes in a structured Day 1 conversation covering:
- Your priorities. What are the three most important things happening in the next 30, 60, 90 days? Your EA needs to understand what you're optimizing for, not just what you need done today.
- Your stakeholder map. Who are the 10–20 people they'll interact with most on your behalf? What's the relationship context for each? What tone, formality, and responsiveness standard applies?
- Your communication style. How do you write? What's your email voice? If you could hand them three emails you've written that represent your best work, which ones would you choose?
- Your calendar philosophy. What time blocks are sacred? What meeting types get accepted without question? What requires your review? What should be declined automatically?
Shadow and observe (Days 1–3)
Before your EA takes ownership of anything, have them observe. Give them read access to your email and calendar and ask them to prepare a summary at the end of each day: "Here's what I noticed, here are the three things I would have handled, here's how I would have responded." This reveals gaps in their understanding before they act on them.
Start with low-stakes delegation (Days 3–5)
Pick three to five tasks you can delegate without anxiety: scheduling a specific meeting, processing your newsletter inbox, booking a known trip. Watch how they handle it. The goal isn't perfection—it's understanding their default approach so you can calibrate.
Week 2: Building Systems
By week two, your EA should be moving from observation to execution on a set of defined workflows. This week is about replacing ad-hoc work with systems.
The inbox system
Build the inbox protocol together. Walk your EA through your actual inbox live: "Here's how I think about this category. Here's what I want you to do with emails from this sender. Here's the draft I'd send to this message." Don't just hand them the keys and hope for the best. The first week's email handling is your best training data.
The calendar system
Define your scheduling rules explicitly: buffer time between meetings, no-meeting mornings or afternoons, travel time for in-person, prep time before key calls. Give them a written version they can reference without asking you every time.
The daily brief
Establish a daily brief cadence. Many EA relationships work well with a 5-bullet async summary at the start of the day (or end of day if time zones are offset): top three priorities, anything requiring attention, flagged items, pending decisions. This keeps you connected without requiring synchronous check-ins.
Week 3: Expanding Autonomy
By week three, your EA should be handling defined tasks with minimal oversight. The goal this week is expanding their decision-making range.
The decision calibration conversation
Review the week two work together. For every task they escalated to you, ask: "What would you have done if I wasn't available?" For every decision they made autonomously, ask: "Walk me through your thinking." This conversation calibrates where their judgment is strong and where they need more context.
Expand stakeholder ownership
By week three, your EA should be responding to some stakeholders directly in your name. Start with lower-stakes relationships—vendors, recurring meeting partners—and expand from there. Give them sample language for common scenarios: meeting requests, follow-ups, polite declines.
Introduce research and prep tasks
Week three is when you can start assigning research requests and meeting prep. This is where EA leverage starts to compound: instead of you preparing for every call, your EA briefs you. Even a one-page summary for a 30-minute meeting saves 20–30 minutes of your prep time. Over a week, that's hours reclaimed.
Week 4: Independence
Week four tests whether the foundation is set. By now, your EA should be handling the majority of defined workflows independently. Your role shifts from managing the workflow to reviewing the output.
The Week 4 audit
Review four areas:
- Inbox: Are the email drafts matching your voice? Are the triaging decisions correct?
- Calendar: Is your schedule reflecting your stated priorities? Is buffer time being protected?
- Stakeholder communications: Is the tone right? Are responses going out in time?
- Research/prep: Are meeting briefs structured the way you want? Are they saving you real time?
Make the feedback specific. "This email is too formal for this relationship" is useful. "This isn't quite right" is not.
Recalibrate and level up
Week four is also when you have enough data to expand scope. What additional tasks could your EA own? What's the next category of delegation? The goal isn't to freeze the scope at day 30—it's to use the foundation of the first 30 days to keep expanding.
What Makes EA Training Different from Other Role Training
Most job training is about processes. EA training is about judgment.
A great executive assistant needs to understand your working style well enough to make decisions you'd be comfortable with when you're not available. That's not something you can write in a manual. It's built through observation, trial, feedback, and recalibration.
Two things accelerate this transfer:
Give context, not just tasks. When you delegate, say "why" as often as you say "what." The EA who understands why you're prioritizing a board meeting differently from a vendor call can extend that judgment to new situations. The EA who only knows what you've told them to do needs to be instructed for every new scenario.
Give feedback in the moment. When an email draft is almost right but the tone is off, say so immediately—and say why. Patterns stack fast. Three pieces of feedback on email tone in week two produces dramatically different week three output than waiting until a weekly review to address it.
How Managed Placement Services Handle This
Companies that use managed placement services like Oceans get structured onboarding support built into the engagement. Oceans works with both the company and the placed EA through the first 30 days to accelerate the calibration process—context-setting protocols, stakeholder introduction frameworks, and check-in structures.
This doesn't replace the work you need to do as the executive. It means you're not doing it alone or starting from zero. The EA arrives with professional training and structure; your job is to layer in your specific context on top of a strong foundation.
Whether you're hiring independently or through a service, the principles in this guide apply.
FAQs
How long does it take to train an executive assistant?
The foundational training period is 30 days. Most EAs are handling core workflows independently by day 14–21. Full calibration—where the EA can anticipate needs and operate with minimal oversight—typically takes 60–90 days.
What should I include in an executive assistant training plan?
Cover four areas: your priorities and context, your stakeholder map and relationship dynamics, your communication style and voice, and your decision thresholds (what they should handle autonomously vs. escalate).
How do I delegate effectively to my EA?
Start with low-stakes tasks, observe their default approach, calibrate together, and expand scope progressively. Give context, not just tasks. Feedback in the moment beats weekly reviews.
What's the biggest mistake executives make when training an EA?
Expecting the EA to figure out what to work on. An executive assistant needs your context—your priorities, your communication standards, your stakeholder relationships. That information only comes from you, and it needs to be transferred deliberately.
Building Brilliant Together
The 30-day plan isn't about grinding through a checklist—it's about building the foundation for a partnership that compounds in value over months and years.
Executives who invest in the first 30 days get an EA who knows their world well enough to operate as a true partner. Executives who skip it get a task executor who requires constant direction.
If you're working with an Oceans Diver, your dedicated account manager will support the first 30 days. If you're hiring independently, this guide gives you the structure. Either way, the investment in proper training is the difference between an EA who changes how you work and one who just handles the easy stuff.
.webp)
.webp)
