1. en
  2. pl
03 June 2026

Articles

Why the team that isn't afraid cooks better

A fear-based kitchen is not a tougher kitchen. It is a kitchen where problems hide deeper — until the moment they become impossible to conceal. Which usually means mid-service, full covers, and no time to fix anything.

 

The experiment

Amy Edmondson began her research on psychological safety in hospitals. She was trying to understand why some medical teams reported higher rates of errors. The intuitive hypothesis: better teams make fewer mistakes. The result was the opposite. Teams with higher psychological safety reported more errors — not because they made more, but because they felt safe enough to say so. Cultures of high psychological safety didn't produce fewer mistakes. They produced more visible mistakes — and could therefore fix them.

This finding, published in 1999 in the Administrative Science Quarterly, became one of the most widely cited in organisational psychology. Its implication is direct and rarely discussed in a hospitality context: the culture of a work environment determines what is visible — not what is happening. In a kitchen that punishes mistakes, mistakes don't stop. They go underground.

 

How fear works

Consider a typical sequence of events in a low psychological safety kitchen. A junior cook preparing mise en place notices the eggs have run out. The head chef is focused at the pass and clearly doesn't want to be interrupted. Last time someone interrupted with information about a missing product, they received a public reprimand in front of the brigade. The junior cook decides to wait, improvise, or simply say nothing — because the risk of speaking feels higher than the risk of silence. The result: the problem surfaces mid-service, when there is no time to solve it.

This sequence is not an anecdote. It is a description of the systemic logic of low psychological safety environments, documented in Edmondson's research and replicated across hundreds of organisational contexts. In hospitality, it manifests in four concrete, measurable ways.

 

  • Problems surface too late

    A food safety incident, a quality failure, an allergen error — detected at the table instead of at the pass. The cost of late detection is always higher than the cost of early flagging. In a fear environment, the risk calculation favours silence.

    Signal: a server who doesn't ask about allergens because "the head chef doesn't like questions" is a high-risk environment — regardless of how good the food is.

  • Learning stops

    In a fear-based environment, mistakes are hidden rather than examined. The same mistake recurs because no one is willing to be the person who says "here is what went wrong." Post-service debrief becomes a ceremony of avoidance, not a tool for improvement.

    Signal: every post-service brief ends the same way — "all good, see you next service." Or by identifying one person as responsible without examining the system.

  • Initiative disappears 
    The team member who might have suggested a better approach, spotted an opportunity, or flagged a problem before it became one — goes quiet. The operational intelligence of the entire brigade flows only through the head chef's decisions, which is always a narrower channel than necessary.
    Signal: the last time someone on the team proposed a change on their own initiative — when was that?

  • Retention collapses

    People don't leave high-standard environments. They leave fear-based ones. Hospitality turnover research consistently identifies fear-based management as a primary driver of voluntary exits — particularly among the most capable team members, who have the most options.

    Signal: the ones who leave first are usually the ones you can least afford to lose.

 

Psychological safety

Before moving to practice, it is worth being precise about the term — because it is frequently misunderstood.

Psychological safety is not comfort. It is not a kitchen without demands, where every mistake is explained by circumstances and standards are flexible. It is not the absence of pressure or consequences for poor quality.

Edmondson's definition is precise: psychological safety is the shared belief that the team is safe for interpersonal risk-taking — that speaking up about a problem, a mistake, an uncertainty, or a missing product will not result in humiliation, exclusion, or informal consequences.

High standards and psychological safety are not in conflict. They are mutually enabling conditions. Standards can only be consistently maintained when people can report their violations in real time, without cost. Without that mechanism, standards exist on paper and in the head chef's presence — and cease to exist at every other moment.

 

How to build psychological safety 

Google's Project Aristotle (2016) — one of the largest studies of team performance in corporate history — identified psychological safety as the single strongest predictor of high team effectiveness. Stronger than individual talent, stronger than process quality, stronger than the clarity of goals.

Nembhard and Edmondson (2006) showed that the key mechanism for building psychological safety is what they call "leader inclusiveness" — behaviours that actively signal that everyone's input is welcome and that the interpersonal risk of speaking up is safe.

In a hospitality operational context, this translates to three concrete managerial behaviours.

Modelling fallibility from the top. When the head chef or floor manager publicly acknowledges their own mistake — "I miscalculated the prep time, here's how we adjust" — they change the risk calculation for everyone below them. If the most experienced person in the room can be wrong without consequence, it becomes safer for everyone else to be wrong too. This is not weakness. It is one of the most powerful leadership acts available to a hospitality manager.

Responding to bad news with curiosity rather than punishment. The server who tells you the table is unhappy before the guest asks for the bill is giving you an operational gift. The cook who flags the problem at the pass is doing exactly what you need. Your response to that information determines whether you will ever receive it again. "Tell me what you noticed" produces more information over time than any standard you can impose.

Creating a consistent space for honest debrief. Not a blame meeting. A brief, structured conversation after service: what worked, what didn't, what we'd do differently. Not who was responsible — but what the system produced. Frazier and colleagues (2017), in a meta-analysis of psychological safety research, showed that regular structured debriefing is one of the strongest interventions for building psychological safety over time — even in environments with high baseline levels of fear.

 

Conclusion

A high psychological safety environment is a high-standards environment — with the difference that standards are maintained through engagement rather than fear. That difference is operationally significant: engagement scales and sustains without supervision. Fear requires constant presence and escalation.

A kitchen that shouts its standards produces results in the head chef's presence and degradation in their absence. A kitchen that builds psychological safety produces something no control system can replicate: people who want to get it right — and who know they can say something when it isn't.

 

 

 

References

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. Wiley.

Google. (2016). Re:Work — Guide: Understand team effectiveness. https://rework.withgoogle.com

Frazier, M. L., Fainshmidt, S., Klinger, R. L., Pezeshkan, A., & Vracheva, V. (2017). Psychological safety: A meta-analytic review and extension. Personnel Psychology, 70(1), 113–165.

Nembhard, I. M., & Edmondson, A. C. (2006). Making it safe. Journal of Organizational Behavior, 27(7), 941–966.

 

 

 

 

Opening times

Monday - Friday 9 -17

Address

Shrewsbury

United Kingdom 

Contact

07925603011

jan@baldconsulting.co.uk