Confidence vs competence is one of the most misunderstood dynamics in the Executive Assistant role. These two ideas are often discussed together because, in practice, they influence the same decisions. How much autonomy is given to an EA? How much is delegated without checking? How much trust an Executive places in someone to act on their behalf.
In the EA role, pay, scope, and seniority are rarely based on task execution alone. They reflect how comfortable others are relying on you to make calls without supervision, and how reliably those calls hold up over time. Confidence and competence are therefore closely linked in how the role is valued, even though they are not the same thing. Problems arise when one is assumed to exist simply because the other is visible.
Confidence vs competence matters because the EA role operates at speed, close to decision-making, and with very little margin for error. So, before we dive in, what do I mean when I say confidence vs. competence in the EA role? I am referring to the relationship between how comfortable you feel acting and how well-equipped you actually are to make the call. Confidence vs competence might sound like an abstract career concept for Executive Assistants, but it really isn’t. It plays out very specifically, for example, when deciding which emails you respond to immediately and which can wait, choosing which meetings can move without causing any issues later on, or flagging a risk in a meeting rather than keeping your opinion to yourself.
When confidence is mistaken for competence or vice versa, what often happens is that EAs are expected to make decisions because they appear confident, even when the rules, priorities, and boundaries for those decisions have never been made explicit. The role expands and grows because you look and act with visible confidence. Because of this, your Executive or those around you who should be offering guidance and feedback don’t because they think you’ve got everything down, and that can result in real competence lagging behind.
As EAs, we rarely develop confidence and competence at the same pace. They don’t arrive neatly packaged together. Many of us build confidence early because the role demands it. Staying calm, sounding steady, responding quickly, and keeping things moving are essential just to get through the day. We learn how to look in control long before we are given the time, context, or feedback to fully understand why certain decisions work better than others.
As a result, confidence and competence can appear balanced on the surface. From the outside, it can look like we have everything covered when really we don’t. The reality is that we know some of the confidence comes from experience and some from plain old necessity. You might think that might be a personal shortcoming, but actually, it is far from it. It is a predictable result of how the EA role operates, especially in really fast-moving organizations where you are expected to step in and act before anyone has explained the rules or context.
This template provides you with practical, ready-to-use dialogues tailored for various common scenarios where you might need to refuse a request at work. Equip yourself with the right words to handle difficult conversations gracefully.
As EAs, we are expected to stay calm when things are messy. It’s a huge part of the role, so for example, if plans change, or senior stakeholders are waiting on a decision, or information is incomplete, but you have to make a choice, we still have to maintain an air of confidence and can-do attitude, even if internally we are falling apart. The work does not pause while someone explains the full picture. Because of that, we learn very early how to sound confident, respond quickly, and keep things moving even when we are still figuring things out. For many of us, confidence vs competence becomes most visible when we are asked to act quickly without time to check assumptions or confirm priorities.
Most of us have said “I’ve got it” more times than we can count, sometimes before we fully understood why one option was safer than another. That is not overconfidence. That is how the role works. Speed and reliability are rewarded from day one, so an outward sense of confidence often develops first. Competence takes longer because it depends on your experience and what you’ve been exposed to. If you’ve been given a lot of areas to grow into, or if you are always kept in the loop or given context. If you get to see the impact of the decisions you’ve made. It all adds up to being much more competent in the role.
This is why we need to be careful about how we talk about confidence and competence. As EAs, what can look like confidence from the outside is often simply us doing what the role requires to keep things moving. We are stepping in, making calls, and absorbing uncertainty so the day does not fall apart. The confidence vs competence dynamic explains why an EA can look highly capable on the surface while still feeling unsure about the impact of certain decisions.
What do I mean by competence in the EA role? I mean the quality of the calls you make when there is no perfect answer. You can see it in how you weigh options, anticipate impact, and move work forward without creating extra problems later.
Competence looks like knowing which meetings can move and which ones will cause problems later if they do. It looks like understanding which emails genuinely need immediate attention and which can wait without consequence. It looks like spotting when a calendar change will create pressure somewhere else in the week. It looks like knowing how your Executive thinks, what they care about most right now, and where they are least flexible.
This kind of competence builds slowly over time. It comes from repeated exposure to similar situations and from noticing what worked, what created extra work later, and what your Executive reacted strongly to. It is quieter than confidence, but it is what makes decisions safer and more consistent. Understanding confidence vs competence helps explain why some parts of the role feel effortless while others quietly drain your energy.
Once you have that base, confidence has a very real impact on how the role feels day to day. You make decisions more quickly because you understand what matters and what does not. You spend less time checking and rechecking because you know how your Executive will react. You are clearer when you explain a recommendation because you understand the consequences if it goes wrong.
This is the balance we are working toward as EAs. Confidence grows out of competence. The more capable you are across the core parts of the role, the more natural confidence becomes. That competence comes from two places. First, being exceptionally strong in the areas that already sit inside your comfort zone. Calendar management, inbox control, meeting preparation, follow-up, stakeholder communication, and understanding your Executive’s priorities inside out. Second, deliberately stretching yourself in small, controlled ways. Taking on decisions that feel slightly uncomfortable, asking for context earlier, and reviewing how those decisions played out. The confidence vs competence conversation matters because trust in the EA role is built through consistent outcomes, not just confident delivery.
When you combine depth in the fundamentals with intentional stretch, you will notice that the confidence you need in the role stops feeling forced. It comes from knowing your role, knowing your Executive, and knowing you can handle what is thrown at you on the regular!
Problems start when confidence and competence drift too far apart. This usually happens when EAs are given more and more autonomy because we appear capable, but without clearer boundaries, shared expectations, or feedback on how decisions are landing.
In practice, this can look like being asked to manage increasingly complex communications on your Executive’s behalf without alignment on tone or positioning. It can look like being expected to filter and reframe information coming from multiple teams, while also deciding what your Executive really needs to see and when. It can show up in travel planning, where you are balancing cost, time, preferences, and last-minute changes, or in event planning, where you are making decisions about format, attendees, and logistics without clear success criteria.
Over time, the role becomes more demanding because more decisions sit with you and fewer are discussed. You are moving faster while carrying more context and more risk, often without the space to step back and think through the implications. From the outside, everything still looks under control. Confidence vs competence is something most EAs experience long before they have language for it, especially as the role expands.
Inside the role, you are reacting to what lands in front of you rather than actively influencing how work flows, how information is framed, and which decisions are made earlier rather than later. As a result, small decisions start to have bigger consequences.
The opposite problem also exists. Some of us have built strong competence across the role, but hold back because we are conscious of overstepping. You draft the message and then pause before sending it. You notice an issue in how information is flowing, but decide to wait rather than step in. You can already see that a travel or event decision is likely to cause friction later, but you hesitate because it technically sits outside your remit. In these moments, your Executive misses out on input that would genuinely help them, and the value you bring stays quieter than it needs to be. Paying attention to confidence vs competence can help you identify where you need more context, feedback, or decision authority.
What we are really aiming for as EAs is balance. Confidence that is supported by competence. Competence that is communicated clearly enough to build trust. This is where the confidence vs competence conversation becomes useful, not as a trade-off, but as a way of understanding how the two need to develop together in the EA role.
When those two qualities develop together, the relationship with your Executive changes in very practical ways. You are brought into conversations earlier, delegation becomes more straightforward, and there is less need for constant checking back and forth. The work feels a little easier and more deliberate because confidence vs competence is working in sync, with confidence grounded in real capability and competence visible enough to be trusted.
If this article resonated, and you’re at the stage where your role is expanding faster than the clarity around it, the Strategic Business Partner course is designed to help EAs build the capability that makes confidence easier and trust more consistent. Over time, confidence vs competence becomes less of a tension and more of a guide for how the role should evolve.
Share this article:
Join 30,000+ Assistants receiving our carefully crafted weekly newsletter packed with valuable tips, tricks, and insights tailored specifically for Assistants like you.
