The Constructive Feedback Script
Deliver hard feedback with observable facts, shared-knowledge framing, and one clear leave-with action
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 95%
A repeatable script for giving performance feedback that keeps the conversation neutral and forward-moving instead of judgmental or venting. It anchors on what you have heard or observed (not accusations), reminds the person you both already know the standard, and ends with an explicit action to leave the conversation with. The goal is feedback that is easy for you to give and easy for them to hear.
Origin
Developed by executive coach Alisa Cohn from her work with C-suite and startup leaders; the observable-facts principle echoes the Nonviolent Communication framework, which Cohn and the host both reference.
Core principles
- 01Feedback exists to help the person improve, not to hurt them or to let you vent
- 02Lead with observable facts and evidence, not judgments or feelings
- 03Stay even-keeled and matter-of-fact so it reads as routine, not 'my manager hates me'
- 04Build a reservoir of specific positive feedback first so criticism lands through a trusting lens
- 05Every hard conversation should end with a clear, agreed action
How to run it
- 1
Get your mindset and evidence right first
Before speaking, confirm your reason is to help them improve, not to vent. Ask yourself 'what's my evidence that this is happening?' and gather the observable facts.
Pro tip If your real motive is to vent or express yourself, wait until you can transform your reasoning before having the conversation.
- 2
Open low-key and name the topic
Start small so it doesn't feel like a huge deal: 'I wanted to have a conversation with you about some things I've been hearing from your peers about the way you're interacting together.'
Pro tip Deliberately keep your tone light — signal 'it's Tuesday, we're going to figure this out,' not confrontation.
- 3
State observable facts, not judgments
Frame with 'what I'm hearing from them is...' or 'what I've observed is...' rather than 'here's what you did wrong.' Sourcing to multiple peers or to observation depersonalizes it.
Pro tip Tie the standard to a reason: 'when we all work together we can execute; when we don't, we can't' — this makes the expectation objective.
- 4
Use the 'we both know' bridge
Say 'now we both know that the most important way you can be successful here is...' This positions the person as smart enough to already see the issue, rather than being lectured.
- 5
Close with the one thing to leave with
End with an explicit call to action: 'the most important thing is that we leave this discussion knowing how you're going to make sure you keep your peers and your team in the loop.'
Pro tip Make it your own each time — use a formula for structure but never recite it identically; vary wording so it feels human.
- 6
If they get defensive, pause
Deploy the defensiveness tool: 'let's just pause for a second — I'm feeling the energy has changed and I can see you're getting a little heated. I have no intention of upsetting you; I just want to help you in your career. We can continue now or take a few moments.'
Pro tip Match the pause language to the person — 'this is really upsetting you' or 'the temperature between us just changed' can land better than 'you're getting emotional.'
Watch out Do not react to their reaction with 'no, you're wrong' — that puts you both into a fight, which is never cool for you as a leader.
In the wild
A division leader kept avoiding feedback with an underperforming older report because 'she's just going to cry.' Cohn wrote him a script and worked it out; he finally had the conversation. She did cry and went home early.
→ The next day the report thanked him, saying she wished someone had told her 15 years earlier because she could have had a different career.
For a report whose documents lacked structure and conclusions, Cohn scripts: 'what I've observed is they can often be not as structured as I'd like and they lack a conclusion... look at these three or four examples of folks doing them really well and model your writing on theirs... the level of your writing reflects the level of your thinking.'
→ Feedback framed as observable fact plus a concrete model and a resonant 'why' makes it actionable rather than a personal attack.
Common mistakes
Giving feedback to vent rather than to help
If your underlying motive is to express frustration or vent, the feedback becomes an unloading rather than a neutral, helpful exchange — identify that motive and hold off until you can reframe your reasoning.
Only ever showing up with criticism
If you never give specific positive feedback, every conversation becomes 'we need to talk about a problem,' so people brace and hear 'my manager hates me' instead of 'my manager wants to help me.'
Is it for you?
Best for
Managers and founders who dread performance conversations and default to avoidance or over-softening
Not ideal for
Feelings-based issues where there is no clean observable data — those are harder and need a different, more exploratory approach
From the transcript
“what's my evidence that this is happening”
“observable facts you know the idea that this is not a judgment”
“now we both know that the most important way you can be successful here and also achieve your goals”
“let's just pause for a second”
“what I've observed is that they can often be not as”
“the level of your writing really reflects the level of your thinking”
“I wish someone had told me that 15 years ago”
From the episode
Scripts for difficult conversations: Giving hard feedback, navigating defensiveness, the three questions you should end every meeting with, more
Alisa Cohn (executive coach)