Community
Automatic translation
24 Oct 2025 | Jorge Sánchez López
Is everything "going great"... but you're not delivering value? Let's talk about servant leadership in Scrum: courage for difficult conversations, useful feedback, and a focus on outcomes, not on "good vibes". How to detect toxic positivity and replace it with practices that protect the team and the value.****
Is your leader saying "everything is going great", but you've gone three consecutive sprints without delivering real value? Do they reframe every failure as a "learning opportunity" without analyzing the causes? Do they ask you to keep the energy positive when what you really feel is exhaustion?
It's possible you don't have a servant leader. It's possible you're experiencing toxic positivity.
The 2020 Scrum Guide describes the Scrum Master as a true leader who serves the Scrum Team and the organization. Servant leadership, a concept developed by Robert Greenleaf in the 1970s, is based on putting the needs of the team first, facilitating people's development, protecting them from external interference, empowering them, and listening with active empathy.
This approach is fully aligned with the five Scrum values: commitment, courage, openness, respect, and focus. It is also grounded in the three pillars of empiricism: transparency, inspection, and adaptation. Servant leadership does not seek to make everyone feel good all the time, but to create the conditions for genuine team growth and the delivery of real value.
Toxic positivity emerges when we interpret servant leadership as "avoiding the uncomfortable". Some examples:
The "always positive" trap Servant leadership: "We're concerned about the quality problems we've been having. Let's analyze the causes so we can improve." Toxic positivity: "Let's not obsess over quality. What matters is that we're learning. Let's keep the energy up!"
Avoiding constructive conflict A servant leader facilitates difficult conversations. One who emits toxic positivity avoids them systematically "so as not to harm the atmosphere". Result: problems pile up and explode.
False empowerment Servant leadership: "Have you already decided how to tackle this phase? What do you need?" Toxic positivity: "Cheer up and go for it!" (without real support).
On the leadership side: They avoid conversations about problems because they "could be negative" They reframe failures without analyzing the real causes The team has stopped reporting problems because they know they'll get an "everything is fine" response There are no honest conversations about performance Feedback is always positive, even when there are clear areas for improvement
On the team side: Any frustration is immediately redirected toward "the positive" Real problems are minimized or ignored A forced "everything is fine" atmosphere that doesn't reflect reality They don't receive specific, constructive feedback They can't show vulnerability or admit difficulties Fundamental differences
Servant leadership: Embraces the full human experience: successes and failures, positive and negative emotions Facilitates difficult conversations in safe spaces Provides balanced feedback: recognizes strengths and points out specific areas for improvement Protects from external toxicity, not from accountability Empowers with support: grants autonomy and provides resources and guidance
Toxic positivity: Accepts only the "positive"; minimizes any difficulty Avoids conflict to "keep harmony" Only validates; positive feedback even when it isn't useful Overprotects, including from natural consequences "Sells" empowerment without support: "you can do it" (without resources)
The recently published Scrum Guide Expansion Pack 2025 (June 2025), co-authored by Jeff Sutherland, reinforces this vision. It introduces the concept of "Definition of Outcome Done", differentiating it from "Definition of Output Done" (finished deliverable). This marks a key distinction: delivering is not the same as generating value.
The Expansion Pack emphasizes the professionalization and accountability of Scrum roles, reinforcing that the Scrum Master must act as an agent of organizational change, not as a cheerleader. It recognizes leadership as resilient, systemic, and based on critical thinking, incorporating approaches such as Lean Thinking, Systems Thinking, Cynefin, and First Principles Thinking.
The complete feedback framework: Situation + behavior + impact + support.
Example: "In yesterday's demo (situation), you explained the features clearly (behavior). The client clearly saw the value (impact). For the next demo with security modules, if you agree, we could practice together how to handle difficult technical questions (support)."
The "yes, and..." technique instead of "yes, but..." Counterexample: "Yes, it's a problem, but look at the positive side..." Example: "Yes, it's an important problem and we need to find the solution. Can I help you with anything?"
Regular calibration conversations: "Do we agree it's fine to talk openly about any problem?" "Are there situations we're ignoring?"
The reality test: "Does this response address the problem or minimize it?" "Does this decision address the problem or avoid my discomfort?"
The sprint that failed due to … Toxic positivity: "It's fine. It's not a failure but a learning opportunity. What matters is keeping the energy positive." Servant leadership: "We didn't achieve what we expected. We need to find out why: technical problems, scope, external interruptions? We need to find the causes and get the resources or changes needed so it doesn't happen again."
Team member with performance problems due to … Toxic positivity: "I know you've had problems lately, but you're important to the team. I'm sure it's temporary and it will get better." Servant leadership: "The sprint tasks have taken longer than planned and were delivered with errors. I'm worried, because I know you can do this well. What's going on? Do you need any tools, a rethink of interruptions, or anything else? Is there something personal we can accommodate?"
Servant leadership requires emotional courage: the ability to create spaces for honest conversation and to give constructive feedback. It is not about choosing between being "nice" or being "effective", but understanding that being truly servant-minded requires honest conversations, clear boundaries, and knowing when to protect and when to challenge.
Transparency, inspection, and adaptation—the pillars of empiricism—only work when there is the courage to look at reality as it is. And that courage, one of the five Scrum values, is incompatible with forced positivity.
If you have a leadership role, ask yourself: Am I a coach or a cheerleader? Do I help the team grow, or do I make optimism an obligation?
The goal is not to make everyone feel good all the time, but to create the conditions for everyone's growth and contribution.
Based on the 2020 Scrum Guide and the Scrum Guide Expansion Pack 2025, grounded in empiricism, Scrum values, and Robert Greenleaf's servant leadership.
If you've made it this far, let me introduce myself: I'm Jorge Sánchez López and I've spent years in the trenches helping companies evolve, discovering surprising and counterintuitive truths about what really works.
If you want to talk about the topic or simply get to know each other, it's up to you. Shall we talk?
This topic has no comments.