Leadership
Difficult feedback: prepare a useful conversation
Prepare difficult feedback with observable behaviour, fair questions and a clear next agreement. Use a practical worksheet without labelling the person.
A handover arrives late again. You spend the next morning repairing the plan, then postpone the conversation because you cannot find a way to raise it without sounding accusatory. By the time you speak, three separate incidents have become one judgement: “You are unreliable.”
Difficult feedback becomes more useful when you narrow it to a work behaviour, explain its consequences and agree what needs to happen next. You can prepare those elements. You cannot script the other person’s response or guarantee a comfortable conversation.
This guide helps you prepare feedback about everyday performance and collaboration. Serious misconduct, discrimination, harassment or a formal capability process require the appropriate organisational procedure and qualified support. An informal conversation should not substitute for those routes.
Decide what the conversation needs to achieve
Begin with an outcome you can reasonably discuss. “Make them care more” is a guess about motivation. “Agree when the handover is complete and how a delay is flagged” describes a work agreement.
Write one sentence: after this conversation, we need a shared understanding of the specific problem and a next action with an owner. If the issue is actually an unresolved priority conflict, feedback alone cannot repair it. The team may need a decision about scope, staffing or deadlines.
The leadership guide places feedback alongside clearer priorities and decision rights. A manager who repeatedly changes the deadline should examine that behaviour before criticising somebody else for missing it.
Choose a private setting with enough time for a reply. Describe the purpose when arranging it. A surprise audience or an ominous meeting title adds pressure without improving the evidence. For remote conversations, check that the person can speak privately and use a format that works for them.
Separate observation, interpretation and impact
Use a simple preparation table.
Swipe or use the arrow keys to see every column.
| Element | Useful preparation | What to avoid |
|---|---|---|
| Situation | Which meeting, delivery or message? | “This always happens” |
| Behaviour | What was said, sent, omitted or delayed? | A personality label |
| Impact | What work consequence can you substantiate? | Predicting everybody’s feelings |
| Interpretation | What explanation are you currently assuming? | Treating the assumption as a fact |
| Question | What do you need to understand? | A question with an accusation inside it |
The Center for Creative Leadership describes a situation–behaviour–impact approach and adds an inquiry into intention in its SBI and SBII guidance. It offers a structure for discussing an episode. It does not make your interpretation automatically correct or guarantee that the recipient will respond well.
For example, “The checklist was not attached to yesterday’s handover” is an observation. “You do not respect the team” is an interpretation. “The reviewer had to ask for the missing checks before starting” is a consequence you can verify. Keep these statements separate.
Also distinguish impact from intent. An unintended omission can still matter. A good intention does not remove the need to change a behaviour. Equally, a harmful outcome does not prove the person intended it.
Check the conditions around the behaviour
Before speaking, ask whether the expectation was clear and achievable. Was there an agreed checklist? Did the person have access to it? Did another manager assign urgent work? Were approvals available?
This check does not excuse every missed commitment. It helps you distinguish an individual action from a broken process. If the system makes the agreed behaviour impossible, repeating the instruction louder is unlikely to help.
Delegation and accountability explains how to make authority, resources and escalation routes explicit. The organisation psychology guide offers a broader way to examine recurring friction.
Check your own contribution too. You might have accepted an ambiguous update, postponed a decision or rewarded a last-minute rescue. Bring relevant responsibility into the conversation without turning it into a performance of self-blame. “I did not confirm who would review it; we need to fix that as well” is specific enough to act on.
A hypothetical handover conversation
Imagine a fictional product team. A designer, Maya, has sent a release handover without the accessibility checklist twice. The delivery lead, Daniel, wants to discuss it. These names and events are hypothetical.
Daniel prepares the two dated handovers, the agreed checklist and the consequences recorded by the reviewer. He does not assemble every frustration from the previous quarter.
His opening could be:
“Can we look at the handover sent on Tuesday? The accessibility checklist was missing, so the reviewer paused the review to request it. We had agreed it would be included. I want to understand what happened and agree a reliable way to complete the next handover.”
Maya explains that the checklist sits in a restricted folder and a colleague had previously attached it. Daniel now has a process problem as well as a responsibility question. He asks what access is needed and whether the ownership was clear.
If Maya had access and simply missed the check, the conversation would take a different route. The expected behaviour still needs an agreement. The purpose of asking is to discover relevant information, not to produce one preferred explanation.
Listen without surrendering the issue
After the opening, stop. Allow the person to answer before adding another incident or a proposed solution.
Useful questions include: “What was happening at that point?” “Which part of the expectation was unclear?” “What would make the agreed step workable?” Ask one at a time. An uninterrupted list feels like an examination.
A response may contain information, disagreement, emotion or all three. You can acknowledge it without agreeing with every interpretation. “I hear that the deadline changed. Let us check when that happened and how it affected the handover” keeps the conversation connected to evidence.
When the person disputes the facts, identify the precise difference. Check the relevant record together if appropriate. If an important fact remains unresolved, pause the judgement and investigate it. Do not force agreement just to complete the meeting.
This is not a technique for controlling feelings. If the conversation becomes too heated to continue productively, agree a pause and a time to return. A pause should have a clear continuation, otherwise avoidance becomes the outcome.
Build the next agreement together
An agreement needs more than “communicate better”. Describe the behaviour, conditions and review point.
For the hypothetical team, it might read: Maya owns the complete handover. Daniel arranges access to the checklist before the next release. If access fails, Maya flags it in the release channel before the agreed cut-off. The reviewer confirms whether the next handover contains the required checks.
This separates the actions each person controls. It also prevents a manager from demanding accountability while withholding the resource that makes the work possible.
The right support can vary by task. Someone completing an unfamiliar process may need a walkthrough; someone who already knows it may need a clearer priority. Situational leadership discusses that distinction without treating people as permanent types.
Do not agree an impossible deadline to create the appearance of resolution. If priorities conflict, route the decision to whoever has authority to choose between them.
Use this preparation worksheet
Complete the following before a consequential feedback conversation. It is an editorial tool, not a validated assessment.
- Purpose: which specific work outcome needs to change?
- Evidence: which one or two episodes support the concern?
- Expectation: where and when was the expected behaviour agreed?
- Impact: which consequences are observed, and which are assumed?
- Context: which dependencies, access issues or priority changes matter?
- Your contribution: what did you do or fail to clarify?
- Opening question: what explanation are you ready to hear?
- Possible agreement: what behaviour would be workable next time?
- Follow-up: when and how will you review it?
If you cannot complete the evidence and expectation fields, consider whether you need a clarification conversation before a performance conversation. You may be discussing an unspoken preference as though it were a broken commitment.
Why more feedback is not always better
Feedback can redirect attention towards the task, but it can also shift attention towards self-defence, status or a vague judgement of the person. Kluger and DeNisi discuss its variable effects in Feedback Interventions: Toward the Understanding of a Double-Edged Sword. Their work is a reason to examine feedback quality and context, rather than assume every intervention helps.
Avoid a mechanical praise–criticism–praise sequence if it obscures the message. Recognition can be sincere, but attaching unrelated praise to soften a difficult point may leave the expectation unclear.
Avoid feedback delivered publicly to demonstrate managerial firmness. The relevant audience is the person who can respond and act, unless a wider process genuinely requires participation.
Avoid claims about inner motives. A manager cannot establish laziness, fear or commitment from a delayed document. The same caution applies when interpreting customer behaviour in online consumer psychology: an observed action does not reveal a complete explanation.
Follow up on the agreement
After the conversation, send a short factual record where appropriate: the agreed action, any resources you will provide and the review point. Let the person correct a misunderstanding. Use the organisation’s policy for records and access; do not promise secrecy that you cannot maintain.
Review the agreed behaviour, not whether the person seemed grateful for the feedback. If the next handover is complete, acknowledge that specific change. If it is incomplete, examine what happened against the agreement and the relevant process.
Repeated failure may require a more formal route. Give clear notice of that route and follow organisational requirements. Avoid quietly turning routine notes into an undisclosed disciplinary process.
Finally, check the effect on the surrounding team. If a missing checklist affects several people, improve the shared workflow without publicly identifying the individual. The useful result is a clearer working practice that survives the next busy release.
If difficult feedback keeps returning to unclear responsibilities in your digital team, tell me about the working situation. We can examine the expectations, handovers and decisions that need to become clearer.
Apply this to your project
Tell me the decision you are facing, the constraints and what you have already tried.
Keep exploring
Decision-making under uncertainty: expose assumptions
Make a work decision with incomplete evidence. Separate facts from assumptions, compare options and define a review trigger with a practical record.
Delegation and accountability: clarify who decides
Delegate with a clear outcome, decision authority and review points, so accountability helps the work instead of creating another approval queue.
Leading AI change: help your team adapt
Lead AI change with clear roles, practical training and honest communication. Plan a bounded pilot, account for review work and define stop conditions.