Doctrine and the Question of Consistency in Overwatch 2's Support Hero Design Rules

On the BlizzCon 2026 stage, the moment the trailer introducing Doctrine faded, the entire hall rose to its feet. I sat in the twelfth row, notebook still in hand, and what I wrote down was not the hero's name. I wrote: "Two Infuse stacks. Survive-kit perks. No patch notes yet."

Seven years ago, I sat in the same posture to log every decision made by referee Nestor Pitana in the France – Croatia final. I was fourteen then, just starting to label every phase of play I saw. Now I am twenty-three, living in Penang, working as a former-referee commentator, but the note-taking reflex has not changed. To me, a new Overwatch 2 hero is like a newly enacted rule. Not something to cheer about. Something to check for consistency with the existing system.

Doctrine is a support hero built around a vampiric archetype. Her central mechanic is Infuse – a two-charge resource that amplifies other abilities to boost mobility and healing output. She carries two named perks: Cost of Life and Transfusion. Her ultimate cannot be Infused. That is everything we have after the announcement show.

For a referee, that is not enough to issue a ruling. But it is enough to pose questions.

Context: a support role caught between two design generations

Overwatch 2 has travelled a long road since launch. The Perks system – introduced as an in-match customisation layer – has changed how players approach support heroes. Gone is the fixed 'one kit, one role' model of 2026-era Overwatch. Today, every support hero is a small system with its own niche and its own dedicated player base.

That is the stage Doctrine walks onto. Not an empty arena. A full row of seats.

Picture the current support role as a back four. Each support holds a zone. Kiriko owns teleport-and-cleanse space. Ana owns long-range pressure and crowd control. Baptiste owns burst healing and area immortality. Nobody overlaps. Stable, ordered, predictable.

Doctrine breaks that order like a box-to-box midfielder. She does not hold a zone. She moves, drains, amplifies herself. The vampiric archetype is nothing new in game history. From Moira to sustain heroes in other titles, drain-based design always carries one question: does the player have the discipline not to turn it into a selfish style?

That is the pivot point. And that is where I want to linger longest.

Analysis: the two-stack Infuse and the trade-off problem

Two Infuse stacks sounds simple. It is a save-or-spend mechanic – a classic design problem.

Imagine a referee holding two VAR reviews. Every use is a gamble. Use too early and you lose it when the decisive moment arrives. Hold too long and you fail to capitalise on a match tilting your way. That is precisely Infuse. Two stacks do not mean two arbitrary spends.

What I have not seen in any announcement: the stack regeneration rule. Do the two Infuse charges restore independently, or share a cooldown? This is not a small detail. It decides the hero's entire power curve. Independent regeneration lets Doctrine sustain constant pressure and likely makes her a top-tier sustain support. A shared cooldown forces her into a slow rhythm, and her value comes from picking the right moment rather than frequency.

I rewatched the trailer four times at 0.5x speed. No information. Blizzard is holding that for PTR.

And the perks. Cost of Life and Transfusion are the two named. I do not have full ability descriptions for either, but the naming says something. 'Cost of Life' suggests a trade-off mechanic – possibly sacrificing self-health for team value. 'Transfusion' suggests blood transfer – the ability to move life resources between units. Read through the vampiric archetype, Doctrine may be the first support hero genuinely built around managing blood as an in-match currency.

That is an interesting design direction. It is also a dangerous one.

Because when blood becomes currency, players optimise toward extreme blood-for-value trades. Overwatch history has seen heroes nerfed for exactly this. Moira was adjusted repeatedly. Brigitte created a sustain meta so toxic it needed a rework. Doctrine stands before the same trap: strong sustain turns the meta into an attrition war; weak sustain makes her useless against burst comps.

Balancing between those two extremes is the hardest problem any support designer has to solve.

There is one more detail I want in the record. The ultimate cannot be Infused. This is a very deliberate design choice. It means Doctrine's peak power is fixed – unamplifiable. In referee language, this is a penalty ceiling written into the law, so nobody can be sentenced beyond the frame. It shows Blizzard has learned from past support heroes that wrecked the meta.

But that ceiling raises another question. If the ultimate cannot be amplified, all Infuse value funnels into basic abilities. The gap between ultimates becomes Doctrine's strongest window – and also her most exploitable one if opponents know how to drain her stacks. This is a hero with a very clearly defined power window, and in professional play, such windows get scrutinised hard.

Contrarian view: a new-hero buzz is not evidence of strength

After every hero reveal, the community runs the same cycle. Beautiful trailer. Cool-sounding abilities. Streamers testing. Then launch day arrives and everything cracks in ways nobody predicted.

I once wrote about Lamine Yamal after his goal against France in the Euro 2026 semi-final. My colleagues called him a generational talent. I spent three days compiling data from 50 Yamal matches at Barcelona in 2026-24, cross-checking against Messi 2026, Mbappé 2026 and Pedri 2026. My conclusion: at least 50 more high-density matches were needed to establish generational status. My piece came out exactly three days behind my colleagues. It was right.

With Doctrine, I apply the same rule. 'Huge healing output' – if anyone says that – is a trailer-watcher's opinion, not match data. 'Stays alive well' is a reasonable inference from the vampiric archetype, not PTR evidence. And 'needs more time' is not a bland phrase – it is the only conclusion the current data permits.

At seventeen, I rewatched 43 crowdless Malaysia Super League matches and found referees favoured home teams 18.2% less than in the 2026 season. That figure did not come from feeling. It came from sitting down and counting. With Doctrine, there is nothing to count. And in my experience, it is precisely in those data gaps that hot takes breed most easily.

One more point few notice. BlizzCon 2026 is a very distant date from now. Revealing a hero this early, before PTR opens and before any balancing data exists, is a deliberate marketing strategy. Nothing wrong with that. But it means every current analysis – including this one – must carry a 'not yet verifiable' label. I am not afraid to say that plainly. For a former referee, admitting you lack evidence is the minimum condition for retaining credibility.

Emotion may tilt, but footage does not. And Doctrine's footage right now is a trailer under three minutes long.

Looking ahead: waiting on PTR and what to track

So what should we track?

First, the Infuse stack-regeneration rule. If PTR shows independent regeneration, Doctrine has the potential to shape a sustain meta. If it is a shared cooldown, she is a high-skill hero, a reward for game sense rather than spamming.

Second, PTR win rate. The thresholds to watch are 55% and 45%. Above 55% means she is over-tuned; below 45% means she will be waiting for a buff cycle. Overwatch history shows new support heroes typically land in one of those two states for at least two weeks before settling.

Third, signals from pro teams. If top-tier support players start grinding Doctrine on stream, that is a sign she has a place in the competitive meta. If not, she stays in ranked and creative content.

And fourth – the one I care about most – is how the community reacts to the vampiric archetype. Overwatch has had periods when sustain metas turned toxic. If Doctrine repeats that loop, she will not just be a new hero. She will be a referendum on the game's support design philosophy.

Every phase of play is a line in the record, and I write without omission. With Doctrine, I am still on page one. The footage has not rolled. The patch notes are unopened. PTR is not live. But if I learned one thing from 47 notebook pages and seven years covering the industry, it is this: referee data is not meant to convict, but to exonerate. Doctrine does not yet need exoneration. She needs time, a PTR cluster, and someone patient enough to count.

I will be that person.