How to write to colleagues
Writing to colleagues is fundamentally different from writing to a manager or a client because you have no formal authority over each other. You can't assign work, you can't approve budgets, and you can't set deadlines. Everything you need from a colleague, you need to earn through clarity, reciprocity, and professional goodwill. This makes peer communication both more egalitarian and more delicate than hierarchical communication.
The biggest challenge in colleague-to-colleague writing is getting things done when you can't make demands. "Can you send me the data by Friday?" is a request, not an instruction, and your colleague may have their own priorities. The most effective approach is to explain why and make it easy: "I need the customer data by Friday to finish the quarterly report for leadership — could you export it from the dashboard? Should take about ten minutes." This tells them the stakes, the effort required, and the deadline. It respects their time by being specific.
Disagreements with colleagues require more care in writing than they do in person. In a meeting, you can soften a disagreement with tone, facial expression, and the immediate give-and-take of conversation. In an email, the same disagreement can read as confrontational. The safest pattern is: acknowledge their position, introduce yours as an alternative rather than a correction, and suggest discussing further. "That's a solid approach — one thing I'd want to consider is the impact on the Q3 timeline. Want to talk through the trade-offs?" This is collaborative, not combative.
Group emails with colleagues are a minefield. Reply-all is the default for many people, and it shouldn't be. Before hitting reply-all, ask: does everyone on this thread need to see my response? If your answer is "probably" rather than "definitely," reply only to the person who needs the information. Unnecessary reply-alls create noise, and the people who generate the most noise tend to be the ones others start ignoring.
When a colleague makes a mistake that affects your work, how you address it in writing matters enormously. "The numbers in the report were wrong" is accusatory, even if it's factually correct. "I noticed a discrepancy in the numbers — can you double-check section three?" achieves the same result without assigning blame. This isn't about being soft — it's about preserving a relationship you'll need tomorrow.
Cross-functional communication — writing to colleagues in other departments — has its own rules. Don't assume they know your team's acronyms, tools, or priorities. A message to engineering from marketing should spell things out: "We need the landing page updated before the campaign launches on March 1st" is clearer than "Can you update the LP before the campaign goes live?" What's obvious to you isn't obvious to them.
Thanking colleagues is underrated and underused. A quick "thanks for pulling that together so fast — it made the presentation much stronger" takes fifteen seconds and builds the kind of goodwill that makes people prioritise your requests next time. Public acknowledgement (a message in a team channel, a mention in a meeting) is even more powerful.
Tone calibration with colleagues is simpler than with managers or clients: match the prevailing culture. If your team communicates casually with GIFs and emoji, that's your register. If the culture is more buttoned-up, follow suit. The goal is to fit in well enough that your messages feel natural, not to stand out by being notably more or less formal than everyone else.
Finally, be careful with humour in written colleague communication. Jokes that land perfectly in person can misfire spectacularly in text, especially with colleagues you don't know well. Sarcasm is the highest-risk form — without vocal inflection, sarcasm reads as sincerity about half the time, and the other half it reads as hostility. Save the jokes for Slack, where the conversational pace and emoji reactions provide enough context to keep things light.