Transformation Leadership

How Resilient Leaders Tackle the Toughest Challenges

Published on
December 11, 2024

The weekly team meeting ends on time. Every agenda item has been covered. On the way out, two colleagues exchange a look, and everyone understands it: the one subject that really mattered was never raised.

‍

Resilient leaders do not avoid that subject. They name it.

‍

Every team has its elephants in the room, the issues everyone sees and no one mentions. They can take many forms:

‍

  • a colleague whose performance has been slipping for months;
  • a conflict between two departments that nobody addresses;
  • a project that stopped moving long ago but still appears in every status report;
  • a decision taken at the top that no one on the ground believes in.

‍

Ignoring them does not make them disappear. They grow, they drain energy, and they slowly teach the team that some truths are not welcome.

‍

This article draws on an episode of The Resilient Leaders Pod with JR Briggs (episode 244, "Great Leaders Befriend Elephants"), on our field experience in healthcare organisations, and on research into how teams learn. It looks at why naming the elephant is so hard, what changes when leaders do it, and five practical steps to make it a habit rather than an act of heroism.

‍

The courage to name reality

‍

Leadership effectiveness starts with an honest description of what is actually happening. Max De Pree, author of Leadership Is an Art, put it this way: "The first responsibility of a leader is to define reality."

‍

That sentence sounds simple. In practice, it is one of the hardest parts of the job.

‍

Defining reality means saying out loud what the dashboard does not show. It means admitting that a plan is not working, that a team is exhausted, or that a behaviour everyone tolerates is hurting patients, colleagues or results.

‍

Courage in leadership is rarely spectacular. Most of the time, it is one honest sentence in a meeting where silence would have been easier.

‍

Why naming the elephant is so hard

‍

Naming an elephant feels risky, and leaders know it. They worry about:

‍

  • hurting someone they respect or depend on;
  • opening a conflict they are not sure they can resolve;
  • damaging the morale of a team that already feels fragile;
  • looking foolish, or being seen as the difficult one.

‍

Remember the Emperor's New Clothes. Everyone could see the emperor was naked. No one said a word until a child, with nothing to lose, stated the obvious.

‍

Organisations replay that story every day. Silence feels safer in the moment, but it is expensive over time. What people stop saying becomes information that leaders no longer receive. Decisions are made on a partial picture, workarounds become the norm, and small tensions turn into structural problems.

‍

In healthcare, the cost goes beyond the organisation. When a nurse hesitates to question a prescription, or a junior doctor does not report a near miss, the silence can reach the patient.

‍

Related topic: Are You Leading from the Inside Out? Here's Why You Should

‍

Naming to tame: what the research shows

‍

Think about how much lighter you feel after telling a trusted colleague what is really bothering you. The problem has not changed. Your relationship to it has.

‍

Neuroscience offers part of the explanation. In a functional MRI study published in Psychological Science in 2007, Matthew Lieberman and colleagues at UCLA showed emotional images to 30 participants. When participants put a word on the emotion they saw, the response of the amygdala, a brain region linked to emotional reactivity, decreased. Activity rose in the right ventrolateral prefrontal cortex, an area involved in regulating emotion.

‍

Putting feelings into words reduces their grip. The researchers call this affect labelling.

‍

The same logic applies to teams. A tension that stays unspoken keeps its full charge. Once it is named calmly and precisely, it becomes a problem the team can work on together.

‍

Take a project that has been stalled for months. As long as no one says it, every meeting ends with the same vague promise to "keep going". The day someone says "this project is stuck, and here is why", the conversation changes. People stop defending the plan and start fixing it.

‍

Psychological safety: the condition that makes honesty possible

‍

Naming the elephant is easier when people know they will not be punished for it. Amy Edmondson, professor at Harvard Business School, calls this team psychological safety: a shared belief that the team is safe for interpersonal risk-taking.

‍

In a study of 51 work teams in a manufacturing company, published in Administrative Science Quarterly in 1999, she found that psychological safety was associated with learning behaviour, such as asking for help, discussing errors and seeking feedback. That learning behaviour was in turn linked to team performance.

‍

Her earlier work in hospitals points in the same direction. In a 1996 study of eight inpatient units in one university hospital, the units with stronger nurse manager leadership and better working relationships reported more medication errors, not fewer. Edmondson's reading: these teams were probably not making more mistakes. They were more willing to talk about them.

‍

A team that reports more problems is not necessarily a weaker team. It may simply be the one where people still dare to speak.

‍

This is why leadership development cannot stop at individual skills. Resilient leaders build the conditions in which others can tell the truth.

‍

Five steps to name and befriend the elephant

‍

Knowing that naming matters is one thing. Doing it on a busy Tuesday, with a full agenda and a tense team, is another. These five steps help turn courage into a practice.

‍

1. Pause and look at your own fear first

‍

Before addressing the elephant, ask yourself one question: "What exactly am I afraid of?"

‍

Maybe you fear a confrontation. Maybe you fear losing a high performer, or being blamed for letting the situation drift. Writing these fears down helps separate the real risks from the imagined ones.

‍

Example: a manager notices that her most experienced team member has become dismissive in meetings, and that younger colleagues have stopped making suggestions. She fears losing his expertise. But by staying silent, she is already losing the rest of the team. Naming her own fear first lets her prepare a calm, factual conversation instead of postponing it for another month.

‍

2. Model vulnerability

‍

Teams copy what their leaders do far more than what they say. If you want difficult subjects to surface, show that it is safe by going first.

‍

Ask your team for honest feedback, including the last 5%: the part people usually keep to themselves because it is the hardest to say. When they share it, thank them sincerely, even when it stings.

‍

Example: at the start of a team meeting, name one area where you know you need to improve, then ask the team where else you could do better. The first honest answer you receive, and how you react to it, will tell the team whether the invitation was real.

‍

3. Recognise in public, address difficulties in private

‍

Most individual issues are best handled one to one. It avoids public embarrassment and gives the person room to respond without becoming defensive.

‍

Some elephants, however, belong to the whole team: a recurring conflict between two functions, unclear priorities, a habit everyone has adopted and no one likes. These need a collective conversation, with clear expectations and shared accountability.

‍

Example: if one person's behaviour is causing problems, start with a private conversation. If the team climate is deteriorating because several issues have gone unaddressed, it may be time for an open discussion with everyone involved.

‍

4. Make naming part of the routine

‍

Psychological safety is not built in a single workshop. It grows when honest conversations become ordinary.

‍

Example: set aside a regular slot, monthly or quarterly, where team members can bring up any unspoken tension or recurring friction. Structured formats help. At Bee'z, we use methods such as Key Issues and "Cards on the Table" to surface tensions in a respectful, organised way, so the conversation focuses on the situation rather than on people.

‍

The aim is for important subjects to reach the table before they turn into crises.

‍

5. Show where you are: the "You Are Here" map

‍

Remember the maps in shopping centres, with a big red dot saying "You Are Here"? They only help you reach your destination because they show you your starting point.

‍

Leadership works the same way. A team cannot move forward on a shared plan without a shared, honest view of where it stands today.

‍

Example: at your next team meeting, present a simple "reality map" of your main projects: what is on track, what is late and what is blocked, including the obstacles no one has named yet. That map becomes the starting point for dealing with the elephants standing in the way.

‍

Developing resilient leaders who dare to speak

‍

Resilience in leadership is often described as the ability to absorb pressure. That is only half of it. Resilient leaders also reduce the pressure that silence creates, by naming problems early, while they are still manageable.

‍

This capacity can be developed. Executive coaching, leadership development programmes and team sessions all help, provided they work on real situations rather than abstract principles. Leaders need to practise naming difficult realities with their own team, in their own context, and to receive honest feedback on how it lands.

‍

In healthcare organisations, where teams work under constant pressure and silence can affect patient safety, this is not a soft skill. It is part of what keeps care safe.

‍

‍

‍

Concluding thoughts

‍

Leading with courage means inviting the elephant to the table and asking what it has to teach you, rather than trying to chase it out of the room.

‍

A team that learns to name its elephants becomes more creative and more effective. It wastes less energy on what goes unsaid, and it learns faster from what goes wrong.

‍

Next time you feel the weight of an unspoken issue in a meeting, take a breath, find your courage and name it, calmly, precisely and without blame.

‍

Naming things helps tame them, and taming them is how they start to change.

‍

Which elephant has been sitting in your team meetings for too long?

‍

If your organisation wants to build a leadership culture where difficult subjects can be raised early, let's talk: https://www.beez-consulting.com/contact

‍

Frequently Asked Questions

‍

What is resilient leadership?

‍

Resilient leadership is the ability to stay clear and steady under pressure while keeping a team able to learn and adapt. It is not only about absorbing stress. Resilient leaders also reduce the pressure that silence creates, by naming difficult realities early, inviting honest feedback and turning tensions into problems the team can solve together before they become crises.

‍

What does "naming the elephant in the room" mean for a leader?

‍

It means saying out loud the issue everyone sees but no one mentions: an underperforming colleague, a conflict between departments, a stalled project or a decision nobody believes in. Naming it calmly and precisely, without blame, moves it from a hidden source of tension to a shared problem the team can actually work on.

‍

Why do leaders avoid difficult conversations?

‍

Most leaders avoid difficult conversations out of fear rather than indifference. They worry about hurting someone, opening a conflict they cannot resolve, damaging morale or looking foolish. In the moment, silence feels safer. Over time it is costly, because unspoken issues keep growing and leaders lose access to information their teams no longer share.

‍

What is psychological safety in a team?

‍

Psychological safety is a shared belief within a team that it is safe to take interpersonal risks, such as asking a question, admitting a mistake or challenging a decision. Amy Edmondson's 1999 study of 51 work teams found it was associated with learning behaviour, which in turn was linked to team performance.

‍

How can a leader build psychological safety?

‍

Leaders build psychological safety mainly through their own behaviour. They admit their own areas for improvement, ask for honest feedback and thank people who give it, even when it is uncomfortable. They react to bad news with curiosity rather than blame, and they create regular, structured moments where unspoken tensions can be raised safely.

‍

What is the difference between executive coaching and leadership development?

‍

Executive coaching is usually individual support for one leader, focused on their own situations, behaviours and goals. Leadership development programmes work with groups of leaders to build shared capabilities across an organisation. Both work best when they are grounded in real situations, such as practising difficult conversations with one's own team, rather than abstract principles.

‍

How does naming emotions help leaders under pressure?

‍

Putting a feeling into words reduces its intensity. In a 2007 functional MRI study published in Psychological Science, Matthew Lieberman and colleagues found that labelling emotions lowered the amygdala's response to negative images and increased activity in a prefrontal region involved in regulating emotion. For leaders, naming what they feel helps them think more clearly before acting.

‍

Why does psychological safety matter in healthcare?

‍

In healthcare, silence can reach the patient. When staff hesitate to question a prescription or report a near miss, risks go unaddressed. Amy Edmondson's 1996 study of eight hospital units found that better-led units reported more medication errors, probably because people felt able to speak about them, not because they made more mistakes.

‍

How do you raise a difficult issue with a high performer?

‍

Start by examining your own fear, often the fear of losing their expertise. Then hold a private, factual conversation that describes the specific behaviour and its effect on the team, without labelling the person. Make clear that their skills are valued and that the behaviour still needs to change, because the rest of the team is watching.

‍

Should difficult issues be addressed in private or with the whole team?

‍

Issues involving one person's behaviour are usually best addressed privately, which avoids public embarrassment and defensiveness. Issues that affect everyone, such as unclear priorities or a recurring conflict between functions, need a collective conversation. A useful rule is to recognise people in public and address individual difficulties in private.

Bee'z Consulting

Transformation starts
with
your people

Does one of these sound familiar?

A hospital or clinic that needs better performance, smoother patient pathways and teams that stay.
‍
A pharma, medtech or biotech company whose strategy gets lost on its way to the teams doing the work.

An organization in the middle of a transformation (merger, restructuring, new tools, AI) where middle managers carry the change without the means to lead it.

None of this is new. What makes the difference is how you tackle it: with the people who do the work, close to where it happens.

Latest articles

Stay informed with our field notes on transformation in healthcare and life sciences.
View all
A nurse manager pauses on a hospital stair landing, between a meeting room above and the ward below
Middle Management Activation
12 min read

In Swiss hospitals, everyone knows what to change. Nobody says who.

Change management in healthcare: the 2025-2026 reports list every lever. None says who translates the strategy in the units, or how to prepare them.

Read more
Ways of Working
10 min

Agile in Healthcare: Challenges, Solutions and Examples

Agile in healthcare works when teams, not tools, change. What agile really means for hospitals, why implementation stalls, and 6 practical steps.

Read more
A training catalogue entry where every field is unbookable, from the course to the registration.
Middle Management Activation
11 min

Training is in the catalogue. Development isn't.

Development isn't decided once a year. What a development conversation contains, why it so rarely happens, and what actually builds capability at work.

Read more