All resources

A practical guide

How to give constructive feedback at work

Constructive feedback explains what happened, why it mattered, and what needs to happen next. Describe an observable action, ask for the other person’s perspective, and agree on a specific change. Keep the discussion focused on work that can change, rather than a judgment about someone’s character.

On a small team, feedback often happens between meetings or after something goes wrong. The challenge is making it useful enough to act on without turning one moment into a verdict on the person.

How do you give feedback someone can act on?

The Center for Creative Leadership’s Situation–Behavior–Impact model offers a starting structure: identify the situation, describe the behavior, and explain its impact. In the conversation, also ask what was happening from the other person’s point of view.

  1. Choose a specific moment. “In yesterday’s planning meeting” is easier to discuss than “You always do this.”
  2. Describe what you observed. Name the action or words. Avoid guessing at motivation.
  3. Explain the consequence. Say how it affected the work or your own understanding. Do not claim to speak for everyone.
  4. Invite their perspective. Ask a real question and allow the answer to change your view.
  5. Agree on the next step. Decide what each of you will do and when to check whether it helped.

Constructive feedback examples

These examples are suggested wording for hypothetical situations, not customer stories or scripts to recite.

When someone interrupts a colleague

In the planning meeting, you started responding twice before Maya had finished explaining the proposal. I couldn’t tell whether we had understood the full idea before deciding. What was happening from your perspective? In the next discussion, can we let the presenter finish and then take questions?

This names a behavior and an impact without labeling someone as disrespectful. If the issue is urgent interruptions rather than ordinary questions, agree on a way to signal urgency.

When a deadline is missed without warning

We agreed the draft would be ready on Tuesday. I learned on Tuesday afternoon that it would arrive on Thursday, which left no time for the planned review. When did the deadline start looking unlikely? Let’s agree when to flag a risk and what support you need from me.

The deadline matters, but so does the cause. If your changing priorities contributed, include a commitment of your own.

When you want a helpful behavior to continue

Before the handover, you wrote down the open decisions and who owned each one. I could pick up the work without asking you to reconstruct the context. Please keep that part of the handover process.

Positive feedback is more useful when it explains what to repeat. “Great job” can be kind, but it does not identify the contribution.

Connect feedback over time without building a case against someone

Performance reviews and one-on-one notes can help you check whether a concern is new, recurring, or already improving. Look for examples that contradict your first impression as well as examples that support it.

Suppose a review mentioned late handovers, but recent notes show that several deadlines changed after work began. The useful conversation may concern how the team agrees on scope. Repeating the review’s conclusion without the newer context would miss that.

Team pulse surveys can add another perspective, but an anonymous response is not evidence about a named employee. Discuss the team-level issue without trying to identify its author.

Use your AI to make feedback more specific

Common Cadence connects performance reviews, pulse surveys, one-on-one notes, and Big Five personality insights with your own AI. You can bring those perspectives into a conversation about what to say, what you may be missing, and what action would fit the situation.

I need to discuss a missed handover. Using the relevant context available to you, separate observed events from assumptions. Draft a short opening that explains the impact without assigning intent. Give me two questions to understand what happened and a next step that includes my responsibility as manager. Point out conflicting or missing context.

Use the draft to prepare, then speak in your own voice. Personality information may suggest a question about communication preferences; it should not become an explanation for someone’s behavior without their input.

When should you give feedback?

Choose a time soon enough that the event is clear, with enough privacy and attention for a useful exchange. You do not need to wait for a formal review. If you are too frustrated to describe the event fairly, prepare first and arrange a time to talk.

What if the person disagrees?

Separate disagreement about the facts from disagreement about expectations. Correct an inaccurate account. If you agree on what happened but disagree on what should happen next, make the expectation explicit and explain why it matters. Write down the agreed action and revisit it in your next one-on-one.