A paradox I have seen in many companies
The person who gets the most of a manager’s attention is usually the one who doesn’t deliver. The one who is late, causes conflict, needs constant hand-holding. They get the extra meetings, corrective conversations and improvement plans. Someone finally starts paying attention to them.
And the person who simply does their job, week after week? They get the next project. Not because they are the best fit for it – they are simply the safest choice. They won’t miss the deadline, won’t leave the team with a problem, will make sure things get done and fix what others got wrong. And so competence starts being punished with extra workload.
Work nobody sees
The best people rarely do only what is written in their job description. They anticipate problems before anyone notices them. They look after quality even though nobody asks them to. They ease tensions, take responsibility when others step back and protect the manager from chaos.
And that is exactly why this work goes unnoticed – because it is done well. There is no crisis, no complaint, no row. There is just the result. And the manager sees the result, not the cost someone paid for that result to happen.
“Doesn’t report a problem” doesn’t mean “has no problem”
This is perhaps the most dangerous assumption a manager can make: “If something were wrong, they would tell me.” Yet independent, results-oriented people can stay silent for a very long time about the fact that they are not coping. Not because they don’t need support – but because they don’t want to let anyone down, don’t want to appear weak, have got used to the role of the reliable one, or simply don’t believe that raising the problem will change anything other than leading to yet another conversation.
The most overloaded person doesn’t have to look overloaded at all. They may still come prepared, meet deadlines, help others and say “I’ll manage”. But “I’ll manage” doesn’t always mean “I have the resources”. Sometimes it just means they see no other way out.
Leaving people in peace is not the same as autonomy
Many managers believe that by leaving their best people in peace they are giving them autonomy. That’s something else. Autonomy means trust, influence, access to resources, the ability to make decisions, regular dialogue and room to grow. Neglect means lack of interest, no feedback, no conversation about workload, piling on tasks without taking any away, and contact mainly when there’s another problem to hand over.
Autonomy says: I trust you and I’m here when you need me. Neglect says: get on with it, you’ve always managed. That is not the same conversation.
The best people rarely leave suddenly
From the outside it always looks the same: “but she never said anything”, “everything seemed fine”, “only a month ago she was leading that project”. But the decision to leave is almost never made on the day the resignation is handed in.
First, a person stops making suggestions. Then they stop fixing what others got wrong. They stop sharing ideas, fighting for quality, believing that a conversation will change anything. Formally, they still do their job – but they stop giving the company what can’t be written into any procedure: initiative, care, energy that goes beyond the role. The resignation is usually the final stage of a process the manager simply didn’t notice earlier.
A company dependent on its heroes
Overloading the most reliable people has one more consequence. The organisation starts relying not on processes but on the heroism of individuals. “Only she knows this project”, “the client won’t accept it without him”, “give it to her, she’ll make sure it gets done”.
In the short term that’s convenient. In the long term – very risky. If one person keeps patching the holes left by unclear responsibilities, weak processes and other people’s mistakes, the organisation isn’t solving its problems, it’s hiding them. The better that person copes, the longer the system can pretend that everything works.
So what should you do if you have someone like that in your team?
If you think of someone “you can always count on her”, don’t automatically assume that everything is fine. Arrange a meeting with her this week – not a status review, and not to hand over another topic. Talk about her.
It’s worth asking directly: what is taking most of your energy right now? Which duties are you doing even though they’re not formally part of your role? What are you picking up from others so the team delivers? What should we drop when the next priority appears? Where do you need a decision or protection from me? Do you have room to grow right now, or only to deliver the next tasks? And what could make you no longer want to work here six months from now?
Just one caveat: don’t ask if you’re not ready to hear the answer. A conversation after which nothing changes can do more harm than no conversation at all.
Recognition is not the same as a decision
“Thank you, great job” matters, but it’s not enough if the next project arrives straight afterwards. Recognition shouldn’t be the currency we pay for chronic overload.
Real appreciation sometimes means changing priorities, removing some responsibilities, extra resources, clarifying the scope of the role, a pay rise, a promotion, access to development, protection from tasks others try to offload, or simply planned rest after an intense period. Sometimes the best proof of recognition isn’t telling someone they’re irreplaceable – but building a team and processes so they don’t have to be.
Mature leadership also sees those who don’t shout
It’s easy to manage what is loud – a crisis demands attention on its own, a conflict lands in the calendar by itself, an undelivered result forces a reaction. It is harder to notice someone who works quietly, effectively and responsibly, doesn’t escalate, doesn’t ask for recognition and simply does their job – often picking up a bit of other people’s work along the way.
That’s exactly why such a person needs an attentive manager. Not when they stop delivering. Not when they go on sick leave. Not when they hand in their notice. Earlier.
“You can always count on her” should be the start of a conversation about recognition, development and support – not a justification for another burden.
If you have someone like that in your team, arrange a meeting with them this week. Not about the project. About them.