Two people deliver the same project, on the same day, with the same result.
One says, "I've been really busy, I think it went okay, I just need to finish a couple of things."
The other says, "We launched Tuesday. Onboarding time is down 18%. Two small fixes ship Friday."
Six months later, only one of them is being talked about for a bigger role.
Language shapes how people perceive your competence, your leadership and your potential. Most professionals underestimate this. They assume the work will carry them, and the words are decoration.
Language is not soft. It's strategic.
Your words are how people judge your thinking before they ever see your work. In interviews, in meetings, in a two-line email to someone in another department, people are quietly asking: Are you confident? Are you precise? Do you understand the problem? Your language answers before your résumé does.
If you're early in your career, this is one of the cheapest upgrades available to you. It costs nothing. It doesn't need permission. And it compounds, because every message you send either builds your reputation or chips at it.
The short version
- Specific beats vague. "Draft to you by 3pm Thursday" builds trust. "I'll try to get it done" builds anxiety.
- Talk in outcomes, not activity. "Busy" sounds overwhelmed. "Reduced X by Y" sounds effective.
- Cut the shrink words. "Just", "maybe", "kind of" and reflexive "I think" make you sound less sure than you are.
- Own, don't deflect. "Here's what I can own" beats "That's not my job" every time.
- Language either widens the table or narrows it. Names, pronouns, plain words over insider shorthand.
The word swaps that change how you're seen
Most of the leverage lives in a small number of everyday phrases. Here are the ones I'd fix first.
What each swap is doing:
1. Commitments: specific builds trust. Overpromising erodes credibility. Vague commitments create anxiety for the person waiting on you. A precise date and deliverable, even a later one, lets people plan around you. If the date slips, say so early with a new date. That's still trust-building.
2. Updates: outcomes, not activity. Everyone is busy. Busy isn't information. Leaders speak in outcomes: what changed, by how much, for whom. If you don't have a number, name the result. "The schedule is posted two days earlier" beats "worked on scheduling."
3. Confidence: cut the shrink words. "Just", "maybe", "kind of" and an automatic "I think" shrink your message before anyone has a chance to weigh it. Keep "I think" when you're genuinely offering an opinion among options. Drop it when you're stating something you know.
4. Ownership: language that accelerates careers. "That's not my responsibility" might be technically true. It still ends the conversation and marks you as someone to route around. "Here's what I can own, and here's where I'll need support" solves the same boundary problem and makes you the person things get handed to.
5. Asking: framing is everything. In any negotiation, from a raise to a deadline extension, the frame decides how your request is heard. "I need" centres your problem. "Based on the results and the market, I'd like to align..." centres a fair outcome. Same goal. Different power.
Key idea: Specificity is a form of respect. It tells the other person exactly what they can count on.
Words in disagreement
Most workplace conflict isn't about intent. It's about interpretation. Someone reads a message as an accusation, gets defensive, and now two reasonable people are arguing about tone instead of solving the problem.
The wrong phrasing escalates. The right phrasing de-escalates. Three tools:
Use "I" statements. "I felt blindsided by the timeline change" invites a conversation. "You blindsided me" invites a defence. You're describing your experience, which nobody can argue with, instead of judging their behaviour, which everyone will.
Assume the misunderstanding might be yours. "I may have misunderstood, can we walk through it again?" costs you nothing and gives the other person room to clarify without losing face. Half the time, you did misunderstand.
Name the shared goal. "We both want this shipped by the 15th. Here's where I see the risk." It moves you from opposite sides of the table to the same side of the problem.
Inclusive and clear: language that widens the table
Inclusive language isn't a political add-on. It's precision. It makes sure your message reaches every person it's meant for, and it signals that you pay attention. Careless, assumptive language signals the opposite. In modern workplaces, this is not optional.
The practical version:
- Use people's names, and the pronouns they use. If you're unsure, use their name, or ask privately and simply.
- Default to neutral terms for groups. "Hey everyone" or "Hi team" instead of "Hey guys." "Chair", "staff", "salesperson" instead of gendered titles.
- Avoid stereotypes, even as jokes. A joke about age, accent or background rarely lands the way you meant with the person it's about.
- Choose plain words over insider shorthand. Acronyms, slang and in-jokes exclude new hires, other departments and anyone working in a second language. Spell it out the first time.
- Don't assume communication norms. As work goes global, directness, humour and formality vary a lot between cultures and people. When unsure, ask respectfully. Curiosity outperforms assumption every time.
Written messages: your reputation when you're not in the room
Your written communication becomes your reputation in every room you're not in. It gets forwarded, screenshotted and reread later. Long emails are often unclear emails.
Every work email or message should have:
- A clear subject line that says what it's about and whether action is needed. "Decision needed: Q3 schedule by Fri" beats "Quick question."
- One purpose. Two unrelated topics means two messages.
- A direct ask. What do you need, from whom.
- A defined timeline. By when, and what happens if you don't hear back.
And when you speak, the spoken equivalent: talk slightly slower than feels natural, pause instead of filling silence, and finish your sentences decisively. Silence feels long to you. It sounds confident to others.
What it looks like in practice
A hypothetical example.
Marcus is a junior account coordinator. A client emails, frustrated, because a deliverable came in late. His first draft of the reply:
"Hey, so sorry, things have been really crazy here and the design team didn't get us the files in time, which isn't really something I control. I'll try to get it to you ASAP. Thanks!"
Every line costs him something. "Crazy" sounds overwhelmed. Blaming the design team makes the whole company look disorganised. "Try" and "ASAP" are commitments nobody can plan around.
His rewrite:
"Subject: Revised files arriving Thursday 10am Hi Dana, you're right, the files were late and that's on us. The final versions will be in your inbox by 10am Thursday. I've also added a check-in to our schedule two days before each deadline so you'll hear early if anything shifts. Thanks for flagging it."
Same facts. One version makes the client want to escalate. The other makes them trust Marcus a little more than before the mistake.
Common traps
- Hedging to seem humble. Shrink words don't read as modest. They read as unsure. Fix: say what you know plainly, and save qualifiers for real uncertainty.
- Narrating effort. "I spent hours on this" asks for sympathy, not trust. Fix: report the result and what it changed.
- Fixing tone over text when it's tense. A heated chat thread almost never cools itself down. Fix: move it to a call, then recap in writing.
- Copying your boss's jargon. Insider language feels like belonging but loses half your readers. Fix: plain words first, the acronym in brackets if needed.
- Over-correcting into robotic. Precise doesn't mean cold. Fix: keep a warm opener or thank-you. Just don't let it bury the point.
Do this this week
Run a language audit on your own sent messages.
- Open your last 15 sent emails or work chats.
- Highlight every "just", "maybe", "kind of", "try", "ASAP" and every update that describes activity instead of an outcome.
- Pick the three phrases you use most and write your replacement for each, using the swap table.
- For the next five days, check every outgoing message for those three phrases before you hit send.
Your tool
| Instead of | Say | Why it works |
|---|---|---|
| I'll try to get that done. | I'll have [X] to you by [time, day]. | A date people can plan around |
| I've been really busy. | This week I [result + number]. | Outcomes sound effective |
| I just wanted to check in. | Following up on [specific item]. | Confidence, no apology |
| Sorry to bother you, but... | Quick question on [topic]: | Respects their time and yours |
| That's not my job. | Here's what I can own, and where I'll need help. | Ownership without overcommitting |
| You didn't explain this. | I may have misunderstood. Can we walk through it? | Invites clarity, not defence |
| You blindsided me. | I felt blindsided by [the change]. | Describes impact, not intent |
| I need a raise. | Based on [results] and [market], I'd like to align pay with impact. | Frames a fair outcome |
| Hey guys | Hi team / Hi everyone | Includes the whole room |
| ASAP | By [time, day] | "As soon as possible" means different things to everyone |
| I think we should... (when you know) | I recommend... | States your position clearly |
| Does that make sense? | What questions do you have? | Puts the burden on clarity, not on them |
WRITTEN MESSAGE CHECKLIST (run before you send anything that matters)
[ ] Subject line says the topic AND whether action is needed
[ ] One purpose per message
[ ] The ask is in the first two lines
[ ] A specific deadline, not "ASAP" or "when you can"
[ ] Updates report outcomes, with a number where possible
[ ] No shrink words unless I mean them (just / maybe / kind of / try)
[ ] Acronyms spelled out the first time
[ ] Names and greetings include everyone
[ ] If this is tense or emotional: talk first, then send the recap
Talk about it
- Which phrase from the swap table do you catch yourself using most, and what do you think it's protecting you from?
- Think of a time a message was misread. Was it the words, the tone, or the channel?
- What insider language or acronyms does your team use that would confuse a new hire on day one?
— Evan
