Ego plays aren't killing your Team. Your Leadership does! - Part 1

Go ahead and argue with that headline. Because that reaction is exactly what this article is about.

When competitive Valorant teams talk about ego, they always talk about the same thing. The Jett who refuses to play off-angle because she needs the highlight. The IGL who never calls a bad round their own fault. The entry fragger who solo-peeks instead of trading because dying in a trade does not look as good on the scoreboard. These are real problems. They are also visible, addressable and nowhere near as dangerous as the ego problem nobody in your organization is talking about.

The ego that actually kills teams long-term does not come from the players. It comes from the people running them.

The Comfortable Lie every Team tells Itself

When a roster falls apart, there is a story that almost every organization reaches for immediately. The players did not understand the vision. They were not committed enough. They did not buy into what we were building. It is a story that is easy to tell, easy to believe and completely useless for actually improving anything.

There is a specific version of this that is widespread enough to deserve its own name. An organization decides to bring in a coach. They hand over responsibility in theory but never fully release control in practice. Every decision the coach makes is second-guessed at the ownership level. Every process they try to implement runs into invisible resistance from a leadership structure that was never actually willing to step back. And then, when results do not come, the coach is blamed, replaced and the cycle begins again with someone new.

The coach changes. The ownership structure does not. The problems repeat. And the organization convinces itself each time that it just has not found the right person yet.

This is not a talent acquisition problem. It is a leadership ego problem that has learned to disguise itself as one.

Union Atta went through this exact moment. After our GC roster could not be held together, for reasons on both sides, we had a choice. We could tell ourselves the comfortable version of events or we could sit down and actually look at everything.

We chose the harder option. And what we found was not pleasant.

The leadership errors we had made were just as numerous as the errors on the player side. Decisions made too quickly without enough information. Processes that existed because they had always existed rather than because they were actually working. Communication failures that we had attributed to players not engaging when the real issue was that we had not built an environment where engagement felt worthwhile.

That realization does not feel good. A lot of things get questioned when you are honest about it. But it was also the most valuable thing we have done as an organization, because it changed how we build.

The problem is that almost no team is willing to do this. The moment a roster falls apart, the narrative calcifies around the players. Leadership walks away with its assumptions intact and repeats the same structural mistakes with the next group of people. The players change. The outcome does not.

Reflection means looking at the entire System!

Here is what genuine reflection actually looks like, as opposed to the version most organizations perform.

It does not start with the question of what the players did wrong. It starts with the question of what the environment we created allowed or encouraged. Were the processes clearly defined? Did every person in the organization know exactly what they were responsible for and where their ownership ended? Was information flowing honestly between roles or was it getting filtered through ego before it arrived at the people who needed it?

At Union Atta, one of the clearest patterns we found was the "we have always done it this way" problem. Processes that had been inherited or improvised early in the organization's existence and then never re-examined. Nobody was actively defending them. They just persisted because changing them would require acknowledging that they had not been working.

But the most uncomfortable finding was more personal than that.

I had built a staff team I trusted. The Strategic Coach, the Analyst, the Team Manager. I believed in what each of them brought to their role. And yet internally I was quietly redoing their work. Checking behind them. Running the same analysis again to look for mistakes they might have missed. On the surface it probably looked like diligence. In reality it was a control problem, and it was entirely driven by ego dressed up as responsibility.

When I actually sat with that realization, I was genuinely shocked at myself. Not because it was malicious. But because it was so obviously counterproductive and I had never seen it clearly until that moment. It took me a while to trace it back to where it came from. For a long time Union Atta was a one-man show. I handled everything alone. Strategy, operations, communication, decisions at every level. That mode of working gets wired into how you think, and it does not automatically switch off just because you have built a staff team around you. The habits of a one-man show do not disappear the moment the org chart changes. They just become invisible problems inside a structure that was supposed to solve them.

The frustration that came from doing two people's jobs in my head while only being paid attention to do one was real. And because I never named it for what it was, it did not stay internal. It transferred. The team felt a tension they could not trace back to a source because the source was never visible. That invisible friction cost us more than any single bad decision ever could.

And if I am being completely honest, those habits do not disappear at all. I still catch myself slipping back into that mode today. The instinct to just handle something directly rather than trust the process, to review work that is not mine to review, to treat delegation as a temporary arrangement rather than a genuine transfer of ownership. What actually helps is having people around you who are willing to call it out. Our Team Manager does exactly that. When I start drifting back into one-man-show territory, they are the first to name it directly and remind me that whatever I am reaching for is no longer my area. That kind of accountability from within the staff is something most organizations never build deliberately, but it is one of the most valuable things a leadership structure can have. Someone who respects you enough to tell you when you are overstepping your own role.

The difference now is that when it happens, it gets named before it does damage. Progress in leadership, at least in my experience, looks less like transformation and more like increasingly early interception. And sometimes that interception comes from the people you hired, not from yourself.

I am fully aware that most coaches and leaders would never say any of this publicly. The fear of being seen as incompetent or weak is real in this space. Admitting that you were part of the problem feels like handing ammunition to people who are looking for reasons to dismiss you. But I genuinely believe a team can only improve if accountability starts with the people at the top, not just the people on the server. You cannot ask players to own their mistakes in an environment where leadership never owns theirs. It does not work that way, and everyone in the room knows it even if nobody says it out loud.

We had named the problem. Honestly, publicly and without the comfortable edits most organizations would make before letting something like this leave the room. But naming a problem is not the same as solving one. In Part 2, we get into what we actually did about it, where we went to find the answers and what the most significant structural change of all turned out to be.