Write difficult work messages more clearly
Some work messages are hard because the content is sensitive. FixMyText.AI helps rewrite drafts so they are clearer, calmer, and less likely to create unnecessary friction.
Why difficult messages fail silently
Most badly written difficult messages do not produce an immediate explosion. They produce silence, distance, or a slow erosion of trust. A message that sounds accusatory when the sender meant it to be factual. A delay notice that sounds defensive rather than accountable. A disagreement email that says nothing directly but radiates irritation throughout.
The problem is that the writer is usually focused on managing their own discomfort rather than on what the reader actually needs to understand and do. The result is a message that is about the sender's feelings rather than the practical situation.
A rewrite before sending helps shift the focus from how you feel about the situation to what the reader needs to know and what you want to happen next. That shift alone can change the entire reception of a message.
The difference between explaining and excusing
When something has gone wrong, there is a significant difference between explaining the situation and making excuses for it. Explaining is useful and expected: it gives the reader the context they need to understand what happened. Excusing is what happens when the explanation becomes a way to avoid accountability.
A delay notice that lists three external factors as reasons for the delay without acknowledging the impact on the reader is an excuse. A delay notice that says "this took longer than expected because of X; here is what we are doing about it and when you can expect the next update" is an explanation.
The test is simple: does the message tell the reader what they need to plan around, and does it give a clear next step? If the answer is yes, you are explaining. If the message is mostly about why it is not your fault, you are excusing.
The emotion check before you send
The first draft of a difficult message is often written under emotional pressure. This is fine: getting the draft out is a necessary first step. The problem is sending the first draft without pausing to read it from the recipient's perspective.
Before sending, ask two questions. First: if someone who had no context for this situation read this message, would they think the writer sounds reasonable or reactive? Second: does the message communicate what you want the reader to do, or does it just communicate how you feel about the situation?
If the answer to either question is uncomfortable, the message needs a revision pass before it goes out. FixMyText.AI can help with this revision, but the most important part is the pause itself. A difficult message sent in anger or frustration without review is rarely the right move.
How to disagree professionally without sounding passive-aggressive
Passive-aggressive professional writing is extremely common and almost universally counterproductive. It tends to involve polite surface language that carries a clear undercurrent of irritation or blame. Phrases like "as I mentioned previously" or "please refer to my earlier email" or "I just want to make sure we are aligned" often fall into this category when used in a context of actual disagreement.
A direct professional disagreement is more effective. It names the specific point of disagreement, explains the reasoning briefly, and proposes an alternative or asks a question. It does not imply that the other person is wrong for their view. It focuses on the work and the decision, not on the dynamic.
A useful structure: start by acknowledging the other person's position or the context. Then name the specific thing you see differently and why. Then propose what you think should happen instead, or ask what the reasoning is. This is professional disagreement: specific, calm, and forward-facing.
Delivering bad news clearly
Bad news delivered badly creates two problems: the news itself, and the additional friction created by the delivery. A message that buries bad news under a long preamble, or that is so softened that the reader does not realize how bad the news is, forces a difficult follow-up conversation that could have been avoided.
Bad news should be stated clearly and early in the message, not buried. The reader should understand what happened and what it means for them by the end of the first paragraph. Subsequent paragraphs can explain the context, what is being done about it, and what the reader should do next.
Being direct about bad news is not the same as being unkind. A message that states the situation clearly and immediately moves to next steps is more respectful of the reader's time and intelligence than one that hedges and delays the main point.
Delay notices that sound accountable
A delay notice has a specific job: to tell the reader that something will not be ready when expected, what will happen instead, and when they can expect the next update. That is three pieces of information, and all three need to be present.
The most common failure is a delay notice that gives the first piece of information (the delay) but not the second (what is being done) or the third (when to expect an update). The reader is left knowing that something is late, but without the information they need to plan around it.
Avoid over-apologizing in a delay notice. One direct acknowledgment of the impact is appropriate. Multiple apologies shift the message from being about the situation to being about the sender's discomfort, and they do not give the reader anything useful.
Phrasing a boundary without drama
Setting a professional boundary in writing is one of the situations where people most often use language that is either too soft (no real boundary is communicated) or too harsh (the boundary is communicated but the relationship takes unnecessary damage).
The most effective boundary messages are specific rather than general. Not "I cannot always be available outside of working hours" but "I am not available on weekends. If something is urgent, please contact X." Specific boundaries are clearer and easier to respect. General boundaries invite negotiation.
A boundary message does not need to include a long justification. You do not owe the reader an explanation of your personal life or your workload management strategy. A clear statement of what you will and will not do, combined with a practical alternative for the reader, is sufficient.
Tone differences between Slack and email in sensitive situations
Sensitive topics carry more risk in shorter formats. A difficult message in Slack has less space for nuance, more risk of being misread without context, and is more likely to produce a quick emotional reaction. An email, by contrast, gives more space for explanation and is less likely to trigger a live back-and-forth before both parties have thought through their positions.
For genuinely difficult professional topics, email is usually a better channel than chat. The extra formality of email creates a slight slowing effect on both sides: the sender is less likely to fire off something reactive, and the reader is less likely to respond immediately without thinking.
If a sensitive message must go through Slack or Teams, it benefits more from a careful rewrite than a similar message sent by email. The shorter the format, the more weight each word carries, and the more important it is to get the tone exactly right before sending.
When to ask for help rather than handle it in writing
Some difficult situations are not well suited to text at all. A situation involving interpersonal conflict, a performance conversation, a legal or HR matter, or a situation where the relationship is already severely damaged may require a phone call, a video call, or a meeting rather than a written message.
Text is excellent for situations where the facts are clear and the goal is to communicate a decision, a delay, a disagreement, or a boundary. It is less effective when the core problem is relational rather than informational, or when the stakes are high enough that a misread could cause real harm.
Use FixMyText.AI for the messages you have decided to send in writing. If you are not sure whether to send a written message at all, that decision requires judgment about the situation that falls outside what the tool can help with. When in doubt, a conversation first is rarely the wrong call.
Before and after: what a rewrite does to a difficult message
Original: "I have to say I am disappointed that this was not completed on time. We had agreed on a clear deadline and it was not met. This is causing problems for the rest of the team and I hope we can get this resolved quickly."
Problems: the message focuses on the sender's feelings rather than the situation, the word "disappointed" can read as parental, and there is no specific ask or next step. A rewrite would acknowledge the delay directly, name the specific impact, and end with a clear question or request: when can you have this done?
The goal is not to remove emotion entirely from difficult messages. It is to ensure the emotion does not crowd out the practical content that the reader actually needs to act on the situation.
A check before sending any difficult message
Before sending any message in this category, run through this checklist. Is the main point stated clearly in the first two sentences? Is there a specific next step or request at the end? Have you read the message from the recipient's perspective and confirmed it will not be read as accusatory or passive-aggressive? Is this the right channel for this message?
Also check: are you sending this message because it needs to be sent, or because you need to express how you feel? These are different motivations and they produce very different messages. If it is the latter, writing the message for yourself first and then rewriting it for the reader is a useful approach.
Finally, if the relationship is important, consider whether a short conversation before or after the message would make the message land better. A difficult message often reads more fairly when the reader already knows it is coming, or when the sender follows up briefly to make sure it was received the right way.