You write an update email to your manager. It is factual. It covers everything you intended to say. You send it without thinking much about it.
Your manager reads it and comes away with a completely different impression than you intended.
This is not rare. It happens because managers—especially experienced ones—read email differently than the people writing them. They are not just processing information. They are looking for signals. And some of the most common phrases people use to sound responsible, thorough, or polite end up sending signals they never meant to send.
What managers are actually reading for
When your manager reads your email, they are usually answering a few background questions:
- Do they have the situation under control?
- Do they know what they need to know to move forward?
- Is there something I need to worry about that they are not saying directly?
- Do I need to get involved, or can I leave this alone?
Most of the time, your manager wants the answer to all four to be reassuring. They want to read your email and feel like things are in hand.
The problem is that certain phrases—used with completely benign intent—trigger the opposite response.
"I'll try my best"
What you mean
You are committed. You are going to work hard. You are not making a promise you cannot keep.
What many managers read
"I'm not confident I can deliver this."
"I'll try my best" is a hedge. It leaves open the possibility of failure. A manager who is tracking deliverables reads it and mentally flags: this one might not come through.
If you are confident you can do it, say so.
Instead: "I'll have it ready by Thursday." or "I can do this—I'll send it over by end of week."
If there is genuine uncertainty, name the specific obstacle rather than a general hedge.
Instead: "I can get this done by Thursday if the data from the other team comes through by Tuesday. I'll flag you if that changes."
"Just wanted to flag this"
What you mean
You are being proactive. You saw something and you want to make sure your manager knows about it.
What some managers read
"I noticed this problem but I'm not sure what to do about it, so I'm passing it to you."
"Just wanted to flag" can read as a way of notifying without owning. You have surfaced the issue, but you have not indicated what you think should happen next.
Whether that is a problem depends on your manager. Some prefer to be flagged early. Others want the flag to come with a proposed next step.
More effective version: "I noticed X. I think we should do Y—does that make sense, or do you want to handle it differently?"
Now you are flagging and proposing. That reads as confident, not as off-loading.
"As per my last email"
What you mean
You already addressed this. You are pointing the reader back to the original information.
What many managers read
Frustration. Passive-aggressiveness. Possibly: this person has a conflict with someone on the team.
"As per my last email" has become one of the most recognized signals of workplace tension. Even when used neutrally, it carries enough cultural baggage that it rarely lands as neutral.
More effective version: "To recap what I sent on Tuesday: [key information]." or just resend the relevant part without commentary.
"I think this might work, but I'm not sure"
What you mean
You are being honest about uncertainty. You do not want to oversell something.
What some managers read
"This person does not have enough confidence in their own recommendation for me to act on it."
There is a difference between intellectual humility (which managers generally appreciate) and uncertainty that makes the recommendation unusable.
If you are genuinely uncertain, say what you are uncertain about specifically.
More effective version: "I think this approach works. The one thing I haven't fully tested is X—I'll know more after the call on Wednesday."
Now the uncertainty is bounded. Your manager knows you have thought it through and you know what you are still checking.
"Sorry for the late reply"
What you mean
You are being polite. You acknowledge the delay.
What some managers read (if it happens repeatedly)
"This person struggles to stay on top of their inbox."
One "sorry for the late reply" is unremarkable. A pattern of them—especially on important threads—starts to read as a signal about responsiveness.
More importantly: excessive apology shifts attention to the delay rather than the content.
More effective version: Skip the apology if the delay was short. If the delay was significant, acknowledge it once and move on: "Sorry for the slow response—here's where things stand."
Then get into the substance. The apology is a speed bump, not the main event.
"I've been really busy"
What you mean
You want to explain why something took longer or why you have not been as available.
What many managers read
"I'm not managing my workload well" or "I'm making excuses."
Busy is the default state of most professional environments. Citing it as an explanation can read as an inability to prioritize—especially if the task that was delayed is one your manager considers high priority.
If you are genuinely overloaded, that is worth raising directly.
More effective version: "I'm at capacity right now—can we talk about what to deprioritize so I can give this the attention it needs?" That reads as self-aware and solution-oriented, not as an excuse.
"Does that make sense?"
What you mean
You want to check that you explained clearly. You are being thoughtful about communication.
What some managers read
"I'm not confident in this explanation" or (occasionally) "I'm checking whether you're following me."
In a peer context, "does that make sense?" is usually fine. In an upward context, it can read as either under-confidence or condescension, depending on how it is phrased.
More effective version: "Let me know if you want me to walk through any of this in more detail." That invites questions without implying the explanation was unclear or that the reader might not have followed.
"I just wanted to make sure we're aligned"
What you mean
You are being collaborative. You want to confirm you are on the same page.
What some managers read (sometimes)
"I'm not sure you agreed to this, so I'm trying to get you to re-confirm it" or "I'm covering myself in case this goes wrong."
This phrase is not always read this way—context matters a lot. But in certain tones or after a tense exchange, it can read as political rather than collaborative.
More effective version: Be specific about what you are aligning on. "I want to confirm we're moving forward with X—is that still the plan?" That is direct and does not carry the same hedging energy.
The underlying pattern
Most of these phrases share a common structure: they soften a statement in a way that accidentally introduces doubt, passes responsibility, or signals anxiety.
The intent is usually the opposite—to sound careful, collaborative, or honest. But the effect undermines the impression you want to make.
The fix is almost always the same: be more specific. Replace the hedge with a bounded statement. Replace the vague flag with a proposed action. Replace the apology with the content the reader actually needs.
Managers are not trying to find fault in your emails. But they are pattern-matching quickly, often across dozens of messages a day. The phrases that trigger concern do so because they have triggered concern enough times before that the association is now automatic.
Knowing which signals you are sending—even unintentionally—is the first step to sending fewer of them.
When the tool is useful
If you are writing a message to someone senior and you are not sure how it will land, Formalizer can help you check the tone before it goes out. Not to make it more formal, but to make sure the phrasing is projecting the confidence and clarity you actually have.
What you mean to say and what lands are not always the same thing. The gap is usually smaller than you think—but worth closing.