How to Talk to an Underperforming Scrum Team Member: Supporting Without Judgment

Elara, the Scrum Master for Team Phoenix, felt a familiar knot tightening in her stomach. Ben, one of their most reliable developers, had been off for weeks. His usually insightful contributions in Daily Scrum had dwindled to mumbled updates, his code reviews were perfunctory, and he was missing deadlines on tasks he'd confidently pulled during Sprint Planning.

The team, usually a buzzing hive of collaboration, was starting to notice. Sarah, the Product Owner, had gently asked Elara if Ben was 'okay,' and Liam, another developer, had privately expressed frustration about Ben's unreviewed pull requests blocking his own work. Elara knew she couldn't ignore it. The Sprint Goal for their current iteration, focused on a critical payment gateway integration, was already looking shaky.

Her instinct screamed to intervene, but how? A direct accusation felt wrong, yet doing nothing felt like a betrayal of her servant leadership role. She needed to talk to Ben, but what exactly should she say to address the decline without alienating him or overstepping her boundaries?

When a team member's performance dips, it's natural for a Scrum Master to feel a mix of concern, frustration, and a desire to 'fix' the problem. However, many common reactions can inadvertently make things worse:

Direct Accusation: 'Ben, your performance has dropped, and it's affecting the team.' This immediately puts the person on the defensive, shutting down open communication. It also assumes you know the 'why', which you rarely do. As a Scrum Master, your role isn't to be a judge or disciplinarian; such an approach erodes trust and stifles the potential for resolution.

Ignoring the Problem: Hoping it will resolve itself often leads to resentment within the team, further impacting morale and productivity. The problem festers, becoming harder to address later. As part of your accountability to remove impediments, you must proactively address such situations.

Micromanagement: Hovering over the individual, assigning simpler tasks, or constantly checking in can erode trust and autonomy, making the person feel incompetent rather than supported. This goes against the principles of servant leadership and undermines the team's ability to self-manage.

Delegating to the Product Owner or Manager: While a line manager might eventually need to be involved for HR-related issues, the Scrum Master's role is to address team dynamics and impediments first. Passing the buck too early misses an opportunity for coaching and team self-management. The initial intervention falls within your purview.

Focusing Solely on Output: While output is a symptom, solely discussing missed deadlines or bugs without understanding the underlying causes is like treating a fever without diagnosing the infection. For true recovery, understanding the root causes is essential.

A Scrum Master's primary accountability is to the Scrum Team and its effectiveness. This means fostering an environment where individuals can thrive, impediments are removed, and difficult conversations are navigated constructively. The goal isn't to judge or punish, but to understand, support, and facilitate a path forward that benefits both the individual and the team.

Addressing a performance decline isn't about disciplinary action; it's about coaching, empathy, and servant leadership. The core skill required here is the ability to observe objectively, communicate non-judgmentally, and facilitate a conversation that empowers the individual to identify their own challenges and solutions, often with the team's support. This is where 'difficult conversations at work' become an opportunity for growth, not conflict.

Non-Judgmental Observation: Separate facts from interpretations. Instead of 'Ben is lazy,' think 'Ben has delivered X fewer story points this Sprint, and his Daily Scrum updates are brief.' The more concrete and measurable your observations, the more constructive the conversation will be.

Active Listening: Truly hearing what the other person says, both verbally and non-verbally, without formulating your response. This builds trust and shows respect. Don't just listen; summarize what you hear to ensure you've understood correctly.

Powerful Questions: Asking open-ended questions that encourage reflection and self-discovery, rather than leading questions that seek a specific answer. Questions like 'What's going on?' or 'What might help you?' empower the person to find their own solutions.

Facilitation: Guiding the conversation without owning the problem or dictating the solution. The goal is to help the individual and the team take ownership. You are a guide, not a problem-solver.

Understanding Team Dynamics: Recognizing how individual performance impacts the collective and how the team can support its members. An individual's performance is often a barometer for the overall health of the team.

This approach requires courage and practice. It's less about having all the answers and more about creating a safe space for the right questions to be asked and heard. This forms the bedrock of Agile coaching skills and is a critical Scrum Master skill.

When approaching a team member about a performance shift, Elara follows a structured yet empathetic framework:

1. Observe and Document (Facts, Not Feelings):

Before the conversation, gather specific, objective observations. 'Ben has missed three Daily Scrums this week.' 'His average story points delivered has decreased by 40% over the last two sprints.' 'Liam mentioned two of Ben's PRs are awaiting review for over 48 hours.' Avoid interpretations or assumptions; stick to what you can see and measure, rather than saying 'Ben seems disengaged' or 'He's not pulling his weight.' This prevents the conversation from becoming defensive.

2. Initiate a Private, Safe Conversation:

Choose a time and place where you won't be interrupted and the conversation can remain confidential. Start with a question like, 'Ben, do you have 15 minutes to chat privately this afternoon?' Frame it as a check-in, not an interrogation, to help the person feel at ease.

3. Share Observations Non-Judgmentally (Using 'I' Statements):

Start by expressing your observations and concern, focusing on the impact. 'I've noticed that your contributions in Daily Scrum have been briefer lately, and some of your tasks from Sprint Planning are taking longer than usual.' 'I've also seen a couple of your pull requests pending review for a while, which seems unusual for you.' Emphasize that this is about observation, not accusation. 'I wanted to check in and see how things are going for you,' leaves the door open.

4. Listen Actively and Empathize:

After sharing your observations, pause and truly listen. Use open-ended questions: 'How are things feeling on your end?' 'Is there anything that's making it harder to focus on your tasks right now?' 'What's been on your mind regarding your work?' Be prepared for silence; don't rush to fill it. Validate their feelings without necessarily agreeing with their interpretation: 'That sounds challenging.' This is key to building trust and allowing the person to express themselves.

5. Explore Needs and Impact:

This phase is crucial for moving beyond symptoms to root causes. Encourage them to reflect on both internal (e.g., motivation, clarity) and external factors (e.g., workload, tools, team dynamics). Frame questions to gently connect their personal situation to the collective responsibility of the Scrum Team, without making them feel guilty. Remember, the Sprint Goal is a shared commitment, and understanding individual challenges helps the team adapt. Ask: 'What do you feel you need to get back on track?' 'How do you think this might be impacting the Sprint Goal or the team's ability to deliver?' (Connect it to team responsibility). 'Is there anything the team or I could do to support you?'

6. Collaborate on Next Steps:

The goal is for them to identify solutions, not for you to provide them. As a Scrum Master, your role is to facilitate self-management. Guide them to brainstorm potential solutions, whether it's adjusting their workload, seeking specific help from a teammate, or even just needing a temporary shift in focus. If the issue points to a broader team impediment – like unclear requirements from the Product Owner or a lack of psychological safety – then this conversation becomes input for a Sprint Retrospective, where the whole team can address systemic issues. Ensure any agreed-upon steps are concrete and actionable. 'What do you think would be a good next step here?' 'How can we ensure the team can still meet the Sprint Goal while addressing what you're going through?'

7. Follow Up:

Schedule a brief follow-up to check in on progress and offer continued support. This shows you care and reinforces accountability. It's a demonstration of your stakeholder management and servant leadership skills.

This structured approach helps navigate the 'Scrum Master interview scenario questions' about conflict resolution and performance management, demonstrating a true servant leadership mindset.

Here's how Elara might phrase some key moments with Ben:

Opening: 'Hi Ben, do you have a few minutes for a quick chat? I've noticed a few things over the last couple of weeks and wanted to check in.'

Sharing Observations: 'From my perspective, your contributions in Daily Scrum have been less detailed, and I've observed a decrease in the number of tasks you've completed compared to previous sprints. Also, Liam mentioned he's waiting on a review from you for a critical pull request.'

Open-ended Question: 'How are things feeling from your side? Is there anything impacting your work right now?'

Empathy & Validation: 'It sounds like you've got a lot on your plate outside of work, and that can certainly make it hard to focus. I appreciate you sharing that.'

Connecting to Team: 'Given where we are with the Sprint Goal for the payment gateway, how do you see this impacting our ability to deliver as a team?'

Collaborating on Solutions: 'What do you think would be a realistic next step for you to manage your workload this sprint? Is there anything specific the team could do to support you, or perhaps a task we could temporarily reassign?'

Setting Expectations/Follow-up: 'Let's touch base again on Thursday to see how those adjustments are working out. My goal is to ensure you feel supported and the team can continue to deliver effectively.'

This kind of dialogue prioritizes understanding and collaboration over judgment, aligning perfectly with Agile coaching skills and the spirit of the Scrum Guide.