Skip to main content

[Project Management] Nice Teams Lose. Kind Teams Win

There is a subtle, high‑leverage difference between “nice” and “kind” in project communication


Most project problems don’t start with bad requirements, unrealistic deadlines, or difficult stakeholders.

They start with politeness.

More specifically:

Teams choose nice over kind, and projects quietly drift off course.

In the modern work environment - global, asynchronous, fast - communication is no longer a soft skill. It’s the operating system that determines whether a project thrives or collapses.

And in that operating system, one distinction matters more than most people realize:

Nice makes people comfortable.
Kind makes people better.

I am that kind of person - that used to be nice, and has moved to being KIND. It’s a tough transition sometimes, if you don’t take it with the right mindset.

And I’ve seen that happening is many projects - so I want to take this topic through the lens of project delays, accountability, and the messy reality of human behavior on delivery teams. If that sounds familiar to you - read further on.


1. Nice vs. Kind: The Foundational Shift

Nice

Niceness is reactive.
It prioritizes harmony right now.
It’s the instinct to avoid tension, soften truth, or not “rock the boat.”

Niceness sounds like:

  • “It’s fine, we’ll manage.”

  • “No worries, we’ll figure it out.”

  • “Let’s just keep it positive.”

The problem?
Projects die in the space between what’s true and what’s spoken.

Kind

Kindness is generative.
It prioritizes long‑term growth, clarity, and mutual respect.

Kindness sounds like:

  • “We’re behind by three days. Let’s realign the plan.”

  • “There’s a pattern here. Can we talk about what’s causing it?”

  • “I want you to succeed, so I need to be honest with you.”

Kindness requires courage, discipline, and clarity - three things more valuable to a project than momentary comfort.

Niceness protects feelings.
Kindness protects the relationship.
And the project.


2. Niceness Quietly Sabotages Projects

Niceness hides reality.

Teams tiptoe around delays to avoid disappointing stakeholders.
Tasks slip without escalation.
Risks remain “internal” until they explode externally.

Niceness creates surprises - the worst enemy of trust.

Niceness avoids boundaries.

The nice PM or team lead says yes too quickly, takes on too much, or absorbs dysfunction instead of addressing it.

This creates burnout, resentment, and unclear expectations.

Niceness enables harmful behavior.

When someone interrupts, misses deadlines, or creates friction, niceness tiptoes around it:

“It’s probably nothing.”
“Maybe they’re having a bad week.”
“I don’t want to cause drama.”

Meanwhile the behavior becomes the culture.

Niceness fuels dysfunction because it avoids friction - the very force required for growth.



3. Kindness: The Ultimate Project Management Meta‑Skill

Kindness, in a project context, is not warm and fuzzy.

Kindness is precision.

Kindness is honest data delivered in a human way.

Kindness is feedback that helps, not hurts.

Kindness does three things consistently:

1. Reduces Ambiguity

Clarity is kindness.
Ambiguity is cruelty.

The kind communicator says the real thing early, simply, and specifically.

2. Builds Trust Through Predictability

People trust what is consistent.
Kind communicators create stable expectations - even in uncertainty.

3. Supports Growth Without Shame

Kindness faces reality without attacking identity.

Instead of:
“You’re always late with deliverables.”
Kindness says:
“We’ve slipped three times this month - let’s look at what’s blocking you.”

High‑performing teams grow because someone dares to tell the truth early.


4. How does Nice vs. Kind look like in Real‑World Scenarios?

A. Communicating a Delay

Nice:
“We might be a bit behind, but let’s see how it goes.”

Kind:
“We’re four days behind. Here are two recovery options. Which one works for you?”

Niceness hides information.
Kindness frames information with solutions.


B. Addressing Unproductive Behavior

Nice:
“No worries, it wasn’t a big deal.”

Kind:
“When the deadline was missed, it created rework for the team. How can we prevent this next sprint?”

Niceness avoids confrontation.
Kindness creates accountability without blame.


C. Saying No to Extra Work

Nice:
“We’ll try to squeeze that in.”

Kind:
“If we add this, here are the trade-offs. What should we deprioritize?”

Niceness overpromises.
Kindness negotiates reality.


D. Handling Chronic Late Deliverables

Nice:
“Let’s see if next week is better.”

Kind:
“I’m noticing a pattern - are the estimates off, or is the workload too high? Let’s adjust together.”

Niceness waits.
Kindness intervenes.


5. The Psychology Behind Nice vs. Kind

Dan Koe often talks about “identity loops”- patterns of behavior reinforced by the stories we tell ourselves.

In project work, these loops manifest like this:

The Nice Identity Loop

“I want to avoid conflict”
→ Avoids direct communication
→ Issues grow
→ Stress increases
→ Avoids more conflict

The Kind Identity Loop

“I want what’s best for the team and the delivery”
→ Communicates truth with care
→ Builds trust
→ Issues get addressed early
→ Communication becomes easier

Kindness rewires team behavior at the identity level.


6. What Communication Templates can You Use for Kindness?

Template 1: Honest Delay Communication

“Here’s the current status: we’re X days behind.
Here’s the impact.
Here are the recommended options.
Let’s choose the best path forward today.”

Template 2: Behavioral Feedback

“I noticed X behavior in Y situation, and it had Z impact.
Can we talk about what caused it and how we can improve it?”

Template 3: Boundary Setting

“I want to support this request, but here’s what it displaces.
Which priority should shift?”

These are small scripts with big leverage.


7. Ready to Build a Culture of Kindness (Without Becoming Harsh)?

  1. State facts, not feelings.

  2. Be early, not perfect.

  3. Describe impact, not intention.

  4. Offer choices, not ultimatums.

  5. Follow up - the real magic is in consistency.

Kindness is a muscle.
It grows through repetition.


Nice teams work in silence until something breaks.

Kind teams surface issues early and solve them together.

Nice teams stay comfortable but stagnant.
Kind teams grow - even when it hurts a little.

Nice feels good temporarily.
Kind builds trust indefinitely.

If you are ready to make the shift, but need some help - reach out to me.

Comments

Popular posts from this blog

Getting PMP certified

I've got a lot of friends asking me about how to get certified. Each time, I had to remember how many hours of experience one had to have, and how many hours of learning, and then which where the links that were most useful for me, as well as all the books and software I have ever used. In terms of specific requirements for getting certified, the best resource will always be pmi.org, with a direct link to the requirements: PMI site - Obtaining the Credential . The site lists a credential overview, and then there (currently) 5 handbooks for the 5 available certifications. There is also a page with how to prepare for the exam, from an administrative point of view. If you are new to project management, then you will have to go with the CAPM certification. Then, the rest of certifications are for more and more experienced PMs. I only know well about the PMP certification, as it's the one I've got. First step is to ensure that you meet the elgibility requirements. At the t...

[Goal driven] A technique that has (almost) nothing to do with tomatoes

I know a lot of theory about time management, techniques, ways of organizing yourself and so. And I am sharing my knowledge with others as well. But the most rewarding part comes from actually applying these techniques myself. For example – using the Pomodoro technique has given me the joy of achieving significant progress in just a small amount of time. Imagine a bright red, glossy tomato-shaped kitchen timer sitting on a clean wooden desk. Its rounded surface gleams under soft daylight, with a small green stem on top, mimicking the look of a real pomodoro. Around its circumference, bold white numbers mark the minutes, with a simple arrow indicator showing the current countdown. The timer’s dial is currently set to 25 minutes, signifying the start of a focused work interval. Nearby, a notebook and pen suggest readiness for productivity, while the timer’s classic wind-up mechanism adds a tactile, satisfying element to the scene – a perfect embodiment of the Pomodoro technique in ...

[Management lessons] When the Best Plans Fail: Lessons from a troubled launch

A few months ago, my team was gearing up to launch a new automation tool for case assignment - a project that is key for the future, and also were we spent so much energy into. We spent weeks identifying scenarios, testing in a dev environment, and reflecting on potential issues. We wrote crystal-clear documentation and worked with a rockstar team of developers, testers, and communicators. We thought we had every base covered. But when launch day arrived, chaos ensued. The tool hit snags that never showed up in testing - edge cases we hadn’t anticipated. Worse, some team members seemed blindsided by the changes, despite our efforts to keep everyone in the loop. It was a classic “complex failure,” as Amy C. Edmondson describes in her book Right Kind of Wrong: The Science of Failing Well . Complex failures, Edmondson explains, aren’t the result of one person’s mistake or a single oversight. They happen in intricate systems where multiple factors - technology, human behavior, and unexpe...
I am a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to amazon.com.