Loading...
communication

Raise a Risk Nobody Wants to Hear

Practice raising a concrete project risk when a teammate is brushing it off. Build the habit of staying calm, specific, and persistent until you get a real next step.

Get Started

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Technology · Professional Services · Operations · Customer Success · Consulting

Overview

Raise a Risk Nobody Wants to Hear is an AI roleplay practice scenario for speaking up when a teammate is minimizing a real project risk. The learner is in a Thursday afternoon check-in before a Monday launch, and the challenge is to name the issue clearly, explain what it could cost, and keep the conversation grounded until the team agrees on a next step.

This template is useful when someone needs to challenge optimism without sounding alarmist. The persona, Maya, is leading the meeting and is under pressure, so she may brush past the concern, reframe it as “basically on track,” or ask to revisit it later. The learner objective is not just to mention the problem; it is to secure agreement on a concrete action before the meeting ends.

Use this template for launch readiness reviews, cross-functional handoffs, client implementation check-ins, and any moment when a hidden blocker could slip through because no one wants to slow things down. Do not use it for general brainstorming, casual status updates, or situations where the issue is already fully accepted and assigned. The value of the practice comes from the tension: the learner must stay calm, specific, and persistent while the persona resists the message.

How to use this template

  1. Read the situation carefully and identify the exact risk, the likely impact, and the decision you want by the end of the conversation.
  2. Start the roleplay with the persona and use a direct opening line that names the problem in concrete terms instead of hinting at it.
  3. Talk through the concern, respond to pushback, and keep the discussion focused on what will happen if the issue is not addressed now.
  4. Complete the attempt and review the scored rubric to see whether you named the risk, explained impact, stayed calm, persisted, and proposed a next step.
  5. Retry the scenario with a sharper opening line or a more specific ask until you can get agreement without losing composure.

Best practices

  • Name the risk in plain language, including the specific system, deliverable, or dependency that is still failing.
  • Connect the risk to a customer, launch, revenue, or timeline impact so the concern feels real rather than theoretical.
  • Use a calm, steady tone and avoid sounding accusatory, even if the persona is dismissive.
  • If the concern is minimized, restate it with one concrete fact and one concrete consequence instead of repeating the same vague warning.
  • Ask for a specific next step, owner, and time frame before the meeting ends.
  • Keep the focus on the business issue, not on proving that you were right.
  • Do not bury the lead with too much context; say the risk early so the other person can respond to it.

What this template typically catches

Issues teams running this template most often surface in practice:

Learner opens with a soft hint instead of clearly naming the risk.
Learner describes the problem in general terms and never states the concrete failure.
Learner explains the issue but does not connect it to customer or business impact.
Learner becomes defensive when the persona minimizes the concern.
Learner backs down after the first pushback and lets the meeting move on without action.
Learner proposes a vague follow-up instead of a specific next step with an owner.
Learner focuses on blame rather than on the risk and the decision needed.

Common use cases

Product manager in a launch readiness review
A product manager notices that a payment flow still fails in staging, but the team wants to declare the release ready. The learner practices naming the blocker, explaining the customer impact, and pushing for a go/no-go decision.
Customer success lead in a client implementation check-in
A customer success lead sees that final copy is still unapproved and the launch date is close. The learner has to raise the risk without sounding alarmist and get agreement on who will chase approval.
Operations coordinator flagging a handoff issue
An operations coordinator knows a downstream team has not completed a required step, but the meeting is moving on. The learner practices interrupting politely, stating the dependency, and securing an owner.
Consultant warning about a missed deliverable
A consultant sees that a client-facing deliverable is not ready for the promised date. The learner must explain the likely impact on trust and timeline while staying respectful with a busy internal teammate.

Frequently asked questions

What does this roleplay template help someone practice?

It helps learners practice speaking up when a project looks fine on the surface but has a real risk underneath. In this scenario, the learner has to name the issue in concrete terms, explain why it matters, and keep the conversation moving until the team agrees on an action. It is especially useful for people who hesitate to challenge optimism in meetings.

When should I use this template instead of a general feedback exercise?

Use it when the goal is to raise a business risk, not to give broad interpersonal feedback. The situation is specific: a launch is approaching, a teammate is minimizing the problem, and the learner needs to push for a decision before the meeting ends. If you want to practice praise, coaching, or performance feedback, a different template is a better fit.

Who should run this practice scenario?

A manager, team lead, facilitator, or the learner themselves can run it. It works well in onboarding, manager training, project leadership practice, and communication skill-building sessions. The key is that the facilitator keeps the persona realistic and scores the learner against the rubric criteria, not against vague style preferences.

How often should someone repeat this roleplay?

Repeat it until the learner can raise the risk without softening it into a hint or a vague concern. Because the scenario is built around deliberate practice, the value comes from multiple attempts with immediate feedback and a retry. It is useful as a one-off assessment or as a recurring exercise for people who lead cross-functional work.

What makes this different from an ad-hoc conversation about project issues?

Ad-hoc conversations often drift, avoid specifics, or end with no decision. This template gives the learner a defined situation, a pushback-prone persona, a learner objective, and scored criteria so the practice is repeatable. That structure makes it easier to compare attempts and improve a specific skill instead of just talking through the problem.

Can I customize the scenario for my team or industry?

Yes. You can swap the launch context, the risk, the teammate persona, and the business impact while keeping the same practice pattern. For example, you could adapt it for product launches, client implementations, internal rollouts, or operations handoffs. Keep the risk concrete and the next step observable so the rubric still works.

What should the learner do if the persona keeps minimizing the issue?

The learner should restate the risk in specific terms, connect it to the customer or business impact, and ask for a concrete decision or owner. The goal is not to win an argument; it is to persist respectfully until the concern is acknowledged and action is assigned. A strong attempt stays calm even when the persona remains optimistic.

What are the most common mistakes this template surfaces?

Learners often lead with vague language, over-apologize, or jump straight to solutions before the risk is understood. Another common miss is backing down after the first brush-off instead of persisting with a clearer statement. The template also reveals whether someone can turn concern into a specific next step rather than leaving the meeting with no decision.

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?

Get started with MangoApps and use Raise a Risk Nobody Wants to Hear with your team — pricing built for small business.

Get Started