It's rarely an obvious crisis. It's the quiet, persistent discomfort. The meeting that always becomes difficult when a certain person is involved. The milestone that's always narrowly missed. The mood that shifts whenever that person walks into the room. And the manager who hopes the problem will resolve itself.
It won't resolve itself. That's the first truth this article needs to make clear.
What defines a low performer
Low performers aren't always people who do nothing. They're people whose performance, or behavior, disproportionately holds the team back. There are three types:
- Performance low performer: Consistently delivers below expectations despite having the resources, support, and clarity around goals they need. Not a skill problem, but a will problem.
- Energy low performer: May deliver the minimum, but drains energy from the team. Negativity, obstruction, passive resistance. Other people have to work harder because this person is in the room.
- Trust low performer: Unreliable, dishonest, or protects their own position at the team's expense. The most dangerous profile because it often remains invisible for a long time.
The chain reaction across the team
What happens when one person consistently fails to deliver and the manager does nothing?
- High performers take over the work: Because the alternative is worse. Their reward? More work. Over time, you lose these people.
- Standards fall: If one person doesn't have to deliver, why should I? That's not laziness. It's a human comparison response (known in research as the “sucker effect,” Kerr 1983).
- Trust in leadership erodes: Everyone sees the problem. Only the manager seems not to see it, or refuses to act. That's toxic to the manager's authority.
- The product launch suffers: When someone in a critical role doesn't perform, milestones are put at risk. And in a launch context, delays of two to four weeks can close market windows.
“Tolerating low performance isn't kindness. It's a signal to your top performers that their performance isn't actually valued.”
The career changer who never develops: a particularly dangerous pattern
One of the most common, and longest tolerated, forms of low performance is the career changer who lacks subject-matter expertise, doesn't continue learning, and whose manager neither demands development nor provides meaningful support. The person is on the team and owns an area of responsibility, but the necessary knowledge was missing from the start. And it never develops.
At first, this sounds like an onboarding problem. It isn't. It's a leadership decision. Or the absence of one. If nobody clearly says, “This is the knowledge you need to have in six months, and this is how you're going to build it,” and nobody follows up to see whether that actually happens, the person stays exactly where they started.
The chain reaction in detail
Knowledge is missing, and development doesn't happen. The person doesn't know how the product works, doesn't know the technical specifications, and doesn't understand the industry. Nobody requires it. Nobody develops it.
The team doesn't get the materials or information it needs. Tasks that require subject-matter expertise don't get done. Materials aren't prepared. Information arrives late or not at all. The team works around the gaps without calling them what they are.
The person doesn't deliver, but goes to the manager. Instead of delivering, they communicate. They go to the manager and claim that someone else is actually doing the work, that they themselves aren't responsible, or that other people interfered. The story turns reality on its head.
The high performer takes over to protect their own reputation. Product presentations, customer meetings, or deadlines are coming up. The high performer can't and won't afford to look unprepared. So they step in: quietly, without being asked, and often without recognition. They save the outcome.
The high performer is set up to fail. Because they take over work that isn't theirs, they become responsible without having decision-making authority. If something goes wrong, they carry the burden. If it goes well, the other person was “involved.” The system rewards passivity and punishes initiative.
This pattern isn't an exception. It appears in Sales, Product Management, Project Management, and Support alike. It's so common because it can remain invisible for so long: operations keep running because high performers compensate. Until they stop.
What leadership fails to do in this pattern
- No clear competency requirements defined when the person joins
- No binding development plan with a timeline
- No regular check whether the required knowledge is actually being built
- No direct confrontation when deliverables are missed
- The person's account is treated as reality without being verified
The result: After a year at the latest, the high performer starts asking whether this is really the environment they want to work in. And reaches a clear conclusion.
Why managers wait too long
Conflict avoidance
The difficult conversation takes courage. Hoping the problem will resolve itself costs... everything else. Most people aren't courageous in uncomfortable situations. That's a human universal, not an individual weakness. But leadership means exactly that: tolerating discomfort for the good of the team.
Empathy without consequences
“He's dealing with personal problems right now.” “She just needs more time.” “We don't want to leave anyone behind.” Empathy matters. But empathy without consequences isn't leadership. It's conflict avoidance with a clear conscience.
No feedback system
Often, there's simply no structured system for identifying and addressing performance problems early. No regular 1:1s, no clear goal framework, and no documented conversations. By the time the problem becomes visible, the solution is more expensive.
What good leadership does in this situation
- Address it early: At the first clear signal, not six months later. The earlier you address it, the more room there is to correct course.
- Be clear and specific: No hints. “I've noticed that X hasn't been delivered over the past three months. This is my expectation. What do you need to change that?”
- Offer support and document it: Coaching, resources, and clarity. And document what was discussed.
- Name the consequences: What happens if nothing changes? That question needs an honest answer, even when it's uncomfortable.
- Act if nothing changes: This is the hardest step. And the most necessary one.
The best teams aren't built by keeping low performers. They're built through clarity about what success looks like and consistency in dealing with people who repeatedly fail to meet that standard. That's not a harsh leadership principle. It's a fair one.
What this has to do with product launches
Product launches are high-stress situations. Under stress, weaknesses become visible and amplified. A low performer who was manageable during normal operations becomes a risk in launch mode. Critical deliverables are delayed. Teams are destabilized. Customers experience a level of quality that falls short of the standard.
The consequence: Resolving a low-performer situation before an important launch isn't an HR task. It's a strategic decision.
Sources: Kerr (1983), Motivation Losses in Small Groups: A Social Dilemma Analysis, Journal of Personality and Social Psychology 45(4), 819–828.
Published June 2026