How to Congratulate a Coworker on a Promotion or New Role
What to write when a coworker gets promoted or takes a new job, including the awkward cases: you wanted the role, they now manage you, or they are leaving.
Read article →Topic
45 articles tagged Team Communication. For the wider topic, see Workplace Writing.
What to write when a coworker gets promoted or takes a new job, including the awkward cases: you wanted the role, they now manage you, or they are leaving.
Read article →Review comments are short, public, and read without tone. How to flag real problems, label what blocks a merge, and keep the author on your side.
Read article →A two-word check-in can feel like an accusation. How to answer it in one short message that gives the real state, the next date, and nothing you will regret.
Read article →Telling a colleague they are moving too fast can read as criticism. How to raise it so it lands as a shared concern, not a complaint, with an example.
Read article →In a noisy Slack or Teams channel, a buried ask gets missed. How to write a message that gets a fast answer: lead with the ask, tag the owner, set a deadline.
Read article →You need work from people who do not report to you. How to write a cross-team request that is easy to prioritize, with a before-and-after example.
Read article →When a reply takes twelve hours to arrive, a vague message costs a full day. How to write so a colleague in another timezone can act without a second round trip.
Read article →When a teammate's silence is blocking your work, a nudge is too weak and an escalation too early. How to write the message in between, with an example.
Read article →When every team member writes status differently, reading them is a tax. How to agree on one format that makes updates fast to write and faster to scan.
Read article →Announcing that an AI agent will take over part of a process is easy to get wrong. How to explain what changes, what stays human, and reassure people.
Read article →A three-page reply to a two-line question is a reading tax. How to ask for the short version without insulting anyone, with before-and-after examples.
Read article →Stop being expected to reply instantly. How to tell colleagues and clients when you actually respond, so a slower reply stops reading as a problem.
Read article →A team member has gone quiet and you are not sure why. How to write a check-in that opens a door without cornering them or sounding like surveillance.
Read article →Praising someone far above you without sounding like flattery. How to recognize a senior leader's work so it reads as genuine, specific, and worth their time.
Read article →A coworker got something wrong and others may have seen it. How to correct the error in writing without humiliating them or letting the mistake stand.
Read article →Pulling a deadline forward without wrecking morale. How to ask for earlier delivery, show you did the math, and make room for the team to tell you the real cost.
Read article →Someone joins a 60-message thread and needs the point in thirty seconds. How to write the summary: current state first, then decisions, then what you need.
Read article →Europe and the US change clocks a week apart, so recurring meetings shift for some people and not others. A short message template that prevents missed calls.
Read article →Secret Santa can be fun or a source of quiet stress. How to announce a gift exchange with a clear price cap, an easy opt out, and rules people can follow.
Read article →Leaving a role or a project means someone inherits your work. How to write a handoff that lets them pick it up without a dozen follow-up questions.
Read article →A team charter says why the team exists, what it owns, and how it works. A one-page structure, example wording, and how to keep it from becoming shelfware.
Read article →Most year-end team messages could have been sent by anyone to any team. How to write one that names real work, real people, and what comes next.
Read article →A holiday party invite has to cover date, cost, dress, food, and who is welcome without sounding like a policy memo. A short structure and a before and after.
Read article →Someone sent you work that is not good enough yet. How to hand it back so it gets fixed, without crushing the person or triggering a defensive rewrite war.
Read article →How managers announce a departure to the team and to clients: what to say, what not to say, handover details, and examples for resignations and other exits.
Read article →The work came back wrong and you need it done again. How to ask for a redo that fixes the work without bruising the person or slowing them down next time.
Read article →Asking for help is hard, and vague requests get ignored. How to write a clear, specific request that colleagues can say yes to quickly, with examples.
Read article →Reviewing a colleague's document? How to give useful, specific feedback that improves the draft, respects their voice, and does not take all afternoon.
Read article →When to reply all, when to reply only to the sender, how to move people to BCC, and how to stop a reply-all storm. Practical email etiquette with examples.
Read article →A working agreement sets how a team communicates, meets and makes decisions. What to include, how to write it with the team, and an example you can adapt.
Read article →Most shout-outs sound like a template. How to write specific, believable thanks to a coworker, with a before-and-after example and a reusable Context.
Read article →A new hire's first email sets the tone for their first month. What to include so they arrive oriented and calm instead of guessing, with a reusable template.
Read article →What to send a colleague who has lost someone: a short message that comforts without creating work, plus how to handle the work question.
Read article →The people who kept their jobs are watching how you handle the ones who did not. What to say to the remaining team, what to leave out, and what comes next.
Read article →Your last day is not the moment to improvise. How to state the practical facts, thank specific people, and leave your contact details without oversharing.
Read article →When AI disclosure matters at work, how to phrase it without undermining trust, and why the quality of your edit matters more than the tool.
Read article →The message people actually resent is the one that hides the requirement inside enthusiasm. What to state upfront, what to explain, and what to leave to HR.
Read article →Spotted an error in AI-generated work? How to flag it clearly and usefully: name the specific mistake, the impact, and the fix, without blame.
Read article →A chat message that gets answered fast is built, not lucky. Put the ask first, make the reply easy, and stop making people decode what you need.
Read article →Rolling out an AI tool is a communication problem before it is a technical one. What to say about jobs, monitoring, and what is actually required.
Read article →The same message reads as efficient in Amsterdam and rude in Tokyo. Practical adjustments for directness, hierarchy, and timing across a distributed team.
Read article →Reorgs, departures, and reporting line changes generate anxiety in the gap between rumor and detail. How to write the message that closes that gap fast.
Read article →Group chats amplify tone and strip context. The specific habits that prevent a normal message from becoming a three-day argument.
Read article →Tell a team what changed, what comes first now, what pauses, and how to handle conflicts between priorities.
Read article →A practical format for handing work to a colleague without losing the owner, deadline, context, or definition of done.
Read article →