When you think of a leader, what words come to mind? Perhaps strong, sure, steadfast, and wise. As we step into leadership, we strive to emulate these qualities. But we are also human, flawed, and sometimes unsure how to navigate the issues of the day. Admitting that can feel risky. Will our teams still trust us if we don’t have the answer, or if the answer we gave was wrong?
Our first inclination may be to hide that uncertainty and create a persona that is free of doubt. I came to recognize that instinct in my own leadership, along with the distance it created between me and some members of my team. Learning to show strength through vulnerability began with facing my fear of being wrong. From there, I learned how to put vulnerability to use by admitting what I did not know and making room for others to influence the path forward.
Facing the fear of being wrong
Before stepping into leadership, I built my reputation on technical knowledge. I understood the instrumentation and chemistry behind the laboratory’s work. I was trusted to have the information others did not.
Once in leadership, I felt it was important to retain those qualities. There was another side to that coin, however. People sometimes grew frustrated with my assumptions and their critiques of my decisions did not get much traction. I had a problem with arrogance, built on fear that without my ability to accurately assess every situation, my value was diminished.
In a subsequent role, some associates valued my leadership while others regularly complained about me to my boss. Conversations with my supervisor and associates prompted a time of personal investigation and discovery. I realized that I assumed I knew what “best” was. If an associate disagreed, I considered it their responsibility to change.
My focus needed to shift toward understanding the people I led. That meant allowing their perspectives to challenge my own.
For a leader facing this fear, a useful starting point is to ask: What am I afraid this admission will say about me? There is a difference between recognizing a gap in your understanding and deciding that the gap makes you unqualified to lead. Your responsibility includes recognizing when a decision needs information or expertise beyond your own.
Consider a hypothetical situation: You present a new workflow to your team designed to fix certain issues. A technician on the team questions the change, explaining that it could create a bottleneck during sample preparation. You realize that, while you were proud of your solution, this is something you hadn’t considered.
Rather than defending or downplaying this new wrinkle, pause, collect your emotions, and engage with the associate. Depending on your candor with your team, the response may be different, but I have said things like “Wow, I completely missed that. Do you have any thoughts on how we can tweak this change to accommodate that issue?” Whether they do or not, they feel heard and like they are part of a team. Whatever the outcome, whether fixed on the spot or having to take more time to iron out that wrinkle, I always thank the associate for helping me see what I did not.
The key, however you do it, is to pause and seek input. Experience the urge to defend your solution but make the “best” solution the priority. Practicing the pause gives you a clearer mind to work on the fear.
Making room for candid feedback
Regular one-on-one conversations offer a place to try out this approach. Give the associate room to discuss their work and aspirations, including concerns that may be difficult to raise in a group. Understanding their perspective provides context for examining your assumptions.
The conversation should also leave room for feedback about your leadership. Questions such as “Where have my instructions been unclear?” or “Have I made a decision recently that made your work harder?” Even encourage freedom of thought saying things like “I know I don’t always see everything. Please tell me what I’m missing.” Invite associates to discuss specific situations.
Questions will open up dialog. Imagine an associate says your frequent requests for updates interrupt their concentration. From your perspective, you feel the urgency of needing the information. Instead of letting that be the only driver, see what your associate is communicating—they are presenting a roadblock to their efficiency.
This is a perfect time to gain partnership with your associate. You can say something like “I am not trying to hinder your work or hold you back. I am responsible for the outcome of your work, but I am open to establishing a cadence to our communication. What sort of compromise can we agree upon, so that we both get what we need?”
That response makes your own behavior part of the discussion. It also gives you and the associate something concrete to revisit. At the next meeting, follow up in case there needs to be any adjustment.
Not all associates will be quick to engage. Some may need time before offering candid feedback. Avoid pressing when someone seems hesitant or thoughtful. An initial “Everything is fine” may not be evidence that there are no concerns. Even if nothing comes from the first invitation, they will be mentally chewing on it until the next meeting. Keep the invitation open and follow through on the feedback people do provide.
Pairing openness with responsibility
Vulnerability becomes useful when an admission leads to action. Saying “I don’t know” identifies a gap. The next step is to explain how you will address it and what the team should do in the meantime. I take action items for myself all the time in this regard.
Suppose an associate proposes a method change and you are unsure if the change falls outside requirements in the reference method. You might say, “I can see how that would improve efficiency, but I don’t know if the method will allow it. Let me look into it with our quality lead and come back to you tomorrow. Please hold off on making the change until then.”
The uncertainty is explicit, and so is the direction.
The same principle applies when you discover that you were wrong. For example, if you built an unrealistic timeline for a project, once you become aware of the issue, acknowledge the error and involve the team in reassessing the work. Gain partnership, balancing the team’s needs to have sufficient time, while helping them understand the reason the timeline was established as-is. Typically, this will require compromise from everyone, and so full partnership in the plan is key.
Making room for others does not require you to set aside your judgment. Listen, examine the evidence, and explain your decision—including when you cannot adopt someone’s suggestion. If new information changes your assessment, say what changed and why.
The goal is to make it possible to examine a problem together while retaining responsibility for the next step. Sharing uncertainty about the work should serve that purpose; associates should not have to reassure you about your value as their leader.
It begins with one conversation where you create the space to be wrong or be shown things you don’t see. When these things are identified, make sure your first response is to listen and understand, not defend. Be open to compromise and always close the loop by explaining what you learned and what you will do. That gives vulnerability a practical role in how you lead.















