There is a part of us that needs to be fed. That needs to hear it did well. That pulls for recognition before it has even checked whether the moment calls for it.

If you are a vendor PM reading this, I suspect you recognize that. Not because you are flawed. Because you are human.

The way I perceive it, ego is not a character flaw. It is something more structural. A survival mechanism that learned a lesson that is not serving, you somewhere along the way. Instead of keeping you safe, it keeps you visible. Instead of protecting the real you, it protects an image.

When the ego is driving, you lose access to the thing you need most in complex situations: the ability to step back, observe, and sense what is actually happening. You stop reading the room. You stop seeing the people in front of you clearly, because you are too busy tracking how you are landing with them. Your attention has turned to managing perception rather than managing reality.

The image

In society, roles come with images. The project manager image is a pretty specific one. The leader. The one in control. Knows it all. Can pull strings and make people do what needs to be done. Certain, assertive, walks chin up, radiates confidence.

So many vendor PMs feel they need to perform exactly that. That they cannot afford to show uncertainty, insecurity, or the simple truth that they do not have every answer. To be your true self, in a complete picture, including the not knowing, the vulnerability, the moments where you are not in control. That is not an image most PMs feel they can afford to radiate.

The image is not just a pressure from within the PM's mind. The world around them holds it too. Stakeholders both at the client and within their own organization. Everyone expects the confident leader in control. When you are not acting according to that image, especially on a project that is in trouble, the usual response from the outside world is that the PM is not helping the situation.

So the pressure to perform the image is real. From inside and outside.

What the act costs you

The cost of letting your ego win is exhaustion. You end up running an act the entire day. You are not being yourself, which comes effortlessly. You are performing an image, which drains you. And subconsciously you do not like it either. You have to do more and more to keep that image alive.

But cost is not just personal. It affects the success of the project as well.

When everyone protects their image, the project becomes a fairy tale. Nobody surfaces the real picture. A positive image is what the ego is after, so that is what gets projected. Challenges get buried in positive context. Status reports become performances of competence rather than reflections of reality. And the true state of the project disappears from view. The part that needs attention. The part where decisions are waiting.

You cannot solve the problem that is not on the table. And for hiding the problem, you can be blamed. The fact that the content or the solution is not progressing the way it should can be undesirable, yes, but there is typically tolerance for that. Especially when it is clear that the process followed, the intent, and the effort to get it right are there. The intolerance is for the hiding. For the fairy tale.

The vulnerability paradox

If you are truly comfortable in your vulnerability, comfortable being your complete self with the good and bad, the world around you actually recognizes the power of it. We perceive a whole person. And we trust whole people.

But if you are vulnerable and trying to hide it, performing confidence you do not have, the world perceives the exact opposite. The inauthenticity is what damages credibility. Not the vulnerability itself. So the cost the PM fears, "if I show weakness I lose credibility", is backwards. The act of hiding is what erodes trust. Not the admission that you do not have every answer.

And yet. This is not a clean before-and-after transformation. I am not perfect at this. There is still ego at play. But it is less and less, and I have the ability to recognize it. Quickly. Which gives me the power to decide what I want to do with it. The work is not to eliminate ego. The work is to notice when it has taken the wheel. To pause before it acts. To ask whether what I am about to do or say is coming from clarity or from my need for recognition.

What vulnerability actually opens up

In my experience, it starts with making it clear to the team that we are after managing reality. That there are few things we can do wrong, but the one thing is projecting an image that does not reflect reality. Because that prevents others from helping. With the right resources, the right decisions, at the right time.

But words alone do not open people up. They need to be accompanied by a clear division of responsibility. The team is responsible for the project content, for the solution quality. My role is to own all consequences that come from it in the outside world. So a solution not being up to standard will result in a conversation between me and my team. Not one aimed at blaming. One aimed at understanding. Where did it go wrong, and what do we need to fix structurally so it does not happen again. With that, I can give an accurate picture of the situation to whoever needs it.

That is the mechanism. When a consultant knows that an imperfect deliverable will not result in them being exposed to client anger, but rather in a conversation aimed at understanding and improvement, the cost of transparency drops. They can show reality without fear. And their openness gives me what is needed to represent the situation honestly. If they hide, I am working with an incomplete picture. If they are transparent, I am equipped to give clarity to the right people at the right time.
Their vulnerability feeds my ability to represent them accurately. It is a cycle.

When it is not your ego but theirs

The reality of the vendor PM role is that you will sit across from stakeholders whose ego is clearly running the show. A client sponsor protecting their image. A steering committee member reacting emotionally because the project status threatens how they look in front of their peers. These are not people you can coach on their ego. They are not your team.

But it helps to recognize that it is ego driving their behaviour. That a disproportionate outburst directed at your performance is a reflection of their ego feeling threatened. Understanding this gives you the space to respond differently. Not from the same place they are coming from.

Your options in the moment are limited. You can acknowledge without absorbing. "I hear your position." Or set a boundary without escalating. "I don't really like what I'm hearing." Both are honest. Neither is a fight.
But the real work happens before the heated moment. I have found it helpful to create clarity with senior stakeholders early, under the neutral umbrella of typical project success factors. From experience with other clients, senior stakeholders engaging in a certain way makes success considerably more likely.

Once a stakeholder consistently shows the opposite behaviour, you can return to that framework.
These senior client stakeholders are not your hierarchical equals. As a vendor PM, directly addressing their ego-driven behaviour can land as overstepping. This is where your own senior colleagues come in. They are the true peers of the client. Bring it to them. That is the right level for that conversation.

One more thing. Ego in a group setting is about not losing face. The same person, in a one-on-one without the audience, is often a different conversation entirely. Proposing to park it, take it offline, and hear this person out in a smaller setting is face-saving for them and opens the door to an actual conversation about what is really going on.

How you know ego has taken the wheel

You get upset. Your mind starts racing, trying to find scenarios that put you in the clear. You are writing scripts in your head to explain that you did nothing wrong. Or you get upset with the person who brought the message rather than dealing with what they actually said.

You are overly invested in how things look rather than what actually needs to happen next. Your calm is gone. Heart rate goes up, temperature rises. You show a temper or lose the thread of your thinking in a way that others can see, even when you think you are hiding it.

The contrast is simple. When ego is not driving, your response to the same situation looks like this: "We have a situation. Given its specifics, what are our options? What is the best way forward?" Same facts. Completely different internal response. The earliest signals are physical before they are mental. Your body knows before your mind will admit it.

Where it comes from

For me, this shift did not happen overnight. It was a side effect of working on personal development. Getting to know myself better, and gradually building the confidence that I do not need to be anything other than what I am, made it easier over time to show more of myself.

The need to perform the image naturally decreased. Not disappeared. Decreased. And the ability to recognize when ego has taken over became faster. That speed of recognition is what matters. Because it gives you choice. And choice, in my experience, is what freedom looks like in this work.

The reality of the role is that you operate in a world where it is expected that you know what is going on, that you have the situation under control. And at times it helps to project exactly that. When you are part of a joint steering committee and you are reporting on project status, showing that you have no idea how things are progressing will cost you the room. I am not saying the project needs to report green. I am saying you need to project that you understand what the status is and why. That is not ego. That is competence.

The distinction between the two is the whole point. Are you projecting understanding because you genuinely have it? Or are you performing confidence because your ego cannot afford for people to see that you do not?

One is your job. The other is a survival mechanism that learned to protect image instead of solve problems. Knowing the difference is the work. And it is work worth doing.