The Frequency

I believe the fastest way to create an environment where people share ideas is to make it safe to be wrong.

One thing I do is build a simple rhythm where ideas are expected, not optional. Every week, we run a short suggestions review where anyone can bring one improvement and the leader responds in the moment with a decision. Yes, no, or not now with a reason. I have seen teams stop sharing when suggestions disappear into a black hole. The moment you close the loop consistently, participation rises because people trust their time will not be wasted.

I remember a quiet engineer who never spoke up in meetings. When we introduced this cadence and explicitly praised thoughtful dissent, she submitted a workflow idea that removed hours of manual work. That single contribution changed how she saw herself on the team.

The impact has been better execution and higher retention. When people feel heard, they take more ownership. You also catch problems earlier because employees speak up before small issues become big ones. Psychological safety is not a soft concept. It is an operational advantage.

Creating a work environment where employees feel comfortable sharing ideas starts with leaders being willing to go first.

I’ve learned, at times the hard way, that people don’t take risks because they’re told it’s safe. They take risks when leaders openly acknowledge their own missteps, share what they’ve learned from failure, and show that growth matters more than being right. When leaders model vulnerability, it sends a powerful signal: learning is valued here, and mistakes are not career-ending events.

I make it a point to share stories from my own leadership journey, decisions that didn’t work, moments I would handle differently, and lessons learned under pressure. Not as confessions, but as learning moments. That transparency lowers defenses and invites others to think more openly and creatively about their own work.

From there, behavior matters more than policy. When ideas challenge existing thinking, my response is curiosity, not correction. Asking, “What led you to that idea?” or “What problem are you trying to solve?” keeps the focus on learning rather than judgment. Even when an idea isn’t viable, the conversation itself reinforces that speaking up is worth it.

Encouraging risk-taking also requires protecting people when things don’t work. If innovation is praised but mistakes are punished, trust erodes quickly. We frame ideas as experiments, small, thoughtful tests rather than final answers. That shift alone increases participation and ownership.

Equally important is closing the loop. When employees see their ideas acknowledged, refined, or tested and hear clear explanations when something isn’t implemented, credibility grows. Silence, even when unintentional, discourages contribution.

The impact of this approach is tangible. Engagement increases. Problems surface earlier. Decisions improve because more perspectives are considered. Teams take greater ownership because they helped shape the direction. Innovation becomes part of the culture, not an initiative.

Most importantly, trust deepens. When leaders model vulnerability, encourage thoughtful risk, and respond with consistency, people don’t just share ideas, they invest themselves.

That’s when cultures shift, and performance follows.

I built Amazon’s Loss Prevention program from the ground up, and the biggest lesson I learned? The warehouse associate who’s scanning packages 8 hours a day knows where fraud patterns are happening before any algorithm does. I created a “red flag hotline”—not for formal reports, but for quick voicemails or texts directly to my team when something felt off. We caught a $2.3M theft ring because a night shift worker noticed the same contractor always volunteering for specific loading dock assignments.

At McAfee Institute, we don’t have suggestion boxes—we have mandatory monthly “kill meetings” where any employee can pitch one thing we should stop doing or change completely. Our student support team pushed back on our original certification renewal model, arguing it contradicted our “lifetime access” promise. They were right. We restructured entirely, and retention jumped 41% because students trusted we meant what we said.

The key isn’t just listening—it’s giving people decision-making authority in their domain. When our course developers said certain modules needed complete rewrites based on student confusion patterns they were seeing in support tickets, I didn’t ask for a proposal. I told them they owned it, set the budget, and had 60 days. Speed of execution beats perfect consensus when your team has the ground truth you don’t.

Creating an environment where employees feel comfortable sharing ideas didn’t happen overnight—it was something I had to be intentional about as I built NerDAI. Early on, I assumed that if I left an open-door policy, people would speak up. What I learned quickly was that permission alone isn’t enough. People need to feel that their input will be heard, considered, and acted on without fear of judgment.

One approach that made a real difference was leading with curiosity instead of authority. I started asking questions in team meetings not to steer answers, but to understand perspectives. I made a point of acknowledging contributions, even when the idea wasn’t immediately actionable, and I encouraged follow-up discussions to refine suggestions. Over time, this shifted the culture from transactional communication to collaborative problem-solving.

I also introduced structured spaces for input, like short weekly sessions where anyone could present a challenge or idea without prior vetting. Initially, participation was quiet, but as people saw that suggestions led to real changes—process improvements, client deliverables, even small operational tweaks—engagement grew. Team members started bringing solutions, not just problems, and the confidence ripple spread beyond those meetings.

The impact has been tangible. Decisions are better informed because they reflect diverse viewpoints. Execution is smoother because people feel ownership of the solutions. We’ve also seen retention improve, as employees describe feeling valued and empowered rather than simply managed. What started as a “nice-to-have” culture experiment turned into a competitive advantage: an environment where innovation emerges naturally, because people trust that their voice matters.

What I’ve learned is that creating psychological safety isn’t about perks or policies. It’s about consistent, visible behaviors from leadership that signal respect, curiosity, and follow-through. When people feel safe to contribute, the organization becomes smarter, faster, and far more resilient.

I prioritize removing fear before soliciting ideas. At Wisemonk, we intentionally foster psychological safety by making it explicit that ideas are not judged based on hierarchy, tenure, or job title. In practice, this translates to leaders speaking last in discussions, encouraging differing opinions, and publicly valuing thoughtful challenges, even when we don’t adopt them.

We also establish structured avenues for input. For instance, we conduct regular retrospectives and utilize written feedback channels where employees can offer suggestions asynchronously. This approach benefits quieter team members and alleviates the pressure of speaking up immediately. When ideas aren’t implemented, we always follow up with an explanation, ensuring people understand their input was truly considered.

The results have been noticeable. We’ve observed improved decision quality, quicker problem identification, and increased ownership across teams. Numerous process enhancements, particularly in onboarding, compliance procedures, and customer experience, originated directly from frontline employees who felt secure enough to voice their thoughts early on. Over time, this cultivates trust, which in turn leads to more robust execution and reduced turnover.

The starting point is not a tactic, it is a promise: no one will be punished for speaking the truth. The most practical thing I do is model that myself in front of the team by admitting when I do not know, when I got something wrong, and what I am learning, because leaders go first when it comes to vulnerability.

Then we build simple rituals around that idea, like regular “idea rounds” in meetings where everyone gets a turn, and dedicated channels for suggestions so speaking up is a normal behavior, not a heroic act. Over time, the impact has been obvious: more ideas from more voices, faster identification of problems, and a noticeable shift from quiet compliance to active ownership. When people feel safe to say, “I see a better way,” the organization moves from managing work to unlocking wisdom.

People share ideas when they feel safe being honest, not when they’re told to ‘speak up.’ We focus on creating consistent, low-friction moments where employees can test ideas, ask questions, and get feedback without it turning into a performance moment.

We do that by embedding structured reflection and dialogue into everyday work, so sharing input isn’t reserved for meetings or surveys. When employees have tools that help them frame ideas, prepare for conversations, or reflect before speaking up, participation becomes more inclusive. It levels the field for people who may not be the loudest voice in the room.

The impact has been tangible. We’ve seen higher participation across teams, faster surfacing of risks and improvement ideas, and stronger signals of belonging, especially among newer hires and underrepresented employees. When people feel heard early and often, connection follows, and better ideas tend to show up right behind it.

We establish that by making idea sharing a low-risk and action-oriented process.

From an operational point of view, we distinguish between ideas and hierarchy. Suggestions and ideas are recorded through shared spaces and reviewed and discussed independently of one’s position. Moreover, leaders show public support and attribute ownership of their ideas, particularly those of smaller scale.

The effects are real. People step up sooner, solutions emerge quicker, and ownership rises. This multiplies into better products and a culture where taking initiative feels safe—and expected, not exceptional.

At Franzy, we encourage employees to share ideas during team check-ins and regular discussions. Everyone knows their input is considered, and no suggestion is dismissed.

This has led to faster processes, improved workflows, and a team that feels invested. Suggestions are turned into practical improvements that strengthen how we work together.

I create safety for sharing ideas by responding with curiosity rather than immediate evaluation. When someone speaks up, they are met with listening first, not correction. This removes fear of being dismissed. Over time people contribute more freely and creatively. The impact has been stronger collaboration and better problem solving. Ideas surface earlier instead of after issues escalate. Psychological safety fuels innovation.

Creating a safe space for ideas isn’t about making everyone feel good. It’s about process. The bedrock of that process is psychological safety, which, as Google’s Project Aristotle discovered, is the most vital ingredient of effective teams. You build psychological safety using explicit, structured forums for feedback. Regular and mandatory “blameless retrospectives” after a project. “Request for comment” documents before you make a decision. The single most important signal? What happens when a team member suggests something that gets hotly debated but is not adopted? Purposely thanking the team member for his thinking. We need to reinforce the message: it’s the act of sharing we value, not the idea itself.

The effect is a dramatic drop in the number of “silent failures,” where a team member sees a training issue, sees the potential crisis, but can’t speak up. When people feel safe to unearth emotionally laden hidden assumptions, managers will discover risks sooner and build a better product. This culture of open contribution is critical in your talent retention strategy, because good engineers want to work in an environment where their good thinking is listened to and respected, not simply assigned.