A difficult conversation is a direct discussion about a disagreement, performance concern, or other sensitive issue. For a lead developer, it is part of supporting the team—not a reason to assign blame or avoid someone. Respectful honesty can surface problems early, while listening helps people feel heard even when a decision does not change. section 11.4 section 11.6.3 section 1.3.3
Prepare for a constructive discussion:
- Gather specific, observable examples and relevant data. Avoid assumptions and hearsay. section 11.4.1
- Invite the person in a tone that fits your usual communication. State your aim as finding a solution and offering support, rather than pointing fingers. section 11.4.1
- Begin by asking how the person is doing. Listen before deciding what explains their behavior or performance. section 11.4
- Say what you disagree with respectfully and honestly. Avoid agreeing merely to please everyone, especially when a decision needs an explanation. section 11.6.3 section 1.3.3
When missed deadlines have a personal cause
A developer was irritable, missed deadlines, and was difficult for teammates to reach. Rather than judge them from complaints alone, their lead asked how they were doing. Personal and family problems affecting their mental health emerged. The lead worked with human resources to identify available resources and discussed leave; when the developer returned, the lead assured them of the team’s support. The performance concern still needed attention, but understanding the circumstances changed how support could be offered. section 11.4
