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

In Part 1 of this article, we talked about how Union Atta went through a period of honest self-reflection after losing our GC roster and found leadership failures just as significant as anything that happened on the player side. If this is your first time here, the short version is this: ego at the leadership level is more destructive than ego at the player level, it is harder to see and almost nobody in esports talks about it openly.

This is the part where we get into what we actually did about it.

We looked outside Esports entirely

Naming the problem was one thing. Knowing what to do about it was another.

The honest reality after going through that self-reflection was that we did not have all the answers ourselves. And that was precisely the point. An organization that had been operating inside its own assumptions long enough to develop these blind spots was not going to find the solutions by looking deeper into those same assumptions. We needed external reference points. Models that had already solved problems we were only just learning to name.

The instinct in esports is to look at other esports organizations. But if the entire space has normalized certain dysfunctions, studying the space will only confirm those dysfunctions as standard practice. We needed to look further.

So we looked at the NASA Artemis program and at how the US Army approaches team building.

Yes. That sounds like an extreme comparison for a Valorant team. We know.

But here is why it made sense. Both of these are environments where the mission is complex enough and the stakes are high enough that individual ego cannot be allowed to compromise team function. Not because everyone involved is a perfectly humble human being, but because the system is explicitly designed to prevent ego from interfering with critical decisions.

In the NASA Artemis program, every role has a documented scope of responsibility and every decision of significance goes through a process that does not allow a single person's confidence or seniority to bypass the input of the people around them. Information flows upward through defined channels because mission success depends on the right information reaching the right people, not the most impressive-sounding information reaching the most senior person.

The US Army operates on a similar principle. The individual is explicitly subordinated to the mission. Not through humiliation or the suppression of identity, but through a structural clarity about what each person's role contributes and how that contribution serves something larger than personal performance. An individual's ego is not destroyed. It is redirected. Your value comes from how well you execute your defined function, not from how you are perceived relative to your teammates.

What both examples share is that the ego problem is solved architecturally, not personally. Nobody sits down with a soldier or an astronaut and tells them to be more humble. The system makes humility structurally rational. Your outcome is better when you operate within it than when you try to distinguish yourself outside of it.

What Sports Psychology actually says about Ego

Alongside the NASA and Army research, we also looked at sports psychology literature on team environments and what it says about why ego behaviors emerge in the first place. The findings pointed in the same direction, just from a different angle.

Ego plays in a team setting are rarely about arrogance in the pure sense. They are about visibility. A player who solo-peeks when they should wait for a trade is not necessarily selfish. They are operating in an environment where they do not trust that the system will register their contribution if they do the unsexy thing. They take the duel because the duel is measurable. The sacrifice play is not.

Sports psychology research on high-performing team environments consistently identifies the same root condition for reducing ego-driven behavior. Players need to trust that the people evaluating their performance can see the full picture of what they are contributing, not just the parts that show up in a scoreboard. When that trust exists, the incentive to manufacture visible moments disappears. You do not need to create evidence of your value when you already believe the right people understand it.

This changes what the coaching staff's job actually is. It is not enough to tell players that team play is valued. The system has to demonstrate it through how feedback is delivered, how performance is evaluated and how development conversations are structured. If a player consistently hears feedback that focuses on kills and deaths, they will optimize for kills and deaths regardless of what they are told in a team meeting.

At Union Atta, this directly shaped how we evaluate and develop players. Performance is no longer measured purely through statistics. Role fulfillment is assessed on its own terms, which means a Sentinel who holds a site flawlessly for three rounds without a single kill is recognized for exactly what they contributed. Every player also has individually defined development goals, so feedback conversations are not generic evaluations but targeted discussions about what that specific player is working toward.

We also introduced regular structured check-ins between staff and players. Not match debriefs and not tactical sessions. Dedicated conversations where a player can communicate how they are experiencing the environment, whether the goals feel achievable and whether the support they are receiving is actually landing. When players know that channel exists and that it is taken seriously, the need to perform for visibility drops. They are already seen. The system is already doing that work.

What WE changed at the Leadership Level!

Trusting someone with a role means accepting that their output is theirs, not a draft waiting for your corrections. One of the first concrete changes we made was a hard separation between operational and strategic decisions. Operational ownership belongs to the person whose role covers it. Leadership input on those areas now goes through a defined process rather than landing as an unannounced second opinion. That distinction sounds simple. In practice it is the difference between a staff that develops genuine confidence in their work and one that quietly learns to wait for approval before committing to anything.

The second change was that decisions at the leadership level are now documented and tracked. When a call is made, the reasoning behind it is written down before it is acted on. This forces clearer thinking at the point of decision and produces a record that can be reviewed honestly afterward. Decisions made under pressure or from incomplete information look very different on paper than decisions made from clarity. Over time that record becomes a mirror on your own judgment that no amount of self-assessment can fully replicate.

But the most significant change of all was one I had to make about myself. As a direct consequence of everything this reflection uncovered, I stepped back from the Head Coach role for our new roster entirely. I am now involved as Owner and as an advisor to the coaching staff. Not because I was forced out or because the role was taken from me. Because the honest conclusion of everything I have described in this article was that the best thing I could do for the team was to stop putting myself in a position where my control habits could interfere with the people I had hired to do their jobs.

That was not an easy decision to sit with. But it was the right one. And I think it says more about what accountability actually looks like in practice than anything else in this article. It is easy to talk about releasing control. It is something else entirely to restructure your own role inside the organization because you have genuinely accepted that the team is better without you in that position.

What I want to be clear about is that this was not an admission of failure as a coach. I did not step back because I am not good enough. I stepped back because I chose to. Because real development, whether it is a player working on their mechanics or a leader working on their habits, requires honest conditions. For me right now, those conditions exist outside the Head Coach role. Staying in it while knowing what I know about my own tendencies would have been the easier path. Choosing the harder one is how the team can grow even bigger. And that is a standard I cannot hold my players to if I am not willing to apply it to myself.

Reflection is NOT a One-Time Thing!

One of the things we committed to after going through that first honest evaluation is that it cannot stay a one-time event. Organizational reflection that only happens after a crisis is just crisis management. It does not build anything. It only repairs damage that has already been done.

At Union Atta, we now build periodic reflection into the ownership level of the organization. Not just a check-in on how the team is performing on the server, but a structured look at how the organization itself is functioning. Are the processes we built still serving their purpose or have they quietly drifted into "we have always done it this way" territory? Is information flowing the way we designed it to flow or are there new bottlenecks forming without anyone naming them? Are the decisions being made at the leadership level coming from clarity or from the same pressure and rushed judgment that cost us the first time?

These questions are uncomfortable every time. That discomfort is the point. The moment reflection becomes comfortable is the moment it has stopped being honest.

Did you get ragebaited?

Here is what most people will take from that headline. They will assume this article is defending ego. That it is arguing players should be allowed to play selfishly or that individual performance matters more than team function. Some will have already typed a response before finishing the first paragraph.

That misunderstanding is intentional. Because the real argument is more uncomfortable than either side of that debate.

Ego at the player level is a symptom everyone can see and most teams already have a conversation for. What this article is actually about is the version that operates above the players, in the coaching staff, in the ownership structure, in the accumulated habits of a leadership that never learned to examine itself because nothing ever forced it to. That version is invisible, structural and far more destructive than any solo peek on a lost round.

If your last project ended badly, the most valuable thing you can do right now is not open a new recruitment form. It is to sit down, without defensiveness and without an audience, and ask whether the environment you built was actually set up for anyone to succeed inside it. That process takes time. It might mean going into the next split without a roster. It might mean admitting things publicly that feel like weaknesses. It might mean discovering that the problems you attributed to players were partly problems you created.

Do it anyway. The teams that keep cycling through rosters without ever questioning the structure around them are not unlucky. They are unwilling. And the difference between those two things is entirely within your control.