"We don't want the team to get complacent." It is one of the most frequent objections when we talk about psychological safety in organizations. There is a widespread belief that creating psychologically safe environments means lowering the bar, avoiding conflict, and turning teams into spaces where no one questions anything for fear of "hurting sensibilities." This confusion has generated resistance to one of the most decisive factors of high performance.
Is it possible to build teams that are both demanding and psychologically safe? Not only is it possible: it is the only sustainable way to achieve excellence.
The confusion between psychological safety and comfort has a real cost. Amy Edmondson, professor at Harvard Business School and the leading researcher on this concept, warns about it: psychological safety is not about being nice or lowering standards. It is about giving people with different perspectives the freedom to speak candidly (Edmondson, 1999).
When Edmondson began her research in the 1990s by studying medical errors, she discovered something counterintuitive: the best teams reported more errors than low-performing teams. Not because they made more mistakes, but because they had created an environment where it was safe to acknowledge them and learn from them. The lowest-performing teams simply swept their mistakes under the rug.
This distinction is fundamental. Psychological safety does not eliminate demands; it eliminates the fear that prevents improvement. It means creating a climate where people can take interpersonal risks without fear of negative consequences for their image, status, or career.
What is psychological safety, really?
Edmondson (1999) defines psychological safety as "a shared belief held by members of a team that the team is safe for interpersonal risk-taking." These risks include:
- Admitting mistakes or gaps in knowledge.
- Asking questions that may seem "basic."
- Proposing unconventional ideas.
- Challenging the status quo or the decisions of superiors.
- Requesting feedback or help.
Project Aristotle at Google analyzed 180 teams over several years to identify what made some of them high-performing and others not. The main finding was clear: psychological safety was the most important factor, above team composition, individual skills, or organizational structure (Rozovsky, 2015).
But here is the nuance that many organizations overlook: the teams with high psychological safety in Google's study also had high standards. They were not complacent teams. They were teams that combined the ability to question with a demand for excellence.
The four-quadrant model
To understand this apparent paradox, Timothy Clark proposes in The 4 Stages of Psychological Safety a useful framework that distinguishes between psychological safety and performance standards. When we cross these two variables (high/low psychological safety and high/low standards), we get four types of cultures:
- Low psychological safety + low standards: culture of apathy. Nobody takes risks because it isn't worth it. The bar is so low that it doesn't matter much either.
- High psychological safety + low standards: comfort culture. This is the one that generates the initial objection. Pleasant teams where everyone gets along, but without real ambition or demands.
- Low psychological safety + high standards: culture of anxiety. The most toxic. A lot is demanded, but no one can admit they don't know something or need help. People hide problems until they explode.
- High psychological safety + high standards: learning culture. The quadrant we should aspire to. Excellence is expected, but the support and candor needed to achieve it are provided.
The key is to understand that psychological safety is not the vertical axis of this matrix. It is not a matter of choosing between safety or demands. It is about building both simultaneously.
How psychological safety strengthens demands
Far from weakening standards, psychological safety makes them achievable in a sustainable way. Let's see how:
- More honest and frequent feedback. In teams with low psychological safety, feedback is postponed until formal evaluations, when it is already too late to correct course. In psychologically safe teams, feedback is an ongoing conversation. Psychological safety allows direct challenge without it being perceived as a personal attack.
- Experiments and rapid learning. Organizations that encourage systematic experimentation consistently outperform their competitors. But experimenting requires accepting that many experiments will fail. Without psychological safety, teams stop proposing experiments or only propose those with guaranteed success, eliminating precisely the potential for learning.
- Transparency about real problems. High-performing teams have a culture where it is safe to admit problems early. This allows them to be resolved while they are still small, instead of being discovered in production or in external audits (Forsgren et al., 2019).
- Productive debate on important decisions. Teams that tolerate dissent make better decisions. But tolerating dissent requires psychological safety. Without it, people practice self-censorship and the team loses valuable perspectives.
Three antipatterns that destroy the equation
When organizations try to create psychological safety without understanding what it really is, they often fall into predictable traps:
- Antipattern 1: confusing safety with the absence of conflict. Some teams interpret psychological safety as "here we all get along and never argue." Lencioni, in The Five Dysfunctions of a Team, identifies precisely this as a dysfunction: the absence of productive conflict. Healthy teams have intense disagreements about ideas while maintaining respect for people.
- Antipattern 2: not giving direct feedback for fear of "damaging psychological safety." Psychological safety does not mean avoiding difficult conversations. It means having them in a way that the person knows the feedback comes from respect and a genuine desire to help them grow.
- Antipattern 3: tolerating systematic underperformance. If someone consistently fails to meet the team's standards and there are no consequences, the psychological safety of the rest of the team erodes. Why? Because other members see that their effort doesn't matter or that they will have to compensate indefinitely for someone else's low performance. Psychological safety requires fairness: clarity about what is expected and consistency in how gaps are managed.
- Antipattern 4: using "psychological safety" as an excuse to avoid unpopular decisions. In these contexts, any action that might cause emotional discomfort is automatically perceived as a threat to the team's safety. The result is a dangerous drift toward inaction. Roles that clearly aren't working are not changed. The scope of unviable initiatives is not reduced. Persistent underperformance is not addressed. People are not removed from the team when the situation requires it. Everything gets stuck under an apparently ethical argument: “we don't want to damage psychological safety.” The problem is that this is not psychological safety; it is conflict avoidance disguised as care.
Building the right quadrant: concrete strategies
So how do we create that space where demands and safety are possible at the same time?
- Define clear, co-created standards. Ambiguity about expectations is the enemy of both safety and demands. The best teams take time to explicitly define what "excellence" means in their context. Not as an imposition from above, but as a conversation in which those who will do the work participate. This includes definitions of "done," quality criteria, working agreements, and collaboration expectations.
- Model vulnerability from leadership. Edmondson (2018) insists that psychological safety starts with those who hold the most formal power. When a leader admits they don't know something, that they made a mistake, or that they need the team's help, they establish that these behaviors are acceptable. It is not about pretending to be incompetent, but about authentic humility regarding the limits of individual knowledge.
- Separate the person from the behavior or result. There is a fundamental difference between "this design decision caused performance problems that we need to solve" and "you are a bad developer." The first is safe and demanding. The second is unsafe and destructive.
- Create structures for productive dissent. It is not enough to say "you can disagree here." Many people won't dare to without explicit structures that facilitate it. Some useful practices:
- Pre-mortems: before an important decision, the team imagines that it has failed and analyzes what could have gone wrong.
- Rotating devil's advocate: someone has the explicit responsibility of challenging the proposal.
- Temporal separation between divergence and convergence: first we generate options without judging, then we evaluate them.
- Celebrate learning as much as success. If we only celebrate when everything goes well, we are encouraging problems to be hidden. Psychologically safe teams have rituals for sharing what they learned from what didn't work.
- Manage underperformance directly and respectfully. When someone is not meeting the team's standards, the conversation should happen early and clearly. The model of difficult conversations by Stone, Patton, and Heen in Difficult Conversations proposes separating three aspects: what happened (observable facts), how we feel about it (emotions), and what it means about the relationship or identity (the most delicate conversation). Addressing all three with honesty is compatible with maintaining psychological safety.
The role of the Scrum Master and the leader
In Scrum contexts, the Scrum Master has a particular responsibility for cultivating psychological safety. Not as the "protector of the team against reality," but as a facilitator of difficult conversations that otherwise would not happen.
Some teams misinterpret the concept of a self-managing team, thinking it means "no one can question the team." The reality is the opposite: truly self-managing teams constantly question themselves. The Scrum Master helps those questions be productive, not destructive.
In retrospectives, for example, a common antipattern is that they become sessions where no one mentions real problems for fear of "pointing fingers." An effective Scrum Master creates structures that allow systemic problems to be discussed without making them personal. Techniques such as "Mad, Sad, Glad" or "Sailboat" help externalize problems, making them safer to address.
Systemic limitations
Not everything is within the reach of the team or the Scrum Master. If the organization has a punitive culture toward mistakes, it will be difficult to create psychological safety in an isolated team. If individual incentives are designed to encourage internal competition, real collaboration will be hard to achieve.
Ron Westrum, in his research on organizational cultures (2004), identifies three types: pathological (power-oriented, information as a weapon), bureaucratic (rule-oriented, information as a nuisance), and generative (mission-oriented, information as a vital resource). Psychological safety flourishes in generative cultures, but has to fight against the current in the other two.
Does this mean it isn't worth trying if we don't control the entire organization? No. It means we must be aware of our sphere of influence. As agile coaches, we can create pockets of psychological safety within teams, knowing that they will have limits in organizations with broader toxic cultures. And sometimes, the honest answer for a professional in that situation is to consider whether the organization deserves their energy in the long term.
The productive tension
Let's return to the initial question: can we have demanding and healthy teams? Not only can we: demands without psychological safety are unsustainable, and safety without demands is a waste of potential.
The tension between the two is not a problem to solve, but a paradox to manage continuously. The best teams move along that tightrope, constantly adjusting. There are moments when they need to tip the balance toward demands (a critical delivery, a commitment to a client) and others when they tip it toward care (after an especially hard sprint, when someone on the team is going through a difficult time).
The skill lies not in eliminating the tension, but in making it explicit and navigating it as a team. Are we demanding enough of ourselves? Are we caring enough about people? These questions never have permanent answers.
Psychological safety is not a state you reach and maintain effortlessly. It is a daily practice that requires intention, structures, and, above all, consistency between what we say and what we do as leaders and as teams.
What tensions do you observe in your team between safety and demands? Are there difficult conversations that are not happening? What small practice could you introduce tomorrow to make it a little safer to tell the truth?
Bibliography
- Brown, B. (2018). Dare to Lead: Brave Work. Tough Conversations. Whole Hearts. Random House.
- Clark, T. R. (2020). The 4 Stages of Psychological Safety: Defining the Path to Inclusion and Innovation. Berrett-Koehler Publishers.
- Dweck, C. S. (2006). Mindset: The New Psychology of Success. Random House.
- Edmondson, A. C.
- (1999). "Psychological Safety and Learning Behavior in Work Teams". Administrative Science Quarterly, 44(2), 350-383.
- (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
- Klein, G. (2007). "Performing a Project Premortem". Harvard Business Review, 85(9), 18-19.
- Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass.
- Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press.
- Stone, D., Patton, B., & Heen, S. (2010). Difficult Conversations: How to Discuss What Matters Most (2nd ed.). Penguin Books.
- Thomke, S. H. (2020). Experimentation Works: The Surprising Power of Business Experiments. Harvard Business Review Press.
- Westrum, R. (2004). A typology of organisational cultures. BMJ Quality & Safety, 13(suppl 2), ii22-ii27.
Comments (4)
Log in to your Scrum Manager area to comment
Jorge Sánchez López ★★★
25 Feb 2026 10:34Excellent reflection, especially because it dismantles a confusion I keep seeing constantly in organizations: believing that psychological safety lowers the bar when, in reality, it makes it possible to sustain that bar over time.
From my experience supporting transformations, the problem is usually not cultural at its origin, but a matter of system design. Many companies ask for transparency, learning, or direct feedback… yet they maintain evaluation structures, incentives, or leadership styles that penalize exactly those behaviors.
That's where the paradox appears: people talk about psychological safety, but the real context pushes them toward self-protection.
In my view, the key lies not only in building interpersonal trust, but in reducing what I call decision waste: when people stop saying what they see because the system turns the truth into a personal risk.
Mature teams are not the most comfortable ones, but those that can hold difficult conversations without breaking down as a system. And that, more than a soft skill, is organizational architecture.
Great contribution to opening this debate
Excelente reflexión, especialmente porque desmonta una confusión que sigo viendo constantemente en organizaciones: creer que la seguridad psicológica reduce la exigencia cuando, en realidad, hace posible sostenerla en el tiempo.
Desde mi experiencia acompañando transformaciones, el problema no suele ser cultural en origen, sino de diseño del sistema. Muchas empresas piden transparencia, aprendizaje o feedback directo… pero mantienen estructuras de evaluación, incentivos o liderazgo que penalizan exactamente esos comportamientos.
Ahí aparece la paradoja: se habla de seguridad psicológica, pero el contexto real empuja a la autoprotección.
Para mí, la clave no está solo en generar confianza interpersonal, sino en reducir lo que llamo desperdicio decisional: cuando las personas dejan de decir lo que ven porque el sistema convierte la verdad en un riesgo personal.
Los equipos realmente maduros no son los más cómodos, sino los que pueden sostener conversaciones incómodas sin romperse como sistema. Y eso, más que una habilidad blanda, es arquitectura organizativa.
Gran aporte al abrir este debate
Automatic translation · View original
Guest
25 Feb 2026 13:09I really enjoyed the article because it puts into words something I constantly try to work on in teams: psychological safety is not comfort, it is maturity.
From my experience and my point of view leading technology, I am clear that teams need tension. But not tension born of fear or excessive pressure, rather tension born of a shared challenge. It is a constructive tension that leads the team to question decisions, raise the technical bar, discuss solutions rigorously, and not settle for "if what we've done already works or is already good enough."
And that is only possible when psychological safety exists.
If a team member feels she cannot say something like "this won't scale," "this architecture is fragile," or "we're fooling ourselves with this estimate," then silence sets in. And silence in technology tends to be very costly (and I say this from experience).
For me, psychological safety is not lowering standards; it is creating the environment where standards can be truly high. It is being able to have uncomfortable conversations without them turning into personal attacks. It is demanding a lot, but also allowing people to make mistakes and learn quickly.
A healthy team is not one that avoids conflict, but one that knows how to manage it with respect and a focus on results.
And this is far from being "soft"; it is a deeply professional matter.
Me ha gustado mucho el artículo porque pone palabras a algo que intento trabajar constantemente en los equipos: la seguridad psicológica no es comodidad, es madurez.
Desde mi experiencia y mi punto de vista liderando tecnología, tengo claro que los equipos necesitan tensión. Pero no tensión desde el miedo o la presión desmedida, sino desde el reto compartido. Es una tensión constructiva que lleva al equipo a cuestionar decisiones, a elevar el nivel técnico, a discutir soluciones con rigor y a no conformarse con un "si lo que hemos hecho ya funciona o ya es bastante bueno".
Y eso solo es posible cuando existe seguridad psicológica.
Si una integrante del equipo siente que no puede decir algo como "esto no va a escalar", "esta arquitectura es frágil" o "nos estamos autoengañando con esta estimación", entonces aparece el silencio. Y el silencio en tecnología suele salir muy caro (y lo digo por experiencia).
Para mí, la seguridad psicológica no es rebajar estándares, es crear el entorno donde los estándares pueden ser realmente altos. Es poder tener conversaciones incómodas sin que se conviertan en ataques personales. Es exigir mucho, pero también permitir equivocarse y aprender rápido.
Un equipo sano no es el que evita el conflicto, sino el que sabe gestionarlo con respeto y foco en el resultado.
Y esto, queda muy lejos de ser "blando", es un tema profundamente profesional.
Automatic translation · View original
Scrum Manager ★★
2 Mar 2026 11:39Totally agree. Avoiding conflicts only causes problems on a larger scale that persist over time. And the longer they go on, the harder they become to address later.
Muy de acuerdo. Evitar conflictos solo trae problemas a mayor escala y que se perpetúan en el tiempo. Y a más tiempo, más difícil resulta atajarlos después.
Automatic translation · View original
David Boixadera Ortega
25 Feb 2026 13:11I really enjoyed the article because it puts words to something I constantly try to work on within teams: psychological safety is not comfort, it is maturity.
From my experience and my perspective leading technology, I'm clear that teams need tension. But not tension born of fear or excessive pressure, but tension born of shared challenge. It's a constructive tension that pushes the team to question decisions, raise the technical bar, discuss solutions rigorously, and not settle for "if what we've already done still works or is already good enough".
And that is only possible when psychological safety exists.
If a team member feels they can't say something like "this won't scale", "this architecture is fragile" or "we're fooling ourselves with this estimate", then silence sets in. And silence in technology tends to be very costly (and I say this from experience).
For me, psychological safety is not about lowering standards; it's about creating the environment where standards can be truly high. It's about being able to have uncomfortable conversations without them turning into personal attacks. It's about demanding a lot, but also allowing mistakes and learning fast.
A healthy team isn't one that avoids conflict, but one that knows how to manage it with respect and a focus on results.
And this is far from being "soft"; it's a deeply professional matter.
Me ha gustado mucho el artículo porque pone palabras a algo que intento trabajar constantemente en los equipos: la seguridad psicológica no es comodidad, es madurez.
Desde mi experiencia y mi punto de vista liderando tecnología, tengo claro que los equipos necesitan tensión. Pero no tensión desde el miedo o la presión desmedida, sino desde el reto compartido. Es una tensión constructiva que lleva al equipo a cuestionar decisiones, a elevar el nivel técnico, a discutir soluciones con rigor y a no conformarse con un "si lo que hemos hecho ya funciona o ya es bastante bueno".
Y eso solo es posible cuando existe seguridad psicológica.
Si una integrante del equipo siente que no puede decir algo como "esto no va a escalar", "esta arquitectura es frágil" o "nos estamos autoengañando con esta estimación", entonces aparece el silencio. Y el silencio en tecnología suele salir muy caro (y lo digo por experiencia).
Para mí, la seguridad psicológica no es rebajar estándares, es crear el entorno donde los estándares pueden ser realmente altos. Es poder tener conversaciones incómodas sin que se conviertan en ataques personales. Es exigir mucho, pero también permitir equivocarse y aprender rápido.
Un equipo sano no es el que evita el conflicto, sino el que sabe gestionarlo con respeto y foco en el resultado.
Y esto, queda muy lejos de ser "blando", es un tema profundamente profesional.
Automatic translation · View original