Leadership Coaching Case Study: Team Ownership

A lot of capable leaders aren’t overwhelmed because their team is difficult. They’re overwhelmed because nothing moves without them.

This case study shows how leadership coaching helped one NHS director shift from being the team’s problem-solver to building more ownership, confidence and thinking capacity across her team.

The leader and the challenge

I worked with a senior NHS director who was highly capable, well respected and liked by her team of 34. She was clear, analytical, organised and known for getting things done.

On paper, things were working. The team was delivering, people trusted her judgement, and she cared deeply about doing a good job. But behind the scenes, too much was coming back to her.

She would sit down to focus on her own work and, before long, someone would appear needing a decision, an answer or reassurance. She would help because she knew the answer, deadlines mattered, and in the moment it felt quicker to solve the problem herself than slow down and support someone else to think it through.

But “quicker” had become the trap. By the end of the day, she had often answered everyone else’s questions, solved multiple small issues and carried decisions that should not all have been hers. The planning, forecasting, succession thinking and strategic work that needed her attention were pushed back, squeezed in later or left waiting.

What concerned her most was not just the workload. It was the dependency. She wanted her team to take more ownership and initiative. She wanted them to come with ideas, options and recommendations, not just problems.

As we explored the situation, it became clear that several things were happening at once. Some of the issue was about real knowledge gaps. Some team members were not yet seeing the wider picture, the risks, the interdependencies or what a good plan actually needed to include. But another part of the pattern was her own leadership style.

Her strengths — pace, clarity, high standards and experience — were also feeding the dependency. When people came to her with problems, she naturally moved into solving, advising or directing. Even when she thought she was being less directive, she was often still giving the answer in a softer form.

What we explored in coaching

The coaching began by slowing the pattern down. Rather than treating it as a simple problem of “the team need to take more initiative”, we looked at what was actually happening in the day-to-day interactions.

When did people come to her? What did they bring? What did she do in response? What made it hard for her not to step in? What was genuinely urgent, and what had become habitual? Which issues reflected confidence, which reflected knowledge gaps, and which were being created by unclear processes or expectations?

This gave us a clearer picture of the dependency loop she had become caught in, and where her own leadership habits were unintentionally reinforcing it. We explored this with care rather than blame. Her pace, clarity and high standards were real strengths, especially in a pressured NHS environment. But when overused, those same strengths could lead her to rescue too quickly, direct too often, or do the thinking on behalf of others.

We also explored standards, feedback and praise. Her standards were high, which was a strength, but she needed to communicate those standards in a way that developed confidence rather than created more caution. That meant being clearer about what good looked like, what was already working, what needed to improve and what was “good enough” in different situations.

This was not about lowering standards. It was about making standards more usable for the team. If she wanted people to bring better thinking, she needed to help them understand what good thinking looked like, notice when they were moving in the right direction, and give feedback that developed capability rather than simply pointing out what was missing.

What we practised

A key part of the coaching was introducing the difference between directive and non-directive communication. This became an important part of the work, but it was more subtle in practice than it first sounded.

It is relatively easy to understand the idea of being less directive. It is much harder to spot, in the middle of a real conversation, that you are still directing.

That is why workshopping specific conversations was so useful. We took real examples from her week and slowed them down. What had the team member asked? What had she said? What was she trying to achieve? How might it have landed? Where was she genuinely inviting thinking, and where was she still steering the person towards her own answer?

In some examples, she would suggest a response that sounded collaborative, such as “May I suggest…”, “Perhaps you could try…” or “If it were me…”. But when we unpacked it, she could see that the answer was still coming from her. The sentence was gentler, but the dynamic was the same.

So we practised different ways of responding. Instead of moving straight to advice, we explored questions such as:

We also worked on how to make those conversations feel developmental rather than interrogative. Some of her team were enthusiastic and wanted to do well, but they were also nervous about giving the wrong answer. So part of the work was about giving people enough space and time to think, rather than expecting them to produce fully formed answers on the spot.

For example, instead of asking a series of questions in the moment, she might say: “I’d like you to think this through and come back to me next Tuesday with your options and recommendation. You don’t need the perfect answer now, but I do want you to own the thinking.”

This gave responsibility without abandoning the person. It also helped her pause before going into solution mode. “Space and time” became the practical thread running through the work: space for her to choose her response, and time for the team to think properly.

My role was to help her see the pattern clearly, practise different conversations, and translate the insight into real leadership moments with her team.

How she applied it

The coaching was not kept at the level of theory. A significant part of the work involved applying these ideas to real individual conversations with team members.

We looked at specific situations where she wanted someone to take more ownership. We explored what she might normally say, what outcome she wanted, and how to create a different kind of conversation. This helped her move from telling people what to do, or asking questions that still contained her answer, towards conversations that supported people to think, prepare and come back with their own recommendations.

In individual conversations, the expectation began to shift from “bring me the problem and I’ll solve it” to “bring me the problem, your thinking, your options and your recommendation.”

The work also shaped how she approached a team development day, which followed on from a previous team session the year before. Rather than using the day simply to update the team or tell them what needed to happen next, she designed it to create structured thinking space.

The team were given preparation beforehand, so they had time to reflect, gather examples and come ready to contribute. This was important because it allowed her to test a different way of leading at team level. If she wanted people to bring more thinking, ideas and recommendations, the team day needed to create the conditions for that to happen.

The aim was not to run a “soft” session with no direction. It was to create a clear, purposeful environment where the team could reflect on what they had learned, bring examples, identify what was getting in the way, and begin generating ideas and solutions themselves.

What changed

The change was not instant, and that is important. When a team has become used to a leader doing much of the thinking, the first attempts to shift that pattern can feel uncomfortable. At times, she stepped back and was met with silence. But that silence was useful information. It showed that the team needed support to build a new habit.

Over the course of the coaching, she became much more aware of when she was about to tell, solve or rescue. She began pausing more intentionally, asking different questions and giving people more time to think before expecting a response.

The team development day became one of the clearest examples of the shift in practice. Because the team had been given preparation, structure and time to think, they came with ideas, examples and reflections. This was exactly what she had wanted to see: people bringing more of their own thinking into the room, rather than waiting for her to provide the answers.

The day was also illuminating for her as a leader. It helped her understand more clearly where the team were at, what they understood, where the real development needs were, and what had been contributing to the repeated fires she kept having to put out.

That distinction mattered. Some of the issue had been about confidence and ownership, but some of it was also about knowledge gaps, unclear processes and people not yet seeing the wider picture. The team day helped make those gaps visible, which meant she could respond more precisely rather than simply feeling frustrated that people were not taking enough initiative.

As a result, she had a clearer sense of what support, training or process changes were needed to reduce some of the firefighting in the first place. She also had evidence that, when given the right preparation, structure and space to think, her team could come forward with useful ideas and examples.

The broader outcome was a move away from reactive problem-solving and towards more deliberate team development. She was no longer only asking, “How do I get this off my desk?” She was asking, “How do I help this person build the judgement to handle this well next time?”

As her team began bringing more thinking, options and recommendations, she also started to get some of her evenings back. The work that needed her director-level attention was no longer always being pushed behind everyone else’s problems.

For me, that was the real leadership shift. Her role was not just to solve problems or protect standards. It was to leave the team in a better place.

Shared with our client’s kind permission. Some identifying details have been changed to protect her privacy.