“That’s not what I asked for” does not help anyone improve. Many founders give vague corrections or rewrite the work themselves. The assistant never learns what success looks like. When you spend twenty minutes fixing a report instead of five minutes explaining what went wrong, you’ve trained yourself to do double work and trained your assistant to wait for rewrites.
This guide explains how to give feedback that actually changes behavior, especially when working across cultures and time zones with Philippines-based executive assistants.
Key Takeaways
- Cultural differences, time zones, and respect dynamics affect how offshore EAs receive feedback. Adjust accordingly.
- Structure matters: Describe desired outcome first, point to specific issues, show correct examples, not just vague criticism.
- Use written feedback for simple, recurring tasks needing references. Use video for complex, visual, or tone-sensitive corrections.
- Give feedback frequently: Quick daily task notes prevent mistakes becoming habits. Weekly reviews address patterns and growth.
- Focus on work, not person. Explain context and stakes. Reinforce improvements, don’t just criticize. Build a feedback culture.
- With Filipino EAs: Be direct but respectful, avoid vague terms, confirm their understanding. Adapt to local communication norms.
Why feedback feels different with offshore teams
Working with an offshore executive assistant requires a different communication approach than managing someone in your office. Three factors change how feedback lands.
Cultural communication differences
Many Philippines-based professionals communicate in a more indirect way than founders in the United States or Europe. Assistants may avoid pushing back or asking clarifying questions because direct disagreement can feel disrespectful in their cultural context.
This means unclear instructions often go unchallenged. If you say “clean up this spreadsheet,” your assistant might not ask what “clean up” means because they don’t want to appear incapable. You get back something technically cleaned up but not what you needed.
Time zone delays
When teams work across time zones, unclear instructions can delay progress by an entire day. You send feedback at 5 PM Eastern. Your assistant sees it at 6 AM Manila time. They have questions but you’re asleep. By the time you respond, another twelve hours pass.
Clear feedback reduces this cycle. When your correction includes the specific issue, the correct format, and an example, your assistant can act immediately without waiting for clarification.
The respect dynamic
In many offshore cultures, assistants show respect by avoiding confrontation. They won’t tell you that your instructions were confusing or that your deadline is unrealistic. This silence can look like agreement when it’s actually uncertainty.
Founders must create space where questions and clarification are welcome. Say explicitly: “I expect you to ask questions when something is unclear. Asking questions is part of doing good work, not a sign that you don’t understand.”
The structure of clear feedback
Effective feedback follows a predictable structure that works across cultural differences.
Start with the desired outcome
Explain what the final result should look like before discussing what went wrong. Your assistant can only hit a target they can see.
Instead of starting with the mistake, describe the format, detail level, or timing you expected for the task. “The weekly report should include three sections: completed tasks with time spent, blocked items with reasons, and priorities for next week. Each section needs specific examples, not summaries.”
When your assistant understands the destination, the correction makes sense.
Point to the specific issue
Focus on one clear example rather than general criticism. Vague feedback like “this needs work” or “not quite right” forces your assistant to guess what you want changed.
Specific feedback sounds like: “The report included the data, but the summary section was missing. I needed a two-sentence summary at the top explaining what the numbers mean for our pipeline.”
One clear problem is easier to fix than multiple vague concerns.
Show the correct version
Assistants improve faster when they can see the correct format or example. Instead of describing what you wanted, show it.
Take two minutes to create a reference version of the task done correctly. A before-and-after comparison eliminates guesswork. Your assistant can match the pattern instead of interpreting your description.
Written vs verbal feedback
Different correction types work better in different formats.
When written feedback works best
Written feedback helps with:
- Task corrections that need a permanent record the assistant can reference later
- Process documentation that applies to future work
- Recurring workflows where the same standards apply each time
- Simple mistakes that don’t require discussion
Short written notes create a reference your assistant can check before submitting similar work. A three-sentence correction in Slack becomes a personal checklist.
When video or voice feedback works better
Short video recordings often explain complex corrections faster than long written messages. A quick screen recording can clarify expectations in minutes when written instructions would take paragraphs.
Use video for:
- Visual tasks where you need to show, not describe
- Workflow explanations with multiple steps
- Tone or style corrections that are hard to articulate
- Situations where your written feedback keeps getting misunderstood
Record your screen while walking through the correct version. Five minutes of video can replace thirty minutes of back-and-forth messages.
How often you should give feedback
Frequent feedback helps assistants improve faster than periodic reviews.
Daily task feedback
Quick comments on completed work help assistants adjust immediately. Don’t wait for weekly meetings to mention that the meeting notes format is wrong.
Daily feedback can be as simple as: “Perfect. Keep using this format.” or “Next time, add the action items at the top instead of the bottom.”
Small corrections made daily prevent large problems from becoming habits.
Weekly review conversations
A short weekly meeting allows founders to discuss patterns, improvements, and questions. This is where you address themes rather than individual tasks.
Weekly reviews work best when you cover:
- What went well and should continue
- What patterns need adjustment
- Questions the assistant has been holding
- Priorities for the coming week
For more detail on structuring ongoing management, see the guide on how to manage an executive assistant.
How to address mistakes without damaging the relationship
Corrections can either build trust or erode it depending on delivery.
Focus on the work, not the person
Correct the task outcome rather than criticizing the assistant. The difference is subtle but significant.
Task-focused: “The meeting summary missed two action items from the conversation.”
Person-focused: “You forgot details again.”
The first version invites correction. The second version invites defensiveness.
Explain the context
Assistants perform better when they understand why the task matters. Context transforms tasks from arbitrary requests into contributions they can own.
Explain how the information will be used. “This report goes directly to the client, so typos reflect on our firm.” or “The CEO reads these summaries before board meetings, so accuracy matters more than speed.”
When your assistant understands the stakes, they can make judgment calls aligned with your priorities.
Reinforce improvements
When assistants adjust successfully, mention the improvement. Positive reinforcement builds confidence and trust.
“The format on this week’s report was exactly what I needed. Keep using this structure.” takes five seconds and signals that you notice when things go right, not just when they go wrong.
Building a feedback culture with offshore staff
Long-term success requires systems, not just individual corrections.
Encourage clarifying questions
Tell assistants that questions are expected, not a sign of failure. Many offshore team members have been trained to figure things out on their own rather than ask for help.
Be explicit: “If you’re spending more than ten minutes uncertain about how to proceed, ask me. A quick question now saves us both time later.”
Then actually respond positively when they ask. If you act annoyed by questions, they’ll stop asking and start guessing.
Document repeatable processes
Documenting workflows reduces repeated corrections. When the process exists in a document, your assistant can self-correct by checking the reference.
Create simple process docs for recurring tasks. Include examples of correct output. Link to previous work that met your standards.
For a full list of what works well with documented handoffs, see tasks to delegate to executive assistant.
Review performance regularly
Short performance conversations help assistants understand expectations beyond individual tasks. Monthly or quarterly reviews address growth, not just correction.
Cover what’s working, what needs development, and what goals make sense for the next period. Assistants who understand their trajectory perform better than those who only hear about mistakes.
Feedback tips for Philippines-based executive assistants
Working specifically with Filipino assistants benefits from understanding local communication norms.
Be direct but respectful
Clear instructions are appreciated when delivered respectfully. You don’t need to soften your feedback with excessive qualifiers, but blunt criticism without context can feel harsh.
Direct and respectful: “The deadline was missed by two days. What blocked you, and how can we prevent this next time?”
Blunt without context: “You missed the deadline. This can’t happen again.”
The first version invites problem-solving. The second version invites silence.
Avoid vague language
Ambiguous phrases often cause confusion across cultures. Words like “soon,” “better,” or “more detail” mean different things to different people.
Replace vague terms with specifics:
- “Soon” becomes “by 3 PM Manila time”
- “Better” becomes “include three examples instead of one”
- “More detail” becomes “add the client name and dollar amount for each item”
Confirm understanding
Ask the assistant to summarize the task to confirm clarity. This isn’t checking whether they listened. It’s checking whether your instructions were clear.
“Before you start, tell me what you’ll deliver and when.” catches misunderstandings before they become wasted work.
Feedback examples founders can use
These phrases keep feedback clear and constructive.
Acknowledging good work:
- “Here is what worked well in this task: the structure made the information easy to scan.”
- “This format is exactly what I needed. Save this as a template for future reports.”
Pointing to specific issues:
- “Here is the section that needs adjustment: the summary uses general statements instead of specific numbers.”
- “The formatting is correct, but the data in column C doesn’t match the source file.”
Directing future work:
- “Next time please include the client name in the subject line so I can find these emails quickly.”
- “Going forward, send a draft for review before finalizing anything over $500.”
Related guidance for CPA firms using offshore assistants
If you’re running a CPA firm with offshore support, these related guides address common questions:
- Executive assistant for CPA firm cost covers typical investment ranges and what affects pricing.
- Onboarding EA for tax season explains how to get an assistant productive before busy season starts.
- What CPAs should never delegate addresses the boundaries around sensitive client work.
- EA skills for accounting firm outlines what to look for when evaluating candidates.
Making feedback work long-term
Feedback is one of the most important responsibilities when managing offshore staff. Clear instructions, specific corrections, and regular communication help assistants improve quickly.
The founders who get the best results from offshore support treat feedback as a skill they develop, not an inconvenience they tolerate. Every correction that sticks is a correction you never have to make again.
With the right approach, feedback becomes a tool for building a strong long-term working relationship where your assistant anticipates your standards instead of waiting for your corrections.
If you’re ready to work with an offshore executive assistant who comes with training, documented processes, and management support built in, schedule a conversation to explore how Outsourced Scale matches founders with the right fit.
FAQs about Giving Feedback to EAs
Start by describing the expected outcome before addressing the mistake. Then point to the specific section that needs adjustment and show an example of the correct format. This sequence helps the assistant understand both the standard and the correction so they can apply the same pattern to future tasks.
Use a simple structure: explain the expected result, identify the exact issue, and provide a correct example or reference version. Clear examples remove guesswork and help assistants match the format or workflow the next time they complete the task.
Written feedback works well for recurring tasks, simple corrections, and process instructions that the assistant can reference later. Short screen recordings or voice messages work better when explaining visual tasks, multi-step workflows, or style and tone adjustments that are difficult to describe in text.
Short feedback on completed work should happen daily so small corrections can be made immediately. A weekly meeting can review patterns, answer questions, and align on priorities for the next week without waiting for problems to accumulate.
Focus feedback on the work rather than the person and explain why the task matters. When assistants understand how their output is used—for example in a client report or leadership meeting, they can make better decisions and adjust their approach more effectively.
