Chase an Overdue Deliverable Without Nagging

This template is for a specific follow-up conversation when a teammate has missed a deliverable that is blocking your work. It fits moments like a late draft, missing copy, an overdue review, or a handoff that slipped past the agreed time. The goal is to practice a respectful reminder that still creates urgency. It is not for performance reviews or conflict mediation.

Use it whenever a deadline has passed and you need a concrete update, not just reassurance. It is especially useful before high-stakes deadlines, client-facing work, or cross-functional handoffs where one delay affects several people. Teams can also reuse it as a rehearsal before real follow-ups. It works best as a short, repeatable practice scenario rather than a one-time exercise.

A manager, team lead, coach, or individual contributor can run it. It is useful for anyone who has to chase work without damaging the relationship. Because the persona is avoidant and slightly defensive, it helps learners practice staying steady when the other person is not immediately cooperative. No special facilitation background is required.

The learner should open with a clear reminder, name the impact of the delay, and ask for a specific status update or revised delivery time. The best outcome is a concrete next step that both sides understand. The conversation should end with a follow-up plan, not a vague promise. This makes the roleplay useful for real workplace follow-through.

A reminder email can be easy to ignore or too vague to move the work forward. This roleplay trains the live conversation skills needed to be direct without sounding harsh. It helps the learner practice tone, pacing, and how to respond if the other person gets defensive. That makes it better for building confidence before a real follow-up.

People often wait too long, soften the message so much that the urgency disappears, or start with blame instead of context. Another common mistake is asking, "Any update?" without stating the deadline, impact, or what happens next. This scenario helps the learner replace vague chasing with a specific, respectful ask. It also reduces passive-aggressive phrasing that can damage trust.

Yes. You can swap in a design draft, legal review, sales deck, client proposal, or engineering handoff while keeping the same structure. The situation, opening line, and follow-up plan can be adjusted to match the team’s workflow and deadlines. The persona can also be tuned to be more busy, more avoidant, or more responsive depending on the learner’s needs. That makes it easy to reuse across departments.

It can be paired with task management tools, but the roleplay itself focuses on the conversation, not the software. Teams often use it alongside a project board, shared deadline tracker, or follow-up note so the next step is captured clearly. The practice is most effective when the learner also decides what will be documented after the conversation. That keeps the follow-up from disappearing once the call ends.