Speaking Up Without Sounding Confrontational: A VA Guide to Truth to Power

TL;DR: This guide for virtual assistants explores how to effectively speak truth to power without sounding confrontational. It emphasizes understanding power dynamics and cultural contexts, and provides a step-by-step approach to naming issues, separating facts from interpretations, and communicating risks clearly. The goal is to advocate for integrity and clarity while maintaining professional relationships, ensuring that VAs can raise concerns that could impact workflows or team dynamics without triggering power struggles.

---

Speaking truth to power as a virtual assistant

Most virtual assistants do not have “authority” on paper. That means many VAs do not have formal decision-making power, even if they have real influence because of their proximity to the work. In remote work, this gets more complicated because the power structure is real. VAs often sit near the bottom of it, which means they may not feel they have “permission” to question decisions even when they can see the risks coming.

But when you work with a client long enough, you start to see the consequences of the decisions they make. Sometimes it is something that breaks the workflow. Sometimes it is the way they ask their team to operate, like telling half-truths to protect a narrative. But you feel it in your gut: you know that something is off. This is when you need to start to speak truth to power.

But what does speaking truth to power actually mean? It means delivering honest, sometimes uncomfortable information to someone with more authority, influence, or decision-making control than you, especially when that truth challenges their plans, assumptions, or beliefs. It is not about being right. It is about naming risks, raising concerns, or advocating for integrity when staying silent could cause harm, even if speaking up puts you at risk professionally or relationally. The phrase comes from civil rights and social justice movements, where activists spoke against systems of oppression despite personal danger. In a workplace context, it simply means you tell the person with power what they need to hear, not just what they want to hear.

This article is about doing it anyway, with emotional maturity. It is an ethical and moral imperative when harm is on the line. It is also a communication skill you can build.

The real issue: power dynamics and cultural context

If you want to speak up without sounding confrontational, you need to account for two things that change how the same sentence lands: the power gap in the relationship, and the cultural norms around “respect.”

Power dynamics: As a VA, you often have less formal authority, less access to full context, and more dependency on the relationship for stability, income, or references, while also being closer to the operational reality, which means you notice risks earlier. That imbalance can make even calm feedback land as “confrontational,” especially when the person with more power is stressed or moving fast. Sometimes you did not “say it wrong.” Sometimes you named something they did not want to slow down and hear, and the power gap makes it easy for the real concern to get reframed as your tone, attitude, or disrespect.

Cultural factors: Norms around hierarchy, directness, saving face, and whether disagreement belongs in public or in private change what “respect” sounds like, and remote work adds friction because tone is harder to read in writing. Emotional maturity is not pretending those differences do not exist. Emotional maturity is choosing the channel and wording that gives your message the best chance of being understood, so you can flag risk without triggering a power struggle or creating an avoidable relationship rupture.

The act of speaking up, and how you do it, reflects the relationship you have with your client. We have to acknowledge that when someone has more authority than you, they not only have more say, but they can afford to move fast, make mistakes, and clean up later. However, as a VA, you usually cannot. So even when you are saying something reasonable in their best interest, the power gap can make it land like you are challenging them instead of supporting them.

Anyone who tells you to “just be honest” is giving incomplete advice. Yes, be honest, but do it with a level of emotional maturity. Emotional maturity is knowing how to tell the truth in a way that protects the relationship and protects your own position. So this is not for you to be right or show how smart you are. This is about you protecting the work.

Start here when your gut says something is wrong

When your gut says something is wrong, this is where you begin.

Sometimes it is one questionable decision. Sometimes it is a whole slew of them. Either way, this is the moment where most VAs go off track in one of two directions. They jump straight into judgment, and come in hot. Or they do the opposite. They talk themselves out of what they can clearly see because they do not have the title, and they confuse authority with accuracy.

Your gut is not a full argument, but it is a reliable alert system. It is pattern recognition doing its job before you have all the words. The mature move is not to ignore it. The mature move is not to weaponize it. The mature move is to slow down, gather clarity, and then say what you are seeing in a way that keeps you credible.

So do not jump to a speech. Move through this sequence instead. The goal is simple: get the truth in the room without turning it into a power struggle.

This is meant to be a quick mental checklist, not a heavy process. Most situations are a 1–2 and take about 30 seconds to 2 minutes. A 3 usually takes about 3 to 10 minutes to pull a few facts and write one clear risk sentence. A 4–5 is when you slow down on purpose, and it can take about 10 to 20 minutes, especially if you need to confirm details or check a policy.

Step 1: Name what kind of “wrong” this is

This step matters because it keeps you from going off the rails in either direction. It keeps you from jumping straight into judgment, and it keeps you from minimizing what you can clearly see. When you can name what kind of “wrong” this is, you get a clear picture of the stakes, which makes it easier to stay steady and speak up with more confidence.

Rate the situation on a 1–5 scale, based on consequences.

• 1–2 means: not really a problem. It is still “off,” but it is not a true risk.

• 3 means: real risk. It can affect delivery, trust, or outcomes if you let it ride.

• 4–5 means: big, serious problem. Slow down and protect the work.

Then name what category of “wrong” you are dealing with.

Category	What it means	Quick questions to rate it	Examples (1 / 3 / 5)
Preference issue	Taste, style, or personal way of doing things. Nothing breaks, but it can create friction or rework.	What actually breaks if we do it their way? How much rework will this create?	1: they prefer Google Docs instead of Notion. 3: they keep changing their mind after delivery. 5: “preference” is used to punish or demean.
Execution risk	The work is likely to fail. Quality drops, deadlines slip, or a workflow breaks.	What is most likely to fail here? If it fails, what is the cost in time, money, or reputation?	1: this takes 10 minutes longer than planned. 3: QA will be skipped and errors are likely. 5: something critical breaks, like payments or delivery.
People harm risk	The human cost. Burnout, coercion, humiliation, unsafe expectations, or a pattern that damages the team.	Who pays for this decision, and how? Is this a one-time stressor or a pattern that will keep harming people?	1: someone will be mildly annoyed. 3: burnout, mistakes, or conflict becomes likely. 5: harassment, discrimination, threats, or serious harm.
Ethics risk	Honesty and integrity. You are being asked to mislead, manipulate, exploit, or represent something untrue.	Are we being asked to imply something that is not true? Would I feel comfortable if this were shown publicly?	1: it feels off, but you cannot name it yet. 3: you are asked to imply something untrue. 5: fraud, exploitation, or intentional harm.
Compliance risk	Rules and exposure. Privacy, contracts, NDAs, data handling, platform policies, or legal liability.	What rule, contract, or policy does this touch? If this goes wrong, what is the consequence?	1: low-sensitivity info, minimal exposure. 3: personal data or restricted files. 5: breach, legal exposure, serious liability.

Once you have a rating, use it to thoughtfully craft your response. A rating of 1 or 2 is usually a quick clarification that lets you move on without turning it into a bigger conversation. However, a rating of 3 is potentially a real risk, which means you offer options so your client can decide on a safer path. A 4–5 is high stakes, which means you need to be more deliberate and careful with your words. Put the concern in writing so you, the work, and the people involved are protected.

Carry that rating into Step 2, and use it to determine what information you need to gather so you can act appropriately, with 1–2 staying light, 3 getting specific, and 4–5 becoming non-negotiable.

Step 2: Separate facts from interpretations

This is how you keep yourself credible. You separate what you can prove from what you suspect. Your gut can start the process, but facts have to finish it.

The output of this step is simple: a few clean facts you can quote, and a clear guess you will not present as fact.

If you rated it…	What to do in Step 2	Example
1–2 (low stakes)	Keep this fast. Write down one or two facts and one question you can ask to confirm context.	“They asked for the deck in a new format.” Then: “Do you want this format going forward, or just for this one deck?”
3 (real risk)	Get specific so you can flag the risk without sounding dramatic. Write three to five facts, then one sentence that explains the risk without guessing motives.	“The launch email says the feature is live. Engineering said it ships next week. The draft is scheduled to send tomorrow.” Then: “If this goes out as written, customers may feel misled and support will take the hit.”
4–5 (high stakes)	Slow down on purpose. Write the facts you can prove, name the policy or agreement it touches, and write what you will and will not do.	“They asked me to upload a spreadsheet with customer emails to a public Drive folder. The contract says customer data must be restricted to internal access only.” Then: “I will not upload this publicly. I can share it via a restricted folder or remove the emails first.”

Your job is to lead with the facts. Now you have the raw materials. Step 3 is where you turn those facts into a message that can actually land.

Step 3: Identify the risk in plain language

This is where you say what goes wrong if you proceed with your client’s request as-is. Keep it plain and clear. Write a version of the language for yourself first as practice, then translate it into something your client would understand.

Use three sentences:

• Risk: “If we follow your client’s request as-is, we may see ,[risk]…”

• Impact: “That could mean ,[impact]…”

• Decision: “Do you want ,[option A] or ,[option B]?”

If you rated it…	What to do in Step 3	Example
1–2 (low stakes)	Keep it light. Name the small risk and ask one quick decision question.	“If we switch formats last-minute, it may slow delivery. Do you want the new format for this one deck, or going forward?”
3 (real risk)	Be specific. Name the risk, name the impact, and give two clear options.	“If we send this email today, customers may think the feature is live. That can create complaints and support tickets. Do you want to update the copy to say ‘shipping next week,’ or hold the email until release?”
4–5 (high stakes)	Be direct and protective. Name the risk, state what you will not do, and offer a safer alternative.	“If we upload customer emails to a public folder, that is a privacy risk. I will not upload this publicly. I can share it in a restricted folder or remove the emails first. Which option do you want?”

Step 4: Choose the channel based on stakes

This is where you decide where to say it so your client understands you and you protect yourself.

If you can, do not wait until a problem happens to figure this out. It is best when your client is trained, or you have a clear agreement, on what each channel is for. For example: “Quick decisions go in Slack. High-stakes issues get a call plus a written recap.”

If you rated it…	Best channel	Examples of what that looks like
1–2 (low stakes)	Quick async message	A short Slack message, a quick email reply, or a comment on the task: one question, one decision, done.
3 (real risk)	Async or private chat	Async (Slack or email) when your client handles feedback well in writing, and you want a clear record. Private chat (call or voice note) when your client gets defensive in writing, and tone matters.
4–5 (high stakes)	Private conversation + written recap	A call or Zoom first. Then a written recap in Slack or email that names: what your client asked for, your concern, the risk, what you will not do, and the safe options.

If you flagged a concern and your client does not answer, do not guess. If you rated the situation a 1–2, make the smallest, lowest-risk choice that keeps the work moving, like following the existing process, using the last confirmed version, or doing the parts that are already clear while you pause only the part you are unsure about. If you rated the situation a 3, stop at the decision point and ask again. If you rated the situation a 4–5, do not do your client’s request until your client confirms.

Scripts you can use (without sounding confrontational with the truth)

These scripts are here because most VAs were never given a playbook for this. They are examples that give you guidance and context, so you are not guessing what to say when you need to raise a concern. Use them to get unstuck, borrow the structure, and then rewrite them in your own voice so they still sound like you.

Situation	What to say
You might be missing context	“I might be missing context. Can I confirm the goal behind this before I proceed?”
You want to flag a risk early	“I want to flag a risk before we commit. If we do X, we may see Y. Do you want to proceed, or do you want an alternative?”
The decision could harm people	“I can do this, and I also want to name a concern. This could impact the team in a way that is hard to undo. Can we talk through options?”
The request involves deception or misrepresentation	“I’m not comfortable representing something that isn’t accurate. I can help us say this honestly while still meeting the goal.”
You need to set a boundary without drama	“I can’t support that approach. I can offer two alternatives that get us close to the outcome without crossing a line.”
You need to document the decision	“To make sure we stay aligned, I’m going to summarize the decision and the reason in writing.”

When to step back

Speaking truth to power is not the same as speaking every truth. Step back when it is a preference issue and the cost of raising it is higher than the benefit, when you do not have enough information yet and you can safely gather more, or when the timing is wrong and a calmer moment will make the conversation more effective.

When it is a safety issue

Sometimes the most mature move is not to keep trying to persuade. Treat it as a safety issue when you are punished for respectful questions, pressured to act against your values, asked to participate in deception, exploitation, or harm, or when your concerns are repeatedly dismissed without consideration. In those cases, your next steps might includ

e documentation, getting advice from a trusted mentor, or planning an exit.

Closing: Integrity is a skill

If you are a VA, you are not “just support.” You are often the person closest to the truth of what is happening. Speaking up with maturity is part of your professionalism. Your goal is not confrontation. Your goal is clarity, integrity, and better outcomes for everyone involved.