In 1999, Amy Edmondson set out to prove that the best hospital teams made fewer medication errors. The data said the opposite — the best teams reported more, not fewer. The behavior was the signal, not the count, and that single finding became the foundation of psychological safety as a discipline. This article defines the term, traces the research from Edmondson through Google's Project Aristotle in 2015, and explains why most modern attempts to measure it — annual surveys, eNPS, engagement scores — fail at the thing they claim to capture.
What is psychological safety?
Psychological safety is the shared belief, held by members of a team, that the team is safe for interpersonal risk-taking. The term was defined by Amy Edmondson in her 1999 paper Psychological Safety and Learning Behavior in Work Teams, published in Administrative Science Quarterly. It is not a feeling of comfort or harmony. It is the structural condition that lets a colleague say "I think we are wrong about this," "I made a mistake," or "I do not understand," without expecting to be punished, ridiculed, or quietly sidelined.
The definition is interpersonal, not psychological in the clinical sense. It is about what a person can safely do in front of others, not what they feel privately.
Edmondson's full definition: "A shared belief held by members of a team that the team is safe for interpersonal risk-taking… a sense of confidence that the team will not embarrass, reject or punish someone for speaking up."
That precision matters. Psychological safety is not the same as trust, comfort, kindness, or harmony. It is the expectation that taking a small social risk — asking a basic question, admitting an error, raising a concern about a senior person's plan — will not cost a person their standing on the team.
Most popular treatments of the term collapse it into something broader: "psychological wellbeing," "feeling comfortable at work," general employee mood. Edmondson's original construct is narrower and more useful. It is the social cost of interpersonal risk, observed at the level of the team.
Why does psychological safety matter?
Because the team's ability to learn depends on it, and in 2015 Google demonstrated that the team's ability to perform does too.
Google's Project Aristotle was a multi-year internal study of 180 teams. The researchers expected to find patterns in seniority, tenure, gender mix, or sheer intelligence. They did not.
The single biggest differentiator was psychological safety.
"Psychological safety was far and away the most important of the five key dynamics we found — it's the underpinning of the other four." Google re:Work · Project Aristotle · 2015
Restated, the finding is sharper still: psychological safety is the single biggest differentiator between teams that perform and teams that don't. That restatement is the line we work from at tru.place. It is not Google's wording; it is the operational form of the same finding.
The Project Aristotle report was published on Google re:Work in 2015 and remains the most widely cited corporate replication of Edmondson's academic work. It also reframed the conversation. Psychological safety stopped being a soft HR topic and became a leading indicator for delivery, innovation, and retention.
When a team is psychologically safe, problems surface faster. Mistakes are caught earlier. Disagreement is processed in the meeting, not in the side conversations after it. When it is not, the costs are observable: delivery slips, quiet quitting, attrition that arrives "out of nowhere," and the slow erosion of judgment.
What did Amy Edmondson's 1999 research actually show?
Edmondson studied hospital teams to test a clean hypothesis: the better the team, the fewer medication errors it would report. The opposite was true.
The best teams reported more medication errors, not because they made more, but because the working environment made it safe to say "this happened, here is what we missed." Lower-performing teams reported fewer errors because the cost of reporting was higher. The errors still occurred. They simply went unreported, and therefore unlearned from.
"The best teams don't make fewer mistakes — they report more of them." Amy Edmondson · Administrative Science Quarterly · 1999
The finding produced a measurable construct. Edmondson built the seven-item Psychological Safety Scale, which remains the most widely used self-report measure in organisational research. The scale asks team members to rate statements such as "If you make a mistake on this team, it is often held against you" and "Members of this team are able to bring up problems and tough issues."
Two methodological notes matter for anyone using the scale today. First, it is a self-report, subject to social desirability bias and to the same psychological pressures it tries to measure. Second, it was designed for team-level analysis, not for individual diagnostics. The unit of measurement is the team, not the person.
Edmondson has since extended the work in The Fearless Organization (2018) and continued empirical research through the 2020s. The core claim, that interpersonal risk-taking is the substrate on which learning, innovation, and performance grow, has held up across more than two decades of replication.
How is psychological safety measured today?
The honest answer: poorly, in most companies. The standard methods — annual engagement surveys, pulse surveys, eNPS — share three structural weaknesses.
They measure opinion, not behavior. A respondent's answer to "I feel safe to speak up on my team" is filtered through mood, social desirability bias, fatigue, and the framing of every prior question. The behavior they actually exhibit on Tuesday at 11am — speaking up, asking for help, admitting confusion — is a more reliable signal.
They measure once or twice a year. By the time a quarterly engagement survey reaches HR, the data is months old. The team has moved on. The patterns that mattered have already produced their consequences.
They are not closed-loop. Employees fill in the survey. Nothing visibly changes. The next survey arrives. Response rates fall — below 40% within three months in most companies†. Once people stop trusting that their input will produce visible action, the data quality collapses.
The alternative is behavioral measurement: short, frequent, channel-native check-ins that capture what people actually do, not just what they say. The HR tech market, by and large, still measures self-report and calls the dashboard "data." The two are not the same thing — and the gap between them is exactly where attrition, burnout, and missed delivery hide.
Tatemae — what people show at work is not what they think
In Japanese, tatemae is the face one shows in public. Honne is what one actually thinks. The two are expected to differ, and in many social contexts the gap is functional and accepted.
Workplaces in every culture have their own version of tatemae. The polite answer in a one-on-one. The slightly upbeat response to "How is the project going?" on Slack. The careful phrasing in a channel where the manager is reading.
"What people show at work is not what people think at work. Most HR dashboards measure the show." tru.place
Most surveys measure tatemae. They ask employees what they think, and employees give a version of the answer that is safe to be seen. The dashboards then aggregate these answers into a score, and decisions are made on a number that is, by construction, the public face of the team rather than its private reality.
The closest observable proxy for honne is not asking again. It is reading behavior. Did the person speak up in the meeting? Did they ask a question that risked looking uninformed? Did they admit a mistake in front of the team? Did they push back on a senior colleague's plan?
These behaviors are visible. They are countable. They are far harder to fake than a 1–5 Likert response. And in aggregate, over weeks, they describe psychological safety more accurately than any single survey can.
This is the philosophical anchor of how tru.place measures psychological safety. Not by reading minds — by reading the behaviors that minds produce.
Six behaviors that predict psychological safety
In the SIGNAL™ Intelligence System — 5 layers · 6 nodes · 21 sub-clusters · 63 behavioral proxies — psychological safety is decomposed into six observable nodes. Each node represents a category of behavior that, when present, indicates a team is safe and, when absent, indicates risk.
The six nodes, by letter, name, and weight: