Many business owners avoid giving their VA direct feedback because it feels uncomfortable, and they fear it will damage the relationship. The result is a VA who never improves because they never know what is wrong — and a client who grows increasingly frustrated while saying nothing. Here is how to give feedback that drives improvement without creating conflict.
For more context, see what a virtual assistant is, virtual assistant pricing, and 50 tasks to delegate to a virtual assistant.
Why Feedback Conversations Feel Awkward
- Power imbalance anxiety: You are paying the VA, which can make criticism feel like a threat to their livelihood.
- Cultural sensitivity: Many VAs from the Philippines, Latin America, and other regions have high-context communication styles where direct criticism can feel harsh.
- Lack of structure: Without a framework, feedback conversations meander and often end without clear resolution.
- Timing issues: Feedback delivered in the heat of frustration (right after discovering an error) is less effective than feedback delivered calmly.
A Structure That Works
The SBI Framework (Situation → Behavior → Impact)
- Situation: Describe the specific context without generalization. "In the report you submitted on Tuesday" — not "You always..."
- Behavior: Describe the specific action or output. "The client name in the header was incorrect" — not "you were careless."
- Impact: Explain why it matters. "This reached the client before I caught it, which required a correction and an apology."
Then: Ask for their perspective. Often there is context you don't have. Then: Agree on the specific fix or standard for next time.
Written First, Verbal Second
For sensitive feedback, write it down before saying it. This forces you to be specific and non-emotional. You can choose to:
- Send the written feedback via Slack or email (works well for minor corrections)
- Use it as a script for a video call (better for performance conversations)
Written feedback is also useful for the VA — they can reference it when improving.
What Not to Say (And What to Say Instead)
| Avoid | Better Alternative |
|---|---|
| "You always make mistakes" | "In the last three reports, there were errors in [specific area]" |
| "This is terrible" | "This doesn't meet the standard we need because [specific reason]" |
| "I thought you understood" | "I may not have been clear enough in my brief — let me clarify" |
| "Why would you do it this way?" | "Help me understand your reasoning here — I want to make sure my instructions are clear" |
Building a Feedback Culture
The best VA relationships have regular, low-stakes feedback built in:
- End of week check-in: "What went well, what was unclear, what should we adjust?"
- Task-level feedback: Brief notes in your task manager after reviewing deliverables
- Monthly performance pulse: A 15-minute call reviewing the month's output and priorities
When feedback is expected and regular, individual corrections feel less threatening.
After the Conversation
- Update the relevant SOP to reflect the corrected standard
- Follow up after the next similar task to confirm improvement
- Acknowledge when improvement happens — positive feedback is as important as corrective feedback
The VA relationships that last are ones where both parties can communicate honestly. Feedback given with specificity and care builds trust — it does not erode it.
Virtual Assistant VA places VAs who actively seek feedback and demonstrate consistent improvement. Find a candidate who treats professional development as part of the job.