What Your Manager Actually Hears When You Say These Things
You said "I'll try to make that work." They heard something completely different - and so did everyone else in the room.
For about three years, I believed “I’ll flag it as a risk” was the most professional sentence in my vocabulary. It sounded measured. It sounded senior. It sounded like someone who had read the relevant frameworks and was handling the situation responsibly.
It was none of those things. It was an alibi. What I was actually doing, every single time, was creating a written record that I had seen the iceberg - so that when the ship went down, nobody could pin it on me. I wasn’t managing the risk. I was managing my own deniability, in advance, in a tone of voice calm enough that I hoped nobody would notice.
My manager noticed. Managers always notice. That’s the part nobody tells you about office language: you think the polite phrase is neutral, a smooth professional surface that gives nothing away. It isn’t. Every one of these phrases is lossy compression of something you didn’t want to say out loud - and the person on the other end decompresses it instantly, because they use the exact same phrases and know exactly what they’re hiding when they do.
You are fluent at decoding this language in other people. You hear “let’s take this offline” and you know precisely what just happened. The trick - the thing that took me years and one genuinely humiliating skip-level - is realising that you’re speaking it just as loudly, and everyone can hear you.
Let’s get into it.
“I’ll try to make that work.”
Received as: probably not, but I’d rather not have the conflict in this meeting.
This is the politest no in the language, and everyone knows it’s a no, which is the problem. A real yes sounds like “yes.” A real no sounds like “no, here’s why.” “I’ll try” is the sound of someone optimising for getting out of the room without a confrontation, and your manager files it as a soft decline they’ll have to chase you on later. If you mean yes, say yes. If you mean no, the no is more respected now than the missed deadline is forgiven later.
“Happy to help with that.”
Received as: I have no working model of my own capacity.
You think this signals that you’re a team player. What it often signals is that you say yes to everything, which means your yes carries no information, which means nobody can plan around you. The person who occasionally says “I can take that, but it pushes the other thing to Thursday” sounds less agreeable and gets trusted with far more - because their commitments actually mean something. Reflexive helpfulness reads as a capacity gauge with the needle painted on.
“Can we loop back on this?”
Received as: I disagree, and I’m not willing to say so in front of these people.
There’s a version of this that’s genuine scheduling. Everyone can tell the difference. The tell is the timing: it arrives at the exact moment a decision is about to land that you don’t like. What your manager hears is that you have an objection you’re declining to put on the table - which is worse than the objection itself, because now they have to go and find it. If you disagree, the cheapest moment to say so is the one you’re trying to escape.
“Just checking in on...”
Received as: I don’t trust that you’ve done this.
The friendliest surveillance phrase in the office. You mean it as a gentle nudge; it lands as a notification that you are now being watched. Said upward, it reads as nagging your manager. Said downward, it quietly informs your report that their work is being audited. Sometimes that’s fine - sometimes you genuinely do need the status. But know that “just checking in” never reads as just checking in. There is no just.
“Let me take that offline.”
Received as: you have said something I cannot deal with in public.
This is the one phrase on the list that’s almost always a tell about the speaker’s position rather than their feelings. People take things offline when they can’t win the point in the open - either because they’re about to correct you and don’t want an audience, or because they don’t actually have an answer and need to go and find one. Either way, the room now knows there’s a real conversation happening somewhere they’re not invited to. “Offline” is where the actual meeting moved.
“I’ll flag it as a risk.”
Received as: I am putting this in writing so it stops being my fault.
My old favourite. There’s a legitimate version - surfacing a real risk to the people who can act on it is the job. But there’s a far more common version, and your manager can tell them apart, where the flag isn’t an attempt to fix anything. It’s an attempt to be on the record as having known. A risk you raise once, calmly, and then never push again was never a risk you cared about solving. It was an alibi with a timestamp.
“We should align on this.”
Received as: someone is about to be told they’re wrong, and I’m establishing now that it isn’t me.
“Align” is the most diplomatic word in the corporate dictionary and one of the least innocent. Genuine alignment is two people reconciling two views. The meeting-room version is one person announcing, in advance and in neutral language, that a correction is coming, and positioning themselves on the right side of it before it arrives. When someone says “we should align,” the useful question is: who’s about to lose, and how do they already know.
The instinct, having read all that, is to resolve never to use any of these phrases again. Don’t bother. You’ll use every one of them by Wednesday - because the alternative, saying the true thing plainly, in the room, in front of the people it implicates, is genuinely costly. These phrases exist precisely because that cost is real. The language isn’t the problem. It’s a reasonable protocol for surviving a place where blunt honesty gets billed to you.
The only thing worth changing is the asymmetry. Right now you decode everyone else perfectly and transmit yourself in the clear. So at least know what you’re broadcasting. Know that “I’ll try” is heard as no, that “happy to help” is heard as no capacity model, that the risk you flagged and dropped is heard as exactly what it was.
And the next time you reach for one of these, you get a genuinely useful half-second of choice: say the safe phrase and accept that they’ve heard the real one anyway, or say the real one and skip the translation entirely. Most days I still pick the phrase. But now, at least, I know I’m choosing it.
I just wish someone had told me before the skip-level.

