If your executive assistant relationship isn't working, the instinct is to blame the assistant. Wrong hire, wrong fit, wrong skill set. But after watching dozens of these partnerships break down, the pattern is almost always the same: the executive is the problem. Not out of bad intentions, but because nobody taught them how to work with an EA. The good news is that setup failures are fixable. Here's what's actually going wrong.
Why Does the Executive Assistant Relationship Fail?
Most EA relationships don't fail because the assistant is incompetent. They fail because the executive never gave the assistant what they needed to succeed. A great EA can handle a remarkable amount of complexity, but only if they have clear information, consistent access, and real authority to act.
Without those three things, even a talented EA spends most of their time guessing. They draft emails they're not sure you'll approve. They schedule meetings without knowing your actual priorities. They hold back on decisions because they've been burned before for acting without explicit permission. The result looks like underperformance. It's actually under-equipping.
Research from Office Dynamics, which surveyed more than 700 assistants, found that the top struggles EAs face all trace back to the same root issue: not enough time with, and not enough information from, the executive they support.
You Never Actually Onboarded Them
Hiring an EA and onboarding an EA are two different things. Most executives do the first and skip the second. They hand over a login and a calendar and expect results within a week. That's not how it works.
A good EA needs to understand your priorities, your communication style, your decision-making patterns, and your pet peeves. They need to know which emails you want to see immediately and which ones can wait. They need to know who gets access to your calendar and who doesn't. They need to know when you want a draft versus a decision.
None of that is obvious. It has to be taught, and it takes time. Full Focus puts it well: building an effective EA relationship is like building any high-trust partnership. You invest upfront, and you get compounding returns over time. Skip the investment, and you'll keep getting disappointing results.
A simple preferences document goes a long way. Write down how you like to communicate, what you want delegated, and how you want to receive updates. Share it on day one. Revisit it monthly until the patterns are established.
Your Expectations Are Unclear or Constantly Shifting
Vague expectations are one of the most common reasons EA relationships stall. If your assistant doesn't know what success looks like, they'll default to doing less rather than risk doing the wrong thing. That looks like passivity. It's actually self-protection.
The fix is specificity. Instead of "help manage my inbox," say "flag anything that needs a response within 24 hours, archive newsletters, and draft replies to vendor inquiries using the templates we've discussed." That gives your EA something concrete to execute against.
Shifting expectations are just as damaging. If your priorities change every week without explanation, your EA can't build reliable systems. They're constantly reacting instead of proactively managing. Regular check-ins, even just 15 minutes a week, solve this. Use that time to share what's changed, what's coming up, and where you want more or less involvement.
You're Not Delegating Enough
Many executives hire an EA and then continue doing everything themselves. They worry about the quality of delegated work. They feel guilty adding to someone's plate. They think it's faster to just do it. All of those instincts work against you.
An EA who isn't given real work can't get good at supporting you. Delegation is a skill that both parties develop together. The more you hand off, the better your EA gets at understanding your standards, and the more confident you become in their judgment.
Start with the tasks that drain your energy most. Email triage, scheduling, travel logistics, research requests. These are high-volume, low-stakes tasks that an EA can handle well with minimal context. As trust builds, you can delegate more complex work.
- Email triage and draft replies
- Calendar management and scheduling
- Travel booking and logistics
- Meeting prep and follow-up notes
- Research requests and vendor coordination
- Tracking action items and follow-ups
How to Reset a Struggling EA Relationship
If your current EA relationship isn't working, don't jump straight to replacing them. Start with an honest conversation. Ask them what they need more of, what's been unclear, and where they feel blocked. Most EAs will tell you exactly what's missing if you ask directly.
Then do the work you skipped at the start. Write down your preferences. Define what good looks like. Set up a weekly sync. Give them more to own, not less. Priority VA notes that leaders who put in the relationship work early end up with EAs who can practically read their minds. That's the goal.
If you're using an AI-based system like River Executive Assistant, many of these onboarding steps are built into the setup process. River learns your preferences over time, adapts to your communication patterns, and gets more useful the longer you use it. But even with River, the underlying principle holds: the more clearly you define what you need, the better the results you'll get.
Executive assistant relationships are one of the highest-leverage investments a busy professional can make. When they work well, they reclaim hours every week and reduce the cognitive load of managing a full calendar and inbox. When they don't work, the problem is almost always fixable. Start by looking at your own setup before you look at your assistant.