Escalate a Blocked Project to Leadership
Practice escalating a blocked project to a busy VP with a crisp summary, concrete business impact, and a specific ask that gets a decision.
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 · Healthcare · Financial services · Retail
Overview
This AI roleplay practice scenario helps learners rehearse a high-stakes escalation conversation with a busy executive when a project is blocked by another team. The situation is specific: a cross-functional project has missed two handoff deadlines, and the delay is now threatening a client launch. The learner must use a short executive slot well, communicate the blocker clearly, explain the business impact in concrete terms, and ask for a decision or action that actually moves the work forward.
Use this template when someone needs to brief leadership on a dependency failure, a schedule risk, or a launch issue that cannot be solved through normal follow-up. It is especially useful for project managers, team leads, and new managers who need practice staying calm, direct, and solution-oriented with a skeptical VP. The persona is designed to push back on vague language, so the learner has to be specific about what is blocked, why it matters, and what support is needed.
Do not use this template for routine status updates, broad planning meetings, or situations where the blocker can be resolved without escalation. It is also not the right fit if the learner needs to practice relationship repair after a conflict; this scenario is about concise upward communication and leadership action. The best attempts end with a clear owner, a defined next step, or a decision that unblocks the project.
How to use this template
- Read the situation and identify the blocker, the business impact, and the leadership action you want the learner to request.
- Start the roleplay with Dana, who is busy, direct, and skeptical, and give the learner a short opening window to make the case.
- Let the learner speak in a live back-and-forth conversation and push back when the explanation is vague, overly long, or blame-focused.
- Score the attempt against the rubric criteria for crisp summary, concrete impact, specific ask, confidence under pushback, and a clear close.
- Review the misses, tighten the opening line and leadership ask, and retry until the learner can deliver the escalation in a concise executive format.
Best practices
- Open with the blocker in one sentence before adding any background detail.
- Name the project, the missed handoff, and the deadline risk so the VP can understand the issue immediately.
- Translate the delay into business terms such as launch timing, customer commitment, revenue risk, or team capacity.
- Make one specific ask, such as a decision, a priority call, or direct intervention with the dependent team.
- Stay neutral about the other team and focus on facts, dependencies, and next steps.
- If Dana pushes back, answer the question directly and then return to the decision needed.
- Close by confirming who owns the next action and when the learner should follow up.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this roleplay template help learners practice?
This template helps learners practice escalating a project blocker to leadership without sounding vague, emotional, or accusatory. The learner has to summarize the situation quickly, explain why the delay matters, and ask for a specific action or decision. It is designed for the moment when a cross-functional dependency is slipping and the project owner needs executive support.
When should I use this template instead of a general status update?
Use it when the blocker is serious enough that normal project follow-up is no longer working and leadership intervention is needed. It is not for routine check-ins or broad project reporting. The scenario is best when a missed handoff is putting a launch, deadline, or customer commitment at risk.
Who should run this practice scenario?
A manager, team lead, project manager, or people leader can run it for anyone who needs to escalate issues upward. It works well for individual contributors who occasionally need to brief executives, and for new managers learning how to advocate for their team. The scorer should look for clarity, confidence, and a concrete next step.
How often should teams practice this kind of escalation?
Use it during onboarding, before high-stakes launches, and whenever people are stepping into cross-functional coordination roles. It is also useful as a refresher after a project misses a milestone because the escalation path was unclear. The goal is to build a repeatable habit, not to rehearse a script once.
What makes this different from an ad-hoc conversation with a VP?
Ad-hoc escalation often drifts into background detail, blame, or a long story without a clear ask. This template gives the learner a realistic executive conversation with a defined situation, a skeptical persona, and scored behaviors. That structure helps people practice the exact moment where brevity and precision matter most.
Can this be customized for different projects or teams?
Yes. You can swap in the project name, the dependent team, the deadline, the customer impact, and the leadership action you want the learner to request. You can also adjust Dana's temperament to be more supportive or more resistant depending on the skill level you want to test. The core pattern stays the same: summarize, impact, ask, and close.
What should the learner say if the VP pushes back?
The learner should stay concise, answer the objection directly, and return to the decision needed. Good responses acknowledge the pushback, restate the business risk, and clarify what action would unblock the work. The goal is not to win an argument; it is to secure a useful next step.
What common mistakes does this template surface?
It often reveals learners who lead with too much context, blame the other team, or fail to make a specific ask. It also surfaces weak business framing, such as describing the delay without saying what it affects. Another common issue is ending the conversation without naming an owner or next step.
Related templates
Go deeper on the topic
-
Change management is the structured discipline for moving people, processes, and organizations through transitions — new systems, new structures, new...
-
DEI — diversity, equity, and inclusion — is three distinct disciplines often collapsed into one program. Diversity is who is in the organization; equity is...
-
Leadership is the practice of getting a group of people to do their best work toward a shared outcome. It is not the same as management (running the...
-
Organizational development (OD) is the discipline of designing, changing, and developing organizations as systems — structure, roles, processes, culture, and...
-
Hospital recognition programs have the potential to revolutionize the healthcare environment, creating a culture of gratitude, motivation, and excellence....
-
The Challenges Of Building A Retail Communication Strategy Communication strategy is the lifeblood of any successful organization, and in the dynamic world...
-
Navigating the complex world of retail turnover can appear as a daunting task. With so many variables at play, it can be difficult to discern where the real...
-
In the fast-paced world of retail, keeping frontline employees well-informed and engaged is essential for smooth operations and exceptional customer...
Ready to use this template?
Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Escalate a Blocked Project to Leadership 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.