What should I do when an engineer is consistently underperforming but not failing outright?

They’re not missing every deadline, but they’re slower, less reliable, and others are starting to notice.

This is one of the hardest situations because it’s easy to tolerate for too long. The key is to move from vague frustration to specific evidence.

Start by defining what “good” looks like in their role. Not in theory—based on your current team. What output, responsiveness, and ownership are normal?

Then compare. Where exactly are they falling short? Be concrete: missed handovers, slow turnaround, needing repeated nudges.

Next, have a direct but calm conversation. Share observations, not judgement. For example: “I’ve noticed tasks are taking longer than expected and sometimes need follow-ups. I want to understand what’s going on.”

You’re looking for one of three things: skill gap, clarity gap, or motivation issue.

Once identified, agree a short improvement plan (2–4 weeks). Keep it focused and measurable. Check in regularly.

If there’s no movement after that, you have clearer ground to escalate. Avoid letting this drift—it impacts the whole team.

• Define clear performance expectations based on your current team
• Write down 3–5 specific examples of the gap
• Have a direct conversation focused on understanding, not blame
• Agree a short, measurable improvement plan
• Review progress weekly and document outcomes

Waiting too long because the problem isn’t “bad enough” yet.

Provides structured reflection prompts before the conversation and helps track performance patterns over time. It keeps your thinking evidence-based rather than emotional.