Behind Two Infuse Charges: Doctrine and the Battle to Redefine the Support Role in Overwatch 2

I remember the evening of November 2026 clearly, sitting in a rented apartment in Shenzhen, recalculating the xG for the match between Saudi Arabia and Argentina. The number 0.35 appeared on the screen, and immediately, I knew it would spark controversy. Not because it was wrong, but because it was right - in a way nobody wanted to accept. Three years later, I find myself in a similar situation, but this time with Overwatch 2 and a hero named Doctrine. And once again, the question is not whether the number is right or wrong - but who has the authority to define it.

There is a moment in Doctrine's test build that I keep thinking about. A support player stands at the edge of a teamfight, hand hovering over the ability key, waiting. Not waiting to heal. Not waiting to cast an ultimate. He is waiting for the right moment to Infuse - and during that window, no statistic on the scoreboard can capture anything. That is why I want to begin this article from that very moment, not from a stat sheet.

When a New Hero Is More Than a New Hero

Overwatch 2 has reached a stage where every new hero is no longer merely an addition to the roster. It is a design manifesto. The game's history shows that each hero release triggers a chain of consequences for the meta, for how compositions organize teamfights, and for how audiences understand each role.

With Doctrine, Blizzard is betting on a familiar but risky direction: vampiric support. This is not the first time the concept has appeared in the hero shooter wave. But the way it is implemented in Overwatch 2, with the Perk system and the Infuse mechanic, adds a new layer of complexity.

Information about Doctrine first appeared in the context of BlizzCon 2026 - a timeframe I must clarify: it lies in the future relative to when I am writing this. That means all my analysis of this hero is projection, not recollection. And I will not pretend I have actual match data to verify.

What I have on hand: an Infuse mechanic with two charges, the ability to amplify mobility and healing, and two Perks mentioned - Cost of Life and Transfusion. Alongside a statement that Doctrine's ultimate cannot be Infused. That is the raw material for me to construct a picture of this hero.

Two Charges, One Resource Management Problem

Infuse is not a simple buff. It is a decision-making system with weight.

Imagine you are playing Doctrine in a 5v5 situation. Your teammate is being pushed back. The first charge can amplify healing, keeping them alive. But if you use it at the wrong moment, before the enemy dumps their full damage, you waste a precious charge. The second charge can be used to move to a safer position. But if you leave that position too early, you abandon your teammate.

This is a structure I call "save vs. spend." It is not new in game design. But with two charges, Doctrine creates a more complex decision space than traditional supports.

Compare with Mercy: Mercy has resurrection and damage boost, but resurrection is a single ability with a long cooldown. There is no stored resource. Compare with Ana: Ana has biotic grenade and sleep dart, but each ability has its own cooldown, not a shared resource.

Doctrine differs in this: two Infuse charges force players to allocate resources between two different purposes - healing and mobility. And with each decision, they are pricing the value of each choice with the match itself.

This is where data becomes interesting. In my previous analyses of new heroes, I usually looked at win rate in the first week of release. But with Doctrine, that metric will not suffice. I need to look at charge usage rate - what percentage of charges are used for healing, what percentage for mobility, and how those decisions correlate with match outcomes.

The problem: that data can only be collected after the hero releases, and only if Blizzard provides a sufficiently detailed API. With what I have on hand, I can only construct hypotheses, not conclusions.

Vampiric Support: Advantage or Trap?

The vampiric mechanic - lifesteal, self-healing - sounds appealing. In theory, it lets Doctrine sustain herself without depending on teammates. In practice, it can create a trap.

Overwatch's history shows that heroes with self-healing are typically balanced by reducing healing output for teammates. Roadhog is the classic example: Take a Breather gives him massive self-healing, but he cannot use it for teammates. If Doctrine has both abilities - self-healing and teammate healing - then Blizzard faces an extremely complex balancing problem.

By design, vampiric supports are typically positioned in the "off-support" tier - heroes who do not heal enough to be a main healer, but compensate with pressure creation and independent survivability. Doctrine may fall into this group, or Blizzard may be experimenting with a new model.

Notably, the two Perks mentioned are: Cost of Life and Transfusion. The names already hint at trade-off mechanics. Cost of Life could be a Perk that converts Doctrine's health into a resource for buffing teammates - a form of "sacrifice" in gameplay. Transfusion could involve transferring health from enemies to teammates - a lifesteal-like mechanic in aura form.

If my hypothesis is correct, Doctrine will be a hero that requires players to constantly evaluate situations: when to sacrifice her own health, when to drain from enemies, and when to simply hold charges defensively.

This is where I must acknowledge my limits. I am writing about a hero I have never played, based on information from an unidentified source, with a timeframe in the future. Every conclusion about Doctrine's strength is speculation.

When Data Has No Provenance

This is the section where I want to take time to speak plainly.

When I received the Doctrine document, the first thing I did was check the source. And I found a problem: most information points were marked "Source: none." No author name. No specific publication date. No link to an official Blizzard announcement.

The "BlizzCon 2026" timeframe only adds ambiguity. If this is a future event, why does detailed hero mechanic information appear before that point? There are three possibilities:

One, this is leaked information from internal sources - possibly right, possibly wrong, but unverifiable.

Two, this is content created from community speculation - a fan-made concept presented as official information.

Three, this is an editorial error - the timeframe was misrecorded, and Doctrine has actually released or is about to release in a nearer window.

In all three cases, the conclusion is the same: I do not have enough basis to affirm anything about Doctrine with high confidence.

And this is where I must choose how to write. I could choose the safe path: only describe what was provided without evaluation. Or I could choose the honest path: present the information, but simultaneously question its reliability.

I choose the second.

The Blind Spot of Esports Media

The Doctrine story is not only a story about a hero. It is a story about how esports information is produced, consumed, and priced.

During a major tournament season - like the current phase - demand for content surges. Every piece of news about a new hero, a meta change, a transfer can become an article, a video, a viral tweet. And in that flow, the boundary between verified information and speculation grows increasingly blurred.

I have witnessed a similar case in the past. In 2026, when Saudi Arabia defeated Argentina, several outlets published different xG numbers, calculated by different methods, but none specified their sources. The result was readers surrounded by conflicting numbers, and the debate became a war of belief, not data.

The same could happen with Doctrine. If information about this hero spreads without provenance, the community will build expectations on false assumptions. And when the hero actually releases - with a different ability kit - the disappointment will be far greater than if the hero was simply not as strong as expected.

This is why I believe the role of a data journalist is not to report fastest, but to report most responsibly. And sometimes, that responsibility demands saying: "I do not know."

When a Weak Hero Is a Good Hero

There is a paradox in hero shooter design that I have observed over many years: the strongest heroes are not those with the highest stats, but those with the highest adaptability.

If Doctrine is designed to depend on two Infuse charges, she falls into the category of heroes whose "power curve" is controlled by the player. This means: this hero will never reach maximum power in the hands of an average player. She will only truly shine in the hands of support players with strong game-reading ability.

And that could be good news for meta health.

In Overwatch's history, heroes with simple kits but high effectiveness - like early Brigitte - often caused negative disruptions. Conversely, skill-intensive heroes - like Ana at launch - took time to be embraced, but then became meta pillars for years.

If Doctrine truly is a "high skill ceiling, low skill floor" hero, she will not immediately shift the landscape. But in the long run, she could reshape how teams organize their support line - from the "main healer + off-support" model to a more flexible one, where each support can take on multiple roles.

This is the point I want to emphasize: the true power of a hero lies not in the stat sheet, but in the decision space it opens. And Doctrine, with two Infuse charges, appears to open a fairly wide decision space.

Signals to Track

With all the limitations on sourcing and timing, I propose several signals to track for evaluating Doctrine once official information arrives:

First, Infuse's recharge mechanic. If charges recharge independently, Doctrine will have continuous sustain capability. If they share a cooldown, she will depend more on timing than volume.

Second, the interaction between Cost of Life and Transfusion. If these two Perks can combine to create an infinite healing loop, Blizzard will have to intervene. If they create a clear trade-off, Doctrine will be an interesting hero.

Third, Doctrine's pick rate in professional play after release. If OWL teams begin building compositions around her, that signals a meta shift. If she only appears in tier-2 matches, she may be a niche hero.

What Numbers Cannot Measure

Returning to the moment I opened this article. The support player stands at the edge of a teamfight, waiting. In that moment, no metric can express his value. No win rate, no healing per minute, no charge usage rate. Only the silence of a decision not yet made.

Data can measure the consequence of that decision, but it can never measure the moment of decision itself. And if Doctrine is designed to live in such moments, then every analysis of her - including this article - will only be part of the story.

I will keep watching. And when official information arrives, I will be the first to admit if my predictions are wrong. Because the truth is: I do not make tables for matches; I make tables for doubt.