You write a Slack message asking a colleague to review something. Before you hit send, you soften it: “Sorry to bother you, I was just wondering if you could possibly take a look when you get a chance?” It feels courteous. It feels safe. Nobody could read that and think you were being demanding.

Here’s the catch. The polite phrases that make you sound less senior are exactly the ones that feel most considerate. To a US, UK, or Canadian ear, that message doesn’t read as extra-polite. It reads as someone who isn’t sure they’re allowed to ask. Every softener you added quietly lowered your perceived rank, and you can’t see it happening because each word felt correct when you typed it.

This is over-softening, and it’s the politeness habit that backfires on international teams. Below are eight of the most common over-softeners, what a native actually hears when you use them, and the senior-sounding version they’d expect instead. The senior version is almost never ruder. It’s usually shorter, warmer, and easier to say yes to.

Why over-softening reads as junior, not polite

Most of us were taught politeness as a safety move: add a hedge and you can’t give offense. Layer “sorry,” “just,” and “maybe” onto a request and you’ve insulated yourself. On the team where you learned English, that math holds.

On an international team, the math flips. A native reader doesn’t add up your softeners as courtesy points. They read tone. A sentence with three hedges in it sounds like it was written by someone checking whether they have permission to speak. And the person on the call who needs permission to speak is rarely the senior one in the room.

The signal isn’t rudeness. It’s rank. That’s the part that catches fluent speakers off guard, because nothing in the sentence is wrong. The grammar is clean, the intent is kind, and the colleague understands you perfectly. The phrase still costs you something. Sounding senior on a US or UK team is largely about register, and these phrases sit on the wrong end of it. (For the wider picture on how requests, updates, and pushback land at this level, the PM communication guide covers the whole range.)

One thing to settle upfront: the direct versions below are not blunt. “Do you have a sec?” and “Could you review this by Friday?” are already polite. You’re not trading warmth for plainness. You’re trading a flinch for composure.

The eight phrases, and what to say instead

“Just wanted to” → make the ask

“I just wanted to check on the timeline.” → “Can you give me a quick timeline update?”

“Just wanted to” is a runway you don’t need. It signals you’re about to ask for something but apologizing for it first. Drop it and the request stands on its own. “Can you give me a quick timeline update?” reads as confident, not pushy, because you’re treating the ask as normal — which it is.

“Sorry to bother you” → skip the apology

“Sorry to bother you, do you have a sec?” → “Do you have a sec?”

Opening with “sorry to bother you” frames you as an interruption before you’ve said a word. You’re telling the reader your message is a nuisance. The plain question is already polite, and it assumes you belong in the conversation. Asking a colleague a quick question is part of the job, not an imposition on it.

“I was wondering if maybe” → ask the question

“I was wondering if maybe we could move the call.” → “Could we move the call to Thursday?”

This one stacks two hedges on a single request: “I was wondering if maybe” is “wondering if” plus “maybe,” doubled up. To a native ear that compounding sounds genuinely unsure, as if you half-expect a no. “Could we move the call to Thursday?” is a clear question with a specific ask, and a clear question is far easier to answer.

“Sorry for the late reply” → thank them instead

“So sorry for the late reply!” → “Thanks for your patience — here’s the update.”

Apologizing for timing puts you on the back foot before you’ve delivered anything. “Sorry for the late reply” draws attention to the delay and asks the reader to forgive you. Flip it: “Thanks for your patience” keeps you composed, credits the reader, and moves straight to the answer they were waiting for. Same courtesy, opposite posture.

“I hope that makes sense” → offer to go deeper

“Let me know if that makes sense.” → “Happy to walk through any of this.”

“I hope that makes sense” can read as doubting your own explanation. You just explained the thing; now you’re flagging that it might not have landed. “Happy to walk through any of this” sends the opposite signal. You’re in command of the material and offering more, not bracing for confusion. The first version checks if you failed. The second assumes you didn’t.

“If it’s not too much trouble” → name the timing

“If it’s not too much trouble, could you send the file?” → “Could you send the file when you get a chance?”

“If it’s not too much trouble” turns a routine request into an imposition. Sending a file isn’t trouble, and framing it that way makes the favor sound bigger than it is. “Could you send the file when you get a chance?” is courteous without the flinch. It respects the colleague’s time by naming when, not by apologizing for asking.

“Could you possibly” → just “could you”

“Could you possibly review this by Friday?” → “Could you review this by Friday?”

“Could you” is already a polite, indirect request. Adding “possibly” hands the reader an easy out and softens a real deadline into a maybe. If Friday matters, “possibly” quietly tells them it doesn’t. The plain version is still polite and far clearer about what you actually need.

“Apologies for any inconvenience” → thank them for bearing with you

“Apologies for any inconvenience this may cause.” → “Thanks for bearing with us on this.”

“Apologies for any inconvenience” is corporate boilerplate that braces for a complaint. It sounds canned because it is, and it assumes the reader is annoyed before they’ve had a chance to be. “Thanks for bearing with us on this” reads human and confident. It credits the reader’s patience instead of pre-apologizing for their irritation.

How this shows up in a normal week

These phrases surface in the most ordinary moments, which is why they’re easy to miss. You’re pinging a busier colleague on Slack, replying to an email two days late, asking for a file, closing an explanation in a standup, sending out a scheduling change. Each time, the softener feels obligatory. It’s the polite thing to do.

The trouble is they travel in packs. One on its own is harmless. But a single message can carry three or four (“Sorry to bother you! I was just wondering if maybe you could possibly take a look at this, if it’s not too much trouble?”), and now the reader is wading through hedges to find the actual request. By the time they reach it, the tone has done its work. You sound junior, even though you’re not.

The fix is rarely to be more direct in a way that feels rude. It’s to trust that the request itself is reasonable. When you assume your ask is normal, the softeners fall away on their own, and what’s left reads as senior.

Spotting it in your own writing

Before you send, do a quick pass for the openers: “just,” “sorry,” “maybe,” “possibly,” “if it’s not too much trouble.” Each one is a small flinch. Cut the flinch and check whether the sentence still says what you mean. Nearly always it does, and it sounds more like you.

You don’t have to strip every softener. There are moments where a genuine apology or a real “I was wondering” fits the situation. The goal isn’t to sound abrupt. It’s to stop sounding unsure when you’re not. Once you can hear the difference between a softener that adds warmth and one that lowers your rank, the choice gets easy.

This is exactly the kind of register calibration FluentSphere is built to train: real workplace scenarios where you practice the senior-sounding version until it’s the one that comes out first. Try FluentSphere — link in bio.