Your team members are sitting on solutions to your biggest problems, but they’re keeping quiet because they don’t trust the environment enough to speak up.
This is the cost of missing psychological safety. Research from Google’s Project Aristotle found that psychological safety was the single most important factor in high-performing teams—more influential than individual talent, experience, or seniority. Without it, employees self-censor, avoid risk, and withhold the ideas that could move your business forward.
The good news: psychological safety isn’t something you inherit or get lucky with. It’s built deliberately through specific leadership behaviors and team practices. Here’s how to construct it in your organization.
Define What Psychological Safety Actually Means for Your Team
Psychological safety is the belief that you can take interpersonal risks without fear of embarrassment, rejection, or punishment. In practical terms, it means your team members feel comfortable admitting mistakes, asking questions that might seem obvious, proposing unconventional ideas, and giving feedback to senior colleagues.
This is not the same as being nice. Psychological safety can coexist with high standards, direct feedback, and accountability. In fact, the best teams separate the two: they maintain rigorous performance expectations while making it safe to fail in the pursuit of those goals.
Start by articulating what psychological safety means specifically in your context. What behaviors are you trying to encourage? What risks do you want your team to feel comfortable taking? A software engineering team might prioritize speaking up about code vulnerabilities early. A sales team might emphasize admitting when a prospect isn’t the right fit. Make it concrete.
Model Vulnerability and Admit Mistakes First
You cannot demand psychological safety from your team while projecting infallibility. The moment you acknowledge a mistake or admit something you don’t know, you signal that it’s safe for others to do the same.
This requires deliberate action. In team meetings, openly discuss decisions that didn’t work out and what you learned. When someone points out an error in your thinking, thank them specifically and explain how their input improved the outcome. When you don’t have an answer, say so directly instead of deflecting.
These moments are more powerful than any memo about culture. A manager at a financial services firm told their team, “I made a poor hiring decision last quarter. Here’s what I missed in the interview process and how I’m changing my approach.” Within weeks, team members began sharing their own failures and lessons learned without prompting.
Start small if vulnerability feels uncomfortable. You don’t need to share personal crises. Professional mistakes and knowledge gaps are enough to shift the dynamic.
Respond to Problems Without Blame
Your team is watching how you respond when things go wrong. If someone brings you a problem and your first instinct is to assign blame, you’ve taught them that problems should stay hidden.
When an issue surfaces, separate the person from the problem. Ask clarifying questions before assigning responsibility: “What happened?” “What were you trying to accomplish?” “What would help prevent this next time?” This approach communicates that you’re interested in solving the problem and improving systems, not punishing individuals.
This is especially critical with high-stakes failures. A manufacturing facility implemented a rule: any safety incident gets investigated for process failures first, before individual accountability is considered. The result was that workers began reporting near-misses and hazards they would have previously hidden, preventing accidents before they happened.
Create explicit norms around this. Tell your team: “If you make a mistake, I want to hear about it from you, not from someone else. That’s how we fix things.”
Invite Opinions Actively and Ensure They’re Heard
Psychological safety isn’t passive. You can’t just say “speak up” and expect it to happen, especially in hierarchical organizations or with introverted team members.
Build structures that make it normal for people to contribute:
- Ask directly for dissenting views in meetings: “I’ve outlined the plan. What am I missing? Where might this fail?”
- Go around the table for input instead of opening the floor to whoever speaks first. Quiet voices get drowned out in free-for-alls.
- Solicit anonymous feedback on major decisions, then discuss what came up.
- Recognize and act on suggestions publicly. People need to see that their input changes outcomes.
One product team started a practice of “pre-mortems” before major launches: they’d imagine the product failed catastrophically and work backward to identify what went wrong. This flipped the dynamic from defending plans to stress-testing them. It generated better ideas because people felt the safety to imagine worst-case scenarios out loud.
Set Clear Boundaries Between Safe and Unsafe Risks
Psychological safety doesn’t mean consequence-free. It means the consequences are proportional and tied to impact, not effort or uncertainty.
Be explicit: experimentation and calculated risks are safe. Violating customer trust, ignoring compliance requirements, or behaving unethically are not. The difference is clarity. Your team should know exactly where the boundaries are.
For a creative agency, this might mean: “We’re safe to propose bold creative directions, test unconventional strategies, and learn from campaigns that underperform. We’re not safe to miss legal reviews or make commitments we can’t keep.” Once people understand what’s protected and what’s not, they can move faster.
Start Building This Week
You don’t need a company retreat or a three-year culture transformation plan. Pick one behavior this week: admit a mistake publicly, or ask your team a genuine question you don’t know the answer to. Notice what happens when you do. Then repeat it next week with a different behavior.
Culture compounds. Small acts of vulnerability and openness create permission for others to do the same. Within a few months of consistent practice, you’ll see the difference in the quality of ideas your team brings forward, the risks they’re willing to take, and the problems they surface early.
If you’re working on culture initiatives like this, consider sharing your approach and lessons with the broader professional community. LinkedIn Daily accepts submit a guest post from practitioners building better teams.
