When Understanding Someone Does Not Change What the Team Needs

The first problem was that I did not hear about difficulties early enough.

Someone on my team was struggling to complete their work independently. Problems were not being raised while there was still enough time to respond, so I began checking progress myself. Those checks revealed mistakes we had already discussed and tasks that still required frequent guidance.

During our conversations, the person seemed to understand. We could go through the work, examine what had gone wrong and discuss how to approach it differently. But afterwards, applying that understanding independently remained difficult.

That gap mattered. I could see a reason to keep helping. If something seemed clear while we worked through it together, perhaps another explanation, a better example or a smaller step would help it become usable without me. For a time, that was where I put my effort.

What I tried to make possible

I explained the work again. I demonstrated it and gave concrete examples. I broke tasks into smaller steps and checked them more frequently. I also addressed the recurring mistakes directly. I wanted to be clear about what needed to change, rather than leave the person trying to interpret my concern.

There was some improvement. That matters, because it was not a situation in which nothing I did appeared to help. But the improvement did not last without continued checking. The same problems returned despite the additional support.

The difficult question gradually changed. At first, I was trying to understand what would help the person carry the work. Later, I needed to consider whether the work could be carried reliably without the level of involvement I was providing.

Those questions are connected, but they ask different things of a leader. One invites another attempt. The other asks for an honest assessment of what those attempts are producing.

Understanding during a conversation

I want to be careful about what I conclude when someone seems to understand me. Being able to follow an explanation is meaningful. It gives us a place to begin. But the work eventually happens outside the conversation, where the person needs to recognise a problem, decide what to do and know when to ask for help.

In this situation, that was where the difficulty remained. I could not know every reason for it. I could describe what I observed: the work needed repeated guidance, familiar mistakes returned, and problems were not being raised early enough.

That was enough to require a response. I did not need to turn those observations into a judgement about the person’s character or their intentions. I did, however, need to take them seriously as information about how the work was functioning.

The rest of the team needed my time too

The additional support had a cost beyond the hours I spent checking a task. It took time I should also have been giving to other team members and to the team as a whole. The more closely I needed to follow one person’s work, the less attention remained available elsewhere.

That does not mean every person should receive an identical share of a leader’s time. Someone learning something new may reasonably need much more support. A person going through a difficult period may need an adjustment that others do not need. I want there to be room for that.

But I also need to notice when an adjustment becomes a continuing requirement without sufficient improvement. My willingness to provide more attention does not make that attention unlimited.

The person I was helping was part of the team. So were the people receiving less of my time while I helped. That was the wider responsibility I needed to keep in view. I could not assess the arrangement only through the conversation immediately in front of me.

When support did not become sustained improvement

The hardest part for me was deciding what to do when the support was not leading to enough improvement.

I had a clear conversation about the lack of progress, and we agreed on what needed to change. I then changed the person’s tasks and responsibilities. I also asked my own manager for help in deciding the next step. I continued to support the person during that process.

Involving my manager mattered. I needed another perspective on what I had tried and on the results we were seeing. I had been close to the work, repeatedly explaining, checking and adjusting. I needed help assessing what that effort amounted to.

My manager’s assessment was that I had done everything I could to help. That did not make the next decision easy. It did help me face the question that remained: was there enough improvement to continue?

In the end, there was not. We decided that I needed to let the person go.

The decision did not erase the effort

I do not see that ending as proof that the support was pointless. There were real attempts to help. There was some improvement. There was also a continuing gap between what the work required and what could be sustained without frequent intervention. All of those things belong in the account.

I also want to be precise about why the outcome mattered. The person did not owe me a successful result because I had invested time in them. Support should not become a personal debt, with gratitude or effort treated as repayment.

The responsibility concerned the work. Was it becoming reliable enough? Were problems being raised in time? Could the person carry their tasks with a level of support the team could sustain? Those questions kept returning to insufficient improvement.

I could recognise the effort involved without pretending that the result had become sufficient. I could also make a decision about the role without claiming to know everything the person might be capable of in another setting.

What I can take responsibility for

There is no comfortable version of this experience in which caring enough guarantees that someone will succeed. I could explain, demonstrate, clarify and change the work. I could make more of my time available. I could seek help with my own judgement. I could not make those actions produce an outcome they were not producing.

That does not release me from examining my part. I still need to ask whether expectations were clear, whether the support addressed the actual difficulty and whether I gave the person an honest account of the concern.

But taking responsibility also includes recognising the limits of what I can achieve through another round of the same support. In this case, continuing required something I could not provide indefinitely: close involvement in one person’s work at the expense of attention the wider team also needed.

What the team still needed

I would have preferred an outcome in which the person gradually needed less checking and became more confident carrying the work. There were moments of improvement, but they did not become sufficiently sustained. Eventually, I had to make a decision based on that pattern rather than on the outcome I wanted.

That is the part of leadership this experience leaves me thinking about. Understanding someone’s difficulty can change what I ask of them. It can change how I explain something, how I organise the work and how much support I offer. It should make me more careful about the conclusions I draw.

It does not always change what the team ultimately needs. The work still needs to move. Problems need to become visible early enough to address. Other people need access to their leader’s attention. Support needs to be something the team can sustain.

I want to remain willing to help someone grow. I also need to remain honest when the help is not producing enough change. In this situation, both responsibilities belonged to me.