Most teams underestimate one basic human need: to feel that we matter.
When this need is neglected, people do not become neutral. They become defensive, withdrawn, performative, or cynical.
When it is respected, teams become calmer, clearer, and easier to operate.
This is not a call for constant praise. I am suspicious of teams that use positivity to avoid hard standards. But I am equally suspicious of teams that confuse emotional bluntness with seriousness.
People do better work when they can tell that their effort is seen and their judgment has a place in the room.
Importance is not ego inflation
Giving people a feeling of importance is not empty praise.
It is acknowledging three things:
- their effort is seen,
- their judgment has weight,
- their growth is worth investing in.
This creates dignity without creating entitlement.
The distinction matters. Ego inflation says, “You are special, so standards should bend around you.” Dignity says, “Your work matters, so the standard is worth helping you meet.”
Those two produce very different teams.
Where teams get it wrong
Common anti-patterns:
- feedback only appears when someone fails,
- contributions are invisible unless they are dramatic,
- critique is specific, appreciation is vague.
This combination trains people to optimize for image instead of substance.
I have seen this most clearly around operational work. The person who prevents incidents by cleaning up a risky deploy path may receive less attention than the person who heroically fixes an outage. The engineer who keeps a migration boring can look less impressive than the engineer who rescues a broken one.
If a team only notices drama, people learn to perform drama.
A practical feedback pattern
I try to use this sequence in reviews and incident retros:
- Name the effort — what hard thing was attempted?
- Name the value — what outcome did it enable?
- Name the gap — what must improve next?
- Name the support — what help is available?
That keeps standards high without humiliating people.
For example:
- “You kept the rollback path clear during a messy change.”
- “That protected the team from turning a deploy issue into a data issue.”
- “The gap is that the verification steps were still too dependent on you.”
- “Let’s turn those checks into a short runbook before the next migration.”
That feedback does not pretend everything was perfect. It also does not make the person defend their worth before they can hear the improvement.
Why this matters for reliability
Systems are operated by humans.
If humans feel disposable, they stop surfacing risk early. If they stop surfacing risk early, incidents become expensive.
Respect is not separate from reliability. It is upstream of it.
The reliability connection is practical:
- People report uncertainty earlier when it is safe to be incomplete.
- They ask for review sooner when review is not treated as weakness.
- They admit a bad assumption faster when correction does not become humiliation.
- They write down hazards when the culture rewards prevention, not only rescue.
This is why kindness in incident response is not softness. It preserves signal quality.
A simple rule
Criticize decisions precisely.
Protect dignity consistently.
That balance builds teams that can handle truth without collapsing trust.
The goal is not to make everyone feel important all the time. The goal is to build a room where people can do important work without turning every correction into a threat.