You Probably Don’t Need More Confidence
Most leaders don’t lack confidence. They need an upgrade to their Operating System.
If you are like most leaders, you probably don't need more confidence, no matter what the little gremlin in your psyche is telling you.
You need relief. Clarity. Space to think one complete thought.
You aren't underperforming and you aren't an imposter. You are trying to sprint underwater while wearing clown shoes and your nervous system is responding accordingly. It looks around at the strain, the awkwardness of it all, and concludes that you must be doing it all wrong.
Meanwhile HR is hanging posters in every breakroom showing how incredibly productive underwater clown shoes are supposed to be and your boss is strolling around in the latest Bozo Loafers like this is all perfectly normal.
So how exactly are you supposed to feel confident in that kind of environment? Truth is... you aren't. No one is.
What you are really seeing most of the time are two things. First, you are seeing the results of other people's systems that work for them. Second, you are seeing a whole bunch of followers who feel just as awkward as you but are desperate to match the model anyway.
So it's probably not a confidence problem. It's a systems problem.
That system might be your calendar, your communication habits, your decision making process, your way of handling pressure, or the set of assumptions you picked up by watching other leaders without ever stopping to ask whether they fit you. But at the root of all of this, I usually see the same issue. You are trying to lead through a model that doesn't match your wiring, your values, your strengths, or the unique reality of the work in front of you.
That's why I work with people to answer the real question they need to think about. Not "How do I become more confident," but instead "What is the leadership operating system that actually works for me?"
That gets you to the real work much faster. Instead of trying on increasingly bizarre clown shoes, and yes, in this context that could be the 5 a.m. cold plunge, timers shaped like garden veggies, the vocal warm ups before back to back Zoom meetings, or whatever other weird little ritual the internet is peddling this week, it lets you step back from the circus entirely and build a way of leading that actually fits.
Because most of the time you don't feel better first and then magically lead better. You build the structure that fits you first and the feeling changes after. Confidence grows out of trusting your own process and using it as a foundation to showcase your actual strengths not forcing you into an endless improv exercise.
It's sorting what's truly important from what's just loud. It's being able to delegate cleanly because you know what's yours, what's your team's, and what doesn't belong in your arena at all. It comes from knowing how to have the conversation that needs to happen in a way that moves things forward instead of letting your resentment write a check your mouth will later regret.
Confidence is the emotional aftereffect of having a usable operating system.
That doesn't mean it makes leadership easier. It makes it more inhabitable, more sustainable, and more humane.
The goal isn't to become a different kind of person, eliminate stress, or erase ambiguity. It's not to become some serene little woodland office sprite floating through the building in a quarter-zip, sprinkling calm onto everyone else while somehow never needing any for yourself.
Quite the opposite. It's about understanding your strengths well enough to build around them. It's about building the system that lets you notice sooner, choose better, and recover faster without also having to pay the nervous system tax of trying to look like every other leader in the company.
This goal sits at the core of something I coach people to called the Calm Leader's Operating System. It's not about perfection. Wood sprites and vibes elves need not apply. It's about having a game plan for how you will lead when things get busy, and then revisiting it often enough that your defaults stop running the whole show.
So what do I mean by a leadership operating system?
I mean the internal and external set of defaults you rely on to handle the work of leading when things get noisy.
It's how you decide what gets your attention and what doesn't. It's how you determine whether something needs a fast answer, deeper thought, delegation, a boundary reinforced, or simply ten minutes for you to think instead of lacing up your clown shoes in reactive mode.
It's the combination of your filters, your habits, your assumptions, your pacing, your decision rules, your communication style and your recovery practices. Some of it lives in your calendar. Some of it lives in your head. Some of it shows up in your posture and face before you even have words for it.
That sounds like a lot, I know. I mean holy cow, that's a long list of things to think about!
The good news is it's not as complicated as it sounds. And I know this because you are already using an operating system, whether you built it on purpose or not.
This is the part people tend to miss.
Leaders don't succumb to leadership overload or burnout because they have no operating system. You struggle because you are running one you inherited by accident. You picked it up some of it from an old boss. Some parts came from a panicky team culture. You imported some from leaders who rewarded speed over thoughtfulness, visibility over sustainability, and control over trust. Some of it got hardwired during the countless stretches where everything was urgent and survival mode made perfect sense.
It worked well enough for a while... so it stayed. Then one day you woke up in a different role with different stakes, a different team, and a different version of yourself staring back at you from the laptop camera. Suddenly the same habits that used to make you successful just make you tired.
So now it's time to build an OS with intention instead of by accident. Not by becoming more like the loudest leader in the room. Not copying the productivity religion of the week. Not memorizing a list of executive presence tricks like you are preparing for the regional production of "Corporate: The Musical."
The real work is simpler than that, even if it's not always easy. It's the conscious practice of keeping what helps you and ditching what doesn't.
For some leaders that means building a cleaner way to sort priorities so everything urgent stops masquerading as everything important. For others it means making decisions sooner instead of carrying them around like open-browser tabs in the their brain. It can mean getting clearer about ownership and moving the mindset from "I own everything and therefore must leave my fingerprints on it all" to "I am accountable for the outcomes, and need to develop my team to be capable of operating with high authority and ownership."
This is what I mean by an operating system. Define the functions. Code in the process. Let it run.
It's not a personality transplant or a miracle cure. Just a practical way of leading that actually brings the best parts of your personality and leadership voice and puts it at the core of what you do, and builds the support around it to make it sustainable under pressure.
In my world, a workable Calm Leader's OS helps you do five things really well.
It helps you decide what merits your attention
It helps you make and hold decisions instead of looping on them indefinitely
It helps you clarify ownership to get you out of the loop of hovering, rescuing and redoing work for your team
It helps you communicate expectations clearly enough that people know what matters, what good looks like, and what isn't truly urgent
And it helps you recover before your nervous system decides to file a formal complaint.
That operating system framing is embedded in the Calm Leader's OS itself which centers attention, decisions, ownership, communication, and recovery as the core functions of leadership.
My next five newsletters will dive into each of these five core elements of the Calm Leaders Operating System in more depth, but let me give you a quick introduction to each conceptually here.
Attention: Any workable plan of action for a leader starts with attention. Not everything that lands in front of you deserves equal weight, but without a filter it can feel that way. A good system helps you separate what is truly important from what is loud, urgent, or politically noisy. When that filter gets clearer, the day stops feeling like a constant game of whack-a-mole and gives you a huge upgrade to your agency over your time.
Decisions: Once your attention filter is cleaner, the second function is decisions. A surprising amount of leadership stress comes from carrying half-made decisions around in your head while waiting for more information, more consensus, or a slightly better mood. A good OS helps you triage your decisions, recognizing that timing often trumps optimization. You come away with a repeatable way to make decisions, communicate them, and move on. Momentum returns in a hurry once those mental tabs start closing.
Ownership: Third up is ownership. You can exhaust yourself before lunch every day by acting as the default owner of everything in a thirty foot radius. A healthy OS makes it clear what is yours to carry, what belongs to your team, and what needs to be ejected from the arena entirely. Once ownership gets clearer, delegation stops feeling risky and starts feeling responsible.
Communication: Fourth up is the communication plan. So much of the tension you all report back to be about isn't even about your performance, it's about unclear expectations, work that landed on you without a clear scope or outcome defined, or reading between the lines of what so and so said in the meeting about such and such. A good operating system helps you name what matters, clarify what success looks like, and address friction directly instead of letting it compound like overdue late fees. And this gets right to the soul of the confidence question. Clear expectations prevent a lot of problems that performative confidence creates in the first place. Get clear. Build confidence. Communicate. In that order.
Recovery: Some people are surprised that recovery is built into the OS. They think that's what weekends or vacations are for. But you can't just park your recovery to the side to be addressed "someday." Leadership is cognitively and emotionally demanding work, even when you are great at it. A functioning operating system then builds in ways to reset your attention, regulate your reactions, and step back before pressure turns into burnout. Without recovery even the best systems collapse under their own weight.
That's it in a nutshell, the Calm Leader's Operating System.
As I said, over the next five newsletters I am going to walk through each of those five pieces in more depth, potentially culminating with a Live Session in April to do some of this work in real time with your questions and challenges. I'll be taking each piece one at a time with practical ways you can start improving your OS without redesigning your entire life or waking up at 4:59 am to sit in an ice bath and contemplate your brand.
If you are already subscribed, you will see these show up over the next few weeks.
If you aren't subscribed, now might be an ideal time to fix that so you don't miss the series.
Because confidence is a nice feeling.
But a system that works for you is much better.
PS - I'm even working on getting a couple of guest stars in to share their thoughts on these OS elements.
