Why does my team feel unsupported when I am working so hard?

Executive summary: A team can feel unsupported even when their leader is working extremely hard. This usually happens when too much context, decision-making, follow-up and risk sits privately with the leader. The issue is not always commitment or character. More often, it is a visibility problem. Leaders support their teams not only through effort, but by making priorities, decisions, dependencies and commitments clear enough for others to act with confidence.

Article: A leader I was coaching recently described a pattern that had started to worry them. They were busy. Really busy. Back-to-back meetings most days. Messages late at night. Requests coming from above, across and below. They were trying to be responsive, helpful and committed.

Then the feedback arrived. The team felt unsupported. Not ignored. Not badly treated. Not abandoned in any dramatic sense. Just unsupported. Decisions were taking too long. Priorities were not always clear. Small pieces of context were staying in the leader’s head. People were having to wait, chase, guess or fill in the gaps themselves. The leader’s first reaction was confusion. They did not feel disorganised. They felt overwhelmed.

But this is the uncomfortable point. From the team’s side, overwhelmed and disorganised can look very similar. Either way, the team does not get what it needs when it needs it. Either way, uncertainty is passed down the system. Either way, good people start spending energy compensating for things that could have been made clear earlier.

This is rarely a simple question of effort. In fact, effort can be part of the problem. The harder the leader works privately, the easier it becomes for the team to lose sight of what is happening, what matters, who is waiting for what, and what the leader has actually committed to.

The leadership challenge is not to carry more. It is to make more of what you are carrying visible.

1: Reframe the issue: from personal failure to visibility problem

When leaders receive feedback that the team feels unsupported, the first instinct is often to take it personally. They hear it as a criticism of their care, competence or character. That is understandable, but it is not always useful. A more helpful starting point is to ask what the team could not see.

Teams rarely experience your intention directly. They experience your availability, your decisions, your clarity, your timing and your follow-through. You may be holding a lot in your head, but if the team cannot see enough of it to act with confidence, the experience is still one of uncertainty.

That uncertainty often shows up in small ways:

• A decision is discussed but not confirmed.
• A deadline is agreed but no checkpoints are created.
• A priority changes but the reason is not explained.
• A risk is known by the leader but not shared early enough.
• A promise is made in a meeting but disappears into an inbox.

None of these moments may feel serious on its own. Together, they create a pattern. The team starts to feel that they have to manage around the leader rather than with the leader.

This is why the distinction matters. If you treat the issue as a personal flaw, you will probably respond with guilt and a vague promise to be better. If you treat it as a visibility problem, you can redesign the way work, decisions and commitments are made clear. The better question is not, am I a disorganised leader? The better question is, what am I holding that other people need to see?

2: Understand why capable leaders end up here

This pattern often appears in capable leaders, not careless ones. That is one reason it can be so difficult to spot. The leader is not avoiding work. They are usually taking on too much of it There are several reasons this happens.

The first is the pull of being useful. When someone asks for help, it feels supportive to say yes. When a quick task appears, it feels efficient to do it yourself. When a problem lands, it feels responsible to absorb it. Each decision makes sense in the moment. Over time, the leader becomes the place where too many things accumulate.

The second is the reward of completion. Doing something yourself gives an immediate sense of progress. Delegating, clarifying, briefing and checking understanding often feel slower. Yet leadership work is rarely just about getting the task done. It is about increasing the capacity of the system to get the work done without everything passing through you.

The third is pressure from above. Many leaders carry expectations from their own manager, senior stakeholders or the wider organisation. If those expectations are not examined, they get passed down to the team as urgency. The team then experiences pressure without context.

The fourth is a misunderstanding of what support means. Many leaders think support means being available, answering questions and stepping in when needed. Those things matter, but they are not enough. Support also means making the operating environment clear enough that people do not need to keep coming back to you for basic direction.

In other words, the leader may be working hard and still be under-leading the system.

3: Make the work visible before people need to chase it

One of the simplest ways to support a team is to make the hidden work visible before it becomes a problem. This does not require a complicated system. It requires discipline around a few basic questions:

• What are we trying to achieve?
• What does good look like?
• Who owns the next step?
• What decision is still outstanding?
• Who else needs to know?
• When will we check progress?

These questions sound obvious, which is why they are so often missed. In busy teams, people assume alignment because a conversation has happened. But a conversation is not the same as a shared commitment. A meeting is not the same as a decision. A deadline is not the same as a plan. Making work visible means moving from assumption to explicit agreement.

For example, instead of saying, can you take this forward, say:

• Here is the outcome we need.
• Here is what good would look like.
• Here is the decision I still need to make.
• Here is who needs to be involved.
• Let us check progress on Thursday before it goes too far.

That extra minute of clarity often saves several days of confusion. The same applies to your own work. If you are holding a decision, name it. If you are late on something, say so. If you are waiting for input from someone else, make that dependency visible. Teams can handle delay far better than silence. What drains confidence is not always the delay itself, but the absence of information around it.

4: Replace distant deadlines with checkpoints

Many leaders unintentionally create risk by treating a deadline as the main support structure. A date is agreed, everyone nods, and then the work disappears until the deadline gets close. That is not support. That is hope.

Checkpoints are different. They create small moments where the work can be seen, adjusted and supported before it is too late. They reduce surprise. They also reduce the need for the leader to intervene dramatically at the end, which is often where frustration and rework appear.

A useful checkpoint does not need to be long. It simply needs to answer three questions:

• Are we still aiming at the same outcome?
• What has changed since we agreed the work?
• What help, decision or information is needed now?

This is especially important when a leader is busy. The busier you are, the more you need rhythm. Without rhythm, everything depends on memory, availability and individual effort. With rhythm, the system catches more of the work before it falls.

A team that has regular checkpoints does not need to guess whether the leader is interested. They can see it. They know when to raise issues. They know when decisions will be made. They know where to bring uncertainty. This is one of the quiet differences between a team that feels managed and a team that feels supported.

5: Put your own commitments where the team can see them

Many leaders ask their teams to make work visible while keeping their own commitments private. The team’s actions are on a board, in a plan or in a tracker. The leader’s actions are in their notebook, inbox or head. This creates an unintended double standard. The team can see what they owe the leader, but they cannot always see what the leader owes them.

If you want the team to experience support, your own commitments need to be visible too. This does not mean exposing every detail of your workload. It means making visible the commitments that affect other people’s ability to move.

For example:

• I owe the team a decision on the budget by Wednesday.
• I need to speak to finance before we can confirm the timeline.
• I have committed to challenging that priority with the steering group.
• I am late on reviewing the proposal, and I will do it by Friday morning.

This kind of visibility builds trust because it shows that accountability moves in both directions. It also gives the team permission to flag when something you are holding is starting to block them.

A useful phrase here is simple: Here is what I am holding that affects you. That one sentence can change the quality of a team conversation. It moves leadership from private effort to shared awareness.

6: Use one weekly check to catch the pattern early

The leader in the opening story did not need a personality change. They needed a small recurring habit that did not depend on them remembering everything perfectly. A weekly check can be enough. At the end of each week, ask yourself five questions:

• What am I holding that only exists in my head?
• Who is waiting for a decision, update or steer from me?
• What commitment have I made that is not visible anywhere?
• Where might my team be guessing rather than knowing?
• What needs to be said before next week begins?

This is not administration for its own sake. It is leadership maintenance. It prevents the slow drift from busy to unclear, and from unclear to unsupported. You can also ask the team a version of the same question: What do you need from me that you are not currently getting clearly enough?

The wording matters. You are not asking, am I doing a good job? That can easily become too personal. You are asking what the system needs from you. That makes the conversation easier, more practical and more likely to produce useful information.

7: Bringing it back to the leader

The leader who started this conversation did not solve the issue by working longer hours. That was already part of the problem. What changed was smaller and more structural.

They started naming what they were holding. They made decisions and dependencies more visible. They replaced distant deadlines with shorter checkpoints. They put their own commitments into the same shared space as the team’s commitments. And once a week, they asked what might fall through if it stayed only in their head.

None of this was dramatic. It did not need to be. The team began to feel more supported not because the leader became a different person, but because the work no longer depended so heavily on the leader remembering to carry everything privately.

That is the central shift. Leadership support is not just about how much you care or how hard you work. It is about whether people can see enough, early enough, to do their work with confidence.

Before you move on, three questions are worth sitting with:

• What am I currently holding that only exists in my head?
• Who would be helped if they could see more of what I am carrying?
• What would fall through next week if I became too busy to remember it?

Follow-up reading

These resources from the leadership library may help you go deeper into the practical habits behind this issue.

• Organising self and others: Useful for leaders who need to create clearer personal and team systems.
• Delegation: A companion topic for leaders who are carrying too much themselves.
• Informing others: Relevant when the issue is less about effort and more about timely information flow.
• Team dynamics framework: A broader way to think about the patterns that shape team performance.
• Accountability: Helpful when you want commitments to be visible in both directions.

FAQ: When the team feels unsupported

Can a leader be supportive and still leave the team feeling unsupported?

Yes. This is more common than many leaders realise. A leader may care deeply and work extremely hard, but if decisions, priorities and commitments are not visible enough, the team may still feel unsupported. Support is not only about intent. It is also about clarity, timing and follow-through.

Is this just poor organisation?

Sometimes it includes poor organisation, but that is not the whole story. The deeper issue is often that too much of the operating system sits privately with the leader. The leader knows what is happening, but the team cannot see enough of it to act confidently. That makes the issue one of visibility and shared structure, not just personal tidiness.

What is the first practical step?

Start by listing everything you are holding that affects other people. Include decisions, promises, risks, updates, dependencies and pieces of context. Then ask which of those need to be made visible to the team, to an individual, or to a stakeholder.

How do I ask the team without sounding defensive?

Keep the question practical. Try asking, what do you need from me that you are not currently getting clearly enough? This frames the conversation around the work rather than your personality. It also makes it easier for people to give specific and useful feedback.

What if the real issue is that I have too much work?

Then the visibility still helps. When your commitments are visible, it becomes easier to have a serious conversation about capacity, priorities and trade-offs. If everything stays hidden, overload remains a private struggle. Once it is visible, it becomes a leadership and organisational question.

References

• Center for Creative Leadership (2025) 10 Steps for Setting Team Norms. Available at: https://www.ccl.org/articles/leading-effectively-articles/the-real-world-guide-to-team-norms/ (Accessed: 2 July 2026).
• Johnson, E. (2025) ‘Why Aren’t I Better at Delegating?’, Harvard Business Review, September to October. Available at: https://hbr.org/2025/09/why-arent-i-better-at-delegating (Accessed: 2 July 2026).
• Sibbet, D. (2011) Visual Teams: Graphic Tools for Commitment, Innovation, and High Performance. Hoboken, NJ: Wiley.
• Watkins, M.D. (2016) ‘Leading the Team You Inherit’, Harvard Business Review, June. Available at: https://hbr.org/2016/06/leading-the-team-you-inherit (Accessed: 2 July 2026).