Teams absorb a performance problem for weeks before a manager raises it, and morale drops because they can see it is being allowed. Ask whether the manager missed it or avoided it, because a tracking gap and a courage gap need different fixes. Then agree the action, the timeline, and the review date.
If you are noticing a performance problem, everyone on that team noticed it about six weeks ago.
That is the part managers forget. You are always the last to know about the person who has been showing up late every day, or handing unfinished work to someone else, or quietly missing what they committed to. Your team already knows. And while you have been not noticing, it has been affecting morale, because they can see that you are allowing it to happen.
Why the team works around a problem instead of reporting it
By the time a manager notices, the team has usually been absorbing the problem for weeks. Deadlines have slipped. Unfinished work has changed hands. The people picking up the slack have been wondering why nobody is addressing it.
They rarely escalate, and the reason is not loyalty to the person causing the problem. It is that raising it feels like informing on a colleague, and they are not confident anything will happen if they do. So they route around the obstacle, which is the most reasonable short-term choice available to them and the most damaging one long-term.
The work still gets done, which is exactly why the problem stays invisible to you. Output holds up because three other people are quietly covering. Nothing appears on a report until one of those three resigns.
Did the manager miss it, or did they avoid it?
As the CEO, this is the question worth asking, because the two answers need completely different responses.
A manager who genuinely did not notice may need better ways to track workloads and spot missed expectations. That is a systems problem, and it is fixable with structure.
A manager who noticed and waited has a different issue. They need to understand that keeping one employee comfortable comes at everyone else's expense. That is a courage problem, and no dashboard solves it.
Most leaders assume the first and are looking at the second. It is worth asking directly rather than guessing, because the fix you choose depends entirely on which one you have.
The cost of waiting for certainty
One reason managers wait is that they are trying to be fair. They want to be sure before they raise it, so they collect another example, and then another.
That instinct is decent and the outcome is poor. While the manager is building a case, the team is reading the silence as a verdict. Waiting for certainty is itself a decision, and it is one everybody else can see being made.
A first conversation does not require certainty. It requires an observation and a question. What I noticed was this, what is going on. That is a fair conversation to have after one occurrence, and it is usually where the real cause surfaces, whether that is a workload issue, a training gap, or something happening outside work entirely.
Five questions to ask the manager
When a performance problem finally surfaces, I would start with these:
- When did you first become aware of the problem?
- What have you communicated to the employee so far?
- Who has been absorbing the extra work?
- How will you catch this earlier next time?
- What needs to improve, and by when?
Then agree on the action, the timeline, and when you will review progress. A conversation without those three things is a conversation you will be having again.
The third question is the one managers least expect, and it usually produces the most useful answer. Naming who has been covering tells you where your retention risk actually sits, and it is rarely the person causing the problem.
The honest conversation is the compassionate one
People sometimes think the kind thing is to leave it alone. I would argue the opposite, and I say that as someone who was on the receiving end of it.
Early in my career a CEO told me directly that people were scared of me and that I was tearing bridges down rather than building them. It was brutal to hear. It was also the most useful thing anyone did for me, because it gave me something I could act on.
I believe the most compassionate way to handle a people issue is to be upfront and honest with the employee. Honest and kind, not honest instead of kind. People understand a decision that is not immediately in their favour when they can see the reasoning behind it.
There is also a practical argument. Be careful when you are not honest and an employee finds out later, or when you avoid the reasons entirely and simply apologise while letting someone go. Those are the employees who become disgruntled, and a disgruntled former employee looks for a cause and for people inside the organization to bring onto their side.
When you are honest about the reasons and respectful in how you deliver them, you reduce that risk considerably. It protects the person, the department, and the organization at the same time.
What addressing it actually produces
When I walk a leader through this, I point at three outcomes, because the first one is the only one they are usually thinking about.
First, the situation resolves. Either the person improves, or they leave and learn something from it. In my experience most people who are let go eventually find where they are supposed to be, and a fair number address the patterns that got them there.
Second, your team sees that you noticed and that you are acting. That is what actually moves morale. They are not asking you to be ruthless. They are asking you to be present.
Third, your bottom line improves, because the hidden cost of an unaddressed performance problem is carried by the people working around it. For more on how that cost accumulates, see the hidden cost of losing the person everyone depends on.
What the delay costs the people who stayed
Every week a performance problem goes unaddressed, somebody else is paying for it in hours and in goodwill.
Usually it is your most reliable person, because work flows toward whoever can be counted on. They absorb the slipped deadline. They redo the piece that came back wrong. They stay late on the shift where coverage did not happen. None of it appears in a report, because from the outside the department is still delivering.
What changes is what that person concludes. They start with the assumption that leadership has not seen it yet. After a few weeks they move to the assumption that leadership has seen it and does not consider it worth acting on. That second conclusion is the expensive one, because it is a judgement about you rather than about their colleague.
This is how strong performers begin leaving without ever raising a complaint. Nothing dramatic happens. They simply stop believing that effort and outcome are connected here, and the next recruiter who calls gets a longer conversation than they would have got three months earlier.
Your team is watching how you handle it
People second-guess whether you can lead when they watch you not address something obvious. That judgement is not really about the underperformer. It is about whether you will act when acting is uncomfortable.
And it is not only how you handle it with the person who needs correcting. It is whether you come back around to the team afterward with enough humility to say something like: I realised there was a problem I was not addressing, I apologise, and next time please bring it to me, because I want to make sure I am helping you be successful.
That goes a long way toward rebuilding trust. It also makes the next problem surface faster, which is the entire point.
How to find out sooner next time
If you only learn about performance problems when they have become undeniable, the issue is your information flow rather than your judgement.
Regular one-to-ones help, provided they are not status reports. Ask who someone is waiting on and what they are working around. Ask what has changed about their workload in the last month, and why. Workload shifts are the earliest visible symptom of someone else's underperformance.
Stay interviews do similar work at a different altitude. Our guide to stay interviews for critical manufacturing roles covers what to ask and how often.
The goal is not to catch people. It is to shorten the six weeks. Your team will tell you what is happening if they believe something will come of it, and that belief is built one addressed problem at a time.
Frequently Asked Questions
Why does nobody tell me about a performance problem sooner?
Raising it feels like informing on a colleague, and people are not confident anything will happen if they do. So they work around it instead, which keeps output steady and keeps the problem invisible until someone who has been covering resigns.
What should I ask a manager who let a problem continue?
When they first became aware of it, what they have communicated to the employee, who has been absorbing the extra work, how they will catch it earlier next time, and what needs to improve by when. Then agree the action, timeline and review date.
Is it kinder to leave a struggling employee alone?
No. The most compassionate approach is being upfront and honest with them. People can accept a decision that is not in their immediate favour when they understand the reasoning, and avoiding the reasons tends to create a disgruntled former employee instead.
What does addressing a performance problem actually change?
Three things. The situation resolves, either through improvement or separation. The team sees that you noticed and acted, which is what moves morale. And the cost currently being carried by the people working around it stops accumulating.
How do I find out about problems earlier?
Use one-to-ones for more than status. Ask who someone is waiting on, what they are working around, and what has changed about their workload in the last month. Workload shifts are usually the first visible symptom of someone else underperforming.