Responding to Critical Feedback
David raises concerns about missed deadlines and asks Emma to communicate risks sooner. Emma listens, clarifies the examples, and suggests practical ways to keep projects on track.
Dialogue10

Thanks for putting together your review, Emma. One area I’d like us to discuss is project deadlines. A couple of deliverables came in later than we’d agreed.
I appreciate you bringing that up. Could you walk me through which deadlines you have in mind? I want to understand where things went off track.
The client report was two days late, and the final dashboard missed its target by about a week. In both cases, I didn’t hear there was a risk until close to the deadline.
That’s fair. The report took longer because the data needed another round of checking, and the dashboard depended on inputs that arrived later than expected. I should have flagged both risks sooner.
I understand those factors were partly outside your control. Still, if a deadline looks shaky, I need an early heads-up so we can adjust the plan or reset expectations.
Agreed. I was trying to solve the problems before raising them, but I can see that staying quiet left you with too few options. Would a brief update as soon as a risk appears work for you?
Yes, that would help. Include what’s at risk, why it’s slipping, and what you recommend. You don’t need a perfect solution before you bring it to me.
That makes sense. I’ll also break larger tasks into checkpoints and build in some buffer time, especially when I’m waiting on input from other teams.
Good. Let’s check in briefly each week while the next dashboard is underway. If we spot a bottleneck early, we can reassign work or make a call on scope before it affects the final date.
I’m on board. I’ll send you a status update every Friday and flag any risks as soon as they come up. If a deadline needs to move, I’ll propose a revised date rather than just letting it slip.
Vocabulary7
- went off track
Something went off track when it did not go as planned. Use this phrase to ask or explain where a project started to face problems.
- flagged both risks sooner
To flag a risk is to point out a possible problem. Here, Emma says she should have warned David earlier.
- an early heads-up
An early heads-up is a warning or update given before a problem becomes urgent. You can use it to ask someone to tell you about risks promptly.
- reset expectations
To reset expectations is to agree on a new understanding of what is realistic, such as a revised deadline. It is useful when a project may not meet its original plan.
- build in some buffer time
To build in buffer time is to allow extra time in a schedule in case of delays. This phrase is useful when planning tasks that depend on uncertain factors.
- spot a bottleneck early
A bottleneck is something that slows down progress. Spotting one early means noticing the cause of a delay before it affects the whole project.
- make a call on scope
To make a call on scope is to decide what work should be included or changed. Teams may do this when the original plan is no longer realistic.
Key Sentences8
- 1
Could you walk me through which deadlines you have in mind?
This is a polite way to ask for specific examples of feedback. Use “walk me through” when you want someone to explain details step by step.
- 2
I want to understand where things went off track.
This shows that you are listening and want to understand the cause of a problem. You can use it to invite an honest explanation without sounding defensive.
- 3
I should have flagged both risks sooner.
This acknowledges responsibility for not communicating early enough. The structure “I should have [past participle]” is useful for recognizing what you could have done differently.
- 4
Still, if a deadline looks shaky, I need an early heads-up so we can adjust the plan or reset expectations.
This gives clear feedback while explaining why early communication matters. Reuse “if [situation], I need [action] so we can [result]” to make a practical request.
- 5
You don’t need a perfect solution before you bring it to me.
This reassures someone that they can raise a problem before they have solved it. Use it to encourage early communication and collaborative problem-solving.
- 6
I’ll also break larger tasks into checkpoints and build in some buffer time, especially when I’m waiting on input from other teams.
This sentence describes concrete steps for keeping work on schedule. The pattern “I’ll also [action], especially when [condition]” is useful for explaining a plan.
- 7
If we spot a bottleneck early, we can reassign work or make a call on scope before it affects the final date.
This connects early problem-solving with practical options. Use “If we [action], we can [options] before [negative result]” to discuss how to prevent delays.
- 8
If a deadline needs to move, I’ll propose a revised date rather than just letting it slip.
This shows accountability by promising to communicate and suggest a new deadline. “Rather than” helps contrast a proactive response with an unhelpful one.