A team can be polite and still be unsafe.
People can nod through a bad plan, keep a mistake private, avoid challenging the senior person in the room and leave a meeting with the same concern they brought into it. The absence of visible conflict tells you very little about whether people felt able to say what needed saying.
Kylee Leota’s Genius Talk interview puts psychological safety in practical terms. She describes it as the ability to speak up without fearing that the act of speaking will threaten someone’s standing. In her examples, team members can challenge an idea, raise a problem and still leave the conversation with respect and trust intact.
That definition matters because psychological safety is often flattened into comfort. The interviews behind this synthesis point in a more demanding direction. Safety should make useful candor easier. It should create room for respectful challenge, difficult feedback and questions that expose uncertainty. Standards still have to be clear. Commitments still matter. Leaders still have to make decisions, and people still remain responsible for their work.
Google’s published Project Aristotle material provides a useful external reference point with a specific scope. In its study of team effectiveness at Google, the company identified psychological safety as the first of five important team dynamics, alongside dependability, structure and clarity, meaning, and impact. Google’s guide describes psychological safety around the perceived consequences of interpersonal risk. Leota references Project Aristotle in her own interview, but her broader leadership interpretation remains her own.
The scope matters. Project Aristotle studied teams inside Google, and Google’s own guide advises organizations to determine what makes teams effective in their own context. The research is useful here as a reference for the concept and for the connection between safety and clear team dynamics. It should not be used as a shortcut for claiming that one management formula will produce the same result everywhere.
A more useful management question asks whether people can contribute honestly while the team continues to expect strong work.
Psychological safety is about the cost of speaking
Most teams do not have a rule that says, “Do not raise problems.”
Silence is usually learned through consequences.
Someone watches a colleague get embarrassed for asking a basic question. A manager becomes defensive when a risk is mentioned. A dissenting opinion gets treated as disloyalty. A mistake becomes a public character judgment. The formal message may still encourage openness, but the social cost of openness has become clear.
Leota’s framing focuses on that cost. In her discussion of respectful challenge, the important feature is that an employee can disagree with an idea without feeling that the disagreement itself puts the job or relationship at risk.
That leaves plenty of room for rigor.
An idea can be rejected. A decision can go against the person who raised an objection. A performance problem can still be addressed. A team can hold a difficult standard and remain psychologically safer if the process protects the person’s ability to contribute honestly.
The opposite can also happen. A friendly team can become unsafe when people discover that only agreeable information travels upward.
This is why “we all get along” is a weak measure of psychological safety.
A better set of signals is behavioral:
Do people ask for help before a deadline collapses?
Can someone say they do not understand a decision?
Are weak assumptions challenged before execution?
Do junior people correct senior people when the facts are wrong?
Can a mistake be discussed without the conversation turning into humiliation?
Does a person who raises bad news get treated as the source of the bad news?
The answers reveal more than the mood of the meeting.
Safety does not require agreement
Daniel Murray’s approach to empathy helps separate understanding from agreement.
He treats empathy as an effort to understand another person’s perspective, including the motives, assumptions and incentives that may be shaping it. His “consciously curious” practice asks people to slow their own conclusions, park assumptions temporarily and ask enough questions to see the situation from the other side.
That is useful in a team disagreement because leaders often collapse two different questions:
Do I understand why this person thinks this?
Do I agree with the conclusion?
A psychologically safer conversation makes space for the first question without forcing the second answer.
This protects challenge from two common failures.
One is premature dismissal. The leader hears opposition and immediately defends the current plan, so the team learns that disagreement creates work without changing anything.
The other is false consensus. Everyone keeps softening the conversation until the actual conflict disappears from the language, even though the underlying disagreement remains.
Murray’s perspective-taking offers another route. Understand the reasoning. Test it. Ask what the person sees that others may be missing. Then make the decision.
Leota’s version of respectful challenge fits the same pattern. The quality of the discussion can improve precisely because people are allowed to contest an idea while maintaining respect for one another.
Safety, in this sense, supports productive disagreement.
Participation depends on more than an invitation
A leader can ask, “Any thoughts?” and receive silence.
That silence can mean many things.
Myriam Hadnes’s facilitation work is useful here because she pays attention to the conditions around participation. In her Genius Talk conversation, she discusses differences in hierarchy, comfort with silence, group interaction and perceived permission to speak when working across cultures. She also begins workshop design by speaking with participants before the session, because the sponsor’s stated need can differ from what the people in the room actually experience.
Her examples should be treated as context-sensitive observations, not fixed traits assigned to whole national or cultural groups.
The practical lesson is to stop assuming that one invitation creates equal permission.
A person may be willing to contribute in writing but reluctant to interrupt a senior colleague. Another may need more time before speaking. Someone may interpret open debate as welcome; someone else may read the same behavior through a different hierarchy or communication norm.
Psychological safety therefore has a design component.
Meeting leaders can vary how input is gathered. They can ask for written concerns before discussion, invite perspectives before revealing the senior leader’s preference, speak with participants in advance when the topic is sensitive, or create a deliberate pause so the fastest speaker does not define the room.
Hadnes’s facilitation approach also favors flexibility over a rigid agenda when the group reveals a different need than expected.
That matters because participation cannot be reduced to attendance.
People need a workable route into the conversation.
Leaders set the emotional cost of candor
The manager’s reaction to difficult information is one of the strongest signals a team receives.
A leader can say that mistakes are learning opportunities, then respond to the next mistake with visible contempt. The policy will lose.
A manager can ask for dissent, then spend twenty minutes proving every dissenter wrong. The invitation will stop working.
Leota’s examples make the leader’s behavior central because psychological safety is experienced through interactions, not declarations.
Angela Heise adds a useful dimension through her concept of emotional productivity. She describes it as being able to feel emotions, understand the needs around them, set boundaries and respond deliberately. She also rejects the idea that emotional intelligence requires a leader to become softer or less task-focused. That is Heise’s professional framework from the interview rather than an independently established organizational finding.
Her emphasis on boundaries is especially relevant to psychological safety.
A safe team does not require leaders to absorb every emotion, accept disrespect or avoid a difficult conversation because someone may become upset. Boundaries help define what constructive candor looks like.
People can be angry and still be responsible for how they speak.
A manager can acknowledge frustration without surrendering the performance standard.
A team can make room for emotion while keeping the discussion connected to the issue that must be solved.
This is a stronger model than treating safety as unlimited accommodation.
It asks both the leader and the employee to take responsibility for how the conversation happens.
Clear standards make candor more useful
Psychological safety becomes harder to apply when nobody knows what good performance means.
Matthew Person’s culture work provides a systems-oriented complement to the more interpersonal perspectives in these interviews. His Square Management System includes identity, instruction, intercommunication and information feedback. In his discussion of feedback, he focuses on how performance is measured, shared and used to improve both employees and the organization.
Person also describes what happens when onboarding, procedures or performance standards are missing. Frontline managers fill the gap with their own interpretations, which can create different operating rules across teams.
That is a standards problem before it is a feedback problem.
If two people receive criticism for the same behavior from different managers, the issue may be inconsistency in the system. If a manager calls for accountability but the expected result was never defined, the conversation begins with ambiguity.
Clear standards reduce that ambiguity.
They give the team something outside the manager’s mood to discuss.
The question becomes: What did we agree good work would look like? What happened? What information was missing? What needs to change next time?
This kind of clarity can make feedback feel more demanding and more fair at the same time.
People know the bar. They also know that raising a concern about the bar, the process or the feasibility of the work is allowed.
That combination is central to psychological safety with standards.
Feedback needs a loop, not a suggestion box
Inviting people to speak is only the first half of the system.
What happens after they speak determines whether they will do it again.
Person’s emphasis on information feedback is useful because it treats feedback as part of how an organization learns. Information has to move, performance has to be discussed and the system has to respond.
For psychological safety, that means leaders need a visible way to handle input.
Some concerns will lead to a change. Others will not. The team can remain safer in both cases if people can see that the issue was considered, the decision has a rationale and the person who raised it is not punished for doing so.
Silence from leadership creates its own interpretation.
If employees repeatedly raise the same problem and never hear what happened, “speak up” starts to sound ceremonial.
A stronger feedback loop has four moves:
- Receive the issue without immediate retaliation or ridicule. The first response teaches the team whether candor is expensive.
- Clarify what is being raised. Separate facts, assumptions, preferences, risks and emotional reactions.
- Decide or assign the next step. Make clear who will investigate, decide or act.
- Close the loop. Return with the outcome, even when the answer is that the original decision stands.
This is an editorial synthesis of the assigned interviews rather than a named guest framework. It combines Leota’s emphasis on safe challenge, Murray’s curiosity, Heise’s deliberate response and boundaries, and Person’s information-feedback logic.
The benefit is practical. Speaking up becomes connected to a process.
Accountability belongs inside the same system
The phrase “psychological safety” can create anxiety for leaders who hear it as a restriction on consequences.
The interviews support a different reading.
Leota’s version includes challenge in service of better work. Person’s system includes performance standards and feedback. Heise includes boundaries and deliberate response. Murray separates understanding from agreement.
None of those ideas requires a leader to pretend that missed commitments do not matter.
Accountability is easier to handle when three conditions are present.
First, the expectation was clear.
Second, the person had a safe way to raise a constraint, disagreement or uncertainty before the failure.
Third, the response focuses on the work, the decision and the next responsibility rather than turning the person into the problem.
If those conditions are missing, a manager should examine the system as well as the individual.
For example, a team member who misses a deadline after repeatedly warning that two priorities conflict is different from a team member who hides the risk until delivery day. A leader who treats both situations identically loses useful information.
Psychological safety helps surface that information sooner.
Standards tell the team what must still be delivered or renegotiated.
Accountability closes the gap between the two.
Mistakes reveal whether the team believes the message
A team’s stated commitment to psychological safety becomes visible when someone admits a mistake.
If the immediate response is ridicule, blame before diagnosis or a public display designed to make an example of the person, others learn to conceal uncertainty. If every mistake is waved away in the name of safety, the team learns something different: standards are negotiable when the conversation becomes uncomfortable.
The assigned interviews support a more useful sequence.
Leota’s safety principle protects the act of surfacing the problem. The person should be able to say what happened without the disclosure itself becoming a threat to their standing.
Murray’s curiosity helps the team understand the cause before choosing a response. Was the problem a judgment error, unclear information, a capability gap, a broken handoff, an ignored warning or a deliberate choice?
Heise’s emphasis on emotional responsibility matters next. Leaders can acknowledge frustration without letting their own reaction take over the conversation. Employees can own the effect of a mistake without being asked to accept humiliation as part of accountability.
Person’s standards and feedback logic then brings the conversation back to the operating system. What expectation applied? Was it understood? What should change in the process or in the person’s behavior? How will the team know the change happened?
This approach does not require every error to receive the same consequence. Context still matters. The useful discipline is to separate four things that often get tangled together: disclosure, diagnosis, accountability and improvement.
When those steps collapse into one emotional reaction, teams lose information.
When they remain distinguishable, a person can be held responsible while the organization still learns from what happened.
That is a practical example of safety and standards working together rather than competing for space.
Meeting design can make candor easier
Meetings are where many teams reveal their real rules.
Who speaks first?
Who can interrupt?
Whose disagreement receives curiosity?
Does the most senior person announce an answer before asking for input?
Are unresolved concerns recorded, assigned and revisited?
Hadnes’s facilitation approach suggests that leaders should pay attention to participation conditions instead of assuming that one meeting format works for everyone. Her use of participant interviews before workshops is one way to discover what may be blocking contribution. Her cross-cultural work also warns against treating silence or participation style as simple evidence of engagement or disengagement.
Germaine team practices can be built from the assigned sources without turning the meeting into a ritual.
A leader might circulate a decision question in advance so people can think before the call. Sensitive input can be gathered in writing before group discussion. The meeting can separate exploration from decision so people know when disagreement is still useful. Leaders can ask what risk the team may be underestimating before stating their own preferred answer. The facilitator can invite people who have not spoken without forcing them to disclose more than they want. The decision, owner and follow-up point should be explicit.
These practices are designed to keep valuable information from disappearing because the room rewarded speed, rank or confidence more than substance. Equal airtime is not the objective.
A practical operating standard for psychological safety
A team that wants psychological safety with accountability can make its expectations explicit.
The following operating standard is a synthesis of the assigned Genius Talk perspectives:
Raise risks early. Bad news becomes more expensive when people wait for certainty.
Challenge the work without degrading the person. Ideas, assumptions and decisions can receive strong scrutiny.
Ask before assuming. Use curiosity to understand why someone sees the issue differently.
Make the bar visible. Define outcomes, roles, decision rights and performance expectations.
Use more than one route for input. Spoken meetings should not be the only way concerns reach the team.
Respect boundaries. Candor does not grant permission for disrespect, forced disclosure or emotional dumping.
Respond to input. People need to know what happened after they raised an issue.
Keep responsibility intact. Safety makes it easier to discuss a problem; it does not erase ownership of the work.
A team can adapt the details, but the tension should remain visible.
Candor and standards need each other.
Psychological safety becomes credible when the team can use it under pressure
The real test arrives when the information is inconvenient.
A project is behind. A senior leader’s idea has a flaw. Someone made a mistake. A cultural difference is affecting participation. An employee disagrees with a decision that will still go ahead.
Leota’s work points toward respectful challenge. Murray adds perspective-taking without compulsory agreement. Hadnes shows why permission to participate is shaped by context and facilitation. Heise adds boundaries and emotional responsibility. Person supplies the standards and feedback infrastructure that keep safety connected to performance.
Google’s Project Aristotle material supports a narrower external point: psychological safety was identified as an important team dynamic in Google’s own team-effectiveness research. It does not turn every broader leadership recommendation in this article into a research finding.
The practical standard is more grounded.
People should be able to bring forward information the team needs, including disagreement and mistakes, without unnecessary interpersonal punishment. Leaders should make expectations and consequences clear enough that openness does not become vagueness.
A team with both can have harder conversations earlier.
That is where psychological safety starts to earn its place in serious work.
The aim is a team that can tell the truth sooner, examine it more carefully and still leave each person clear about what they are expected to do next. Safety becomes useful when it improves the flow of information without dissolving the responsibilities attached to the work.
Leaders can test this by watching what happens after the first difficult contribution. If the next person becomes more willing to add a concern, the room has learned something about the cost of candor. If everyone retreats, the leader has useful evidence about what still needs to change in the system.