Constructive Feedback: Addressing a Missed Deadline

feedbackMid10–15 min
How to Use This: Run this roleplay with 2–3 people, or try it solo by voicing each role. Introduce curveballs to enhance realism. Reflect afterward to evaluate effectiveness.

Roleplay Scenario

Scenario Overview

A recent project deadline was missed, affecting team outcomes. You need to have a constructive feedback session to discuss what happened, why it happened, and how to prevent it in the future. The goal is to focus on understanding the situation and developing a plan for improvement.

Roles & Setup

Role A – Team Lead (You)
You are responsible for ensuring the team meets its deadlines and supports its members.
Your goal: Facilitate an open dialogue that identifies obstacles and encourages solutions.

Role B – Team Member
You missed the deadline and are aware of the impact.
Your goal: Receive feedback constructively and collaborate to find ways to improve.

Suggested Openers

Team Lead:

  • “Hey, can we chat for a bit about the deadline we missed recently? I’d like to understand what happened so we can avoid it next time.”
  • “I wanted to touch base about the project timeline. Let’s see how we can make things work better moving forward.”

Team Member:

  • “Sure, I’ve been thinking about it too. I have some thoughts on what went wrong and what I can do differently.”
  • “Thanks for reaching out. I’d like to discuss it and figure out how I can improve.”

Sample Roleplay in Action

Team Lead:
“Hey, thanks for sitting down with me. I wanted to talk about the deadline we missed. I’d like to hear what challenges you faced and how we can tackle them.”

Team Member:
“Yeah, thanks for bringing it up. I misjudged how long the integration would take, and it set me back.”

Team Lead:
“I get it, that happens. What do you think could help with more accurate time estimates in the future?”

Team Member:
“I think having more frequent check-ins could help catch these issues early. Also, if we could prioritize tasks more clearly when there’s a lot going on, that would help too.”

Team Lead:
“Sounds like a plan. We can definitely set up more regular updates and make sure priorities are clear. Let’s make that a focus moving forward.”

Team Member:
“Great, I’ll also start flagging any risks earlier so we have more time to adjust.”

Team Lead:
“Perfect. Let’s keep communication open, and I’m here to help with anything else you need.”

Post-Scenario Tools

Curveball Mode (Optional)

Introduce one of these mid-roleplay to increase complexity:

  • The team member reveals additional personal or technical challenges that contributed to the delay.
  • The team lead discovers they provided unclear instructions or insufficient resources.
  • The project timeline was unexpectedly shortened by upper management.

Reflection Checklist

As the Team Lead:

  • Did you maintain a supportive and solution-focused tone?
  • Did you encourage the team member to share their perspective?
  • Did you work together to develop a clear action plan?

As the Team Member:

  • Did you accept feedback constructively?
  • Did you identify specific improvements you can make?
  • Did you express any additional needs or barriers?

Common Mistakes to Avoid

  • Turning the conversation into a blame session.
  • Focusing only on problems without discussing solutions.
  • Failing to follow up on the agreed action plan.

Pro Tip

Feedback conversations should be a two-way street, where both parties gain insights and agree on actionable steps. This approach not only resolves current issues but also strengthens team trust and collaboration.

Practice What You Read

Test Your Poise in the Live AI Simulator

Reading case study scripts builds awareness. Rehearsing against an AI counterpart who interrupts and pushes back builds real leadership muscle memory.

Launch Live Simulator