Give feedback after a missed deadline
A missed deadline conversation fails when it starts with judgment. The other person needs to hear what happened, what it caused, and what you need next.
Goal
Finish with three things on the table: the facts of this miss, the impact, and a next date (or an explicit blocker). The other person should still be able to say what got in the way.
Typical setup: a handoff, a review, or an external promise sat on that date. You may have already felt the miss in Slack (“any update?”) before you asked for a meeting. The conversation is late if the first time they hear impact is in a hallway aside.
Method
The hard part is keeping the date, the artifact, and the person in separate places. “Thursday,” “the spec,” and “you’re unreliable” in the same breath turns a date problem into an identity problem. Skipping impact so nobody feels bad means you repeat the conversation with more heat next time.
Prepare observable facts: when it was due, what arrived (or did not), and who waited. Leave a beat for their context before you lock a new date. Skip that beat and you get compliance in the room, then the same miss later.
Write the facts as SBI first. If you need their side or a negotiated next step, run COIN once you are talking. Channel choice is in Steps.
Steps
1. Decide the channel
Small miss, usually reliable: a short written note. Other teams blocked, or a repeat: talk live. Do not hide a verdict in a long email.
2. Write three SBI lines privately
Situation: the agreed date and the piece of work (one sentence). Behavior: arrived late, arrived incomplete, or no ping when it slipped. Impact: who waited, and what slipped because of it. If a third party was waiting (QA, a customer, another team), name them as impact.
3. Open without a trial
Connecting is naming that you want a working plan. Live: “I want to talk about Thursday's API handoff so we can set a date that holds. I'm not here to pile on.” Then the facts.
4. Ask what got in the way
One question after the facts: “What got in the way of Thursday?” If they name a blocker you can remove, remove it. If they name a pattern (“I didn't want to flag it until I was sure”), make the next agreement about the ping, not about trying harder.
5. Close with a date and a ping rule
A new date, an owner for the ping if it slips again, and when you will check. Written note when the miss is small:
Thursday's spec was due noon; it arrived Friday with no heads-up. QA lost a day. Can you send a new handoff time, and ping me before noon the day before if it moves?
Do not stack a character paragraph under either version.
Frameworks
How each framework helps with this problem.
Primary — facts
SBI Model
Word one feedback message as a specific situation, an observable behavior, and a work impact, without motive or personality labels.
Alternative — live talk
COIN Model
Structure a feedback conversation as Context, Observation, Impact, and Next Steps so the talk stays factual and ends on a joint next move.
Example
Prepare (SBI):
- Situation: last Thursday's API handoff, due noon.
- Behavior: spec arrived Friday noon; no ping that it would slip.
- Impact: QA lost a day; Friday's test pass did not happen.
Live (COIN):
Connect: “I want a handoff time we can both trust. I'm not interested in a lecture.”
Observe: “Thursday noon was the date. The spec landed Friday, and I didn't see a note that it was moving.”
Impact: “QA lost a day, so we missed Friday's pass.”
Ask: “What got in the way?”
Suppose they say the upstream schema changed Wednesday and they hoped to absorb it. Next: “New handoff is Tuesday 10:00. If it moves, ping me before noon the day before — even if you're still working it. I'll ask data for a freeze window so you're not catching schema changes the night before.”
You could have said “you were late and it hurt QA.” The close above adds a date, a ping rule, and a blocker you can remove.
If they have no cause and this is a repeat, the next step is still a date and a ping rule. A second conversation about pattern can wait until the facts of *this* miss are shared. Do not jump to character in the first five minutes.
Mistakes
- Starting with a verdict on the person
- Mixing “Thursday,” the artifact, and “you’re unreliable” in the same breath
- Labels (“always,” “never,” “you don’t care”)
- Skipping impact so nobody feels bad
- Sending a long written verdict and calling it feedback
- Closing on a vibe that “we’re good” instead of a date or an explicit blocker
- Jumping to character or pattern in the first five minutes
Next step
Write the three SBI lines before you speak. Send the short note if the miss is small. Talk live and run COIN if other teams are blocked or this is a repeat. SBI and COIN have the full patterns if you want them before the meeting.
Apply this to your own context
Bring your situation into Advisor. It helps you choose a framework and work through the next step.