Doctrine and the Two-Charge Infuse Test: Overwatch 2 Just Rewrote the Rules of the Support Role

The big screen at BlizzCon 2026 had just gone dark when the name appeared: Doctrine. No long cinematic, no flashy skill showcase. Just a slim silhouette, a staff, and the word “support” blinking long enough for the hall to understand that Blizzard had announced the next support hero for Overwatch 2. The crowd applauded. I stayed silent.

Over the past four years, I have sat in front of a screen long enough to recognize an uncomfortable pattern in this game: every new support hero is marketed with the same vocabulary — “versatile,” “meta-defining,” “opening up a new playstyle.” Then, once ranked queues begin, players realize that most of them never even touch the skill threshold that hero demands. Doctrine, with its two Infuse charges and vampiric mechanic, stands right in front of that trap. But this time I suspect it is different.

Two Infuse charges are a resource-management problem shoved straight into a role that history has never forced to manage resources.

Before dissecting Doctrine, we need to rebuild the wider landscape. Overwatch 2 runs on a seasonal hero-release cadence, and every time a support hero appears, the community splits into two camps: one arguing Blizzard is refreshing the support role, the other arguing Blizzard is trying to sell skins. Each camp is half right. The dry answer lies in pick rate, and it is always harsher than either camp wants to admit.

Looking back at the supports added after Overwatch 2 launched, one pattern repeats. Kiriko, Lifeweaver, Illari, Juno — each name arrived with a promise of a new playstyle. But only a handful of them held their ground on the professional stage after a few months. The rest became situational picks, appearing in a few niche compositions before vanishing from OWCS teams’ selection screens. What separated the survivors from the discarded was not healing output, and not the beauty of the animation. It was the number of decisions that hero forces a player to make in each teamfight.

That is why I believe Doctrine sits in a special position. It does not just add another support to the list. It adds an opportunity-cost management variable to a role that was designed to react, not to plan.

Doctrine’s kit revolves around Infuse, a two-charge mechanic that amplifies other abilities. One charge feeds into healing output to boost the amount restored. One charge feeds into mobility to increase movement speed. The ultimate sits outside the amplification loop. And above all is the vampiric theme — the kind of hero whose survivability comes from dealing damage rather than hiding behind teammates.

At first glance it echoes the hybrid damage-support model seen before. But Infuse changes the nature of the story. A standard support makes decisions on a cooldown rhythm: if the ability is off cooldown, use it; if not, wait. Doctrine makes decisions on a resource rhythm: you have two charges, you must choose where to spend them, and you must accept that spending them here means losing them there. Those are two different cognitive problems.

To picture it more concretely, put yourself in a typical 5v5 teamfight. Your tank teammate is dropping health, but two enemy DPS are diving your backline. You have two Infuse charges. You push one charge into healing to save the tank and hold one charge for mobility to escape the two DPS. That is the safe option. But if you push both charges into healing, the tank lives, your team holds position, and the fight can flip in your favor. Or you push both into mobility, save yourself, let the tank die, and watch the teamfight collapse. Three choices, two charges, a window measured in seconds.

This is the kind of decision I call an “opportunity-cost choke point.” And this choke point has a dangerous property: it rewards good players and punishes average ones brutally. An average support playing Ana or Kiriko can still contribute, because their skill is mostly reflex. An average Doctrine will get stuck in paralysis out of fear of spending a charge wrong. They will hold charges too long, heal less than necessary, and turn a high-ceiling hero into a burden.

This is the point most analysts skip. They look at the potential healing number and conclude Doctrine is strong. But potential is not outcome. Potential is the ceiling; outcome is the floor. And Doctrine’s floor, judging by its kit structure, is lower than the floor of most existing supports.

What makes the story more interesting is the Perks system. Doctrine has at least two perks named in the reveal material: Cost of Life and Transfusion. The name Cost of Life already says a great deal about the design philosophy — the price of living. Transfusion hints at transferring blood, meaning moving life energy from one place to another. Both reinforce the core theme: Doctrine exists by moving life energy around the battlefield.

Tactically, this is a design direction worth tracking. In many recent seasons, the professional Overwatch 2 meta has revolved around short teamfights, high burst damage, and fast finishes. A vampiric support, if strong in that meta, would act like a brake. It would stretch fights out, turning quick strikes into attrition battles, and reward the team that can sustain pressure longer. If Doctrine is balanced at a strong but not excessive level, it could push the meta toward sustain, where endurance compositions return to a leading role.

But there is a paradox here worth facing directly. Sustain meta is a viewer’s nightmare. Long fights, few deaths, heavy healing — that is the kind of match that makes viewers change the channel. Blizzard knows this. They know a sustain meta that drags too long will reduce OWCS viewership, which is why their balance history always tends to crush strong sustain before it takes root. So Doctrine, despite being designed around a vampiric theme, will most likely enter the PTR phase in a deliberately limited state. And if you see it looking weak in the first week, do not rush to conclude. That may be design, not a mistake.

Another interesting detail lies in the ultimate. The material states clearly that the ultimate cannot be Infused. That decision breaks an assumption many players will carry over from other heroes: that resource always applies to every ability slot. On Doctrine, one slot sits outside the system. This implies Blizzard does not want players dumping all charges into a decisive ultimate moment. They want charges spent within the rhythm of normal teamfights, not in a climactic instant. This is a silent design statement: Doctrine is a hero of small decisions, not of highlight plays.

And this is where I draw my central argument. The Overwatch community has a habit of evaluating new heroes by their ability to create beautiful moments. Highlight clips sell heroes. But highlight clips do not win series. Series are won by minimizing mistakes, holding position, and managing resources. A lost teamfight is worth more than a boring win, because the loss teaches you what the boring win hides.

Doctrine, by its structure, is a hero built to teach those lessons. It does not give you a “win the teamfight” button. It gives you two charges and forces you to decide. After a hundred hours of play, you will be better at the support role in general, because you have been forced to think about resources in a way Ana or Baptiste never forced you to. That is a form of value that is hard to measure, but it exists.

Of course, that is the optimistic scenario. And as usual, I have to put the optimistic scenario on the scale against what opposes it.

What opposes Doctrine is simple: cognitive cost. Overwatch 2 players already process an enormous amount of information every second. They track teammate positions, enemy positions, enemy cooldowns, teammate health, ult economy, and countless audio cues. Adding a two-charge resource-management layer on top of all that may exceed the tolerance of most players, even at semi-pro level. If so, Doctrine will become a hero for a small, specialized group, much like other mechanically complex heroes in the game’s history.

There is a precedent worth referencing. During the period I watched the no-crowd tournaments of 2026, I noticed something about competitive pressure: when there is no audience, small mistakes are not magnified, and teams tend to take higher risks. A hero like Doctrine, with a high skill ceiling, would benefit from that environment — where mistakes are less punished by the sound of the crowd. But when the audience returns, pressure rises, and bold resource decisions become more expensive. This is a two-way effect not many people account for.

So which scenario is most likely? In my assessment, Doctrine will have a slow start. In the first two to three weeks after live release, its win rate will sit below the balance line. This is a familiar pattern for heroes that demand high skill. Later, as the community learns the resource rhythm and OWCS players begin exploiting it, the win rate will rise gradually. If Blizzard does not intervene with a nerf patch in that window, Doctrine could become a fixed part of sustain compositions next season.

Here I must be honest about my limits. I have watched many matches, but I have not held Doctrine myself. Everything above rests on reveal material and historical patterns, not on actual PTR data. And as always, data can betray the most beautiful intuition.

People call it delusion; I call it a hypothesis that needs testing. My hypothesis here is very specific: if you sample one hundred Doctrine players at Diamond rank or below two weeks after release, most will end matches with healing output lower than the hero’s kit allows. Not because the hero is weak. Because they have not yet learned to spend two charges at the right time. Their mistake is a mistake of perception, not of numbers.

That is what makes Doctrine different from most other support heroes. With Ana or Kiriko, the gap between ceiling and floor is filled by aiming skill. With Doctrine, that gap is filled by decision-making skill. Aim can be trained in the practice range. Decision-making can only be trained through failure in real teamfights. And failure in real teamfights costs time, costs rank, and costs your teammates’ patience.

There is another possibility I have not mentioned, and it deserves serious consideration. It is the possibility that Doctrine becomes a niche hero, shining only in certain compositions and neutralized by other heroes. In Overwatch 2, every hero has weaknesses, and a vampiric hero is often sensitive to anti-heal or healing-reduction effects. If the current meta contains many such tools, Doctrine will struggle to find stage time no matter how intelligently its kit is designed. This is a variable I cannot assess without PTR and actual OWCS data.

So let me close with what I truly believe. I believe Doctrine is an interesting design gamble, and that gamble deserves to be watched regardless of the outcome. If it succeeds, it will open the door to a new generation of resource-management heroes, and the support role will no longer be a role of pure reflex. If it fails, it will become a lesson about the cognitive limits of players — a lesson game designers will study for years. Both endings have value.

I wrote this article so you would argue with me, not so you would agree. Open the PTR, pick up Doctrine, count how many times you hold a charge too long, and tell me whether I was right or wrong. If its win rate exceeds 55% in the first month, I will admit I underestimated the community’s skill ceiling. And if it struggles below 45%, remember I said it first: this is a hero of small decisions, and most players will spend those two charges wrong in the very first week.