Low performance is one of the hardest parts of being an engineering manager. It's uncomfortable, often unclear and easy to avoid. Many managers hope the situation will resolve itself. Others compensate by redistributing work or lowering expectations. Both approaches create short-term relief but long-term problems.
When low performance isn't addressed, it affects more than the individual. It impacts team trust, delivery predictability and overall standards. Strong performers start to notice the imbalance. Over time, it erodes motivation and creates quiet frustration across your team.
Handling low performance well isn't about being harsh. It's about being clear, fair and consistent.
The real problem is often unclear
Low performance is rarely as simple as "someone isn't good enough."
In many cases, the problem isn't clearly defined. Expectations are vague. Feedback has been indirect. The person may not even be aware that there's a gap.
Before you take action, it's important to understand what's actually happening. Low performance typically falls into one of three categories.
Sometimes it's a skill gap. The person doesn't yet have the technical or problem-solving ability required for the role. They're trying, but the work is beyond their current level.
Sometimes it's a motivation or engagement issue. The person can perform but isn't fully invested in the work. They deliver the minimum, avoid ownership or have disengaged from the team.
Sometimes it's contextual or personal. External factors or temporary situations are affecting performance. A personal crisis, burnout or an unsustainable workload outside their control.
These categories often overlap. Someone with a skill gap may also lose motivation over time. Someone dealing with personal challenges may appear to have a skill issue. The point isn't to pick one label, it's to understand what's actually driving the gap so your response fits the situation.
Start with clarity, not assumptions
Your first step is to make expectations explicit.
Many performance issues exist because expectations were never clearly defined. What does "good" look like in this role? What's expected in terms of quality, ownership, communication and delivery?
Without that clarity, feedback becomes subjective and difficult to act on. Telling someone they "need to step up" doesn't give them anything to work with. Telling them "you're expected to identify risks in your work before they reach code review, and that isn't happening consistently" does.
Anchor the conversation in observable behavior and outcomes. What's happening today that isn't meeting expectations? Where is the gap? What impact is it having on the team or the work?
This shifts the conversation away from personal judgment and toward shared understanding.
Have the conversation early
Delaying the conversation rarely improves the situation.
You might wait because you want more evidence, or because you hope the issue will resolve on its own. In practice, delay increases uncertainty and makes the conversation harder. By the time you finally address it, weeks of frustration have built up on both sides.
Addressing the issue early creates space for improvement. It also signals that expectations matter.
The tone matters. You're not there to confront or accuse. You're there to align on what's expected, what's currently happening and what needs to change. Think of it as the same kind of clarity you'd bring to any other leadership conversation, just with higher stakes.
Clarity is more important than comfort.
Separate support from accountability
Handling low performance requires balancing two things: support and accountability.
Too much support without accountability leads to drift. You keep adjusting, the team keeps compensating and the gap stays. Too much accountability without support creates pressure without a path forward. The person knows they're failing but doesn't know how to improve.
The person needs to understand what's expected and what isn't working. At the same time, they need to know what support is available. Support can take many forms: clearer prioritization, more frequent feedback, pairing with a stronger engineer, or breaking down work differently. But support should not remove responsibility. The expectation to improve needs to remain clear.
This works best in a team where people feel safe raising problems, where honest performance conversations can happen without turning adversarial. That foundation is what Culture, Psychological Safety and Team Health is about.
Follow up with specifics
Improvement isn't a single event. It's a process, and without regular follow-up it drifts.
Both you and the individual need to know where things stand. Without that, you assume nothing has changed while they assume they're improving. Neither of you knows for sure.
Regular check-ins fix this, but only if they're specific. "How are things going?" isn't useful. "Last week we agreed you'd flag blockers within a day instead of waiting for standup. How has that been going?" is. That kind of specificity makes it easier to reinforce progress, adjust support and address remaining gaps.
When the issue is skill
If the root cause is a skill gap, your focus should be on learning and development.
This means identifying the specific skills that are missing and creating a path to build them. It might involve smaller, more scoped tasks, more structured guidance or pairing with someone more experienced. The approaches described in Growth in Engineering Teams apply here: stretch opportunities matched to the person's level, regular feedback and deliberate knowledge sharing.
Be realistic. Skill development takes time, and not every gap can be closed quickly. The role and expectations may need to be adjusted in the short term while someone builds capability.
What matters is whether there's progress and whether the trajectory is moving in the right direction. Someone who's growing steadily is in a very different situation from someone who's stuck.
When the issue is motivation
If the issue is motivation, the conversation is different.
The question isn't "can this person do the work?" but "why aren't they engaging with it?"
Sometimes the work itself isn't meaningful to them. Sometimes expectations are unclear and they've quietly given up on understanding what success looks like. Sometimes there's frustration that hasn't been addressed, a sense that their input doesn't matter or that the environment isn't fair.
Understanding this requires open conversation. The goal is to identify what's blocking engagement and whether it can be changed. Adjusting responsibilities, providing more context or reconnecting someone to the impact of their work can make a real difference. In other cases, the misalignment may be harder to resolve.
When the issue is contextual
Sometimes performance drops because of factors outside of work.
In these cases, empathy matters. But so does clarity.
Acknowledging the situation doesn't mean removing expectations entirely. It means adjusting them in a way that's realistic and transparent. Your team shouldn't carry hidden load indefinitely, and the individual shouldn't feel uncertain about what's expected during a difficult period.
Be honest about what you can accommodate and for how long. That's fairer than pretending the situation doesn't exist.
When improvement doesn't happen
Not all situations will lead to improvement. Even with clarity, support and time, there are cases where the gap remains.
Continuing without change isn't neutral. It affects the rest of your team. Strong performers notice when standards aren't enforced, and over time that erodes both trust and motivation.
When improvement doesn't happen, the next step needs to be clear. That might mean changing the role, adjusting responsibilities or ultimately starting a formal process to move on. Work closely with HR here: documentation, structured improvement plans and fair timelines matter both for the individual and for the organization. Avoiding the decision altogether creates more harm than making it.
Final thought
Handling low performance isn't about being strict or lenient. It's about being clear and consistent.
People perform better when they understand what's expected, receive direct feedback and know that improvement is possible. Teams perform better when standards are real and applied fairly.
Avoiding the problem delays it. Addressing it with clarity, support and honest follow-through creates the possibility of change.