Your Virtual Assistant Isn't Working Out.

delegation executive support working with a va Aug 26, 2026

It's usually a Tuesday.

You asked for something on Thursday. You followed up Monday. What came back is close, but wrong in a way that will take you longer to fix than it would have taken to do yourself. And the thought shows up fully formed, no warm-up required:

This isn't working.

Take the thought seriously. Then slow down for ten minutes, because the decision on the other side of it is expensive in both directions. Replacing a VA costs you the search, the onboarding, and another three months of ramp. Keeping the wrong one costs you the thing you hired them to protect. Getting it wrong in either direction is the same mistake made from opposite ends.

So before you decide, work out which problem you have.

The uncomfortable version first

Sometimes it is the person.

Anyone who tells you otherwise is selling something. There are VAs who oversold their experience, VAs who are stretched across too many clients to give yours real attention, and VAs who are in the wrong role entirely and know it. That's real, and later in this post there's a short section on how to tell.

But it is not where the odds sit.

When a VA relationship goes sideways in the first ninety days, the far more common story is a capable person who was handed work without the thinking behind it, no definition of what finished looks like, and no structure to operate inside. They're not failing at the job. They're guessing at it, and guessing looks identical to incompetence from the outside.

Which points at a different question than the one you were asking.

Not: is my VA good enough?

But: was this handoff ever built to work?

Three checks will tell you.

Check 1: Did you skip four doors to get to the fifth?

At Vamped we teach a filter for anything sitting on an executive's plate. Five moves, in order:

Own. Delete. Batch. Automate. Delegate.

Delegate is last. That order is the whole point, and it's the step almost everyone skips.

Watch what happens when a new VA starts. The executive finally has help, so they clear the decks — every recurring annoyance, every half-abandoned process, every task they've been dreading, all of it moves across in the first two weeks. It feels like progress. It feels like exactly what you hired for.

But a good portion of that pile never should have survived the first four doors. Some of it needed deleting, because it was reporting nobody reads and follow-up nobody wanted. Some of it needed batching. Some of it needed a tool, not a person. What's left after that filter — the work that still needs a human's judgment and coordination, just not yours — is the real job.

Hand over the unfiltered version and you've given someone a role built out of your leftovers, with no way to tell which parts matter. When they prioritize badly, that reads as poor judgment. When they drown, that reads as slow. Neither is a fair read of a person who was handed a pile nobody had sorted.

Test it: open the task list you gave your VA and run each line through the five moves as if they'd never been hired. If more than a third of it belongs somewhere other than delegate, you don't have a performance problem. You have an inventory problem.

Check 2: Did the work arrive with its thinking attached?

You've been doing this a long time. You know why the Thursday report goes to one client differently than the others, which vendor emails need a softer tone, and when "urgent" from a particular person means today versus this week.

None of that is written down. It doesn't feel like knowledge — it feels like common sense, because for you it is. It's also the entire difference between a task getting done and a task getting done right.

When you transfer the mechanics and keep the reasoning, you've handed over the visible half of the job. Your VA can execute the steps. They cannot make the call you'd make, because the logic behind the call never came with it. So they either interrupt you constantly, which reads as needing hand-holding, or they decide for themselves, which reads as going off-script.

Both of those are the same missing piece wearing different clothes.

Test it: take the last piece of work that came back wrong. Ask yourself what you'd have needed to know to get it right, and then ask whether you ever said it out loud. Most of the time you'll find the correct answer depended on something that has only ever existed in your head.

If the same errors keep resurfacing after you've raised them, that's a specific and fixable problem — the feedback loop, covered here.

Check 3: Is there a structure, or only a relationship?

Ask an executive how their VA is set up and you'll usually get some version of: we talk most days, they know what to do.

That is a relationship. It is not a structure, and it holds right up until the first thing goes wrong.

Support that survives contact with a real week has parts you can name:

Onboarding that transferred context, not just logins
Access levels that expanded on a schedule as trust was earned
An approval line — what they send, what you see first
Communication rules, including how fast a response is reasonable and what counts as urgent
Documented workflows for anything that repeats
A standing check-in that isn't triggered by a problem
Clear ownership, so nothing sits in the gap between you

Read that list again against your own setup. If most of it isn't there, your VA has been improvising a job for however long they've been with you, and doing it while trying not to bother you too much.

Vague delegation is why this fails. Structure is why it works. That's not a slogan — it's the difference between someone who needs you and someone who protects you.

When it is the fit

Two situations don't respond to better structure, and it's worth naming them plainly so you're not stuck in a reset that was never going to land.

Trust. Anything involving dishonesty, a covered-up mistake, or the mishandling of something confidential. Structure fixes performance. It doesn't fix trust, and the calculus here is the same as it would be for any employee.

A real capability gap. Not "they're still learning" — a genuine mismatch between the work and the person, visible after they've had clear standards, examples of good work, and a fair window to use both. The order matters. A gap you diagnose before you've supplied those three things isn't a diagnosis. It's a guess.

Everything outside those two is a setup problem, and setup problems are fixable in weeks. If you're weighing the decision seriously, the full version of that call is here — including the four situations where letting someone go is the expensive mistake.

What the next thirty days look like

If the checks pointed at your side of the desk, don't restart the relationship with an apology and a vague promise to communicate better. Restart it with structure.

Re-filter the list. Run every task through Own, Delete, Batch, Automate, Delegate. Expect the delegate column to be shorter than what you handed over, and expect that to feel like a relief for both of you.
Narrow the scope, then deepen it. Pick three to five recurring tasks and give your VA full ownership — not "help me with," but yours. Consistency on a small surface beats partial coverage of a wide one, every time.
Write the definition of done. For each of those tasks: what finished looks like, what good looks like, and one real example of the output you'd approve without edits.
Move feedback closer to the work. Feedback that arrives at Friday's check-in is feedback on a task that has already been repeated several times the wrong way that week. Same note delivered Monday costs one correction instead of five.
Put a check-in on the calendar that isn't about a problem. Twenty minutes, weekly, same slot. It's where the small confusions surface before they become the thing you're reading a post like this about.

Thirty days of that is enough to tell you what you're working with. Either the work steadies — which is the usual outcome, and the reason we do this for a living — or you now have a clean, honest read on fit, made against a standard the person had a fair shot at meeting.

The week-by-week version of that reset is laid out in The First 30 Days With a VA. It's written for a new hire and works just as well as a restart.

Either way you'll know. And you'll have stopped paying for the question.

Score your setup in ten minutes

Reading a diagnostic and running one on yourself are different things. The VA Scorecard walks the five dimensions that decide whether a VA relationship works — ownership, context, communication, structure, and measurement — and gives you a score with the specific gaps that produced it.

Twenty questions, about ten minutes.

Score your setup →