Coach a Report on Alienating Written Communication

This template helps you practice coaching a strong performer whose written communication is efficient but alienating. The goal is to name the specific pattern, explain the collaboration impact, and agree on a few behavior changes the report can actually use. It is designed for manager coaching conversations, not performance review write-ups. You get a realistic direct-report persona that may push back on the feedback before softening if you acknowledge the strengths and the business impact.

Use it when the problem is tone in written communication, especially Slack messages, comments in docs, or project updates that sound abrupt, corrective, or dismissive. It fits situations where the person is delivering results but creating avoidable friction with coworkers. If the issue is missed deadlines, poor quality, or attendance, a different scenario is a better fit. This one is specifically about interpersonal impact and communication style.

A manager, team lead, or anyone preparing to coach a direct report can run it. It is especially useful for people who need to give candid feedback without sounding vague or overly harsh. The learner should be the person delivering the coaching conversation, while the persona plays the defensive but reasonable employee. It also works well for new managers practicing how to balance support with accountability.

The roleplay itself is a one-time practice exercise, but the real-world coaching it supports should happen as soon as the pattern is visible. In practice, that usually means addressing the issue after a few examples, not waiting for it to become a formal conflict. Follow-up conversations can be short and frequent until the new behavior sticks. The template helps you rehearse both the first conversation and the check-in after it.

The most common mistake is leading with criticism before acknowledging that the person is effective and well-intentioned. Another is staying too vague, such as saying the tone is 'off' without naming a real message or pattern. Learners also often skip the impact on teammates and jump straight to advice, which makes the report feel judged rather than coached. The scenario is built to surface those habits and replace them with specific, behavior-based feedback.

Yes. You can change the team context, the communication channel, or the kind of message that caused friction, such as code review comments, status updates, or customer-facing notes. You can also adjust how defensive the persona is if your audience needs an easier or harder conversation. The core structure should stay the same: specific example, clear impact, and concrete next steps. That keeps the practice realistic while matching your workplace.

Ad hoc feedback often stays general, inconsistent, or too polite to change behavior. This template gives you a repeatable scenario with a defined learner objective, a dynamic persona, and scored criteria so you can practice the exact conversation before you have it. That makes it easier to stay calm, specific, and outcome-focused in the real meeting. It also helps you avoid overcorrecting a high performer in a way that damages trust.

Acknowledge the intent first, then redirect to impact. For example, you would recognize that the messages are concise and fast, but explain that the tone is landing as abrupt and making it harder for teammates to collaborate. The persona is designed to test whether you can hold both truths at once: the person is competent, and the current style is still causing friction. The best response is to stay calm, name one or two observable changes, and ask for agreement.