Skip to main content
Loading...
leadership

Coach a Report on Alienating Written Communication

Coach a talented direct report on blunt Slack messages and terse updates that are landing as dismissive. Use this roleplay to give specific feedback, explain the impact, and agree on clearer written communication habits.

Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Technology · Professional services · Operations · Education · Healthcare

Overview

Coach a Report on Alienating Written Communication is a leadership roleplay for practicing a difficult but common 1:1: a strong direct report is effective at the work, but their Slack messages, email replies, or project updates are landing as blunt and dismissive. The situation centers on a high performer who believes they are saving time by being concise, while teammates experience the tone as cold, abrupt, or unhelpful.

Use this template when you need to give feedback that is specific enough to change behavior without turning the conversation into a debate about personality. The learner practices naming the exact communication pattern, citing examples, acknowledging the report's strengths, explaining the impact on collaboration and trust, and agreeing on observable changes for future messages. The persona is defensive and efficiency-focused, so the learner has to stay grounded, avoid vague advice, and connect tone to team outcomes.

Do not use this template for performance issues unrelated to communication, for one-off misunderstandings with no pattern, or when the real problem is a policy violation or conduct issue that needs a different process. It is also not the right fit if the learner only wants to vent or rehearse a generic "be more professional" talk. The value of the scenario is in practicing a precise coaching conversation that produces a concrete commitment the direct report can actually follow.

How to use this template

  1. Read the situation carefully and identify the specific written communication pattern you need to address, including the channel, examples, and likely impact on teammates.
  2. Start the roleplay by opening the 1:1 with a clear, respectful coaching frame that acknowledges the direct report's strengths before naming the concern.
  3. Talk to Jordan as you would in a real conversation, using concrete examples, explaining the effect on collaboration, and responding to defensiveness without backing away from the feedback.
  4. Complete the roleplay against the scored rubric, making sure you have named the pattern, connected it to impact, and agreed on specific future behaviors.
  5. Review the feedback, revise your approach if needed, and retry until your language is specific enough to produce a real change in written communication.

Best practices

  • Name the exact pattern you are seeing, such as short one-word replies, missing context, or abrupt project updates, instead of describing the person as rude.
  • Lead with a genuine strength so the feedback lands as coaching, not a character attack.
  • Use one or two concrete message examples from the scenario to show that you are reacting to behavior, not making a vague impression-based critique.
  • Explain the impact in team terms, such as slower collaboration, more follow-up questions, or reduced trust, rather than focusing only on your personal preference.
  • Ask the direct report what they intended, then bridge that intent to how the message was received.
  • Agree on observable changes like adding a greeting, adding one sentence of context, or softening a request before the next send.
  • Avoid overcorrecting into wordiness; the goal is clearer tone, not bloated messages.

What this template typically catches

Issues teams running this template most often surface in practice:

Jumps straight to criticism without acknowledging the direct report's strengths or intent.
Uses vague feedback like "be nicer" instead of naming the specific written pattern.
Argues about whether the report meant to sound blunt instead of focusing on how the messages were received.
Fails to connect the tone to concrete team impact such as confusion, friction, or reduced trust.
Leaves the conversation without any specific commitment for future Slack messages or updates.
Treats the issue as a one-time style preference instead of a repeatable communication habit.
Overexplains the feedback and dilutes the main point until the direct report never hears the correction.

Common use cases

Engineering manager coaching a senior developer
A senior developer ships solid work but replies to teammates with terse messages that shut down discussion. The manager uses this scenario to practice giving feedback that preserves the developer's confidence while changing how they communicate in shared threads.
Operations lead coaching a high-output coordinator
A coordinator moves quickly and sends short updates that leave stakeholders unsure what changed or what is needed next. This roleplay helps the learner practice turning a style complaint into a concrete expectation for clearer written updates.
Director coaching a newly promoted manager
A new manager is efficient in writing but their messages to peers and direct reports are being read as dismissive. The learner practices a coaching conversation that links tone to leadership credibility and team trust.
Customer-facing team lead addressing internal Slack friction
A strong account specialist uses blunt internal messages that create tension across support and implementation. The learner works on naming the pattern, explaining the collaboration cost, and agreeing on a more constructive communication habit.

Frequently asked questions

What does this roleplay template cover?

This template covers a 1:1 coaching conversation with a high-performing direct report whose written communication is efficient but alienating. The learner practices naming the specific pattern, giving concrete examples, and explaining how the tone affects collaboration and trust. It also includes the step of agreeing on observable changes for future Slack messages and project updates.

When should I use this template?

Use it when a strong performer is creating friction through blunt messages, terse status updates, or dismissive replies. It fits situations where the issue is not the work quality, but how the work is communicated to teammates. It is especially useful after peer feedback, a manager observation, or a pattern of avoidable misunderstandings.

Who should run this practice scenario?

A people manager, team lead, or anyone practicing a coaching conversation can run it. It is designed for someone who needs to give corrective feedback without flattening the person's strengths or turning the discussion into a personality critique. The learner should be the person delivering the feedback in the 1:1.

How often should a manager address this kind of issue?

Address it as soon as the pattern is visible and repeat the coaching if the behavior continues after the first conversation. This is not a one-time script to memorize; it is a conversation pattern to revisit when the person slips back into terse written communication. The template helps the learner practice setting a clear expectation and following up later with examples.

What is the biggest mistake managers make in this conversation?

The most common mistake is jumping straight to criticism without acknowledging the direct report's strengths or intent. Another pitfall is using vague feedback like "be nicer" instead of naming the specific messages, tone, and impact. This template pushes the learner to be concrete, calm, and behavior-focused.

Can this be customized for Slack, email, or project updates?

Yes. The core pattern stays the same, but you can swap in the communication channel that matters most in your team. You can also customize the scenario with examples from customer replies, internal project threads, or executive updates so the practice feels closer to your actual workflow.

How does this compare with an ad-hoc coaching conversation?

An ad-hoc conversation often stays too general, too soft, or too reactive to one bad message. This template gives the learner a repeatable practice scenario with a specific situation, a realistic persona, and scored criteria. That makes it easier to rehearse the exact behaviors that lead to a better real-world outcome.

What should I look for in a strong response?

A strong response names the communication pattern with examples, acknowledges the person's strengths before correcting course, and explains the impact on trust and collaboration. It also ends with specific commitments, such as adding context, softening openings, or checking for tone before sending. The best responses turn the feedback into a concrete habit change, not a vague promise.

Go deeper on the topic

Related concepts
  • Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
  • Change management is the structured discipline for moving people, processes, and organizations through transitions — new systems, new structures, new...
  • Collaboration is the coordinated work of two or more people toward a shared outcome — arguing, deciding, producing, and shipping. It is not the same as...
  • Communication is the movement of information from one person or group to another — announcements, updates, instructions, questions, acknowledgements....
Related guides

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Coach a Report on Alienating Written Communication ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.