Skip to main content
Loading...
communication

Have a Hard Conversation Over Video

Practice a hard conversation over video with a remote teammate who expected approval and is about to hear the project is paused. Build skill in empathy, clarity, and a constructive close.

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 · Education · Nonprofit · Healthcare

Overview

Have a Hard Conversation Over Video is an AI roleplay practice scenario for rehearsing a difficult remote conversation before you have it live. The setup puts you on a scheduled 15-minute video call with a teammate who expected approval for work they cared about, and your job is to tell them the project will not move forward this quarter because priorities changed.

Use this template when the message is disappointing, the relationship matters, and you need to stay warm without sounding vague or defensive. It is especially useful for managers and project leads who want to practice the opening line, the reason for the decision, and the close that keeps the door open for future work. The persona reacts like a real person on video: professional, disappointed, and likely to push back if the message feels unclear or overly polished.

Do not use it for performance reviews, disciplinary conversations, or anything that requires a formal HR process. It is also not the right fit when you are simply sharing routine status updates with no emotional weight. The value of the template is in the specific moment where you must acknowledge disappointment, explain a changed priority without overexplaining, and end with a concrete next step the other person can act on.

How to use this template

  1. Read the situation carefully and identify the exact bad news, the likely emotional reaction, and the one constructive next step you want to leave with.
  2. Start the roleplay on video by opening with empathy and a respectful tone, then state the decision clearly without burying it in setup.
  3. Talk to the persona as the conversation unfolds, acknowledging disappointment before you move into a brief explanation or alternative path.
  4. Complete the attempt against the scored rubric, checking whether you were direct, calm, and concrete rather than vague or defensive.
  5. Review the feedback, tighten the opening line or close, and retry the scenario until you can deliver the message clearly and warmly.

Best practices

  • Open by naming the person and the purpose of the call so the conversation feels intentional, not accidental.
  • Deliver the decision in plain language early in the call instead of circling around it.
  • Acknowledge disappointment before explaining the reason, especially when the project mattered to the other person.
  • Keep the explanation short and specific; one clear reason is usually stronger than a long justification.
  • Avoid sounding like you are asking permission for a decision that has already been made.
  • Offer one concrete next step, such as a follow-up date, a revised scope, or a future opportunity to revisit the work.
  • Watch your pacing and facial expression on video so the tone stays steady even if the other person reacts strongly.

What this template typically catches

Issues teams running this template most often surface in practice:

softens the message so much that the learner does not clearly hear the project is not moving forward
overexplains the priority change and sounds defensive
jumps to next steps before acknowledging disappointment
uses vague language like maybe, probably, or we’ll see instead of a clear decision
fails to set a respectful tone at the start of the video call
argues with the persona’s reaction instead of acknowledging it
ends without a concrete follow-up or alternative path

Common use cases

Engineering manager telling a remote developer about a paused feature
A manager needs to tell a developer that a feature they built is being deprioritized after a planning shift. The learner must protect trust, explain the change briefly, and leave the developer with a clear next step.
Agency lead updating a client-facing designer
A project lead has to tell a designer on a video call that client approval did not come through and the concept will not launch this quarter. The learner practices staying calm, direct, and respectful while the persona reacts with frustration.
Nonprofit director speaking with a remote program coordinator
A director needs to explain that a grant-backed initiative is being delayed because leadership shifted priorities. The conversation focuses on empathy, clarity, and preserving the relationship for future work.
Healthcare operations manager revising a team project
A manager must tell a remote operations specialist that a workflow improvement project is on hold due to higher-priority staffing issues. The learner practices a concise explanation and a constructive close.

Frequently asked questions

What kind of situation does this template cover?

This template is for a scheduled video call where you need to deliver disappointing news to a remote teammate. The core scenario is a project they expected to be approved, but priorities changed and it will not move forward this quarter. It is designed for practicing a calm, direct conversation rather than a generic feedback talk. Use it when the message is sensitive, time-bound, and likely to trigger disappointment or frustration.

Who should use this roleplay?

Managers, team leads, project owners, and anyone who has to communicate a hard decision over video can use it. It is especially useful for people who know what they need to say but want practice saying it with empathy and composure. The persona is set up to respond like a real remote teammate, so it works well for leadership and communication training. It also helps new managers who need a repeatable way to handle difficult updates.

How often should someone practice this scenario?

Use it whenever you are preparing for a real hard conversation, especially if the message affects someone’s work or expectations. It is also useful as a recurring practice exercise for managers who regularly deliver updates about scope, timing, or priority changes. Because the scenario is short and focused, it works well as a quick rehearsal before an actual call. Repeating it helps you avoid sounding defensive or overly scripted.

What makes this better than improvising the conversation?

Ad hoc conversations often drift into overexplaining, mixed messages, or a weak close. This template gives you a concrete situation, a realistic persona, and scored criteria so you can practice the exact behaviors that matter. You get immediate feedback on whether you acknowledged emotion, explained the decision clearly, and ended with a next step. That makes the practice more repeatable and easier to improve.

Can I customize the project, relationship, or tone?

Yes. You can swap in your own project details, team context, and level of formality while keeping the same structure. The situation can be adjusted for different stakes, such as a delayed launch, a rejected proposal, or a changed priority. You can also tune the persona’s temperament to be more calm, more frustrated, or more skeptical. The rubric still works as long as the learner objective stays focused on clarity, empathy, and a concrete next step.

What should the learner do during the roleplay?

The learner should open with empathy, state the bad news directly, explain the reason briefly, and respond to the persona’s reaction without getting defensive. The goal is not to win agreement; it is to deliver the message clearly and preserve trust. The best attempts acknowledge the disappointment before moving to options or next steps. The conversation should end with something actionable, such as a follow-up, alternative path, or timeline for revisiting the work.

What are the most common mistakes this template surfaces?

People often soften the message so much that the other person does not hear the decision clearly. Another common mistake is overexplaining the reason, which can sound defensive or invite debate. Learners also jump to solutions too quickly and skip the emotional acknowledgment that helps the conversation land. This template surfaces those habits because the persona reacts realistically when the message feels vague or rushed.

How can this template fit into a training rollout?

It works well as a standalone practice scenario or as part of a manager communication track. Pair it with other roleplays about feedback, expectation-setting, and difficult 1:1 conversations to build a broader skill set. You can assign it before a live conversation, then review the attempt and retry with a stronger opening or closer. It also fits well in onboarding for new managers who need a safe place to rehearse hard news.

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...
  • 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....
  • Communication at work is the practice of moving information reliably — announcements, decisions, expectations, problems — between the people who have it and...
Related guides

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Have a Hard Conversation Over Video 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.