There is a widespread and deeply mistaken belief that psychological safety and the demand for results are incompatible. According to this view, a team where people feel safe to speak up and make mistakes would be a soft, undemanding team where nobody is held accountable. And conversely, a results-driven team would have to give up its members' comfort. It is a false dilemma, and holding on to it causes real harm to teams.
The Starting Misunderstanding
The confusion stems, in part, from a misunderstanding of what psychological safety is. Many people interpret it as a friendly environment where nobody feels uncomfortable, nobody receives criticism, and everyone agrees. With that definition, it is easy to see why it seems to clash with high standards. But that definition is wrong.
Amy Edmondson, the researcher who coined the concept in organizational settings, defines it differently. Psychological safety is the shared belief that the team is a safe space for taking interpersonal risks, such as admitting a mistake, asking for help, disagreeing, or raising a doubt, without fear of humiliation or punishment. It has nothing to do with the absence of demands. It has to do with the absence of fear of the social consequences of being honest.
Seen this way, psychological safety is not the opposite of accountability. It is the condition that makes accountability work well. On a team where telling the truth is punished, people hide problems, cover up mistakes, and stay silent about disagreements, which is exactly what prevents real accountability.
The Two Axes That Almost Everyone Merges Into One
Edmondson's clearest contribution to this debate is showing that psychological safety and demanding standards are two independent axes, not the ends of a single line. And because they are independent, they can combine in four different ways.
When there is little safety and little demand, the team falls into apathy. Nobody cares much, nobody dares to say anything, and the team simply does the minimum. When there is a lot of safety but little demand, the team drifts into a pleasant but unproductive comfort zone, where people feel at ease but not much gets accomplished. This is the soft team that critics of psychological safety fear, and its problem is not too much safety but too little demand.
When there is a lot of demand but little safety, the anxiety zone appears. People feel enormous pressure to perform, but because they are afraid, they hide problems instead of solving them, do not ask for help when they need it, and do not flag risks until they blow up. It is an environment that burns people out and, paradoxically, performs worse than its pressure would suggest.
Only when a lot of safety and a lot of demand coincide does the zone of learning and high performance emerge. There, people dare to take on ambitious challenges precisely because they know they can make mistakes, ask for help, and tell the truth without being punished. Safety does not lower the bar; it makes high standards sustainable.
Why They Need Each Other
It is worth looking at why these two things not only coexist but reinforce each other.
Accountability without safety degrades into fear. When demanding results is not accompanied by safety to be honest, people learn to protect themselves. They dress up the real state of things, hide mistakes until it is too late, and avoid the risks that would be needed to achieve something great. The organization believes it is being demanding, but in reality it is manufacturing opacity. Problems do not disappear; they just become invisible until they explode.
Safety without accountability, on the other hand, degrades into complacency. An environment where anything goes and nothing is expected may be pleasant, but it does not help anyone grow or achieve results. Psychological safety does not mean not holding people to account; it means being able to do so without destroying the person.
The combination of both produces something valuable and hard to achieve: teams that can have tough conversations about their work without those conversations turning into personal attacks. You can say "this is not up to standard and needs to be redone" in an atmosphere of respect, and that sentence, said with both safety and high standards, helps people grow instead of freezing them.
The Role of the Leader
Building this combination is not automatic, and it falls largely on whoever holds authority, because their behavior defines what is safe and what is expected.
Edmondson points out that leaders build psychological safety above all through how they react when someone takes an interpersonal risk. If the first time someone admits a mistake they are humiliated, the message sinks in across the whole team and silence sets in. If, on the other hand, that mistake is met with curiosity and treated as an opportunity to learn, the door to honesty opens. At the same time, maintaining high standards means not letting mediocre work slide out of fear of causing discomfort, but expecting the best from each person and saying so clearly.
The combination demands something that seems contradictory from the leader: being very demanding and very human at the same time. Kim Scott framed this in the context of feedback as the combination of caring personally about the person and challenging them directly on their work, two things many people believe are opposites but which in fact strengthen each other. You can be tough on the problem and gentle with the person at the same time.
The Context of AI: New Reasons to Need Both
The arrival of artificial intelligence gives this balance renewed relevance, for two reasons worth keeping in mind.
The first has to do with safety. AI is generating a quiet anxiety in many teams about the future of their own work and their own competence. In an environment without psychological safety, that anxiety is hidden, and with it, the legitimate doubts about when AI gets things right and when it gets them wrong. A team that fears looking incompetent for not mastering the latest tool will not say out loud that a generated result seems doubtful to them, and that silence is dangerous.
The second has to do with accountability. When part of the work is produced by a machine, there is a temptation to dilute accountability into the tool, to say the error was made by the AI. Keeping accountability means that a person continues to answer for what the team delivers, no matter who or what generated it. The combination of safety to question the machine's output and accountability for what is ultimately delivered is exactly what a team needs to work well with AI. Without safety, nobody questions the machine. Without accountability, nobody answers for it.
The idea that you must choose between a safe team and a demanding team is one of those false dilemmas that do so much damage precisely because they sound sensible. The reality, backed by research and experience, is the opposite: both are needed, and the teams that truly perform over time are the ones that cultivate them together.
Perhaps the best way to check where your team stands is to ask two questions at once. Can people tell the truth, admit mistakes, and disagree without fear? And at the same time, is each person expected to do their best, with mediocre work not being allowed to slide? If the answer to both is yes, you are in the difficult but valuable zone where learning happens. If it is yes to only one, you know what to work on.
And in your team? Which of the four zones would you say you are in, and what would it take to move toward the zone of learning?
Bibliography
- Duhigg, C. (2016). Smarter Faster Better: The Secrets of Being Productive in Life and Business. Random House.
- Edmondson, A. C. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350-383.
- Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
- Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass.
- Rozovsky, J. (2015). The five keys to a successful Google team. re:Work, Google.
- Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press.
Comments (0)
Log in to your Scrum Manager area to comment