Doctrine and Two Charges: What BlizzCon 2026 Hasn't Said About Overwatch 2's New Support Hero

BlizzCon 2026 closed with the debut of Doctrine, Overwatch 2's new support hero, and among the released materials one detail made me pause mid-broadcast: the "Infuse" ability has only two charges. Two charges. No more. For a hero designed to amplify both healing and mobility for the entire team, the number two is a thin line between control and collapse. I have spent seven years watching K League matches and Korean esports to understand one thing: when a designer introduces a limited-charge mechanic, they are handing decision-making power to the player — and betting on how many times that player will be wrong before they are right. Doctrine is no exception. She is a test. Doctrine arrives as Overwatch 2 enters its fifth season, with the Perk system having become an inseparable part of the meta. Unlike traditional supports such as Mercy or Ana, Doctrine is built around a "vampiric" archetype — a design direction Blizzard has tested in previous expansions but never pushed to become a core mechanic. This is the first time they have staked an entire support hero's kit on it. Doctrine's kit is organized around "Infuse" — allowing players to amplify other abilities, including both healing and mobility. Notably, most of this hero's power lies not in raw stats but in the timing of decisions. The two Perks showcased at the event — "Cost of Life" and "Transfusion" — revolve around the same logic: trading resources for greater effect within a short window. According to my notes, this is the first time in Overwatch 2's history that a support hero has been designed with two layers of resource management simultaneously: Infuse charges and in-match Perk selection. These two layers are not independent — they interact in ways I believe even the design team has not fully anticipated. In Overwatch 2's annual season format, where teams must maintain form across dozens of consecutive matches, a support hero carrying two variables within the basic kit is a change far larger than its surface suggests. The first thing to analyze is the Infuse mechanic. With two charges, Doctrine players face the classic "save or spend" dilemma. In a professional environment, this type of mechanic tends to produce two groups of players: those who spend too early and die in the opponent's hands, and those who save too long and let teammates die before they can intervene. Both lose. In theory, Doctrine has the potential to create an "active support" model that Overwatch 2 has long lacked. This hero does not wait to heal — she enables teammates to heal themselves or move themselves. This type of design has appeared in other team-based games and always comes with a consequence: it raises the skill ceiling of the support role very high while pushing the floor of experience very low. Weak players will find Doctrine weak; strong players will find her nearly invincible. The interesting part is the interaction between Infuse and the Perk system. If "Transfusion" allows converting health into resources for teammates, while "Cost of Life" trades Doctrine's own health to amplify effects, then players are forced to choose between two very different playstyles within the same match. This is not a choice between two upgrades — it is a choice between two play philosophies. At the tactical level, I believe Doctrine will produce a phenomenon I call the "narrow window effect." Specifically, her true power does not lie in continuous healing, but in the brief windows when both Infuse charges are activated simultaneously. Within that window — lasting perhaps three to five seconds depending on how Blizzard tunes it — Doctrine can reverse the outcome of a skirmish. Outside that window, she is just an ordinary support with average stats. The question I put to any professional team reading this: do you have enough coordination to exploit that three-second window, or will you let it slip every time due to broken communication? Esports history shows most teams lose for the second reason. And this is where I must speak plainly about my limits. The entire analysis above is built on a product introduction article — not from PTR data, not from win rates, not from any balance metric. When I checked the source, most information points in the original article lacked verified attribution. This problem is larger than any tactical assessment. Data never lies, but it preserves the questions no one has asked — and this time, I do not have enough data to answer. One detail in the original introduction concerns me even more: the timestamp recorded as "BlizzCon 2026." In the current context, this is a future date. The problem is not whether the information is right or wrong — the problem is that if I cannot verify the date, I cannot verify any conclusion about Doctrine's impact on the meta. I wrote about the 2026 World Cup and predicted Germany's shock exit because I had PPDA data as an anchor. This time, I have no anchor at all. Statements like "Doctrine heals a lot" or "Doctrine will survive well" are subjective opinions of the original author — not facts. And in my profession, opinions without numbers behind them are just noise. Germany had already lost before the match began — I have the spreadsheet to prove it. This time, I have no spreadsheet to prove anything about Doctrine. That is the truth I must admit, and also what I want readers to remember before sharing any article that hypes this hero. What I will track in the coming weeks is not Doctrine herself, but the speed of the Overwatch 2 community's reaction once PTR data actually appears. If Doctrine's win rate exceeds 55% in the first week, that signals an undervalued hero. If it is below 45%, the BlizzCon introduction overstated an unfinished product. And if it lands somewhere in the middle — that is the most interesting scenario, because it means Blizzard has learned to design a balanced hero from the start. And in Overwatch history, that rarely happens. The question left unasked in the press room is the strongest signal I have ever recorded. Let the data answer. I will only keep the question.