Kind, Not Nice
Nice gets you along; kind says the uncomfortable thing that needs saying.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 80%
Inside the relationship-skill domain, Goleman draws a distinction most people collapse. Being nice means doing whatever will help you get along, and he says plainly it's not actually that helpful. Being kind might mean bringing up that one thing that needs to be said even though it's uncomfortable in the moment. His marker of a good team is precisely this: high-performing teams have a social contract with each other that lets them do that. And emotionally intelligent people do it naturally — it isn't an act of will for them. The distinction sits on top of empathic concern: you say the hard thing because you want what's good for the other person, which is exactly what separates it from criticism.
Origin
Goleman raises it while listing the competencies of the fourth EQ domain — persuasion, inspiration, teamwork, conflict resolution — as an aside on what 'good team player' actually means. He ties it directly to the research showing the competencies that make people outstanding performers in the workplace.
Core principles
- 01Being nice means doing whatever will help you get along — and it isn't actually that helpful.
- 02Being kind might mean bringing up the one thing that needs to be said even though it's uncomfortable in the moment.
- 03High-performing teams have a social contract that permits this with each other.
- 04Emotionally intelligent people do it naturally, not as an act of courage.
- 05Candor without empathic concern is just criticism — the concern is what makes it kind.
How to run it
- 1
Separate nice from kind
Define nice as doing whatever will help you get along. Define kind as bringing up the one thing that needs to be said even when it's uncomfortable in the moment. Notice which one you default to.
- 2
Ask what needs to be said
In any team situation, identify the one thing that needs saying but isn't being said. That's the kind move, and it's the one nobody makes by accident.
Pro tip Ground it in empathic concern — you're saying it because you want their good, which is what makes it land as kindness rather than attack.
- 3
Build the social contract
High-performing teams have an explicit shared agreement that they can say these things to each other. Establish the norm before you need it.
Watch out Without the contract in place, the first uncomfortable truth reads as an attack and the norm never forms.
In the wild
Goleman describes good teams as having a social contract with each other where saying the unpleasant necessary thing is permitted — and notes that emotionally intelligent people do it naturally.
→ He classes it among the competencies that research shows make people outstanding performers in the workplace.
Common mistakes
Mistaking niceness for a virtue
Nice is optimized for your own comfort in the relationship, not for the other person's good. Goleman is direct: it's not actually that helpful.
Being blunt without concern
The kind version rests on empathic concern — wanting what's good for the person. Strip that out and the same words are just criticism with a candor label on them.
Is it for you?
Best for
Team leads and members building the candor norm on a team that currently avoids friction.
Not ideal for
Groups with no established trust — the social contract has to exist before the candor lands as kindness.
From the transcript
“there's a difference between being nice and being kind i think being nice just means do whatever will help you get along and it's not…”
“being kind might mean bringing up that one thing that needs to be said even though it's uncomfortable in the moment”
“good teams high-performing teams have that social contract with each other they can do that with each other and people who are mostly intelligent will…”
From the episode
Daniel Goleman: Level Up Your Emotional Intelligence
Daniel Goleman