I've Written a Draft But the Tone Feels Wrong and I Can't Identify What's Off. How Do I Get Claude to Find the Problem?
The solution to this problem is: have Claude read your draft from the recipient's perspective, then tell you what it perceives.
Prompt: 'Please read the following email draft and answer three questions from the recipient's perspective: (1) What is your overall impression of the sender after reading this email (in three adjectives)? (2) Is there any sentence or paragraph that makes you feel uncomfortable, confused, or defensive? If so, which one and why? (3) What is your most likely emotional response after reading this email? [paste draft]'
Claude's response can usually pinpoint exactly where the tone issue is. You might discover: a particular sentence has 'I' as the subject instead of 'you,' making the whole sentence sound like self-defense; or a paragraph focuses on explaining reasons, making the reader feel you care more about being understood than about apologizing.
Once you've found the problem, ask Claude to 'address this specific problem and rewrite this paragraph.' This is far more precise than 'help me revise this email to improve the tone.'
For a Difficult Email to My Manager, Should I Talk Face-to-Face First or Send the Email First? Can Claude Help Me Decide?
Claude cannot make this judgment for you — it doesn't know your relationship with your manager or your company's culture. But it can help you think through this decision systematically.
Prompt: 'I need to communicate a difficult message to my manager: [describe content]. I'm considering (1) notifying directly by email, or (2) speaking in person first, then following up with an email for the record. Please help me analyze the pros and cons of each approach, considering: how my manager typically prefers to receive communication, the severity of the situation, whether there is time pressure, and the importance of having a written record if things go wrong.'
General guidance (not absolute): if the news is very significant (e.g., project failure, major error), speaking in person first is usually better — giving the manager the opportunity to react and ask questions in real time, then following up by email for the record. For routine bad news (e.g., schedule delays with manageable impact), a direct email is usually more efficient and creates a paper trail.
Your knowledge of your manager runs far deeper than Claude's. The final call is yours. What Claude helps with is clarifying the decision criteria, not making the decision for you.
Claude's Draft Sounds Too Formal and Not Like How I Speak. How Do I Adjust It?
Over-formality is one of the most common output issues with Claude for difficult conversation emails — too much official language, reading more like a legal document than a real person speaking.
Three adjustment approaches:
Approach 1: Give Claude a sample of your speaking style. Paste one of your ordinary emails (doesn't need to be a difficult conversation — just a typical day-to-day email you wrote) and say 'this is my writing style — please rewrite the following draft in a similar voice.' Claude is skilled at mimicry; with a sample, the output shifts noticeably toward your natural tone.
Approach 2: Tell Claude directly what style you want. For example: 'Please make this email sound more like a person speaking rather than a corporate announcement. Use short sentences. Avoid official phrasing like formalese. Give it some personal warmth while maintaining courtesy.'
Approach 3: Make the final adjustments yourself. Accept Claude's draft as a '70-80% complete' version, then spend 5 minutes yourself replacing any sentences that read as 'very AI' or 'too formal' with how you'd naturally say them. This step is necessary, particularly in difficult conversation scenarios — because the email ultimately needs to represent you as a person, not AI output.
Are There Difficult Conversation Emails Where Using Claude Actually Carries More Risk and You Should Write Entirely Yourself?
Yes — and this judgment matters.
Here are situations where writing primarily yourself, with Claude only assisting rather than leading, is recommended:
Situation 1: Apology letters involving legal liability. If your apology letter could involve determination of legal liability (e.g., a product liability incident, an employee dispute), legal review is absolutely required first. Claude can make legally problematic wording mistakes, and it cannot assess legal risk. Have Claude draft an initial version, but the final must be confirmed by legal counsel.
Situation 2: Very personal apologies. If the letter involves a deeply personal relationship (e.g., apologizing to a longtime client you've worked with for years), overly 'AI-sounding' language will actually damage feelings. In this case, Claude can help you clarify your thinking and structure, but the final language should be as much your own voice as possible.
Situation 3: Your details and context are things Claude doesn't know. If the persuasive power of this email hinges on specific details or relationship context that only you know, Claude's generated version may be missing the most important element. Here, Claude's role should be providing structural framework while you fill in the content only you can write.
Summary: Claude is best suited to helping you find tone and structure — not replacing the real relationship between you and the other person.
There's a category of email in the workplace that everyone knows needs to be written, knows is important, but is most likely to be postponed until the last moment — written, deleted, then rewritten: difficult conversation emails. Bad news for a manager, apology letters to clients, declining a colleague's request, raising an uncomfortable issue. What these all share is that you know very clearly what needs to be said, but don't know how to start saying it, or how to let the other person receive difficult news while preserving a good relationship.
Claude's core value in this scenario isn't helping you deceive or embellish — it's helping you find that hardest-to-master tone: honest without being hurtful, firm without being rude, clear about the problem while still giving the other person a graceful way to respond. This tone is very difficult to find under pressure, but Claude can help you test several versions in five minutes so you can choose the most appropriate one.
Difficult conversation emails have three specific challenges that cause people to get stuck:
First, you're simultaneously serving two goals: transmitting information and preserving the relationship. An ordinary informational email only needs the recipient to understand the information. A difficult conversation email also requires ensuring that after receiving difficult news, the other person still holds a positive view of you, your company, and your relationship. These two goals sometimes conflict: the more clearly you communicate bad news, the easier it can be to damage feelings.
Second, every word choice carries risk. Imprecise wording in an ordinary email causes confusion at most. Imprecise wording in a difficult conversation email can cause misunderstanding, anger, or make the problem worse. 'Some issues' versus 'serious problems,' 'we did our best' versus 'we deeply regret' — these subtle word differences carry significant weight in difficult conversation contexts.
Third, you can't test the effect before sending. In ordinary work communication, saying something wrong can be corrected or clarified. But a difficult conversation email sets its first impression the moment it's sent. You can't know in advance how the recipient will feel reading it, which leads many people to hesitate and revise repeatedly before sending, consuming enormous time and energy.
The most effective framework for using Claude with difficult conversation emails: first tell Claude your goal, then tell it your constraints, then let it give you several versions with different tones to choose from.
Framework prompt: 'I need to write a [type] email to [recipient] about [core content]. My goal is: [the outcome you want, e.g., get them to accept the news, preserve the working relationship, help them understand our position]. My constraints are: [things you can't say, tones to avoid, cultural or courtesy requirements]. Please provide three versions: (1) the most direct version; (2) the most diplomatic version; (3) the version you think is most appropriate.'
After receiving the three versions, your job is to compare them, understand their differences, choose the one closest to what you need, then add your personal details — the specific circumstances you know, your relationship history with this person.
Scenario 1: Telling your manager bad news (project delay)
Situation: An important project you're responsible for will be delivered two weeks later than planned. You need to inform your manager before Monday morning's progress meeting.
Prompt: 'I need to email my manager that Project A, which I'm responsible for, will be delayed by two weeks, from the planned June 30 delivery to an estimated July 14. The primary cause is a supplier issue, but I share some responsibility for not responding quickly enough. My goals: (1) let my manager know before the meeting to avoid being caught off-guard in the session; (2) clearly explain the cause and remediation steps; (3) demonstrate accountability for this situation rather than deflecting. Tone should be direct and accountable but not so self-deprecating that it makes my manager worry about my capability. Approximately 150 words. Please give me three versions.'
Scenario 2: Apologizing to a client (product issue)
Situation: Your product experienced an issue affecting the client's business operations, causing them losses. You need to write an apology letter representing your company.
Prompt: 'I need to write an apology letter to our client [company name]. They experienced [problem description] while using our product, resulting in [impact description] to their business. My goals: (1) sincerely apologize without making excuses; (2) explain the remediation steps we are taking; (3) make the client feel valued and preserve the long-term partnership. Constraints: cannot promise compensation we cannot deliver, cannot legally admit liability (only express regret), tone should be genuine but professional. Please give me three versions: one more formal, one more personalized, and one you think is most effective.'
Scenario 3: Declining a colleague's request (capacity issue)
Situation: A colleague is asking you to help with a task that exceeds your current capacity. You need to decline without damaging the relationship.
Prompt: 'I need to decline a colleague's request for help. They want me to complete [task description] for them this week, but my current workload cannot accommodate new tasks. My goal: clearly communicate that I cannot help, while letting them know I genuinely want to help but truly cannot — not that I don't want to. I don't want them to feel I'm making excuses, nor that their request isn't important. Please give me one direct but warm decline version, and one version that offers an alternative (e.g., I can help next week, or suggesting they approach someone else).'
After receiving Claude's draft, do these four self-checks before sending:
First: if I were the recipient, how would I feel reading this? Try reading it from the other person's perspective. If you feel any sentence would cause discomfort or misunderstanding for a recipient, revise that part.
Second: are there any sentences that could be taken out of context? Difficult conversation emails are particularly susceptible to being screenshot or forwarded and taken out of context. Check for sentences that look bad in isolation, even if they're reasonable within the complete email.
Third: can I deliver on everything I've said? In apology letters or commitment letters, every 'we will...' is a promise. Confirm that every claim you make is something you can actually deliver. The subsequent trust damage from an unfulfilled promise is worse than having stated things more conservatively at the outset.
Fourth: if this email were seen by a third party (your manager, legal, media), would I still be comfortable with it? Especially for emails involving apologies, errors, or liability acknowledgment, this question is critical. Ensure the email's content represents a position you'd still accept even if made public in the worst case.
The quality of difficult conversation emails often determines how you're perceived in the workplace. Delivering the same bad news, one person leaves the recipient feeling 'they were honest, accountable, I trust them,' while another leaves them feeling 'they're making excuses, they're not taking responsibility.' This difference isn't in the facts themselves — it's in how the communication is handled.
The biggest value of using Claude for this type of email isn't removing the need to think. It's helping you systematically clarify — through the drafting process — what goal you're trying to achieve, what constraints you're operating within, and what different tonal approaches will each produce. This thinking process itself produces better outcomes than starting to type under pressure.