Doctrine and Two Infuse Charges: The Data Gamble of Overwatch 2 Season 5

BlizzCon 2026. The big screen froze on two Infuse icons placed side by side, and in the hall, applause broke at exactly the right beat. On my laptop, a new data column had just been added to the spreadsheet I had left open. The first question when a new hero is revealed is never "is this hero strong." The first question is: what rhythm does this resource mechanic create for team fights, and how does that rhythm match the way professional teams operate their supports?

Doctrine — Overwatch 2 Season 5's new support hero — arrives with a vampiric theme and an ability-amplification mechanic called Infuse. Two charges. A new decision layer. And a larger question: is Blizzard trying to break the old assumption that a support must choose between personal survivability and healing output for teammates?

When home advantage is no longer home advantage, I am forced to rewrite every assumption. In this case, "home" is the support evaluation model I have built across multiple seasons. And Doctrine has just touched the foundation of that model. I do not predict the future with intuition; I only read the traces numbers leave behind.

Context: The support landscape before Doctrine

After multiple balancing seasons, Overwatch 2's support picture had reached a relatively stable state. Ana holds the sniper-healer role with burst creation through Nano Boost. Kiriko takes the flexible role with dive potential and rescue through Suzu. Lucio brings speed and space control. Moira compensates for healing output with self-defense. Baptiste is the ideal support for static compositions thanks to Immortality Field.

Each support on this list has a "fixed contribution point" — an ability or mechanic that a team relies on to run a specific strategy. Ana provides long-range neutralization. Kiriko provides effect cleansing. Lucio provides speed to force engagements. Moira provides raw healing output. Baptiste provides zone-based protection.

This stability has a side effect. Once each support has a clear "slot," teams begin building strategies around those slots. They stop asking "which support is strongest" and start asking "which support does this map need." This is the state any new hero must face: it does not just compete on power, it must create a new slot or take over an old one.

Doctrine enters this picture with two distinctive traits. The Infuse mechanic allows amplification of other abilities — meaning Doctrine has a mid-match customization layer. The vampiric theme suggests self-sustain is central to the design.

The notable part is not whether Doctrine is the first support to own a resource mechanic. The notable part is where that mechanic sits in the player's decision framework. If Infuse has two charges, the player must choose between two actions out of many possibilities. This is the classic "save vs. spend" model in game design, and it often produces a clear gap between skilled players and casual players.

BlizzCon 2026 gave Doctrine a large reveal stage. But a stage is not data. Data arrives later, when the hero drops onto PTR and players begin testing. In the window between those two events, an analyst's job is to build hypotheses and publish them — so they can later be verified or refuted.

Historically, Overwatch 2 has introduced several new heroes in recent seasons. Each hero was designed to fill a gap or create a new playstyle. Kiriko was introduced to provide cleanse. Lifeweaver was introduced to open a rescue-by-pull playstyle. Illari was introduced to bring steady damage output. Each hero carries a design hypothesis Blizzard wants to test.

With Doctrine, the design hypothesis sits at the intersection of resources and survival. If this hero succeeds, it can open a new direction for support: self-sufficient rather than dependent. If it fails, it becomes a lesson in how a resource mechanic can turn into a burden.

Core analysis: Infuse and the rhythm of resources

Infuse is the heart of Doctrine. According to the announced information, players have two Infuse charges — two amplifications of an ability within a certain window. The mechanic can apply to a healing ability to boost output, or to a mobility ability to increase movement.

The first important point: Infuse cannot be applied to the ultimate. This limits the mechanic's scope and creates a clear decision threshold — players cannot use Infuse to "save" a losing situation with an ultimate. They must use it before that.

From a design perspective, this is a notable choice. It makes Infuse a "real-time" mechanic rather than a "match-ending" mechanic. Players must decide to use Infuse while a fight is still unfolding, when information is still incomplete. This is the kind of decision I call "a decision in tactical fog."

In any competitive game, the value of a resource mechanic lies in the gap between "knowing you need to use it" and "using it at the right moment." If that gap is too small, the mechanic becomes automatic and low-value. If it is too large, it becomes a source of frustration.

With two Infuse charges, Doctrine puts players into a classic saving problem. Spending both charges in one fight means the next fight has nothing left. Holding one charge means the current fight is weakened. This is the kind of decision I have seen across many sports — from saving substitutions in football to saving timeouts in basketball.

My spreadsheet on current supports shows an interesting trend. Supports with short, stable cooldowns (like Moira with unlimited healing) get played more at casual levels because they punish mistakes less. Supports with long, decisive cooldowns (like Ana with Nano Boost) get played more at the professional level because they reward well-timed decisions.

Doctrine, with two Infuse charges, sits between the two poles. It punishes mistakes — wasting two charges leaves the hero clearly weaker. But it also rewards correct decisions — two well-timed charges can create a swing.

The unanswered question is Infuse's recharge rate. If the two charges recharge independently, Doctrine can maintain a high tempo and suffer less punishment. If the two charges share a cooldown, Doctrine must be more selective. Current public information does not clarify this, and this is the first "data gap" I must record in my model.

Without that data, any conclusion about Doctrine's power must carry a wide confidence interval. This is not a weakness of the analysis. This is how honest analysis operates.

The vampiric architecture: self-sustain as a design philosophy

Doctrine's vampiric theme is not merely aesthetic. It reflects a specific design philosophy: a support should not be entirely dependent on teammates to survive.

In Overwatch 2, support is the most vulnerable role in a fight. They have the least health, the least mobility (with some exceptions), and are often the priority target for DPS. Professional teams build strategies around pressing the opponent's supports into hard spots. If the support dies, the whole team loses sustain.

A vampire, in popular culture, is a creature that drains blood to survive. In the context of hero design, this typically translates into a lifesteal mechanic. If Doctrine has such a mechanic, it would create another resource loop: deal damage to heal, and heal to keep dealing damage.

This loop has an important tactical consequence. Ordinary supports must choose between "dealing damage" and "healing." Doctrine can break that choice by binding the two actions into one. This is the design pattern I call "action fusion" — when one action serves multiple purposes at once.

However, caution is needed with this argument. Action fusion does not automatically create an advantage. If the lifesteal is too weak, it fails to compensate for the damage dealt. If it is too strong, Doctrine becomes unkillable in extended fights. Balance is everything.

In my data on lifesteal heroes across competitive games, I see a pattern. Lifesteal heroes often struggle to stay balanced. If the lifesteal rate is below 20% of damage dealt, the mechanic is nearly symbolic. If above 40%, the hero is usually nerfed within a few patches. The "sweet spot" sits between, and it is very narrow.

With Doctrine, the problem is even more complex because lifesteal combines with Infuse. Players can amplify damage to amplify healing. This creates a potential multiplicative effect — and multiplicative effects are usually the source of balance problems.

Morocco 2026: when defensive data spoke first, the world listened later. In that case, defensive data showed that a team could generate outsized value without controlling possession. In Doctrine's case, a similar question is asked: can a support generate outsized value without teammate protection?

The Perks system: Cost of Life and Transfusion

Overwatch 2 introduced the Perks system as an in-match customization layer. Doctrine has at least two Perks mentioned: Cost of Life and Transfusion.

Cost of Life, based on the name, likely involves trading health for a benefit. In game design, this is the classic "high risk, high reward" mechanic. The player accepts losing some health in exchange for a temporary advantage.

Transfusion, based on the name, likely involves transferring blood — either from self to ally, or from enemy to ally. In either case, this is a "transfer" mechanic — the player moves a resource from one place to another.

The notable point is that both Perks revolve around health. This is a clear signal that health is Doctrine's central resource unit. While other supports usually revolve around cooldowns or energy, Doctrine revolves around health as a convertible unit.

From a design perspective, this is an interesting direction. Health in Overwatch 2 is usually treated as a linear resource — losing health is losing, healing is healing. Doctrine can turn health into a non-linear resource — health can be traded, converted, and invested.

If Cost of Life allows trading health for damage or speed, Doctrine players must decide whether they have enough health to "invest" in an offensive push. This is the kind of decision I have seen in games with blood magic mechanics — often producing a clear gap between players willing to trade and cautious players.

If Transfusion allows moving health between teammates, Doctrine can take on the role of the team's "blood coordinator" — shifting health from those who need it less to those who need it more. This is a role with no clear precedent in Overwatch 2, and it could be Doctrine's "slot" in a composition.

Still, I must hold to my principle: no conclusions without data. A Perk name is not data. The specific mechanic, the specific numbers, and the specific interactions are data. While waiting, I record both Perks in the "hypotheses to verify" column.

The unknown of ultimate and cooldown

One of Doctrine's most notable points is what is not said. The ultimate is mentioned with a single piece of information: it cannot be amplified by Infuse. There is no description of the ultimate's effect, no cooldown information, no range information.

This is a significant "data gap." In Overwatch 2, the ultimate is usually a hero's decisive ability. It can flip a fight, break an enemy formation, or save a team from a loss. Not knowing Doctrine's ultimate is like evaluating a player without knowing which position he can play.

Infuse's cooldown is also unclarified. These are two data gaps I must place in the model as unknown variables. In data analysis, we often face unknown variables. The honest way to handle them is to record them and adjust confidence intervals.

Player value is just a number — until you read the error in the calculation. Similarly, a hero's value is just a set of numbers — until you read the error in the evaluation model. With Doctrine, I have an incomplete set of numbers. My model will carry high uncertainty until the data is more complete.

Comparison with current supports

To place Doctrine in context, I built a simple comparison table with current top supports.

Ana: ranged damage, shot-based healing, enemy neutralization through Sleep Dart and Anti-Heal. Strength: decisive impact. Weakness: vulnerable when pressured.

Kiriko: directional healing, teleport, effect cleanse via Suzu. Strength: rescue ability. Weakness: inconsistent damage.

Lucio: area healing, speed boost, enemy displacement. Strength: space control. Weakness: weak single-target healing.

Moira: strong directional healing, lifesteal for self-healing, mobility. Strength: high healing output. Weakness: no rescue ability.

Baptiste: explosive shot healing, Immortality Field, damage boost. Strength: zone-based protection. Weakness: low mobility.

Doctrine, based on current information, combines some Moira elements (lifesteal self-healing) with some new elements (Infuse amplification). Theoretically, it sits at the intersection of "self-sufficient support" and "amplifier support."

The core difference lies in the decision layer. Current supports revolve around the question "which ability, when." Doctrine adds a further question: "which ability to amplify, when." This is an additional decision layer, and like any additional decision layer in game design, it can produce depth or noise.

Impact on the OWL meta

If Doctrine is allowed in the Overwatch League, it will create adaptation pressure on teams. Top teams usually adapt quickly — they use an "exploitation week" to figure out how to use a new hero before other teams catch up.

With Doctrine, the exploitation week will revolve around one question: who is the support player with the best resource management? This is not a question about aim. This is a question about game sense — about reading fight tempo and timing decisions.

In my OWL data, I see a pattern: teams that succeed with complex supports (like Ana) usually have a support captain with strong game reading. Teams that succeed with simple supports (like Moira) usually rely on composition structure. Doctrine, with two Infuse charges, belongs to the first group.

This means Doctrine can create differentiation between teams. Teams with elite support captains can exploit Doctrine strongly. Teams without can skip the hero. This is the kind of "polarizing hero" Overwatch history has seen before — Sombra in certain patches being one example.

Pressure on elite supports

A less-discussed consequence of a new hero is the pressure on professional players. Every new hero means a new ability set to learn. For professional supports, learning Doctrine is not just learning a mechanic but learning a rhythm.

I have witnessed this across many seasons. When a new hero drops, professional supports must spend hours on PTR to become familiar. This is a time investment that is not directly paid — but it determines whether they can play the hero in competition.

With Doctrine, this investment may be larger than usual because of two decision layers (which ability to Infuse, when). This is "meta decision-making" — deciding how to decide. In sports, this is the hardest skill to teach.

I recall a conversation with a senior European analyst — the man who later sponsored my internship. He said the hardest part of support analysis is not measuring healing output, but measuring "the quality of decisions that were not made." Doctrine, with its two-charge mechanic, will produce many such "decisions not made."

Balance risks and historical lessons

Overwatch 2 history shows new heroes typically go through a standard balance cycle: overtuned at launch, nerfed in subsequent patches, stable after a few months. Kiriko, Lifeweaver, and Illari each went through this cycle in different ways.

With Doctrine, balance risk sits in two points. First, the lifesteal mechanic combined with Infuse can create a multiplicative effect — and multiplicative effects are hard to balance. Second, the two-charge mechanic can create too large a gap between good and weak players — making the hero "all or nothing."

In my data on resource-mechanic heroes across competitive games, I see a trend. Heroes with too high a "skill threshold" often have low win rates at casual levels but high at professional levels. This may be acceptable from a design standpoint, but it creates a problem for "casual player experience."

Blizzard in recent years has tried to lower the "skill threshold" of new heroes to make them more accessible. Doctrine, with its two-charge mechanic, appears to go against this trend. This is a notable design choice, and I will track whether it succeeds on revenue and player retention.

The contrarian angle: two charges can be a weakness

Most analysis of Doctrine will focus on how two Infuse charges create power. I want to pose a counter-hypothesis: two charges can be a design weakness.

My argument is as follows. In competitive games, resource mechanics have two sides. The positive side is decision depth. The negative side is cognitive load.

If players must constantly track two Infuse charges, on top of tracking teammate health, their own health, other ability cooldowns, and enemy positions, they may become cognitively overloaded. When overloaded, players tend to "simplify" — choosing one action rather than optimizing across many.

In practice, this can lead to a pattern I call "paralysis saving." Players hold both Infuse charges too long, waiting for the perfect moment, and eventually never use them. This is a behavior pattern I have seen in many similar resource mechanics — from energy bars in MOBAs to action counts in card games.

If this pattern happens with Doctrine, the hero will have "effective output" lower than "potential output." And in elite sport, effective output is everything.

There is a related lesson from Overwatch 2 history. When Baptiste was introduced, Immortality Field was considered a strong ability. But it also created a "saving effect" — players held Immortality Field for the perfect moment, and in many cases, they failed to use it in time. This is an example of a powerful mechanic delayed by caution.

With Doctrine, this risk may be larger because there are two charges. Players can fall into a loop: "I still have one more charge, I'll save it for the next situation." And the next situation never arrives.

This leads to a counter-intuitive conclusion: Doctrine's true value may be measured by "Infuse usage rate," not by "maximum healing output." And this rate will depend on the cooldown design — information we do not yet have.

I publicly record this hypothesis. If, after Doctrine launches, the Infuse usage rate is high, my hypothesis is wrong. If the rate is low, my hypothesis is correct. This is how I work: publish first, verify later.

Progressive conclusion: signals to track

Doctrine is a data gamble. It bets on a hypothesis: that a support can be self-sufficient rather than dependent. It bets on a mechanic: that two Infuse charges create depth rather than paralysis.

I do not predict the future with intuition; I only read the traces numbers leave behind. The traces will arrive when Doctrine hits PTR. At that point, I will track four signals.

First, Infuse recharge rate. If the two charges recharge independently and quickly, Doctrine will have a high tempo. If slow or shared, Doctrine will have a low tempo.

Second, Infuse usage rate. If players use charges frequently, the mechanic works as designed. If they hold charges too long, the mechanic is causing paralysis.

Third, the ultimate description. This is the missing part of the picture, and it could change every assessment I have made.

Fourth, the impact on the OWL meta. If top teams begin building strategies around Doctrine, the hero is creating a new "slot." If not, it will be pushed into the "situational support" position.

For those patient enough to wait a season to prove a number. I will be the first to open the spreadsheet when Doctrine officially launches. And I will be the first to publish publicly if my model is wrong.

The final question is not "is Doctrine strong." The question is: can a support be self-sufficient in a game where every mechanic is designed around mutual dependence? Doctrine is Blizzard's answer. Data will be the referee.