Surface Conflicting Directions from Two Leaders

It helps learners surface two conflicting instructions, explain the tradeoff in plain language, and ask for a clear priority decision. The goal is not to pick a side or solve the project itself. It is to practice a calm, neutral conversation that prevents rework and confusion. The scored rubric focuses on clarity, tone, and closing with a next step.

Use it when the problem is not interpersonal tension but competing direction from two leaders. This template fits moments where the learner needs to protect time, clarify scope, and avoid doing both tasks badly. It is especially useful when one instruction came from a direct manager and another came from a department head or senior stakeholder. If the issue is a customer dispute or peer disagreement, a different scenario is a better fit.

A manager, team lead, coach, or L&D facilitator can run it, and it also works well as self-guided practice. The learner should be the person who needs to reconcile the conflict, not the leaders giving the instructions. Because the persona is direct and busy, the facilitator should encourage concise answers and a clear ask. This makes the roleplay feel realistic and keeps the learner focused on the decision point.

Use it during onboarding, manager training, or anytime a team is seeing confusion around priorities and escalation paths. It also works well as a refresher before busy periods when deadlines and stakeholder requests tend to collide. The scenario is short enough for repeated attempts, which matters because learners usually improve after a few tries with immediate feedback. Repetition helps them build the habit of naming the conflict early instead of silently absorbing both tasks.

Learners often soften the conflict so much that the leader never hears the real tradeoff. They may also sound accusatory, blame one leader, or jump straight into a solution without asking for a decision. Another common miss is failing to state the impact on the client-facing update in concrete terms. The rubric is designed to catch those behaviors and reward a neutral, action-oriented close.

Yes. You can swap the project type, deadline, and leader relationship while keeping the same core skill: surfacing conflicting direction and asking for priority. For example, a sales team might use a client deck, while an operations team might use a launch checklist or incident update. You can also adjust the persona's temperament to make the leader more rushed, more collaborative, or more firm. The structure stays the same even when the context changes.

Ad hoc handling often leads to vague updates, hidden assumptions, or doing extra work that no one asked for. This template gives learners a repeatable way to name the conflict, frame the tradeoff, and request a decision before time is wasted. It also creates a shared standard for what good escalation sounds like. That makes it easier to coach the behavior across a team.

A strong response states both instructions accurately, explains what changes if one task is prioritized over the other, and asks for a clear call. It should sound neutral and professional, not defensive or political. The learner should leave the conversation with a next step, such as which task to complete first or who will confirm the decision. If they can do that without blaming either leader, they are meeting the core objective.