Why Virtual Assistants Fail: 6 Causes, and Only One Is the VA
Search for why VA relationships fall apart and you'll notice something about the results before you notice anything about the answers.
Nearly every page is published by a company that places VAs.
That's not a scandal. Placement firms know this territory better than anyone, and plenty of what they write is useful. But it does shape where the analysis stops. If your business model is finding people, the diagnosis tends to arrive at a person, and the fix tends to be another person. Better screening. Better matching. A replacement, at no charge, within thirty days.
Run that logic across an industry and you get a strange conclusion: VA relationships fail because the wrong VA was hired, over and over, at scale.
The pattern in the actual work says something different. Six things break these relationships. Five of them happen after the hire, on the executive's side of the desk, and they're the ones nobody has a commercial reason to write about.
1. The hire was treated as the finish line
Watch how the process is built and you can see the assumption inside it.
Enormous effort goes into the search — screening, interviews, skills tests, background checks, time-zone matching. Then the VA starts, and the machinery stops. What follows is a call, a set of logins, and a general sense that things will be figured out as they come up.
Everyone involved has done their job. The placement firm placed. The executive hired. And the two people now expected to build a working relationship have been handed no structure to build it inside.
The search was the visible problem, so the search got the investment. The handoff is where the money is won or lost, and it's the part with no owner. What that handoff should look like is laid out week by week in The First 30 Days With a VA.
What it looks like from the outside: things start fine, then get worse around week three. The early tasks were simple enough to explain in a sentence. The later ones aren't.
2. The role was written as a task list, not an outcome
Most VA job descriptions read like an inventory. Inbox management. Calendar. Travel. CRM updates. Follow-ups. Social posting.
Reasonable list. It also produces a task-doer, because it's the description of one.
Compare two versions of the same role. One person is told to post four times a week. The other is told they own the brand's visibility, and posting is how that happens. The first waits for content and asks what to post today. The second asks what the business is trying to grow this month, what questions keep coming up in sales calls, what assets exist, and what needs to be requested from the team.
Same work. Different job. Only one of them gets called proactive.
We build entire training tracks around this distinction, because it's the difference between someone who costs you attention and someone who returns it. And it's a difference the executive creates, in how the role is framed on day one.
What it looks like from the outside: they do exactly what you ask and nothing more, which reads as a lack of initiative. It's usually a lack of standing.
3. The context never transferred
You've been running this business a long time. You know which client wants bad news by phone, which invoice always needs a nudge, and what "as soon as you can" means from each of the three people who say it.
None of that is documented. It doesn't feel like knowledge — it feels like judgment, and judgment feels like something a person either has or doesn't.
But most of it isn't judgment. It's accumulated context, and context is transferable if anyone bothers to transfer it. When it stays in your head, you've handed over the mechanics of the work and kept the reasoning. The VA can execute the steps. They cannot make your call, because the logic behind your call never made the trip.
From there it goes one of two ways. They ask about everything, and you conclude they need too much hand-holding. Or they decide for themselves, and you conclude they go off-script. Two symptoms, one missing piece.
What it looks like from the outside: work that's technically complete and directionally wrong.
4. Nobody defined what "done" looks like
Ask most executives what good work looks like on a given task and you'll get a version of I'll know it when I see it.
That's honest. It's also unworkable, because it makes your VA's job a guessing game where the answer key only appears after they've submitted.
Definition of done is three things, and the third is the one people skip: what the finished output includes, what quality bar it has to clear, and one real example of something you approved without edits. The example does more than the other two combined. It carries all the standards you'd never think to articulate — tone, length, level of detail, how much context to include, when to flag versus decide.
Skip it and you've asked someone to hit a target you've described but never shown them. It's also the reason the same error keeps coming back — the mechanics of that are here.
What it looks like from the outside: endless revision cycles on work that keeps missing in a different direction each time.
5. There was no operating rhythm
Ask an executive how their VA is managed and the answer is usually that they talk most days.
Talking most days is not a rhythm. It's proximity, and it degrades in exactly the situations where structure matters — a busy week, a travel stretch, a stressful quarter. When you go quiet, the work goes quiet with you.
A rhythm is boring and specific. A standing weekly check-in that isn't triggered by a problem. A written update that arrives whether or not you asked. An approval line so the VA knows what to send and what to run past you. Feedback that lands close to the work rather than at Friday's review, because a note delivered on Monday costs one correction and the same note on Friday costs five.
The written update is the piece executives underrate most. We give Vamped VAs a weekly format built around what an executive needs to read: a thirty-second snapshot, what got done and what it moved, the numbers week over week, what's in motion, what needs a decision only the executive can make, and where they're focused next. Once that lands every week, most of the anxiety about whether a VA is working evaporates, because the question stops being a feeling and starts being a document.
What it looks like from the outside: you have no idea what they did all week, so you assume the answer is not enough.
6. Sometimes it is the fit
Which brings us to the one cause that is about the VA.
It's real, and pretending otherwise would be its own kind of dishonesty. Some VAs oversold their experience. Some are stretched across too many clients to give any of them a real week. Some are in a role that doesn't suit them and would be excellent somewhere else.
Two situations don't respond to better structure:
Trust. Dishonesty, a covered-up mistake, mishandled confidential information. Structure fixes performance. It doesn't fix trust, and the calculus is the same as it would be with any employee.
A genuine capability gap — visible after the person has had clear standards, an example of good work, and a fair window to use both. The sequence is what makes it a diagnosis instead of a guess. A gap you identify before supplying those three things isn't a read on the VA. It's a read on the setup, wearing a disguise.
If you're at the point of weighing that decision, the full version is here — the two cases that justify it, and the four that look identical from the inside.
Why the order matters
Reading a list like this, it's tempting to treat all six as equally likely and go looking for whichever one fits your situation.
They're not equally likely. Causes one through five are ordinary, and they compound — a role written as a task list makes the missing context harder to notice, which makes "done" harder to define, which makes the weekly rhythm feel like it isn't worth having. By month three you have a relationship that looks broken and a person who looks wrong for it.
Cause six is the least common and the most expensive to act on. It's also the only one the surrounding industry is set up to sell you a solution for. That combination is worth holding in mind the next time you read an article suggesting your VA might not be a fit.
The useful move is to work the list in order. Fix the setup, give it thirty days, and then look again. Either the work steadies, which is the usual outcome, or you now have a clean read on fit that was made against a standard the person had a fair shot at meeting.
Both are answers. Only one of them is available if you skip to the end.
Find out which cause is yours
The VA Scorecard runs your setup against the five dimensions that decide whether a VA relationship works — ownership, context, definition of done, operating rhythm, and measurement — and shows you the specific gaps producing your specific symptoms.
Twenty questions, about ten minutes.
If you're in the middle of it right now, start with Your Virtual Assistant Isn't Working Out. The Setup Is. — the same diagnosis, run on your situation rather than the pattern.