How to Approach a Declining Team Member's Performance as a Scrum Master

Elara, the Scrum Master for the Phoenix Team, had noticed a shift in Liam's behavior over the past few Sprints. Liam used to be one of the most enthusiastic and engaged members of the team – often the first to speak in Daily Scrums, offering creative solutions in Sprint Planning, and providing constructive feedback in Retrospectives. Lately, however, Liam had grown quiet, struggled to complete his tasks on time, and even started arriving late to some meetings. Team members exchanged glances, and Sarah, the Product Owner, began expressing concerns about meeting the Sprint Goal.

Elara knew she needed to talk to Liam, but she wasn't sure how to approach it. 'Is Liam demotivated?', 'Perhaps he's dealing with a personal issue?', 'Has he grown tired of the team?' — these questions swirled in her mind. This situation wasn't just affecting Liam; it was starting to impact the entire team's morale and productivity. As a Scrum Master, approaching such situations without judgment, understanding the context, and empowering the team was critically important.

As a Scrum Master, when you notice a dip in a team member's performance, your initial reaction might be to 'fix' the problem or 'hold the person accountable.' Phrases like 'Liam, why aren't you finishing your tasks?', 'You need to try harder.', or 'You're jeopardizing the team's goals.' — even if well-intentioned — often backfire.

Such direct and judgmental approaches:

Create Defensiveness: The individual feels blamed and becomes defensive, making it harder to uncover the real reasons.

Erode Trust: They weaken the trust relationship between the Scrum Master and the team member. The person might choose to hide their struggles rather than share them.

Miss the Real Issue: The underlying causes of performance decline (insufficient tools, overwhelming workload, personal difficulties, team dynamics, etc.) remain unexplored.

Diminish Team Accountability: Placing the problem solely on an individual ignores the team's collective role and responsibility in the situation. According to Agile principles, the team is a self-managing unit and should collectively own its challenges.

Before speaking with Liam, Elara paused. She knew that if she started with 'Why are you doing this?', Liam would likely shut down, and she wouldn't learn the true issue. Practicing such conversations, finding the right words, and maintaining a non-judgmental approach requires practice.

Talking to a team member whose performance is declining is one of a Scrum Master's most delicate tasks. This situation is less about 'problem-solving' and more about 'understanding' and 'supporting.' The skills you need are the ability to observe without judgment, listen actively, and empower the team's capacity for self-management.

Adopting a coaching approach best reflects the Scrum Master's role. This means helping the individual find their own solutions, creating space for them, and protecting the overall health of the team. The goal is not to 'fix' the individual, but to understand the situation with them and support them in contributing effectively as part of the team.

This approach focuses on discussing the impact of behavior, not the behavior itself. It highlights the consequences of actions rather than speculating on intentions. This preserves the individual's dignity and fosters a culture of transparency and trust within the team.

Structuring your conversation with a team member experiencing performance decline will make it more productive for both of you. Here's a step-by-step framework:

1. Observe, Don't Assume:

Before the conversation, gather your concrete observations. Phrases like 'Liam was late to the last three Daily Scrums,' 'The 'User Registration Flow' task in the Sprint has been 'In Progress' for two days with no visible movement,' or 'He hasn't spoken in Retrospectives.' are verifiable facts that don't contain judgment. Avoid assumptions (e.g., he's demotivated, he doesn't care).

2. Initiate with Care:

Conduct the conversation in a private, calm environment and at an appropriate time. A beginning like 'Liam, do you have a few minutes? I'd like to chat with you briefly.' reduces tension. State your intention to be supportive upfront.

3. Share Observations, Not Judgments:

Start the conversation using 'I' statements and share your observations. Use phrases like 'I've noticed that...', 'It seems to me that...', 'What I've observed recently is...'. For example: 'Liam, I've noticed you've been late to the last few Daily Scrums, and I see that the 'User Registration Flow' task in the Sprint hasn't progressed.'

4. Listen Deeply:

After sharing your observations, remain silent and allow Liam to speak. Practice active listening: don't interrupt, ask clarifying questions ('What are your thoughts on this?', 'How is this affecting you?'), and summarize what they've said to show you understand. Sometimes, all they need is to be heard.

5. Explore and Empower:

Once you understand Liam's perspective, use coaching questions to explore the situation more deeply. Questions like 'What do you think are the impacts of this situation on the team?', 'Is there an underlying reason for this?', 'How can we support you with this?', 'What steps are you considering to address this?' encourage the person to find their own solutions and take ownership.

6. Define Next Steps Together:

Allow Liam to propose his own solutions. If he struggles, you can offer options (e.g., 'Perhaps we could re-evaluate your workload?', 'Would you like to ask your teammates for support?'). Agree on a mutual action plan and clarify when and how this plan will be followed up.

7. Reinforce Team Accountability:

Remember that this is not just Liam's problem, but the team's problem. In team events like the Sprint Retrospective, bring up the topic with general questions (without singling out Liam), such as 'What are your thoughts on the challenges we faced completing tasks in the last Sprint? What could we do differently?' This strengthens the team's self-management and problem-solving capabilities.

Here are some phrases Elara might use in her conversation with Liam:

Starting the Conversation:

"Liam, do you have a moment? I'd like to chat briefly. My intention is to support you and ensure everything is going well."

Sharing Observations:

"I've noticed you've been late to the last few Daily Scrums, and I see that the 'User Registration Flow' task in the Sprint hasn't progressed. I wanted to talk about how this might be affecting you and the team."

"Last week, I observed you were quiet in the Retrospective, where you're usually very active. Is everything okay?"

Listening and Understanding:

"What are your thoughts on this?"

"Is there an underlying reason for what you're experiencing?"

"How does this situation make you feel?"

"If I understand correctly, you're feeling a lot of pressure right now and struggling to complete some tasks. Is that right?"

Solution-Oriented Questions:

"What do you think are the impacts of this situation on the team?"

"How can we support you with this?"

"What steps are you considering to improve this situation?"

"How might your teammates be able to help you?"

"What do you think about us reviewing your workload for the upcoming Sprint?"

Managing such sensitive conversations effectively requires experience and practice. Practicing with real-life scenarios is one of the most effective ways to develop these skills.

A difficult conversation with a team member experiencing performance decline, when approached correctly, can be an opportunity for growth not just for the individual, but for the entire team. Your role as a Scrum Master is not to judge or fix, but to observe, listen, coach, and empower the team's self-management and problem-solving abilities.

Remember, every individual is different, and every situation is unique. Be flexible, remain empathetic, and always focus on preserving the health of the team as a whole and its commitment to Agile principles. Developing these skills will not only make you a better Scrum Master but also a more effective leader and human being.