Common EA Hiring Mistakes

Hiring an executive assistant seems simple. Pick a service, get matched, start delegating. But most people who try it for the first time make the same handful of mistakes, and those mistakes are expensive—not just in dollars, but in wasted time and the false conclusion that "an EA doesn't work for me." Here are the five that come up again and again, with specific guidance on how to avoid each one.

Mistake 1: Hiring Before Knowing What to Delegate

The most common mistake happens before you even sign up. You know you're busy. You know you need help. So you hire an EA and figure you'll sort out the details later. Then your EA starts, you're in back-to-back meetings, and you can't find 20 minutes to assign them meaningful work. They sit idle. You get frustrated. The engagement fizzles.

This happens to roughly half of first-time EA clients. The enthusiasm of signing up crashes into the reality that delegation requires upfront effort. Your EA cannot read your mind, and they cannot invent work for themselves in their first week. If you do not have tasks ready to hand off, your expensive new resource becomes an expensive new problem.

The fix: Before hiring, spend one week tracking every task you do. Write them all down, even the small ones. At the end of the week, sort them into three categories: only I can do this, someone could do this with instructions, and someone could do this better than me. The second and third categories are your delegation list. If that list doesn't add up to at least 10 hours a week of work, you might not need an EA yet—or you need to think harder about what you're holding onto and why.

Go further: for each task on your delegation list, write a one-sentence description of the expected output. "Manage my calendar" is not a task. "Schedule all meeting requests within 24 hours using my Calendly preferences and decline anything that conflicts with my focus blocks" is a task. Having this list ready before your EA starts means you can hit the ground running instead of stalling.

Mistake 2: Choosing on Price Alone

There's a meaningful difference between a $10/hour VA from a marketplace and a $3,000/month managed EA service. Both have their place, but they're not interchangeable. The cheap option works for structured, repeatable tasks where you provide detailed SOPs. The managed service works when you need someone who can operate with autonomy and judgment.

Founders who choose purely on price often end up spending more in the long run. They cycle through two or three budget assistants, spending weeks onboarding each one, before landing on a premium service that sticks. The total cost of failed experiments exceeds what they would have spent just starting with the right tier. Each failed onboarding costs you three to four weeks of lost productivity, plus the dollar cost of paying for an assistant during a ramp-up period that never pays off.

The reverse is also true. Some people overshoot on their first hire, signing up for a $5,000/month premium service when their needs are entirely administrative. If 90% of your delegation list is calendar management, email triage, and data entry, a $1,500/month service handles that fine. You do not need a US-based assistant with 15 years of C-suite experience to manage your Calendly links.

The fix: Match the service tier to the task complexity. If 80% of your delegation list is process-heavy and well-defined, a budget service is fine. If you need someone drafting client communications, managing nuanced scheduling, or making judgment calls, invest in quality. Check our comparison table to see what each tier actually gets you. Be honest about what your tasks actually require, not what sounds impressive.

Mistake 3: Skipping Onboarding

People treat EA onboarding like it should be instant. They expect their assistant to read their mind from day one. When the first deliverable isn't perfect, they blame the EA instead of the onboarding.

Every EA needs a ramp-up period. Even a senior assistant who's worked with dozens of executives needs to learn your specific preferences, tools, communication style, and standards. Skipping this phase doesn't save time. It creates a shaky foundation that cracks under pressure.

The onboarding mistake often looks like this: you sign up on a Monday. Your EA sends a welcome message. You reply with "great, can you handle my inbox?" with no further context. By Wednesday, your EA has archived an email from an investor you were waiting on, and you are convinced they are incompetent. They are not. They just did not know that the email from john@acmecapital.com is from someone who matters. That is an onboarding failure, not a talent failure.

The fix: Dedicate a full week to onboarding. Write a "How I Work" document. Do a kickoff call. Start with low-stakes tasks and build up. See our full first-week guide for the complete playbook. The time you spend on onboarding in week one saves you from the frustration of re-doing work in weeks two through twelve.

Mistake 4: Not Giving Feedback Early

This one is subtle and destructive. Your EA does something slightly wrong. Not wrong enough to correct, so you fix it yourself and move on. This happens three more times. Now you have a pattern: your EA does the task their way, you quietly redo it, and resentment builds on both sides. Your EA thinks everything is fine because you never said otherwise. You think they should know better.

Small uncorrected errors compound into large misalignments. After two months of silence, the gap between your expectations and their output is so wide that the relationship feels broken. It isn't. It just needed a five-minute conversation in week one.

The feedback avoidance often stems from not wanting to seem difficult or micromanaging. But the paradox is that early, specific feedback prevents the need for micromanagement later. An EA who gets clear feedback in their first week calibrates quickly and needs almost no correction by month two. An EA who gets no feedback develops habits you hate and is much harder to redirect later.

The fix: Give feedback within 24 hours, every time. Be specific and direct. Not "this isn't what I wanted" but "I need three options instead of one, and list the price for each." Not "the email was off" but "my emails to clients are always three sentences or fewer, never use exclamation marks, and always include a specific next step." Schedule a weekly review for the first month. After that, you'll find you rarely need to correct course because the early calibration did the work.

Frame feedback as investment, not criticism. "Here is how to do this in a way that matches what I need" lands better than "you did this wrong." Most EAs genuinely want to improve and appreciate specific guidance. The ones who do not respond well to feedback are the ones you should replace, but you will not know the difference until you actually give feedback consistently.

Mistake 5: Treating Your EA Like a Task Robot

The most underrated mistake: never sharing context. You fire off tasks like "Book a restaurant for Thursday" without saying it's a dinner with a prospective investor who loves Japanese food. Your EA books a casual pizza place. You're annoyed. They had no way to know.

EAs who understand the why behind tasks make dramatically better decisions. They prioritize correctly. They catch errors you would have missed. They anticipate follow-up tasks. But they can only do this if you treat them as a thinking partner, not a vending machine for completed tasks.

The context gap shows up everywhere. Your EA books a meeting at 3pm, not knowing that you had a draining board call at 2pm and wanted a buffer. They schedule a call with a vendor, not knowing you are about to cancel that vendor's contract. They send a follow-up email to a prospect, not knowing the deal fell through yesterday. Every one of these situations is preventable with 10 seconds of context.

The fix: Add one sentence of context to every request. "Book a restaurant for Thursday—this is a dinner with an investor, somewhere upscale, preferably Japanese." That one sentence takes five seconds to type and completely changes the output. Over time, your EA builds a mental model of how you operate and starts filling in the context themselves.

Beyond individual tasks, share broader context periodically. Tell your EA what your big priorities are for the quarter. Let them know when you are in fundraising mode versus heads-down building mode. Share when you are stressed about a deadline so they know to protect your calendar more aggressively. This broader context turns a reactive assistant into a proactive one.

Mistake 6: Giving Up Too Soon

The first month with a new EA is the hardest. You are spending time on onboarding that you could be spending on work. Your EA is making mistakes as they learn your preferences. The delegation feels like it is creating more work, not less. This is normal. Every EA relationship goes through this phase.

The people who quit after three weeks never get to the payoff. The payoff comes in month two, when your EA has absorbed your preferences and starts operating with real autonomy. By month three, they are saving you 10-15 hours a week and you wonder how you functioned without them. But you have to get through the initial investment period to reach that return.

The fix: Commit to a minimum 90-day evaluation period. The first 30 days are onboarding. The second 30 days are optimization. The third 30 days are where you see the real value. If you are still unhappy after 90 days of genuine effort on both sides, the match might be wrong and you should try a different assistant or service. But do not bail at week three because it feels like work. It is supposed to feel like work at first. The entire point is that it stops feeling like work later.

The Meta-Mistake

Every mistake above shares a root cause: treating the EA relationship as transactional instead of collaborative. You're not buying a software tool. You're building a working relationship with a human who gets better the more you invest in them. The people who get the most value from their EAs are the ones who spend the first month setting things up properly and giving honest, constructive feedback. After that initial investment, the system runs itself.

If you take one thing from this guide: the quality of your EA relationship is primarily determined by the quality of your delegation, not the quality of the assistant. A good assistant with bad delegation produces mediocre results. A decent assistant with excellent delegation produces outstanding results. The variable you control is the delegation. Focus there first, and the rest follows.