The Ego-less EA
Why the Best Executive Assistants Don’t Need to Prove They’re Important
There is a quality we see again and again in truly exceptional Executive Assistants, and it has very little to do with calendar management, travel planning, technology, or even years of experience. They simply have remarkably little ego about the work.
That doesn’t mean they lack confidence. They aren’t meek, deferential, invisible, or endlessly agreeable, and they certainly shouldn’t tolerate disrespect or allow other people to take advantage of them. Many of the best EAs we know are extraordinarily confident people. They have strong opinions, they push back when necessary, they know their value, and they can walk into a room full of senior executives and hold their own. They just don’t feel the need to constantly prove that value.
That distinction matters because ego can start to get in the way when an EA begins evaluating the work based on what it says about them rather than what the executive, team, or organization actually needs. Is this task important enough for me? Why should I have to do that? Will anyone know I did this? Why did she get thanked when I did most of the work? Why wasn’t I included? Why wasn’t my idea chosen? Why should I fix something that wasn’t my mistake?
None of those thoughts are particularly unusual. Most people have them from time to time. The problem is when they start influencing how you work. An EA can be extremely capable and still become surprisingly ineffective if too much energy goes toward getting credit, protecting their status, or making sure everyone recognizes their contribution.
The strongest EAs understand that their value doesn’t come from being seen as the most important person in the room. It comes from being the person who can look at what needs to happen, put their own ego aside, and figure out how to make it happen. Sometimes that means taking on something that technically isn’t their responsibility. Sometimes it means letting someone else get the credit. Sometimes it means fixing a problem they didn’t cause because fixing it is more important than proving it wasn’t their fault.
That isn’t a lack of confidence. If anything, it usually comes from having enough confidence that you don’t need every task, decision, or outcome to reinforce your sense of value.
The Job Is Not Always Glamorous
Executive support exists at a strange intersection of highly strategic and incredibly mundane work. At 10:00 a.m., you might be sitting in a leadership meeting discussing a multimillion-dollar transaction, and 45 minutes later you’re trying to figure out why your executive’s lunch never arrived.
You might spend hours preparing materials for a board meeting and then realize the conference room is freezing, so you go find someone to fix it. You might coordinate an international trip involving five cities, three executives, security, and multiple time zones, only to realize your executive forgot a charger and need to figure that out too.
That range is part of the job. Some days you’re managing an enormous project; other days you’re tracking down a missing FedEx package. The best EAs don’t see the second category as beneath them because they understand that the importance of a task isn’t necessarily determined by how impressive it sounds. It’s determined by what happens if nobody takes care of it.
Of course, there’s a difference between being willing to help and allowing a role to become poorly scoped. If an EA was hired to operate at a senior strategic level but ends up spending 80% of the week doing work that should belong elsewhere, that’s a legitimate organizational problem and something that should be addressed. But… occasionally doing something small simply because it needs to get done isn’t beneath you. It’s part of being a good teammate, and in executive support, knowing when to put the bigger picture ahead of your own job description is often part of what makes someone valuable.
Ego Shows Up in More Places Than We Realize
When people hear the word “ego,” they often picture arrogance. In the workplace, though, it’s usually much subtler. Perhaps you don’t even realize it.
It can show up in the moment someone gives you feedback, and your first instinct is to defend yourself, or when you start explaining why something happened before simply acknowledging that it did actually happen.
It can mean holding onto information because being the only person who knows something makes you feel indispensable, becoming territorial when another assistant works with “your” executive, or refusing a small task because you feel like you’ve earned your way out of doing that kind of work.
Sometimes it’s as simple as needing everyone to know which part of a successful project was yours, or resisting a better idea simply because it wasn’t your idea! None of those behaviors necessarily mean someone is a bad person or a bad employee. More often, they come from pretty normal insecurities. We want to be respected. We want our work to matter, and we want people to understand how much we contribute. There’s nothing unusual about wanting those things.
The problem is what happens when those feelings start driving your behavior. Unmanaged ego can turn perfectly normal desires into workplace friction, and for Executive Assistants, that friction can be particularly costly. The role depends so heavily on trust, flexibility, judgment, and the ability to work well with a lot of different people that even small amounts of defensiveness or territorial behavior can have a much bigger impact than you might expect.
You Don’t Need Credit for Every Win
Imagine your executive is hosting an important dinner. You research venues, negotiate the private room, track RSVPs, manage dietary restrictions, prepare the seating plan, coordinate transportation, confirm the guests, and catch three potential problems before anyone else even knows they exist.
The dinner is flawless. The next morning, the CEO tells the leadership team, “Everyone did such a great job last night,” and your name isn’t specifically mentioned.
It’s easy to think, Seriously? I did almost all of that! (Maybe even all of it!). But there’s another way to look at it: It worked. That ability to let a successful outcome speak for itself is one of the quieter strengths of excellent support professionals.
That doesn’t mean you should allow a pattern where your contributions are deliberately overlooked. Recognition matters, and so does career development. Your executive should understand the impact you’re having, and there are appropriate places to make that visible: performance reviews, one-on-ones, project debriefs, and other conversations about your work.
But not every successful moment needs individual attribution.
Sometimes the team gets the win. Sometimes your executive looks extraordinarily prepared because you prepared them extraordinarily well. Sometimes a meeting feels completely effortless because you spent three hours making sure it would be.
There is a lot of professional maturity in being able to think, I know what I contributed. The people who need to know understand what I contribute. I don’t need to interrupt this moment to make sure everyone else knows I was responsible for it.
That confidence allows you to stay focused on the outcome rather than constantly looking for proof that you were the person who made it happen.
“That Wasn’t My Mistake” Can Still Be the Wrong Response
Another place where ego can get in the way is around mistakes. Suppose a meeting is scheduled incorrectly, and it turns out someone else actually entered the wrong time. It might be tempting to immediately say, “I didn’t schedule that. Sarah changed it yesterday.” And that may be completely true, but before you worry about establishing who was responsible, the more useful response is to figure out how to fix the problem: “I see what happened. I’m fixing it now.”
You can always clarify what happened afterward if it matters. Accountability doesn’t mean accepting blame for something you didn’t do, and there’s nothing wrong with making sure the facts are accurate. The difference is in what you prioritize first. If your instinct is to make sure everyone knows the mistake wasn’t yours before doing anything else, you’re protecting yourself when you could be solving the problem.
Great EAs understand that ownership and blame are not the same thing. You can take ownership of finding the solution without taking responsibility for causing the problem. In fact, that ability is often one of the things that separates a more experienced operator from a less experienced one. Earlier in your career, it’s natural to focus on who made the mistake, especially when you know you weren’t the person who caused it. With experience, you learn that it usually matters more to get everyone through the problem first and sort out the details afterward.
So fix what needs fixing, get things back on track, and then look at what happened and whether anything needs to change to prevent it from happening again. You can establish who was responsible without making that the most important thing in the moment.
The Same Is True When You Did Make the Mistake
Ego can make mistakes much more expensive than they need to be.
Imagine an EA misses an important email from a prospective client. The first instinct might be to explain why it happened: “I’ve just had so many emails lately, and it came in while I was dealing with the board meeting, and he didn’t mark it urgent, and normally he texts me about things like that.”
Some of those details may be relevant, and there may be a time and place to explain them. But what your executive is likely to hear first is, This isn’t really my fault.
Now compare that with: “I missed it. That’s on me. I’ve responded, and I’m changing the way I flag incoming prospect emails so this doesn’t happen again.”
That response creates a very different experience. It tells your executive that you understand what went wrong, you’re taking responsibility for it, and you’re already thinking about how to prevent it from happening again.
You don’t become trustworthy by never making mistakes. Everyone makes mistakes. You become trustworthy by making it easy for the people around you to address them with you. When your manager has to spend 20 minutes working through your defensiveness and explanations before the two of you can even talk about what went wrong, the original mistake becomes almost secondary. Now the problem is not just that something was missed; it’s that dealing with the mistake became a problem too.
The goal isn’t to take the blame for everything or pretend that circumstances never matter. It’s to be able to acknowledge your part, deal with the immediate problem, and then have a reasonable conversation about the context if there is more to understand.
Territoriality Is Another Form of Ego
Executive support roles can create unusual feelings of ownership.
“My executive.”
“My calendar.”
“My meeting.”
“My vendor.”
“My process.”
A strong EA absolutely should have command over their domain. But command and possession are two different things.
Imagine another EA reaches out directly to your executive to coordinate something. Maybe that isn’t your preferred process, or maybe there is a legitimate reason everything should normally funnel through you. It would be easy to take it personally and think, Why is she going around me? But a more useful question is, What process will make this easiest and safest for the executive?
If there is a reason the protocol needs to be reset, then reset it. Have the conversation, explain the process, and make sure everyone understands how things should work going forward. But the goal isn’t to defend your territory or prove that you’re the person who should be in the middle of everything. The goal is to make the system work as well as possible for the executive.
The same principle applies to information. An EA who holds onto knowledge because being the only person who knows how something works feels like job security eventually becomes a bottleneck. The EA who documents systems, shares information appropriately, creates backup plans, and helps colleagues understand how things work becomes much more valuable because the organization no longer depends entirely on one person.
That shift—from being an EA who has to know everything to being the EA who documents systems, shares appropriate information, builds backup plans, and helps colleagues succeed becomes something far more valuable: A leader.
Being “Above” Things Is Usually a Warning Sign
One phrase that should make any support professional pause is: “That’s not my job.”
Sometimes, it genuinely isn’t. Boundaries matter, role clarity matters, and so does capacity. If responsibilities are continually being added without any conversation about priorities, resources, or compensation, that’s a legitimate issue that should be addressed.
But there’s a big difference between saying, “I don’t have the capacity to take on this ongoing responsibility, so can we talk about where it should live?” and simply saying, “I’m not doing that. That’s beneath my level.”
Great EAs understand that being senior doesn’t mean being above small tasks. If the CEO can carry a box into the conference room, there’s no reason the EA can’t carry one too. If the COO notices that coffee has spilled just before an important guest arrives and grabs a towel, that doesn’t make her any less senior. She’s simply taking care of what needs to be taken care of.
The people who are most confident in their roles are often the least concerned with whether a particular task feels important enough for their title. They understand that their value isn’t diminished by occasionally doing something small, and they don’t need to protect their status by proving that certain things are beneath them.
Ego Can Quietly Destroy Relationships
The most damaging part of ego in an EA role usually isn’t one dramatic incident. It’s what happens when a lot of small interactions start adding up.
A colleague may stop asking you questions because you seem territorial. Your executive may hesitate before giving you feedback because every conversation turns into an explanation. Another assistant may stop sharing information because every collaboration seems to become a question of who owns what. Someone on the operations team may start to feel like you see their work as less important than yours. Eventually, people start finding ways to work around you instead of with you.
That can be incredibly damaging for an EA because so much of the role depends on relationships. You need people to answer your calls and help you squeeze your executive into an already full schedule. You need the facilities person to jump in when something goes wrong five minutes before a meeting, and you need another EA to tell you that her executive’s flight changed before anyone else knows.
Those relationships are part of how you get things done. Your reputation inside the organization is, in many ways, part of your professional infrastructure.
Being competent matters. But so does being someone people trust, respect, and genuinely want to help. When people know you’re reasonable, collaborative, and focused on getting the right outcome rather than protecting your territory, they’re much more likely to go the extra mile when you need them to.
Ego-less Does Not Mean Spineless
This point deserves some emphasis because “check your ego” can easily be misused in the workplace. You are allowed to disagree, say no, ask for recognition, advocate for a promotion, document your accomplishments, negotiate your compensation, and correct someone who repeatedly takes credit for your work. You can say, “I don’t think that approach is going to work, and here’s why.” You can establish boundaries and expect to be treated with respect.
Having less ego doesn’t mean making yourself smaller or staying quiet when something matters. It means not making every interaction about you.
You can be confident in what you bring to the table without needing everyone around you to acknowledge it in every moment. You can know that you deserve recognition without needing to be the person who gets credit every time. You can disagree with someone without needing to prove that you’re right.
That distinction is important. Confidence comes from knowing your value. Ego comes in when you need other people to validate it for you.
How Do You Actually Work on Your Ego?
You cannot simply decide, “I’m going to have less ego.” You have to practice noticing it. Start by paying attention to moments when you feel unusually defensive, slighted, territorial, or offended. Before reacting, ask yourself:
What am I actually protecting right now? The executive? The company? The quality of the work? Or my own status?
Do I need credit here, or do I simply want credit?
Am I explaining because context is necessary, or because I don’t want to look wrong?
If nobody knew I handled this, would I still think it was worth doing?
Am I resisting this task because it is genuinely an inappropriate use of my role—or because it feels beneath me?
Would I rather be right, or would I rather get this solved?
Is someone stepping on an important process, or am I simply uncomfortable that I’m not controlling it?
What would the most useful response be if my feelings weren’t part of the equation?
There is also tremendous value in practicing the language of low-ego professionalism.
“I missed that.”
“You’re right.”
“I hadn’t thought about it that way.”
“That’s a better idea.”
“I can take care of it.”
“I don’t know, but I’ll find out.”
“Sarah actually deserves most of the credit for that.”
“We all worked on it.”
“I see where I created confusion.”
None of those statements make you look weak. In the right workplace, they usually make you look confident and secure enough to admit when you’re wrong, give credit where it belongs, and focus on getting the work done rather than protecting your ego.
Let Other People Be Good Too
One of the easiest ways to see whether ego is getting in the way is to watch what happens when someone else gets to shine. Can you genuinely support a colleague’s good idea, even when it isn’t yours? Can you tell your executive, “Actually, that was Michelle’s idea,” without feeling the need to add what you contributed? Can you teach someone something you know without needing to establish that you’re the expert? Can you let another assistant take ownership of something you could probably do yourself? And when the whole team gets praised, can you be happy about the outcome without worrying about whether your individual contribution was recognized?
Senior EAs should be looking for opportunities to help other people succeed. That might mean sharing context, making an introduction, giving someone credit for a good idea, teaching a newer EA a trick you’ve learned, or making sure an executive knows when someone behind the scenes did exceptional work.
There’s a funny thing that happens when you consistently give credit where it belongs: people tend to trust your judgment more, not less. You don’t have to make sure everyone knows how much you contributed because, over time, people notice who makes things work.
You don’t have to announce it constantly.
The Goal Is to Become Secure, Not Small
The ego-less EA is not the quiet person sitting in the corner saying yes to everything. Quite the opposite. They may be the person confident enough to tell the CEO, “I don’t think that’s a good idea,” while also being perfectly comfortable refilling the printer paper afterward without wondering whether that task is beneath someone at their level.
They can run the board meeting and move the chairs. They can receive praise without needing more of it, and they can watch someone else receive praise without feeling diminished by it. When they make a mistake, they can acknowledge it without immediately becoming defensive. And when they need to advocate for themselves, they can do that without turning every interaction into a referendum on their importance.
They can say, “I was wrong.” They can say, “She deserves the credit.” They can say, “I’ll handle it.” None of those things take away from their value. If anything, the ability to say them without feeling threatened is part of what makes them so effective.
That combination—confidence without constant self-protection—is extraordinarily powerful in an Executive Assistant. Because ultimately, the best EAs aren’t asking themselves all day: How do I make sure everyone knows how valuable I am?
They’re asking: What does this situation need from me right now?
And, over time, that is often exactly why everyone comes to understand just how valuable they are.