Handling Underperformance — Mentoring Language for Tech Leads
Practice the vocabulary for addressing underperformance: delivering difficult feedback, setting expectations, and supporting improvement plans.
0 / 5 completed
1 / 5
An engineer has missed their last three sprint commitments. How do you open the conversation?
Opening with a factual observation (not a character judgement), expressing curiosity before conclusions, and inviting the engineer to explain creates a psychologically safe space to surface the real root cause — which might be personal, technical, or organisational.
2 / 5
After the conversation you discover the engineer is overwhelmed by context-switching. What is the most useful next step?
Addressing underperformance means diagnosing the cause and fixing the system, not just the symptom. Context-switching is often a team or process problem as much as an individual one.
3 / 5
How do you set clear expectations when starting a performance improvement conversation?
Expectation-setting requires: naming the specific behaviour expected, giving a clear timeframe, expressing genuine commitment to supporting improvement, and being honest about consequences — all without being punitive in tone.
4 / 5
An engineer responds defensively: Everyone else misses deadlines too. How do you handle this?
Acknowledging the concern without abandoning the conversation is the skilled response. You validate the feeling, commit to investigating the broader concern, and redirect to what you can act on. Dismissing the point escalates defensiveness.
5 / 5
After three weeks of improvement, an engineer slips back into old patterns. How do you address this?
Regression is common in performance improvement. Acknowledging previous progress, avoiding shame, and investigating root causes of regression maintains the working relationship and often surfaces new information that drives real improvement.