In brief. Kind leadership is not about being nice or lowering the bar. It means keeping high standards in a team where anyone can report a mistake without fear of being humiliated. Research links this “psychological safety” to team learning and performance. In an IT department it is also a security control: an error reported early costs far less than one that stays hidden. Kindness becomes a weakness only when it replaces clarity, decisions and follow-through.
Kind leadership: what are we actually talking about?
As of 20/11/2026. “Kindness” splits executives. Some see it as plain decency; others as an open door to complacency. The two camps rarely mean the same thing.
Kind leadership, as we practise it at Beneficis, fits in one sentence: demanding about the work, respectful of the people. The point is not to lower expectations but to make sure problems surface quickly, disagreements are voiced and mistakes become lessons. It is a way of organising work, and it shows in results.
So is it a strength or a weakness? It is a strength when it rests on clear goals, rules that hold and honest feedback. It turns into a weakness when it becomes an excuse not to decide. This article draws on French labour law, academic research and public frameworks, then sets out a practical approach for an executive team or a CIO.
What the law and the research say
A legal duty, not a perk
In France, Article L4121-1 of the Labour Code requires employers to take the measures needed to ensure workers’ safety and protect their physical and mental health. Those measures cover prevention of occupational risks, information and training, and an appropriate organisation and resources, adapted as circumstances change. How people are managed is part of that organisation.
France’s occupational health institute, INRS, groups psychosocial risk factors into six families: work intensity and hours, emotional demands, lack of autonomy, poor working relationships, value conflicts and job insecurity. Relationships with management, attention to employee well-being and lack of social support (help and recognition from colleagues and managers) are explicitly listed.
The health effects are documented. In a press release updated in January 2025, INRS presents its epidemiological review of more than 800 studies. Among its examples: high psychological demand is associated with twice the risk of burnout, and lack of social support with an excess risk of low back pain of more than 40%.
Psychological safety drives learning
In 1999, Harvard researcher Amy Edmondson published in Administrative Science Quarterly a study of 51 work teams in a manufacturing company. She defines team psychological safety as “a shared belief that the team is safe for interpersonal risk taking”. In practice: daring to ask a question, admit an error or challenge a manager. Her finding: psychological safety is associated with team learning behaviour, which in turn links to performance.
Crucially, Edmondson states that psychological safety is not the same as group cohesiveness, nor a careless sense of permissiveness. It is confidence that the team will not embarrass, reject or punish someone for speaking up.
Google reached a similar conclusion with Project Aristotle, which studied 180 teams. Of the five dynamics it identified (psychological safety, dependability, structure and clarity, meaning, impact), psychological safety comes first. How the team works together matters more than who is on it.
Managers are under strain too
Gallup’s State of the Global Workplace 2026 reports that global employee engagement fell to 20% in 2025, and manager engagement to 22%, down from 27% in 2024 and 31% in 2022. Asking managers to be kind without supporting them simply adds to their load.
In IT, kind leadership is a security control
In an IT department, leadership quality has a very concrete consequence: how fast an error or incident gets reported. A sysadmin who removed the wrong firewall rule, a developer who pushed an access key to a repository, an assistant who clicked a malicious link: the first minutes count. If people fear blame or ridicule, they hesitate, try to fix it alone, or stay silent.
The UK National Cyber Security Centre is blunt in its phishing guidance: blaming users for clicking doesn’t work, and users who fear reprisals will not report mistakes promptly, if at all. It advises against a punishment culture and suggests measuring how many people report a phishing email, not only how many click.
Google’s reliability engineers formalised the same idea in the blameless postmortem: after an incident, causes are analysed without indicting any individual or team, assuming everyone acted in good faith with the information they had. The rationale is practical: where fingers are pointed, issues stop surfacing.
The DORA research programme, which studies software delivery teams, uses sociologist Ron Westrum’s typology. In a “generative” culture, failure leads to inquiry rather than scapegoating, and messengers are trained rather than punished. DORA states that such a high-trust culture predicts software delivery performance and organisational performance in technology.
For a mid-sized company, the takeaway is simple: kindness is not a soft extra alongside cybersecurity. It shapes incident detection, the quality of lessons learned and the team’s ability to improve.
When kindness becomes a weakness
Critics of kind leadership are not always wrong. They often point to real drifts, seen in IT teams of every size.
- Complacency. Weak work goes unchallenged to avoid upsetting anyone. The person does not grow, and colleagues quietly compensate.
- Avoiding decisions. Seeking consensus, a manager postpones a call between two projects or two people. The resulting ambiguity creates more tension than a clear, explained decision.
- Rules that bend. Security rules, change procedures or deadlines are negotiable for some and not others. Perceived unfairness erodes trust faster than a strict rule applied to all.
- The sponge manager. Absorbing pressure from leadership, users and suppliers to shield the team, until burnout. Gallup’s manager figures show this is not hypothetical.
- Kindness for show. Gentle words in meetings, but an unsustainable workload, poorly organised on-call duty and no recognition.
In each case the problem is not too much kindness but too little clarity or standards.
Kind and demanding: practices that work
Here is how we see it, situation by situation, with the two drifts to avoid each time: one too hard, one too soft.
- Production incident. Neither hunting for a culprit nor skipping the analysis: a blameless review with tracked actions.
- Phishing click. Neither sanction or mockery nor silence: thank the person for reporting, explain, strengthen technical controls.
- Weak work. Neither public criticism nor saying nothing: factual feedback in private, a clear expectation, an offer of help.
- Technical disagreement. Neither deciding without listening nor waiting forever for consensus: hear every option, decide, explain the decision.
- Overload. Neither “just hold on” nor accepting everything: prioritise with leadership and say no to what can wait.
Three principles stand out. Clarity is a form of respect: known goals, priorities and rules prevent much friction. Honest feedback is a service: early, private, factual, with an offer of help. Leaders go first: a manager who admits their own mistakes gives the team permission to do the same.
These issues come up often in IT leadership assignments: an interim CIO has to stabilise operations, hold the executive team’s priorities and rebuild the confidence of a sometimes tired team. Standards and kindness move forward together or not at all.
Where to start
No need for a big programme. A few common-sense habits often change the climate of a team:
- Take time to listen to each person, one to one: what works, what weighs on them.
- Say clearly what matters: a few priorities everyone knows, and what can wait.
- Thank whoever reports a mistake, then look for what made it possible rather than who made it.
- Lead by example: admit your own mistakes and apply the same rules to everyone.
And if you manage the team yourself, keep some time for yourself: nobody supports a team for long when running on empty.
An IT team under strain? A leader leaving, overload, incidents that no longer get reported, friction between teams: an outside perspective often helps restore clarity without breaking trust.
Frequently asked questions
Is kind leadership compatible with crisis management?
Yes, as long as you separate the phases. During a crisis, steering is directive: clear roles, fast decisions, short messages. Kindness happens before (training, trust) and after (blameless review, recovery time).
Should we stop sanctioning mistakes?
Distinguish honest errors, which should be reported and analysed without blame, from repeated negligence or deliberate rule-breaking, which remain management and, where relevant, disciplinary matters. A blameless review does not remove accountability: it avoids making one person the scapegoat for an organisational problem.
How can I tell whether my team feels safe?
A few simple signs: are incidents reported by the team or discovered by users? Do meetings surface open disagreement? Do newcomers ask questions? A short anonymous survey twice a year lets you track the trend.
Written with the help of AI tools, then reviewed, fact-checked and approved by the founder of Beneficis, who takes editorial responsibility for it.
Sources
- Article L4121-1 of the French Labour Code – General principles of prevention, OPPBTP (PreventionBTP), sheet updated 29 September 2022
- Preventing psychosocial risks – Risk factors (in French), INRS, updated 9 November 2021
- Psychosocial risks at work and effects on employee health (in French), INRS, press release, updated 14 January 2025
- Psychological Safety and Learning Behavior in Work Teams, Amy Edmondson, Administrative Science Quarterly, vol. 44, no. 2, June 1999
- Understand team effectiveness (Project Aristotle), Google re:Work, published 2015, accessed 20 November 2026
- Global Employee Engagement Continues Decline (State of the Global Workplace 2026), Gallup, 7 April 2026
- Phishing attacks: defending your organisation, UK National Cyber Security Centre, reviewed 13 February 2024
- Postmortem Culture: Learning from Failure (Site Reliability Engineering, ch. 15), Google / O’Reilly, 2017
- Generative organizational culture, DORA (Google Cloud), accessed 20 November 2026




