It's the third time. The draft was due Tuesday and it landed Friday again, and you've been telling yourself you'd say something for two weeks now.
You like them. You don't want to make it weird. So instead, you've been quietly absorbing the cost — re-reviewing under pressure, smoothing things over with the rest of the team, hoping the next one is different.
Avoiding the conversation is starting to hurt more than the conversation would. The longer you wait, the bigger it gets, and the bigger it gets, the harder it is to open the door without it sounding like a verdict.
The goal is not to win the moment. The goal is to make the gap visible, name what it costs, and agree what changes.
The mistake that makes hard conversations harder
People usually make one of three mistakes — sometimes all three.
- They wait too long. What could have been a Tuesday note becomes a quarter-end ambush.
- They soften the message until it's unclear. Three caveats, two reassurances, and the actual ask buried in the middle. The other person walks away thinking everything is fine.
- They make it about the person, not the behaviour. "You're unreliable" is a personality verdict. People defend their identity. It's their job.
Direct feedback that names a specific behaviour is consistently easier to act on than vague impressions — research on intent vs. impact recommends grounding feedback in what was observed, not what it implied about character. (source)
You're being difficult.Your attitude is a problem.This keeps happening and everyone is frustrated.
Each of those gives the other person something to fight rather than something to fix.
Start with the gap, not the verdict
A verdict tells someone who they are. A gap describes a specific moment.
- Verdict: "You are unreliable."
- Gap: "The draft was due Tuesday, and I received it Friday. The review window disappeared."
The verdict starts a debate about identity. The gap starts a conversation about a Tuesday. One of those is much easier to resolve.
When you describe a gap, you describe three things in plain language: what was expected, what happened instead, and why it matters.
We agreed the first draft would land on Tuesday so the team had two days to review.
It came in on Friday afternoon. The team reviewed it in an hour and we shipped without catching the numbers issue.
I want to talk about what needs to change so the next draft lands on the agreed date.You haven't called them anything. You've described one Tuesday, one Friday, and one consequence. There's nothing to defend — only something to fix.
The three-part structure
When you can't think clearly in the moment, fall back on three lines:
- Name the gap. What was expected vs. what happened.
- Explain the impact. What it cost — time, trust, risk, rework.
- Ask for the next step. A concrete, observable change.
That's the whole structure. It works for feedback, for resetting expectations, for raising a concern up the chain. It works because it keeps the conversation on observable behaviour and ends with ownership rather than blame.
I want to talk about the timeline for the last two drafts.
We agreed they would be ready by Tuesday. Both arrived on Friday, which meant the team had to review them under pressure.
What needs to change so the next draft is ready on the agreed date?You're not diagnosing their character. You're making the gap visible and asking for ownership. The question at the end matters — it hands the next move to them, which is where it belongs.
Reading this is the easy part. Saying it out loud, calmly, while a real person looks at you, is the part that takes reps. TalkCraft drills the openings — short scenarios, a coach note on every choice.
Scripts you can use
Five scripts for situations people put off for weeks. Each one uses the same shape: gap, impact, next step.
Giving feedback to a teammate
Can I flag something from yesterday's meeting?
When the client asked about the timeline, you jumped in before Priya finished her answer. The thread of the conversation broke and we ended up with two half-answers instead of one clear one.
Next time, can we agree that whoever opens the topic finishes the answer?You're a peer, so you don't have positional authority. What you do have is one specific moment and one concrete agreement to land on. That's enough.
Resetting expectations with a direct report
I want to reset on something. The expectation I've been carrying is that drafts land on Tuesday so the team has time to review properly.
The last two have come in on Friday. Both times we shipped under pressure and missed things.
From here, the standard is Tuesday. If something is going to slip, I need to hear from you on Monday — not a missed deadline on Tuesday. What gets in the way of that?You've named the standard, named the early-warning expectation, and asked them to surface the obstacle. That's a reset, not a reprimand.
Raising an issue with your manager
I'd like fifteen minutes on something — not urgent, but worth getting on the table.
The way the Q3 scope is currently set, I think we're going to miss either the deadline or the quality bar. I've laid out two options for what to cut, with trade-offs on each.
Can I walk you through them on Friday?You're not complaining and you're not asking them to solve it. You're showing up with the gap, the impact, and a structured next step. Managers respond to that very differently than they respond to "this is too much."
Setting a boundary without sounding controlling
A boundary describes what you will do — not what the other person has to do. The version that requires their compliance to work is a request. The version that works whether or not they cooperate is a boundary.
I'm not going to reply to Slack after 7pm — anything that comes in then I'll pick up the next morning.
If something is genuinely urgent, text me with "urgent" in the first line.You haven't told them when they're allowed to message. You've told them what you'll do. They keep their autonomy, and you keep your evening.
Following up when nothing changed
Two weeks ago we agreed drafts would land on Tuesday and that you'd flag risks on Monday if something was slipping.
This Tuesday's draft came in late again, and I didn't hear from you on Monday.
Help me understand what got in the way — and let's agree what we change so we're not having this same conversation in a fortnight.Follow-ups go wrong when they sound like punishment. This one quotes the agreement back, names the gap, and invites them to diagnose with you. The conversation is about the system that broke, not the person who broke it.
If they get defensive
Sometimes you do everything right and the person still goes defensive. That doesn't mean you got it wrong — it means you touched a real nerve. The job is to stay anchored: keep your tone calm, keep the content specific, and keep returning to the next step.
"Why are you bringing this up now?"
Honestly — I should have raised it earlier. That's on me.
I'm raising it now because the pattern is clear and I want to fix it before the next cycle. Can we agree what changes from here?You take the timing point, you don't relitigate it, and you re-anchor on the next step.
"Nobody told me this before."
You're right that I should have raised this earlier.
I want to be clear from here: the expectation is that we flag timeline risks before the deadline, not after it passes.
Can we agree on how you'll signal risk next time?You acknowledge the point without making the rest of the conversation about your delay. The expectation is now explicit, on the record, and agreed.
"You're making this personal."
I'm not — I'm talking about two specific drafts and what they cost the team.
This isn't about you as a person. It's about the timeline we agreed. Can we land on what changes for the next one?You separate the moment from the identity, out loud. Then you re-anchor on the request — not on whether you're being fair.
"I'm doing my best."
I believe that. I'm not asking you to work harder.
I'm asking what needs to change in how the work is set up so the next draft lands on time. What's getting in the way?"I'm doing my best" is often a request for reassurance, not a counter-argument. You give the reassurance, then move the conversation from effort to system.
Silence or shutdown
We don't have to solve it right now.
Can you sit with it and we'll come back to it tomorrow? The one thing I need by then is a plan for the next deadline.You give them space without giving up the conversation. The specific ask stays alive, so "I'll think about it" doesn't quietly become "we never spoke about this."
Try this today
Sixty seconds, before the conversation, before the meeting, before the message.
Write three lines:
The expectation was...
What happened instead was...
The impact was...
Then turn those into one calm opening sentence.
Read it out loud once. If it feels too sharp, it's probably about right — direct isn't harsh, vague is. If it feels vague, you're hedging. Cut a softener, not a specific.
That's the rep. The next rep is the conversation itself.
Practise difficult conversations in short, realistic drills — feedback, boundaries, negotiation, conflict. The first time you reach for the words shouldn't be in the live meeting.
If this is really about timelines, read how to push back on unreasonable deadlines. If the conversation is with your manager, read how to disagree with your manager professionally.