The draft arrived late again. You have a sentence ready about reliability, three examples in your head, and no idea how to begin without sounding furious.
Start by separating what you know from what you have concluded. Then prepare for more than the opening. A useful difficult conversation includes the other person's account, a feasible agreement and a later check on what changed.
The examples below are fictional. Adapt the facts and your authority to the actual situation.
Start with the gap, not the verdict
“You're unreliable” is a conclusion about a person. “The draft was due Tuesday and arrived Friday” is a claim you can check together. Even that needs context: was Tuesday actually agreed, and did the work change afterward?
The Center for Creative Leadership's Situation-Behavior-Impact framework and inquiry about intent distinguish observable behavior from assumptions about motives. Use the observation to open a discussion, not to prove you already understand the cause.
Before you book the conversation, write down:
| Check | In the late-report example |
|---|---|
| Observation, not interpretation | The report arrived Friday at 2pm; “doesn't care” is an interpretation. |
| Communicated expectation | The project note says Tuesday at noon. Did both people understand it? |
| Known impact | Review time fell from two days to one hour. |
| Uncertainty | Was an input late, or was another priority changed? |
| Authority | Who can freeze inputs, move the deadline or reduce scope? |
| Outcome needed | A workable handoff and an early risk signal for the next report. |
For managers, checking expectations and resources is part of the job. University of Iowa HR guidance recommends defining outcomes, providing examples and support, and checking understanding before judging performance.
The conversation from opening to agreement
Choose a private setting and enough time to hear an answer. Share the subject beforehand: “Can we spend 20 minutes on the report handoff and agree a better plan for next week?” Avoid disguising corrective feedback as an unexplained casual chat.
1. Open with one example and a question
We agreed the report would be ready Tuesday at noon. I received it Friday afternoon, so review was compressed to an hour. I'd like us to find a workable handoff for the next one. What happened from your side?Then listen. Do not stack your remaining examples on top of the first pause.
2. Let new information change the plan
The employee says: “Sales replaced the input file Tuesday morning. I thought you wanted the new numbers, so I rebuilt the report.”
I hadn't realized the input changed that morning. I didn't specify what to do after the cutoff; that's a gap in my instructions. We still needed an early signal that Tuesday was at risk. Let's agree both parts.The deadline was missed, but the explanation changes the remedy. Asking the employee to “be more reliable” would leave the conflicting instructions in place.
3. Make both sides' responsibilities concrete
I'll confirm the data cutoff with Sales by Thursday. Please flag any change that threatens the draft date as soon as you see it, with your revised estimate. I'll decide whether we use the original inputs or move the date. Does that give you what you need?A manager's next move may be to resolve priorities or obtain access. A peer cannot impose the same standard, but can propose a shared handoff: “Could we agree to flag changed inputs in the project channel before either of us reworks the report?”
If they get defensive
A reaction does not prove your feedback was correct. Check whether the evidence, timing or delivery needs correcting while keeping the practical issue visible.
Which part sounded personal? I want to discuss the two drafts, and I may be missing context. Let's check what we agreed and what changed.Let's check the original instructions. If I didn't make the expectation clear, I need to own that. We can set it explicitly for the next cycle.If the discussion becomes unproductive, agree a specific time to return and what each person will bring. “Let's pause and look at the input history tomorrow at 10” is more useful than “We'll talk later.” See responding to defensive feedback reactions for more next-turn options.
Write down the agreement
A short recap lets both people correct misunderstandings. Acas guidance on reviews and objectives recommends regular discussion, achievable objectives and shared records. Its management guidance is useful here; formal employment procedures depend on the employer and jurisdiction.
Employee action: Flag changed inputs and the estimated timeline impact.
Manager support: Confirm the cutoff and decide on post-cutoff changes.
Due date: Next draft Tuesday at noon, based on agreed inputs.
Review point: Ten minutes after the next handoff.
Still unresolved: Sales has not yet confirmed the cutoff.
Send this as “Here's my understanding; please correct anything I missed.” Do not write “we agreed” where the other person explicitly disagreed.
Following up when something changed—or didn't
At the check-in, compare the agreement with what happened:
You flagged the changed file on Monday, and we made the scope decision before you rebuilt it. That preserved the review window. Is there anything in this process that still needs adjusting?If the same problem continues, check whether each promised action happened, including your own. Establish whether the issue is understanding, capacity, support or failure to follow an achievable agreement. Repeated performance problems may need the organization's management process; another carefully worded opening is not the whole solution.
For a narrower task, use giving clear feedback, setting expectations or negotiating an infeasible deadline.
Try this today
Prepare one fact, one known impact, one unanswered question and one outcome you need. Read the opening aloud. Check it for neutral facts and a reasonable request—not whether it sounds sufficiently sharp. Leave room in your notes for the answer you have not heard yet.
