Hero Bans in Overwatch 2: Strategic Depth or a UX Trap?
And Why 93% of Players Ban Sombra
February 2, 2026 · 8 min read · Game UX, Overwatch 2, Case Study
With Season 16, Overwatch 2 introduced a feature the community has debated for years: Blizzard finally gave us the “Ban” button.
As a Game UI/UX Designer and an active player, I’m looking at this update from two perspectives. On one hand, it’s a powerful meta-game tool that forces players to think strategically. On the other, it’s a controversial UX decision that creates subtle conflicts and friction before the spawn doors even open.
In their deep-dive report (Weekly Recall), Blizzard revealed initial data confirming a key theory: bans aren’t just about tactics. They are the most honest player satisfaction survey available.
Let’s break it down: why does the industry need this, where does the system clash with user psychology, and how can UI design fix it?
Context: Why Bans at All?
Introducing bans is a direct response to one of the biggest challenges in long-running competitive games: Meta Stagnation.
- The “One-Trick” Problem: In any MOBA or Hero Shooter, “ideal” compositions eventually crystallize over time. Players get exhausted from seeing the same heroes (like the eternal Pharah-Mercy duo) in every single match.
- Player Agency: Systems Designer Gavin Winter emphasizes that the goal is to give players a tool for self-regulation. Instead of waiting months for a balance patch from Blizzard, a team can essentially “patch” the match themselves, right there and then, by removing a problematic hero from the equation.
Data Don’t Lie
The numbers from the report served as a stark diagnosis for the game’s current state:
- Sombra: The undisputed champion of hate at the system’s launch, 85% ban rate on PC and a staggering 93% (!) on consoles.
- Zarya: A confident second place (59%).
The Key Insight: Players don’t just ban heroes who are mathematically stronger (Win Rate). They ban those who are frustrating and ruin the Fun Factor. Blizzard confirmed this observation:
Heroes that are very unpopular might see more adjustments regardless of performance.
We finally have a tool to “vote with our wallets” (or in this case, our bans) against toxic mechanics, and the developers have heard us.
The UX Conflict: “Illusion of Control”
On paper, it sounds logical. But in practice, the implementation of the Preferred Hero phase creates significant friction in the user experience.
Problem A: Violation of the Mental Model
The interface asks the player to select a Preferred Hero before the ban phase. From a UX perspective, when a system asks a user to make a choice, the user subconsciously expects that choice to carry weight or protection.
Reality: Your choice has no technical impact. You can select a hero, and an opponent (or even a toxic ally) can immediately ban them. This leads to frustration: “Why did you ask me if you weren’t going to protect it?”
Problem B: The “Self-Ban” Paradox
I personally encountered a logic flaw: after selecting a Preferred Hero, the system allows me to vote to ban my own choice on the very next screen.
Reality: Sure, a modest text warning appears (in a standard system font): “Warning! You’re voting to ban your teammate’s preferred hero.” But the button remains active. The system allows users to destroy their own decision made 5 seconds ago. This isn’t user protection; it’s chaos.
Problem C: The Prisoner’s Dilemma
Players face a strategic trap: be honest and help the team build a strategy OR hide intentions to avoid losing their hero.
- If I show I play Ana, I help my team pick a tank that synergizes with me.
- But if I show Ana, some allies might ban her simply because they deem her “weak” in the current patch (or just to troll).
Result: A tool designed to improve communication paradoxically encourages silence and secrecy.
Problem D: Chaos at Lower Ranks
At high ranks, bans are chess. At Bronze/Silver ranks, they are Russian Roulette. Players often lack a deep understanding of the meta and ban randomly or target heroes who simply annoyed them in the last game. Without UI guidance, this phase turns into unnecessary noise.
How Do We Fix It?
Blizzard is already testing a “Negative Vote” mechanic (where a Preferred Hero receives -1 vote towards a ban). It’s an excellent step, the system starts acting as a Tiebreaker, protecting the hero in disputed situations.
However, as a UX designer, I see room for more elegant solutions that reduce cognitive load:
Solution 1: Soft Lock & Error Prevention
Don’t let me ban the hero I just selected as Preferred without a hard confirmation (e.g., a long-press interaction). This eliminates misclicks and accidental “self-sabotage” that often happens in the heat of the draft.
Copy Update: Change the warning to a blocker: “You cannot ban your own Preferred Hero.”
Solution 2: Managing Expectations via Copywriting
The current interface is too dry. Instead of a simple request to choose, be honest:
“Selecting a Preferred Hero helps your team plan, but does not guarantee protection.”
Transparency reduces toxicity. The player must understand the rules of the game before placing their bet.
I explored several UI patterns, from tooltips to system messages, but settled on a prominent sub-header (Option A) as the most effective way to arrest the user’s attention before they commit to a choice.
Solution 3: Planning Phase “Lite”
Overwatch 2 has a communication problem: the pick phase is often silent. Players select a Preferred Hero but say nothing about their playstyle. My proposal: Add a simple “Flex” button or an Archetype Selector (e.g., “Rush”, “Poke”, “Dive”).
- Reduces Pressure: If I don’t want to reveal my main (fearing a ban), I click “Flex.” The team sees: “Okay, this player is adaptable, no need to ban their pool.”
- Shifts Focus: Instead of thinking “Who do we ban to hurt the enemy?”, the team starts thinking “What style do we want to play?”
- Removes Noise: If 3 players select “Flex,” it becomes much easier for the others to coordinate bans without fear of tilting allies.
I propose this as an alternative to the rigid “Show your hero or stay silent” choice. It makes the system softer for those who just want good teamwork without the drama.
Conclusion
The Hero Bans system in Overwatch 2 is an excellent vaccine against meta stagnation. It adds strategic depth and forces players to broaden their hero pools.
However, for this phase to stop feeling like “Russian Roulette” (especially in Bronze, where stats show teams banning 6 different heroes chaotically), the interface must become the player’s ally, not a source of anxiety.
The introduction of the “Negative Vote” proves that Blizzard is listening and using data to improve the experience. I hope future UX iterations will make this process even friendlier.
What do you think? Does the strategic value of banning heroes outweigh the potential stress during the selection phase? Or should balancing be left entirely to the developers?