Last month, I spent two days with one of the most talented leadership teams I’ve worked with all year. This company is crushing it, rapid growth, powerful mission, brilliant people doing work that genuinely matters. And one of their most talented people was practically invisible.
She’s the kind of leader who, when she speaks, everyone should stop and listen. Her insights were gold. But she spoke maybe three times a day. The rest of the time? Silent observer.
On day two, I pulled her aside before we started and offered some direct leadership feedback: “What you’re bringing here is incredibly valuable. The team needs more of it. Would you be willing to share more today?” She laughed and said, “Not the first time I’ve been told that.”
For the rest of that day, she did. The whole dynamic shifted.
Here’s what I learned, again: being nice is killing our teams. We confuse kindness with niceness constantly. Nice protects our comfort. Kind helps people get better. If you want to build a team that actually performs at the level you know they’re capable of, you need to learn the difference between kind leadership feedback and nice avoidance masquerading as politeness.
The Nice vs. Kind Distinction That Changes Everything
Why “Nice” Feedback Fails Senior Teams
Let’s start with the uncomfortable truth: most of us aren’t actually giving feedback at all. We’re managing our own discomfort.
According to a performance management survey spanning 53 countries, only 5% of employees believe their managers provide candid, critical feedback (HBR, 2025). Think about that number. Ninety-five percent of people aren’t getting what they need to improve. Meanwhile, 95% of managers are frustrated with their own feedback systems. Everyone knows it’s not working. But we keep being nice instead of kind because kind feels harder in the moment.
The science explains why this pattern persists. Research from Leadium examining feedback neuroscience reveals why nice feedback fails: “When receiving critical feedback, the brain’s threat detection system—specifically the amygdala—activates defensive responses that can cause individuals to become defensive and dismiss valuable input” (Leadium, 2024). This explains why even well-intentioned feedback that tries to “soften the blow” often gets dismissed entirely.
The SCARF model shows feedback threatens five hardwired domains—Status, Certainty, Autonomy, Relatedness, and Fairness—creating brain patterns similar to physical pain. When we’re being nice, we’re trying to reduce this pain. When we’re being kind, we’re helping people move through it toward growth.
And here’s the kicker for senior leaders specifically. McKinsey research documents a particularly troubling pattern: “As leaders ascend organizational hierarchies, they receive progressively less constructive criticism—subordinates don’t want to offend the boss and may believe constructive suggestions are unwelcome” (McKinsey). The higher you climb, the nicer people get with you. And the more isolated you become from feedback that would actually help you improve.
This is why kind feedback matters most at senior levels—because nice feedback has already stopped flowing entirely.
The Three Markers of Truly Kind Feedback
So what separates kind feedback from nice feedback? Three things.
First, kind feedback serves the recipient, not the giver. Nice feedback makes you feel better about being a “good” leader. Kind feedback makes them better at their job. If you’re primarily worried about how you’ll feel after the conversation, you’re being nice. If you’re focused on what they need to hear to improve, you’re being kind.
Second, kind feedback addresses real behavior with real consequences. Nice feedback speaks in generalities: “Maybe consider being more assertive.” Kind feedback gets specific: “In yesterday’s meeting, when the CFO challenged your assumptions, you went silent. The team needed you to defend the strategy. Your silence made everyone doubt whether we’re on the right path.”
Third, kind feedback creates action, not just awareness. Nice feedback leaves people nodding thoughtfully but unchanged. Kind feedback equips them with a clear next step. “Here’s what I’d like to see you try in next week’s meeting…”
Research from Harvard Business School reveals a critical insight supporting this distinction: “Negative feedback rarely leads to improvement unless delivered within a framework that reduces defensiveness” (HBS, 2025). In their study, employees receiving critical peer feedback simply adjusted their roles to work with people who would give them better reviews. They didn’t get better—they got strategic about avoiding criticism.
This is the judo move we need.
The Judo Move: From “To Them” to “For Them”
Stop thinking about feedback as something we deliver TO someone. Start thinking about it as a framework FOR helping them succeed despite their defensiveness.
The shift is subtle but powerful. When I approached that quiet brilliant leader on day two, I wasn’t thinking, “I need to tell her she’s too quiet.” I was thinking, “She has something valuable the team needs. How can I help her give it?”
That reframe changes everything. It’s not about fixing her. It’s about unlocking what’s already there for the team’s benefit.
This is where we bridge from nice to kind. Nice would have been pulling her aside privately after the session and gently suggesting she could maybe speak up a bit more if she felt comfortable. Kind was saying directly: “What you’re bringing is incredibly valuable. The team needs more of it.”
One protects my comfort and hers. The other serves the team.
The “Because of You, We” Framework
Why Traditional Feedback Creates Defensiveness
Here’s where most leadership feedback frameworks fall apart. They focus on the “you.”
“You need to improve this.” “You should try that.” “You’re not meeting expectations in this area.”
Every sentence starts with an accusation, even when we don’t mean it that way. And the brain responds accordingly.
Research from the Journal of Experimental Social Psychology involving 2,751 participants reveals the power of pronouns in feedback reception: “You pronouns signal aggressiveness and reduce perceived receptiveness, while we pronouns foster closeness and inclusivity” (JESP, 2024). Messages using “you” in feedback contexts were consistently perceived as less receptive and less persuasive.
This isn’t about semantic games—it’s about brain response. “You need to improve this” activates threat detection. “We could strengthen this if…” activates collaboration.
The “because of you, we” framework leverages this psychological reality.
How Collective Language Removes Shame
Let me show you how this works in practice. After each person on that leadership team shared what they appreciated about how others showed up, I added one observation about where a shift would make us even better as a team.
For the quiet brilliant woman, I said it publicly: “I would love if you’d speak up more. Your perspective is incredibly valuable. If you’d bring more of that to the team, we’ll all be better.”
That’s the frame that matters: Because of you, we.
Not “you need to fix this.” Not “here’s what’s wrong with you.” Instead: “When you do this thing, we become better. And when you could adjust this other thing, we’d become even better.”
Research from MIT and Stanford shows that how leaders frame challenges matters more than resources or expertise. In a study of hospital teams implementing new technology, “the difference between success and failure wasn’t determined by management support, resources, or expertise—it was determined by how project leaders framed the challenge” (MIT/Stanford). Teams whose leaders framed implementation as collective learning outperformed teams given the same challenge framed as individual execution.
The “because of you, we” framework applies this principle to feedback: frame the improvement as team benefit, not individual failure.
It removes the shame. It removes the ego hit. It makes feedback about collective improvement, not individual criticism.
When Individual Accountability Meets Team Benefit
Now, some of you are thinking: “But dusty, what about individual accountability? Doesn’t this let people off the hook?”
No. It actually increases accountability.
According to research published in PLOS ONE, team-level feedback proves more effective than individual feedback for interdependent work: “Team-level performance feedback promotes team reflection processes and attention to team goals, proving especially successful when team tasks are interdependent” (PLOS ONE, 2024).
This doesn’t mean we avoid individual conversations. It means we frame individual improvement in team context. “Because of you, we” maintains individual accountability while activating team-level motivation.
Think about your team right now. Who needs to hear something they’re not hearing? What conversation are you avoiding because it feels uncomfortable?
Here’s what I know: That discomfort you’re feeling? It’s costing your team progress. It’s keeping someone stuck. It’s preventing the “we” from becoming what it could be.
You’re not being nice by staying quiet. You’re being selfish. You’re protecting your own comfort at the expense of their growth.
The Group Affirmation Exercise (With a Twist)
Step 1: Model the Behavior First
At the end of our two days together, I ran an exercise I love. Everyone goes around the room and shares what they appreciated about how each person showed up. What they valued. What made the room better.
But here’s the twist I added just for me. I told them not to copy this part yet. After each affirmation, I shared one observation about where a shift would make us even better as a team.
Why did I tell them not to copy it? Because I needed to model the behavior before asking them to do it. Leaders go first. Always.
This is servant leadership in action. I’m not asking them to be vulnerable in a way I’m unwilling to be. I’m showing them what kind feedback looks like wrapped in genuine appreciation.
Step 2: Appreciation Before Observation
The sequence matters more than most leaders realize.
According to neuroscience research, positive feedback triggers dopamine release in the brain’s reward system, encoding the behavior as worth repeating, while constructive feedback activates error detection in the anterior cingulate cortex (Neuropsychology, 2024). This is why step one of the conversation guide starts with genuine appreciation—you’re priming the brain’s reward system before activating its error detection.
When you deliver “because of you, we” observation after appreciation, you’re sequencing the neuroscience in the right order: reward first, then course correction.
For that quiet brilliant leader, the sequence was: 1. “What you’re bringing here is incredibly valuable.” (Dopamine activation) 2. “The team needs more of it.” (Social motivation) 3. “If you’d bring more of that to the team, we’ll all be better.” (Collective benefit frame)
She left that conversation thinking about how to help the team, not defending herself against criticism.
Step 3: Public Reinforcement of Growth Areas
Now here’s where it gets interesting. Some feedback works publicly. Some doesn’t.
According to a 2025 healthcare education study, context determines whether feedback should be public or private. Students preferred private feedback for subjective competencies like attitude and patient care, but public feedback for objective technical skills (Healthcare Education, 2025).
The distinction matters: technical feedback feels less threatening publicly because it’s observable and measurable. Developmental feedback about leadership presence, communication style, or team dynamics? That requires privacy to protect dignity while pushing growth.
But here’s the nuance: once you’ve had the private conversation, public reinforcement accelerates behavior change.
Research analyzing group-based behavior change reveals why witnessing feedback matters: “Public feedback operates through multiple mechanisms: social facilitation, social influence, and group problem-solving” (Integrative Framework, 2019).
When the quiet brilliant person on your team hears public affirmation plus growth-focused observation, three things happen. First, she internalizes the feedback more deeply because it’s witnessed. Second, other team members learn what good looks like. Third, the group implicitly agrees this feedback culture is safe.
Annual reviews in conference rooms can’t create these dynamics.
Why This Works When Annual Reviews Don’t
Let’s talk about why annual performance reviews are mostly theater.
Gallup research makes the case for continuous feedback overwhelming: employees receiving weekly feedback are 2.7x more engaged, 3.2x more motivated, and 5.2x more likely to find feedback meaningful (Gallup, 2024). Meanwhile, only 14% of employees say annual reviews motivate improvement.
The shift is already happening—82% of companies used annual reviews in 2016, but just 54% by 2019. Organizations making the switch report 40% higher engagement and 26% better performance.
The “because of you, we” framework works because it’s designed for continuous deployment, not once-a-year conversations.
That quiet brilliant leader didn’t need an annual review six months from now documenting that she was too quiet in Q1. She needed someone to say in the moment: “What you just said was exactly what we needed. More of that, please.”
Real-time. Specific. Framed as team benefit.
That’s how behavior changes.
Practical Application Framework
The Four-Step Conversation Guide
Alright, let’s make this actionable. Here’s exactly how to have a kind feedback conversation using the “because of you, we” framework.
Step 1: Start with genuine appreciation (30 seconds) Name something specific they did well. Real examples. Real impact. This isn’t buttering them up—it’s activating their reward system so they can hear what comes next.
Example: “Sarah, the way you walked the team through that financial model yesterday was exceptional. You made something complex feel accessible.”
Step 2: Name the observation (45 seconds) Describe what you observed without judgment. Stick to behavior, not character. Use “I observed…” or “What I noticed…” language.
Example: “What I noticed is that when the CFO pushed back on your assumptions, you went quiet for the rest of the meeting. The questions you were asking earlier stopped.”
Step 3: Frame the “because of you, we” connection (60 seconds) Explain how their behavior change would benefit the team. Make it collective, not individual. Show them how they matter to the “we.”
Example: “Here’s why that matters. When you go quiet after pushback, the team interprets that as doubt. They need you to defend the strategy or explain your thinking. Because of your expertise, we make better decisions. When you stay engaged, we’re all more confident in the direction.”
Step 4: Create the action step (30 seconds) Give them something concrete to try. Make it small enough to implement immediately. Make it specific enough to measure.
Example: “Next time you get pushback in a meeting, here’s what I’d like to see you try: pause for three seconds, then respond with either your reasoning or a clarifying question. Don’t go silent. Stay in the conversation.”
Total conversation time: less than three minutes. Total impact: potentially career-changing.
Research analyzing 131 feedback intervention studies reveals a sobering truth: “More than one-third of interventions were associated with worse performance” (Meta-Analysis, 2009). Bad feedback doesn’t just fail to help—it actively harms.
This is why the four-step conversation guide matters. Without structure, even well-intentioned feedback triggers defensiveness that makes performance decline. With structure, you reduce that risk by 60%+.
The stakes are higher than most leaders realize.
30-Day Implementation Timeline
Week 1: Practice privately Pick one person on your team. Block 15 minutes on your calendar. Write out your four-step conversation following the guide above. Say it out loud to yourself. Refine it. Then have the conversation.
Week 2: Expand to direct reports Have one “because of you, we” conversation with each direct report. Focus on developmental feedback, not performance management. You’re building the muscle, not fixing problems.
Week 3: Introduce to leadership team Share the framework with your leadership team. Run the group affirmation exercise. Model it first. Let them see what kind feedback looks like.
Week 4: Make it cultural Build “because of you, we” language into team meetings. When someone does something valuable, name it publicly with the collective frame: “Because of what you just did, we’re better positioned to…”
According to research in the Journal of Public Economics studying 500+ teams, private feedback boosts effort more than public recognition when deployed separately—but combining them dilutes effectiveness (JPE, 2021). This is why the timeline separates private conversations (weeks 1-2) from public culture building (weeks 3-4). You’re not mixing messages. You’re sequencing them strategically.
Common Pitfalls to Avoid
Pitfall 1: Fake appreciation If your appreciation isn’t genuine, they’ll smell it. Don’t compliment something you don’t actually value just to soften the feedback. Start with what you genuinely appreciate or don’t start at all.
Pitfall 2: “But” transitions “Sarah, you did great work on that model, BUT…” The word “but” erases everything before it. Use “and” instead. “You did great work on that model, AND here’s where we could be even stronger…”
Pitfall 3: Vague observations “You need to be more assertive” tells them nothing. “When the CFO challenged your assumptions and you went silent, the team needed you to stay engaged”—that tells them everything.
Pitfall 4: Individual frame instead of collective “You need to improve your presentation skills” activates defensiveness. “When you present with more confidence, the team buys in faster and we move from discussion to decision”—that activates motivation.
Pitfall 5: No action step If you end the conversation without a concrete next action, nothing changes. Always close with: “Here’s what I’d like to see you try…”
Success Metrics
How do you know if this is working? Look for these indicators:
In the moment: – The person asks clarifying questions instead of defending – They repeat back the “because of you, we” connection in their own words – They leave the conversation talking about next steps, not what happened
Over 30 days: – You see the specific behavior change you requested – They bring you feedback about their progress unprompted – Other team members start using “because of you, we” language
Over 90 days: – Team performance metrics improve (decision speed, execution quality, innovation) – Psychological safety scores increase (you can measure this with pulse surveys) – People stop avoiding difficult conversations with each other
Research from the Ferrazzi Greenlight Research Institute analyzing 3,000 teams over 20 years found that 72% of team members avoid conflict—and this avoidance “represents one of the most erosive behaviors in high-performing teams and is corrosive to shareholder value” (Ferrazzi, 2024). Teams that embrace candor show significantly higher innovation and lower risk.
The kind vs. nice distinction isn’t soft skills philosophy. It’s hard business strategy. Your niceness is costing your organization measurable performance.
The Teams That Win Tell Each Other the Truth
According to Google’s Project Aristotle research examining hundreds of teams, psychological safety is the number one predictor of team effectiveness (Google). But here’s what most leaders miss: psychological safety doesn’t mean avoiding difficult conversations. It means “creating environments where people feel safe to take interpersonal risks like speaking up, challenging ideas, admitting errors, and seeking feedback.”
You don’t build psychological safety by being nice. You build it by being consistently kind—saying what people need to hear in ways that help them grow.
That quiet brilliant person on your team? She left that two-day session contributing at a completely different level. Not because I was harsh with her. Because I was kind enough to tell her what she needed to hear.
The teams that win are the ones where people tell each other the truth wrapped in genuine care. Not nice. Kind.
Think about your team right now. Who needs to hear something they’re not hearing? What conversation are you avoiding because it feels uncomfortable?
That discomfort you’re feeling? It’s costing your team progress. It’s keeping someone stuck. It’s preventing the “we” from becoming what it could be.
Ready to start having these conversations? Take 15 minutes today and answer these three questions about one person on your team:
1. What do I genuinely appreciate about how they show up? (Be specific. Real examples.)
2. What have I observed that, if adjusted, would make our team better?
3. How can I frame #2 as “because of you, we” instead of “you need to”?
Then have the conversation. Start with appreciation. Be direct about the observation. Frame it as collective benefit.
You’ll know you did it right if they leave thinking about how to help the team, not defending themselves.
What’s one conversation you’ve been avoiding that would help someone get better?
If you’re ready to elevate your leadership and make a lasting impact, schedule a complimentary clarity call with our Founder and CEO, Dusty Holcomb. Gain tailored strategies, unlock new perspectives, and refine your leadership approach with a trusted guide who has helped countless leaders excel.
Frequently Asked Questions
Start by writing it out first. Seriously. Take five minutes before the conversation and write down your “because of you, we” statement. Say it out loud. Refine it. The first few times will feel awkward because you’re learning new language patterns. That’s normal.
After 5-10 conversations, it becomes natural. You’ll find yourself thinking in “because of you, we” frames automatically. The key is not to wing it at first. Prepare. Practice. Then deploy.
Also, remember this: authenticity isn’t about being spontaneous. Authenticity is about meaning what you say. If you genuinely believe their behavior change will help the team, the framework is authentic regardless of how much you prepared.
First, check your tone and framing. Are you actually using “because of you, we” language or are you still anchored in “you need to”? Sometimes we think we’re using the framework but we’re not.
Second, acknowledge the defensiveness directly. “I notice you’re pushing back pretty hard on this. Help me understand what’s going on.” Then listen. Really listen. Often defensiveness reveals something important you’re missing about the situation.
Third, separate the conversation into two parts. “I can see this is landing in a way I didn’t intend. Let’s pause here. I want to come back to this when we’ve both had time to think about it.” Then schedule part two for 24-48 hours later. Time creates space for reflection.
Finally, remember that defensiveness isn’t failure. It’s information. The person cares enough about the topic to defend their position. That’s actually a positive sign if you can work through it.
Default to private for developmental feedback. Public for reinforcement after private conversation has happened.
Here’s the decision framework: Is the feedback about objective, observable behavior that’s already known to the team? Public might work. Is the feedback about subjective leadership presence, emotional intelligence, or blind spots they don’t know they have? Always private first.
The group affirmation exercise I described works because I’m doing public reinforcement of themes that have already been discussed privately. I’m not surprising anyone with critical feedback in front of their peers. That destroys psychological safety instantly.
The exception: real-time coaching during live situations. If someone is facilitating a meeting and missing something important, a quick sidebar whisper or immediate redirect is appropriate. But extended developmental conversations? Private first, public reinforcement second.
The feedback sandwich (positive-negative-positive) tries to hide criticism between compliments. The “because of you, we” framework does something completely different—it reframes the entire conversation as collective benefit rather than individual criticism.
Feedback sandwich: “You did great work on this report [positive]. But you missed the deadline and that caused problems [negative]. Overall though, nice job [positive].”
“Because of you, we” framework: “You did great work on this report—the analysis was exceptional [genuine appreciation]. What I noticed is the deadline got missed, and that pushed back our client presentation by two days [observation]. Here’s why that matters: when you deliver on time, we maintain credibility with clients and the whole team stays aligned to schedule [collective benefit]. Next time, if you’re going to miss a deadline, flag it 48 hours in advance so we can adjust. That keeps the team synchronized [action step].”
See the difference? One tries to soften criticism. The other frames improvement as service to the team. Completely different psychology.
Use “What I observed…” or “My perception is…” language. Own that it’s your perspective, not absolute truth.
Example: “Sarah, what I observed in yesterday’s meeting is that when the CFO challenged your assumptions, you went quiet. That’s my perception from where I was sitting. Help me understand what was happening from your perspective.”
Then listen. Maybe she wasn’t silent—maybe she was processing. Maybe she had good reasons for not responding in the moment. Your observation might be incomplete.
The beautiful thing about the “because of you, we” framework is it creates space for dialogue. You’re not declaring truth from on high. You’re sharing perception and inviting response.
If your observation turns out to be wrong, that’s valuable information. “Thanks for clarifying. From your perspective, you were giving the CFO space to fully explain his position before responding. That makes sense. Here’s what would help me and potentially others: when you’re doing that, maybe signal it. ‘Let me make sure I understand your full position before I respond.’ That way we know you’re engaged, not checked out.”
Absolutely works for peer feedback. In fact, it might work better for peers because the power dynamic doesn’t complicate the collective benefit frame.
When you’re giving peer feedback, the “because of you, we” connection is even clearer. You’re literally on the same team at the same level. “When you do X, our team benefits. When you adjust Y, we’re even stronger together.”
The structure stays the same: – Genuine appreciation – Observation – “Because of you, we” connection – Action step
The only adjustment is tone. With direct reports, you can be slightly more directive on the action step. With peers, frame it as invitation: “What if you tried…” instead of “Here’s what I’d like to see…”
Some of the most powerful feedback I’ve ever received came from peers using this framework. They had no positional authority over me, which made the collective benefit frame feel even more genuine.
Weekly minimum for your direct reports. Not formal sit-down conversations—just real-time “because of you, we” observations as you work together.
“Hey, the way you handled that client call just now was perfect. Because of how you reframed their concern, we kept the relationship strong and moved forward. More of that.”
That’s kind feedback. Takes 20 seconds. Massive impact.
For developmental conversations using the full four-step guide, aim for monthly per person at minimum. Some people need more frequent coaching, some need less. Use your judgment.
But here’s the key: make “because of you, we” language constant, not episodic. Build it into how you talk about work every single day. When someone does something that helps the team, name it in real-time with the collective frame.
The Gallup research is clear: weekly feedback creates 5.2x more meaningful engagement than annual feedback. That doesn’t mean weekly formal reviews. It means weekly recognition of how individual contributions create collective benefit.
Start small. Pick one person. One “because of you, we” observation per week. See what happens. Then expand from there.
