Skip to main content
Loading...
content

Giving Difficult Feedback

A manager practice page for addressing a specific work behavior: prepare accurate examples, explain the impact, listen to context, agree an observable change, and follow up.

Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Professional services · Technology and software · Healthcare administration · Manufacturing operations

Overview

Giving Difficult Feedback is a manager practice page for preparing and holding a focused conversation about a specific work behavior. Its fictional Northstar Services example follows a project coordinator whose handoff notes arrived after an agreed 3 p.m. cutoff twice, delaying the next team’s review. The page shows how to describe those checkable events and their work impact without labeling the employee, then invite their perspective.

The content moves from replacing judgment with an observable example to a five-step conversation sequence: prepare accurate examples, open privately, listen and clarify, agree a specific change, and set a follow-up point. A response section covers disagreement, new context, and a heated exchange. A worked dialogue demonstrates an early warning message as a practical adjustment, while the closing section recommends reviewing the agreement at the next regular check-in.

Use this page as a coaching aid when a manager needs to address a defined work expectation and can discuss the relevant examples accurately. Before adopting it, replace the fictional scenario with applicable expectations and link to an authoritative internal people-support resource if one is available. Do not use it as a form letter, an employee record, or a substitute for formal performance, conduct, grievance, or disciplinary procedures. Where the matter is sensitive or outside the manager’s remit, use the organization’s established process instead.

Standards & compliance context

  • Treat the page as a conversation aid, not as legal advice or a replacement for applicable employment policies and formal procedures.
  • Use accurate, relevant examples and distinguish observed behavior from assumptions to support a fair, fact-based discussion.
  • Refer sensitive employment matters or issues outside the manager’s role to the organization’s established people-support process.
  • Keep the page’s heading structure and visible text clear for readers using assistive technology, and check the published page against WCAG 2.1 AA accessibility practices.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Start with what happened and what needs to change

The fictional handoff scenario shows why feedback should focus on a specific behavior, its work impact, and the need to understand context.

  • A practical conversation guide for managers Fictional example: at Northstar Services, a project coordinator’s handoff notes arrived after the agreed 3 p.m. cutoff twice, delaying the next team’s review. The aim is not to label the person; it is to describe the behavior, explain its work impact, hear their view, and agree a workable change. Keep the discussion private and focused on examples you can describe accurately. Separate what you observed from what you assume, and make room for context you may not know.

Replace judgment with an observable example

This comparison makes the difference between a personal label and a specific, checkable description clear.

  • Describe an action and its effect rather than making a claim about someone’s character. Avoid a label “You’re careless with handoffs.” It judges the person rather than naming an action. It gives no example the other person can clarify. It does not say what needs to change. Name the behavior and impact “The last two handoff notes arrived after the 3 p.m. cutoff, so the review started the next morning.” It identifies two specific, checkable examples. It explains the impact on the next team’s review. It leaves room to discuss context and agree a change.

Prepare, talk, agree, and follow up

Use this ordered sequence to move from accurate preparation to a concrete agreement and review point.

  • A short sequence to keep the conversation specific and two-way Prepare the examples Write down the instances you can describe accurately, the agreed expectation, and the work impact. Check that you are not relying on hearsay or assumptions. Open with the purpose Meet privately. State the behavior and impact plainly, then explain that you want to understand what happened and agree what should happen next. Listen and clarify Pause. Ask for the other person’s view, listen without interrupting, and ask a neutral follow-up if you need to understand the sequence or constraints. Agree a specific change Describe the next observable action and when it is expected. In the example, agree that the next handoff is sent by 3 p.m., or that the manager is told early when that cutoff is at risk. Set a follow-up point Agree when you will check how the change is working. Ask what support or adjustment would help, and use the organization’s established people-support route if the matter needs additional guidance.

Respond to what you hear

These scenarios offer practical ways to handle disagreement, new information, or a conversation that becomes heated.

  • Keep the conversation curious and grounded in the example. If they disagree Compare what each of you observed. Ask, “What did you see on those two handoffs?” Check the dates and expectation before deciding on next steps. If new context emerges Ask what got in the way and listen before agreeing a change. A scheduling constraint may affect the plan, but the handoff still needs to be coordinated. If the conversation becomes heated Slow the pace and restate the shared purpose. If a useful discussion is not possible, pause and agree a suitable time to resume; use the established people-support route when appropriate.

Worked example: a short dialogue

The fictional exchange demonstrates how a manager can state the impact, listen, and agree a workable next action.

  • Illustrative exchange based on the fictional handoff scenario Manager: “I want to talk about the last two handoffs. Both notes arrived after the 3 p.m. cutoff, and the review started the next morning. I’d like to understand what happened and agree how we can keep the next handoff on track.” Coordinator: “I was covering an urgent request at the end of the day, and I did not realize the review team was waiting on my note.” Manager: “Thanks for explaining. When did you know the note might be late, and what would have helped you flag it sooner?” Coordinator: “I could have sent a brief message when the urgent request came in.” Manager: “Let’s agree that the next note is sent by 3 p.m. If it looks at risk, please flag that early so we can coordinate. We’ll check how that worked at our next regular check-in.” This is an illustrative practice dialogue, not a record of a real employee conversation. Apply the actual expectation and context when agreeing next steps.

Check whether the change is working

The follow-up prompt helps the manager and employee review the agreed action and decide what to do next.

  • Use the next regular check-in to review the agreement Ask: “What changed, what got in the way, and what support or adjustment would help?” Compare what happened with the agreed action and timing. Recognize what improved, clarify any remaining gap, and agree the next step. For sensitive employment matters or questions beyond your role, use your organization’s established people-support route rather than treating this practice guide as policy.

How to use this template

  1. Review the page and replace the fictional handoff scenario with the actual expectation, accurate examples, and work impact relevant to your organization.
  2. Before meeting, write down the instances you directly know, confirm the agreed expectation, and separate observed facts from assumptions or hearsay.
  3. Meet privately, state the behavior and impact plainly, and explain that you want to understand what happened and agree what should happen next.
  4. Pause to hear the employee’s account, ask neutral questions about the sequence or constraints, and check details if the examples are disputed.
  5. Agree an observable next action and timing, including how the employee should flag a likely delay or other obstacle early.
  6. Set a follow-up point, review what happened against the agreement, and use the organization’s established people-support route if further guidance is needed.

Best practices

  • Use specific examples you can verify, such as the two late handoffs in the sample, rather than relying on hearsay or broad impressions.
  • Describe the action and its work impact before asking for the employee’s perspective.
  • Hold the conversation privately and keep the opening focused on the stated work expectation.
  • Ask neutral questions about what happened and what got in the way, then listen without interrupting.
  • Agree a next action that another person could recognize, such as sending the note by 3 p.m. or flagging a risk early.
  • Name a follow-up point during the conversation so both people know when they will review the change.
  • If the employee disputes the example, check dates and expectations before deciding what to do next.
  • Pause a heated conversation when a useful discussion is not possible, and resume at a suitable time or use the established support route.

What this template typically catches

Issues teams running this template most often surface in practice:

A manager describes someone as careless instead of naming the specific behavior that needs to change.
The feedback cites no dates, examples, or agreed expectation the employee can clarify.
The discussion names a behavior but does not explain its effect on the work or another team.
The manager reaches a conclusion before hearing about a scheduling constraint or other relevant context.
The agreed improvement is too vague to check, such as asking someone to communicate better.
No follow-up point is set, so neither person knows when the change will be reviewed.
A sensitive or formal employment issue is handled as an informal coaching conversation instead of using the established process.

Common use cases

Project manager addressing late handoffs
A project manager uses the fictional 3 p.m. handoff example as a model, then prepares accurate dates and impact for the situation at hand. The conversation ends with a clear delivery expectation or an early warning action and a planned check-in.
Operations manager coaching a team lead
An operations manager can use the behavior-versus-label comparison to help a team lead prepare for a private discussion about a repeated process gap. The response guidance prompts the lead to check disputed details and consider constraints before agreeing next steps.
People manager practicing a difficult conversation
A manager can rehearse the opening and neutral follow-up questions using the worked dialogue, then adapt them to a real work expectation. The page keeps the conversation focused on observable actions, impact, context, and a review point.
Service delivery manager resolving a coordination delay
A service delivery manager can apply the sequence when a missed handoff affects another team’s review. The page helps identify an actionable change, such as notifying the next team early when a cutoff is at risk.

Frequently asked questions

What kinds of feedback conversations is this page designed for?

It supports private, manager-led conversations about a specific work behavior and its impact, such as late handoff notes. The example shows how to move from a judgment about a person to observable events and a clear next action. It is not a substitute for a formal performance, conduct, grievance, or disciplinary process.

Who should lead the conversation?

The manager responsible for discussing the work expectation should prepare and lead it. They should use examples they can describe accurately, explain the work impact, and invite the employee’s perspective. If the issue is beyond the manager’s role or involves a sensitive employment matter, they should use the organization’s established people-support route.

When should a manager follow up?

Agree a follow-up point with the employee during the conversation; the page’s example uses the next regular check-in. Match the timing to the agreed change and the work involved rather than applying a fixed cadence to every situation. At follow-up, compare what happened with the action and timing you agreed.

Does this page meet employment-law or HR requirements?

No single practice page can establish compliance across jurisdictions or replace an organization’s policy. Use the guide to support a clear, respectful conversation, then follow applicable workplace procedures and local requirements for formal or sensitive matters. Do not treat the sample dialogue as an approved script or record.

What if the employee disagrees with the example?

Compare what each person observed and check the dates, the expectation, and the sequence of events before deciding on next steps. Ask a neutral question about what they saw, and make room for context that may change the plan. Avoid turning disagreement into a judgment about character.

How can we customize the page for our organization?

Keep the sequence of preparing examples, opening privately, listening, agreeing a change, and following up. Replace the fictional Northstar Services handoff scenario with a clearly identified, work-relevant example and your organization’s actual expectations. Add a people-support destination only when you have an authoritative internal page to link.

Does the template connect to HR systems or record the conversation?

The supplied page is instructional content; it does not include a connected HR system, form, or conversation-recording workflow. Any system connection or recordkeeping process must be configured separately through your organization’s established tools and policies. Do not assume the example dialogue is an employee record.

How is this different from giving feedback ad hoc?

The page provides a repeatable sequence and a worked example, so managers can prepare evidence, explain impact, hear context, and agree a next step instead of improvising around labels. It also addresses disagreement, new context, and a heated conversation. Managers still need to use judgment and follow the organization’s procedures.

Go deeper on the topic

Related concepts
  • Change management is the structured discipline for moving people, processes, and organizations through transitions — new systems, new structures, new...
  • A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
  • DEI — diversity, equity, and inclusion — is three distinct disciplines often collapsed into one program. Diversity is who is in the organization; equity is...
  • Employee Net Promoter Score (eNPS) is a single-question engagement metric: "On a scale of 0–10, how likely are you to recommend this place as somewhere to...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Giving Difficult Feedback ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.