Why “Being Nice” Isn’t Leadership

A lot of managers I talk to are proud of being nice. They don't raise their voice, they say yes when people ask for things, and they rarely deliver bad news. Their teams like them. And a surprising number of those teams are stuck.

This post was prompted by a Wall Street Journal piece I read on the subject, and it got me thinking about the ways "nice" quietly fails the people it's meant to protect. My view is that the fix isn't being colder. It's being clearer.

"It's fine" isn't feedback

Managers who avoid uncomfortable feedback usually believe they're protecting morale. What the team hears is different. Silence reads as indifference, and a lack of clarity chips away at trust, because people can tell when something isn't fine and nobody will say so.

If you're afraid to tell someone where they're falling short, that's a clarity problem wearing a kindness costume, and they'll pay for it later, usually at review time when it's too late to fix. A nicer approach is to say what needs to change while it's still small, then help them change it. That pairing of a clear bar with real help is what I mean when I talk about setting higher expectations and supporting them relentlessly.

Saying yes to everything isn't generous

The nice boss says yes to every initiative, every request, every meeting invite that lands on the team. It feels helpful. It produces chaos.

A team pulled in ten directions isn't productive, no matter how hard it works. Leaders who protect their team's time and energy are the ones who create room for work that actually matters, and enforcing those boundaries is your job, not theirs. The same goes for your own calendar. You can't protect anyone's focus if you've never learned how to stay accessible without burning out.

Avoiding conflict doesn't make it go away

Conflict on a team is going to happen. Avoiding it is the optional part.

The better approach is to step into hard conversations with empathy and a clear point of view. Handled well, those conversations are often where people grow the most. That doesn't mean taking over or dictating every answer. There's a real skill in coaching someone through a problem without micromanaging it, and it's worth learning, because the alternative is a team that works around its problems instead of solving them.

Being liked is the easy part

Being liked doesn't take much. Being respected takes some nerve, especially when you're giving hard feedback, making a call people won't love, or holding the standard when everyone would be more comfortable lowering it.

Leadership isn't a popularity contest. You're responsible for the people on your team and for the customers they serve. You can care a great deal about your people and still disappoint them sometimes. In fact, if you never disappoint anyone, I'd question whether you're making any real decisions.

So what does the balance look like?

None of this is an argument for the old top-down style. The leaders I'd want to work for aren't barking orders from the top of the org chart. They set ambitious expectations, coach with empathy, and show up the same way every week. Kindness is part of it. It just can't be the whole thing.

That's the core of servant leadership in a high-growth company, which people often mistake for being soft. Serving your team means telling them the truth early, removing what's in their way, and caring enough to challenge them.

Your team doesn't need you to sugarcoat things. They need you to raise the bar and then help them clear it.

If you're trying to find that balance between support and standards on your own team, I'm happy to talk it through.