A coworker keeps delivering late, and it is already affecting your timeline and outside commitments. You need to address it without pushing the relationship into open conflict.
Goal: Practice describing the impact of repeated delays and making a clear collaboration request instead of only expressing frustration.
Start with the shared outcome and concrete impact before discussing priorities, ownership, or resources.
Name verifiable facts and remove words such as “always,” “never,” or assumptions about intent.
Describe what you actually feel instead of disguising a judgment about the other person.
Connect the feeling to a need such as clarity, respect, cooperation, or safety.
Use “Practice describing the impact of repeated delays and making a clear collaboration request instead of only expressing frustration.” to shape a specific, actionable request that leaves room for a response.
Scenario-specific practice
Use these lines as practice prompts, not a script to repeat word for word. Replace bracketed details and example counts with facts you can verify, then adjust to the response you actually receive.
“I want to align on the status of [deliverable]. We agreed on [due time]. As of [check time], its observable status is [current status], which has caused [verifiable impact] for [downstream work or commitment]. I need a more dependable handoff and earlier notice of risk. Would you explain the current blocker and confirm [new deliverable or checkpoint] by [time]?”
“I was affected by [verifiable constraint], and [dependency or requirement] was not clear until [time]. Focusing only on the missed date leaves those conditions out.”
Verify the constraints and dependencies they raise and incorporate any supported new facts rather than debating who worked harder. Then separate the cause from the current recovery: restate the downstream impact and request the smallest checkable milestone and warning condition. If no usable commitment emerges, document the unresolved risk and use the existing project escalation path based on delivery impact, not a judgment of the coworker.
Likely to escalate the conversation
“You are always late, and you clearly do not take our commitments seriously.”
A clearer rewrite using NVC principles
“We agreed that [deliverable] would be ready by [due time]. As of [check time], its observable status is [status], which has caused [specific impact]. I’m concerned because I need reliable handoffs and enough notice to adjust dependencies. Please confirm [next deliverable or checkpoint] by [time], and if it becomes at risk, notify me by [trigger or time] with [needed status information].”
You can recognize the constraint and describe the impact at the same time. Update your understanding of the cause, then return to the recovery plan, next checkpoint, and the condition for earlier warning. Understanding the reason does not remove the need for a workable handoff.
Do not pressure them into a date they cannot support. Ask for the next verifiable checkpoint, the dependency still missing, and a time for the next status update. If downstream risk remains, document the facts and use the team’s existing escalation process.
Guest mode
Guests can try 1 free scenario and history is not saved. Sign in to keep practicing and save your latest 5 sessions.
You will practice this scenario with this role.
Choose a personality type for the AI to play, simulating real conversation challenges.
Reinforce the same skills with more workplace conversations.
You want to ask your manager for a raise and need solid reasons, evidence, and a clear communication strategy.
Start practiceEverything on your plate is being treated as urgent. You need to realign priorities, deadlines, and scope with your manager.
Start practiceA coworker made an unreasonable request outside your scope. You need to refuse politely while maintaining a workable relationship.
Start practiceWant context for this category first? Explore the workplace use case guide