I'm Anh Ly, founder and CEO of Mim Concept, a premium furniture company, and I also lead the design process day to day. One practice that has built the most trust on my team is separating idea review from personal judgment. In our weekly design and operations check-ins, everyone is expected to point out one risk, one improvement, and one thing that is working before we make decisions. That structure makes it normal to speak up early, especially for quieter team members, because feedback is about the work, not the person. Over time, it changed collaboration in a very practical way. We started catching production and customer experience issues much earlier, and our revision rounds on new product launches dropped by roughly 30 percent over a six-month stretch because people stopped holding back concerns until the last minute. My tip is to give feedback a repeatable format so honesty does not depend on confidence. Psychological safety is built when people learn that speaking up will not cost them credibility, it will improve the outcome.
The practice that built the most psychological safety on our team was normalising public mistakes starting from the top. Not in a performative way not a leader standing up at an all-hands saying they value vulnerability while clearly reading from a script. It started when our CEO began opening monthly team meetings by sharing one decision she'd made recently that she'd got wrong or would handle differently. Not catastrophic failures. Just honest reflections a hire she'd rushed, a client conversation she'd misjudged, a feature she'd prioritised based on assumption rather than evidence. The first time she did it the room went quiet. People weren't used to a leader volunteering mistakes without being forced to by consequences. By the third month something shifted. Other senior leaders started doing the same. By the sixth month it had filtered through the team to the point where someone would flag a mistake in a project channel and the response was problem-solving rather than blame. The impact on collaboration was measurable. The number of issues surfaced during projects before they became crises roughly doubled within two quarters. People stopped sitting on problems hoping they'd resolve themselves because they'd seen repeatedly that raising a concern early was met with support rather than judgment. Cross-team projects improved because people were willing to admit when they were stuck or out of their depth rather than quietly struggling until deadlines slipped. The single most important detail was consistency. When the CEO skipped her reflection one month because the agenda was packed, a team member actually asked about it. It had become expected part of the operating rhythm rather than an occasional gesture. That consistency is what separates genuine psychological safety from a one-off exercise that people see through immediately. The tip I'd share is that psychological safety cannot be built through policy or training. It is built through repeated demonstrated behaviour from people with power. If leaders only share mistakes when things are going well and retreat into defensiveness during difficult periods, the team learns that honesty is conditionally safe which means it isn't safe at all. The practice has to hold especially when it's uncomfortable and that's what makes it credible.
Hi, Chris here — I run Visionary Marketing, specialist SEO and Google Ads agency. We're a team of 12 and the thing that's made the biggest difference to how openly people communicate wasn't a policy or a workshop. It was normalising failure in public. Every Friday we do a 15-minute "wins and wrecks" round. Everyone shares one thing that went well and one thing that didn't. I go first, and I always lead with something I personally got wrong that week. Last month it was a bidding strategy I'd pushed for on a client's Google Ads account that burned through about £800 before we caught it wasn't converting. The month before, it was a client email I sent that was too blunt and needed a follow-up call to smooth over. The reason I go first matters. If the founder only ever shares wins, nobody else is going to volunteer their mistakes. But when your boss openly says "I wasted £800 this week because I was wrong about a hypothesis," it gives everyone else permission to be honest without worrying it'll count against them. The impact on collaboration has been measurable. Before we started this, problems would surface late — usually when a client noticed, which is the worst possible time. Now they surface in the Friday round when they're still small and fixable. Our average issue resolution time dropped from about 9 days to 3. More importantly, people started asking each other for help mid-project instead of struggling alone and delivering something subpar. One of our junior PPC specialists told me she'd never worked somewhere where admitting a mistake didn't feel career-threatening. She's now one of the most vocal people in strategy meetings because she's not afraid of suggesting something that might not work. My tip: if you want psychological safety, you can't delegate it. The most senior person in the room has to go first and be genuinely vulnerable. Not performatively. Actually admit the real thing you got wrong. People can tell the difference. Chris Coussons Founder, Visionary Marketing chris@visionary-marketing.co.uk
The one thing that helped build more trust on my team than anything else was admitting when I didn't have the answer. Real estate appears from the outside to be a solo sport. But running a brokerage will mean every person on the team has an impact on the client experience, and that requires that people speak up when something isn't working. You don't get that if your team has the sense that mistakes get punished. Early in my career, I ran my business like most business owners do. Project confidence; have the answer ready; keep the energy up. But what I realized over time is that my team would no longer bring me problems early enough to fix them. They'd wait until something was already a bigger issue, because the culture around me didn't make it safe to raise a flag. So I changed the standard. I began to be open about my own uncertainty in front of the team. When I didn't know how a listing was going to do, I said so. When I made a pricing call that didn't stick, instead of passing quietly, I talked about it openly. That changed the way my team talked to me and the way they talked to each other. The tip I'd give any business owner is simple: Model the behavior you want. If you want your team to admit to problems early on, you have to do it first and do it consistently. People follow what they see rather than what they're told to.
For us, it was normalizing saying "I don't know" out loud. Sounds small but in a technical environment there's a tendency for people to hedge or overcomplicate rather than just admit they're not sure about something. When I started doing it more openly myself the team followed and the quality of conversations improved noticeably. People started asking better questions earlier instead of quietly spinning on something for hours. The collaboration impact was real. When people feel safe admitting uncertainty they flag problems faster, which in our work means catching issues before they reach a client's live site rather than after. That's a direct quality outcome not just a culture one. The tip I'd give is that psychological safety is set from the top and it's set fast. New people especially are watching how leadership responds the first time someone admits a mistake or asks a basic question. If that interaction goes well the whole tone gets established early. If it goes poorly people spend the next six months figuring out what's actually safe to say.
Most leaders say that they want their team to speak up when something goes wrong. But what they are really rewarding in doing that is people who fix problems quietly before anyone notices them. I've been down that road before, managing teams across retail operations and what it produces is a group of people who are very good at hiding bad news until it becomes a much bigger problem than it needed to be. The reason that happens is that people don't hide problems because they're lazy. They keep them hidden because past experience has taught them that bringing up a problem puts a target on their back. And that is why for After Action Cigars, instead of keeping track of whether mistakes happened, we decided to keep track of how fast people flagged mistakes. We created a shared Google sheet that all members of the team had access to, where anyone could record an issue, a step missed or a bad call with three fields: what happened, when did they catch it and what did they do next. There was no approval process, no review by a manager and no consequence to logging something. The only thing that posed direct response from me was to find out about a problem through a customer complaint rather than through that sheet. That structure told the team something very specific. Flagging that there was a problem in the first place was the right thing to do and nothing bad would happen because of it. That is what psychological safety actually looks like in practice. It's not a value on a wall. It's a system that it proves that the message is real.
One thing our company does that I actually love is these casual "open mic" sessions. Basically, anyone can bring up ideas, questions, or even admit mistakes—no judgment, no filters. At first, I didn't really know if I should say anything. It felt weird admitting stuff wasn't perfect, like everyone else had it together. But after a couple of sessions, I realized people actually wanted to hear the messy ideas, the half-baked thoughts, the "oops" moments. And that made it so much easier to speak up. For me, it's changed how I work with the team. Conversations feel like we're figuring stuff out together instead of pointing fingers. And honestly, projects move faster because problems get caught early instead of festering. My tip? Just start small. Even one meeting a month where it's safe to speak freely can totally change the vibe. Once people feel like their voice matters, collaboration just... works better. It feels way more human, less like trying to hit targets all the time.
We build trust by making disagreement part of the process, not a sign of disloyalty. In important meetings, the person closest to the work speaks first, not the most senior person. This allows people to share what they really see before others start following leadership's view. Over time, it creates a culture where people know their judgment is valued and raising a concern is seen as helping the business, not creating conflict. This approach improves collaboration because decisions are based on real work experience rather than hierarchy. Teams work together with less second guessing and fewer hidden concerns. A simple change in the order of speaking can make a big difference. If the highest ranking person speaks last, we hear more honest feedback earlier.
One of the best ways to build true trust in a project is to normalize the messy middle. This means the project team must share their thoughts, ideas, and roadblocks at the early stages of the project. If all projects are just a series of ongoing conversations rather than high-stakes presentations, the employee experience improves significantly. Employees will get better feedback, and mistakes will cost less money before they happen. All the emphasis will be on the solutions to the problems that the team needs to solve, not on the employee. To help your leadership build a culture like this, I would suggest that you initiate a "Rough Draft Sync." Create space for employees to share ideas or rough drafts of documents. No criticism should be allowed in a session like this. Only questions and support. You'll be creating a tremendous amount of psychological safety for the team by helping them understand that they are each other's safety net, not the jury.
In over 15 years of experience managing safety in the workplace, I have found building trust largely comes down to company culture. Most organizations sit somewhere on a spectrum. On one end are workplaces that are consciously unsafe, where leaders and employees can see the hazards around them but lack the systems, accountability, training, or commitment to address them. Organizations without a safety culture or commitment will end up here, as safety will be shortcut in order to increase output. Just marginally improved from a consciously unsafe culture lies unconscious unsafety, where awareness fades and risk becomes normalized. Dangerous conditions are simply accepted as the way things are, and incidents are written off as bad luck or human error. Most organizations start here in their safety journey. Organizations that invest in leadership, accountability, and open communication develop conscious safety habits. Here, employees are trained and held to the expectation of safety performance. The organization actively reflects on its culture, deliberately reinforces safe behaviors, and builds systems that sustain it long term. The highest stage is in our progression is unconscious safety, where safety becomes so engrained in the workforce that its second nature. Employees no longer "think" about putting on PPE or locking out equipment, they do it because it's the right thing to do and what the culture expects. This progression mirrors what the DuPont Bradley Curve describes: organizations moving from reactive compliance driven by fear, through dependent rule-following, toward independent ownership, and ultimately to interdependent cultures where employees genuinely look out for one another. In each model, the bridge between stages is psychological safety. When employees trust that raising a concern won't cost them their job, near-miss reporting increases, hazards get caught earlier, and collaboration strengthens naturally. In my experience, the single most effective thing a leader can do is visibly respond to every report, even when the answer is "we looked at it and no change is needed." Silence kills reporting culture faster than anything else. Trust isn't built through posters or policies. It's built through consistent, visible action at every level of the organization.
At Jacoby & Meyers, trust comes from clear responsibilities at each stage of a case. Intake qualifies and signs clients, with a target of converting about 95% of qualified leads. Records handles medical documentation, case managers coordinate treatment and updates, and negotiators manage settlement. Many of these roles operate in remote or hybrid setups, while trial attorneys handle litigation and must attend in-person hearings, depositions, and trial preparation. Each role has defined expectations, so people know what they own and what good performance looks like. That clarity reduces uncertainty and makes it easier to speak up or move work forward. Collaboration stays direct because work is handed off by stage rather than managed by one person. One practical tip is to be clear on both responsibility and expectations.
DeWitt Pharma Services adheres to a safety mechanism called Stop Work Authority. It empowers every staff member to suspend production if a certain aspect that does not satisfy our quality or safety requirements is identified. No approval is required and no negative consequences will follow. Employees who have a feeling of security in expressing their concerns are able to spot and deal with the issues while they are still minor. This is one of the reasons why our production and quality teams are able to collaborate quite efficiently. Here is one suggestion for other leaders: Making a clear and visible policy is the first thing, which will enable employees to raise their concerns without any fear. Besides, do it by recognizing and also aligning the performance metrics with the quality priorities. Once employees can witness that the leader really appreciates speaking up, trust is naturally incorporated into the culture.
Assistant Director of Communications at Alliance Redwoods Conference Grounds
Answered a month ago
One thing we do at Alliance Redwoods that builds trust fast is make expectations explicit and consistent--then have leaders model them. On our forest property, we host schools, nonprofits, churches, and corporate groups, so psychological safety starts with "everyone knows the rules of the trail" before anyone takes a risk. A concrete example is our cabin group expectations and orientation: cabin groups stay together with an adult, buddy system for bathrooms, doors open except bathrooms, lights-out/quiet hours, and simple meal norms like "strive for no waste." That structure isn't about control--it removes ambiguity, prevents small conflicts, and lets people relax into the experience and collaborate without guessing what's acceptable. I've seen this directly in guest communications and operations (and in redwood adventure settings like zipline guiding): when the container is clear, people ask for help sooner, give feedback without fear, and teams coordinate better because they share the same "operating language." It's the same reason our corporate retreats work well--clear plan + supported activities = people show up honestly and actually work together. Tip you can steal: write a 1-page "working agreement" for your team (how we communicate, how we handle mistakes, how we escalate concerns), review it out loud, and revisit it after stressful weeks. Psychological safety isn't a vibe--it's repeated, visible behaviors that lower the cost of speaking up.
The biggest thing we do at Simply Noted to build trust is radical honesty about what is going well and what is not. Every Monday I run a team standup where I share exactly where the company stands. Revenue numbers, pipeline health, machine issues, client feedback. No sugarcoating. When I started doing this, a couple of team members told me they had never worked somewhere the founder told them the truth about business performance. That blew my mind. But it tracks. Most companies keep employees in the dark and then wonder why nobody feels invested in outcomes. We have 11 people right now. At that size, trust is not a nice to have. It is survival. If someone on the production floor notices one of our handwriting robots is not writing correctly and they are afraid to speak up because they think they will get blamed, we ship bad product. That costs us real money and real client relationships. So I borrowed something from my NFL days. The best teams I played on had one rule: nobody takes feedback personally. You call out the problem, not the person. We run Simply Noted the same way. When something breaks, we talk about the process that failed instead of pointing fingers. That one shift made our team way more willing to flag issues early rather than hiding them until they became expensive. My tip for any company: share more than you think you should. When your employees understand the full picture, they make better decisions on their own and they genuinely care about results. Rick Elmore, Founder/CEO, Simply Noted (simplynoted.com)
It starts with honesty. If something goes wrong on a remodel, we say it out loud fast. No sugarcoating, no finger-pointing. When my team knows they can flag a problem without getting their head bitten off, they actually flag it early. That saves homeowners from bigger headaches down the road. We have a simple rule: bring the problem and bring your idea for fixing it. That mindset has made our crews way more proactive on the job site. It has changed how we work together too. People stop protecting themselves and start protecting the project. That shift is huge in this industry. My tip is straightforward. Create space for bad news early, and you cut down on bad outcomes late. Silence on a job site is usually hiding something. After two decades remodeling homes across New Jersey, I have seen teams crumble over communication issues more than skill issues. Trust fixes that faster than any training. Bottom line: Psychological safety at Magnolia means saying hard things early. That keeps our team aligned, our projects clean, and our clients happy with the final result.
Trust and psychological safety aren't built through statements, they're built through repeated behavior. In most workplaces, people don't hold back because they lack ideas, they hold back because they're unsure how those ideas will be received. The real work is not encouraging people to speak, it's reducing the perceived risk of speaking. One of the most effective ways we've built psychological safety is by normalizing incomplete thinking. Instead of expecting fully polished updates or "perfect" contributions, we created space for work-in-progress discussions. This shifts the culture from performance to progress. It signals that clarity is something we build together, not something individuals need to arrive with. Over time, this reduces hesitation, especially in diverse teams where differences in communication style or confidence levels can otherwise limit participation. The key is consistency. If leaders only reward polished outcomes, people will continue to filter themselves. If leaders engage with early-stage ideas, people start showing up earlier in the process. In one team, we implemented a simple but intentional change to project updates. Instead of reporting only completed work, every update had to include one challenge or uncertainty. At first, responses were surface-level, but leadership modeled depth by openly sharing their own constraints and missteps. That changed the tone. Within weeks, team members started flagging real issues earlier, asking for input, and offering perspectives more freely. What used to surface late in projects began appearing early, which improved both speed and quality of execution. Research from Google through Project Aristotle identified psychological safety as the strongest predictor of high-performing teams. Similarly, Harvard Business Review highlights that teams that openly discuss uncertainties and mistakes adapt faster and collaborate more effectively because they reduce hidden risks. Psychological safety is not created by asking people to be open, it's created by proving that openness won't be punished. When teams consistently see that incomplete ideas and honest concerns are welcomed, trust becomes embedded in how work happens. The practical tip is simple but powerful: don't wait for perfect input. Build systems where contribution starts earlier, and safety will follow.
I fired someone in front of the entire company once, and it was the best thing I ever did for psychological safety. Here's what happened. We had a warehouse supervisor who was talented but toxic. He'd belittle people, take credit for others' work, and create an environment where nobody spoke up in meetings. I knew about it for months but kept making excuses because his numbers were good. One day during our all-hands, he openly mocked a warehouse associate's suggestion about our picking process. I stopped the meeting, asked him to leave, and told everyone we'd reconvene in an hour. He was gone by lunch. The next all-hands meeting, I stood up and said "I screwed up by letting that behavior continue. If you see something like that again and I'm not acting on it, you have permission to call me out." Three people spoke up that same meeting with ideas they'd been sitting on for weeks. One of those ideas saved us about forty thousand dollars in our first year implementing it. At Fulfill.com now, we do something I learned from that disaster. Every Friday, our leadership team shares one thing we failed at that week. Not sanitized corporate learning moments. Real failures. I'll say "I completely botched that investor call because I didn't prepare" or "I avoided a difficult conversation with our head of sales for three days and it made everything worse." When your CEO admits he's regularly screwing things up, suddenly everyone else feels safe saying "I don't know" or "I need help" or "this isn't working." The collaboration impact is measurable. Our product team ships features thirty percent faster now than six months ago, and when I ask why, they say it's because people flag problems immediately instead of trying to fix them quietly and failing. My tip? Make it unsafe to fake safety. If someone asks a question in a meeting and gets a corporate non-answer, call it out right there. "That was a dodge, let me actually answer you." Trust gets built in those micro-moments way more than in any team building exercise.
We have an open-door policy, and I mean that literally. Anyone on the floor can walk up and tell me something isn't working. That kind of access changes everything. People stop hiding problems and start solving them. We've been around since 1947, so there's a lot of history here. But history can also mean "that's how we've always done it," which kills good ideas fast. When I made it clear that pushback was welcome, our mill guys started flagging waste we hadn't noticed. That saved us real money. The tip I'd share is simple. Stop waiting for a formal meeting to hear from your team. Just ask people directly, in the moment, what's frustrating them. Most owners think trust comes from big gestures. It doesn't. It comes from small, consistent moments where people feel heard. When your team trusts you, they collaborate better because they're not protecting themselves. They're focused on the work. Bottom line: Trust at House of Hardwood is a daily habit. When people feel safe speaking up, the whole shop runs better.
At Togo, I stick to a simple rule: there are no bad ideas in the room. When someone speaks up, they get heard first. After that, we can challenge what was said. That order matters more than people think. Once someone feels shut down, you don't just lose their idea. You lose their next five. I've found this reduces self-censorship quickly, and teams start solving problems earlier. I've seen deals saved because a junior team member named a risk everyone else was avoiding. That only happens when people feel safe enough to say the uncomfortable thing out loud. Collaboration improves too. When the team can share concerns and suggestions without waiting for permission or second-guessing how it'll land, work moves faster. Decisions get cleaner. The real issues surface sooner. One thing I tell leaders: go first. When you're wrong, say it. Say it out loud, and say it in front of your team. I've seen that build psychological safety more effectively than any written policy. Bottom line: Trust doesn't come from a program. It comes from what you do every day.
Trust tends to grow when people know they can speak up about problems without being blamed for them, so one practice that has made a real difference at Southpoint Texas Surveying is normalizing early issue reporting. If a field crew notices a boundary discrepancy or a records conflict that could delay a project, the expectation is to raise it immediately, even if it means admitting something was missed earlier. That removes the pressure to hide small issues until they become bigger ones. Over time, it has changed how the team works together because conversations stay focused on solving the problem instead of assigning fault. Collaboration improves naturally when people are not second guessing whether they should say something. A simple tip that supports this is responding to every issue raised with clarity and next steps rather than criticism. When the first response someone hears is "here's how we'll handle it," it reinforces that speaking up is part of the process, not a risk. That consistency builds a workplace where people stay engaged and contribute more openly.