Doctrine and the Rhythm of Supports: When Overwatch Went Looking for Someone Who Knows How to Drain Life

Opening: Six Seconds of a Runner

On a September evening in Seoul, I sat rewatching a support player's sequence in an Overwatch match. It wasn't a flashy highlight. There was no ultimate tearing through the enemy formation, no decisive headshot. Just a short movement: the support ran from the backline to the frontline, dodged a projectile, healed a teammate on the brink of death, then retreated before being chased. The whole sequence lasted roughly six seconds.

I rewound it ten times. And within those six seconds, the player made twelve small decisions: three direction changes, two cooldown calculations, four target selections for healing, and three risk assessments. I have spent my entire career analyzing moments like this in traditional sports, from track and field to swimming. But it took watching Overwatch for me to fully understand: support is the role with the highest decision density in any combat sport I have ever studied.

Nobody thinks about support that way. Audiences remember the scorer. Media reports on the clutch plays of DPS. Meanwhile support - the ones who keep the formation alive - are pushed into the shadow of the highlight reel.

Until Doctrine appeared.

I have been following news about this new Overwatch hero for months. A support with a vampiric theme, an Infuse mechanic with two charges, and a perk system that allows for playstyle customization. But what caught my attention wasn't the hero's power. It was the question it raises: is Overwatch trying to redefine the rhythm of support?

Context: A Role Never Properly Understood

To understand why Doctrine matters, we need to look back at the history of the support role in Overwatch.

When Overwatch launched in 2026, support was designed with a simple philosophy: heal your teammates. Mercy, Lucio, Zenyatta, Symmetra - each hero had a different approach, but all revolved around maintaining the team's health bar. The role was seen as "low-skill," dismissed by DPS players, and often assigned to newcomers.

By Overwatch 2, the picture changed. Blizzard introduced the 5v5 system, removed a tank, and forced supports to be more proactive. Ana, Baptiste, Kiriko, Lifeweaver - each new hero brought a new tool: blinding, invulnerability, cleanse, pulling teammates. Support was no longer just healers standing in the back. They were the ones orchestrating the rhythm of the match.

But one problem remained unsolved: support always depends on teammates to survive. A Mercy cannot save herself if her teammates don't protect her. An Ana can do nothing if she gets dived without peel. The role is strong in coordinated teams but weak in solo queue environments.

Doctrine was designed to solve exactly that problem.

It is a support with a vampiric theme - capable of self-sustaining through dealing damage. The idea is not new in the world of games, but it is new to Overwatch. In a game where support is seen as a "dependent role," a hero capable of sustaining their own life is a bold design statement.

And I think this is the moment to be clear: I do not believe in hero promotional articles. Those previews are often written by people who have never played the hero at a high level, based on trailer information and a few lines of patch notes. We need more than that.

Based on my experience following Overwatch matches and hero release cycles over the years, I have learned one thing: new heroes are never as strong as the trailer. But sometimes, they are strong in a completely different way than the developers predicted.

Core Analysis: Dissecting Doctrine

Let's start with what we know for certain about Doctrine.

Layer One - The Kit

Doctrine is a support whose central mechanic is called Infuse. This is a resource system with two charges, allowing Doctrine to amplify her other abilities. More specifically:

• Amplified Mobility: Doctrine can use Infuse to increase her own or a teammate's movement speed. This is an important tool in the current meta, where speed determines map control.
• Amplified Healing: Infuse can be used to increase the output of healing abilities. This is what makes Doctrine a potential "burst healer."
• Ultimate Cannot Be Infused: Doctrine's Ultimate cannot be infused, which creates a clear ceiling on the hero's overall power.

The notable point: Infuse has two charges, but I have no information on how the charges regenerate. This is an important information gap. If the two charges regenerate independently, Doctrine can maintain continuous pressure. If they share a cooldown, the hero's power is severely limited.

In Overwatch, two-charge resource systems often create a particular psychological pressure. Players must constantly face the question: use it now or save it? This is the kind of decision I call "save versus spend" - one of the hardest decision types in combat sports, because it has no absolute right answer. It depends on the state of the match, the skill of the opponent, and the mental state of the player themselves.

Layer Two - The Perk System

Overwatch 2 introduced a Perk system that allows players to customize heroes within a match. With Doctrine, we know of two perks:

• Cost of Life: I do not have detailed information, but based on the name, this may be a perk that trades health for power. If so, it fits Doctrine's vampiric theme.
• Transfusion: This perk appears to relate to the life-drain mechanic, possibly increasing recovery when dealing damage. This could be a key factor in Doctrine sustaining herself during prolonged teamfights.

The Perk system is one of the biggest changes Overwatch 2 made from the original. It allows players to adapt to each match, rather than using a fixed ability set. With Doctrine, this system could create multiple playstyles - from a pure healer to a damage-dealing support.

Layer Three - The Problem With Current Information

This is where I have to be blunt: most of the information about Doctrine currently comes from unverified sources. The original article I read did not specify sources, and many information points were marked as "no source." The reference to BlizzCon 2026 - a future event - raises further questions about the content's authenticity.

This does not mean the information is wrong. But it does mean we need to be cautious. In my profession, an unverified source is not a source - it is a rumor.

So let's analyze Doctrine as a design problem, not as a statement of power.

The Rhythm of a Life-Draining Support

Let me return to my track-and-field metaphor - but this time, with purpose.

In the 800m, there are two main tactics: positive split (faster in the first 400m, slower in the last 400m) and negative split (slower in the first 400m, faster in the last 400m). Most athletes choose positive split out of the psychological fear of being left behind. But the greatest athletes - like Emmanuel Korir at Tokyo 2026 - choose negative split. They understand that the race is not decided in the first 400m, but in the last 400m, when everyone else has exhausted themselves.

Doctrine, with her life-drain mechanic, operates on a similar logic. A life-draining support does not win by healing the most. They win by sustaining their rhythm the longest.

Imagine a situation: your team is losing a teamfight. The DPS have fallen, the tank is holding on with 20% health. A normal Mercy would try to heal the tank, but she cannot deal damage to change the situation. A Doctrine, with her life-drain, can both deal damage to reduce pressure on the tank and recover herself and her teammates. This is the core difference.

But this is also a potential weakness. A life-draining support depends on dealing damage. If the opponent has strong control tools - like Ana with anti-heal, or Sombra with hack - Doctrine loses her main source of recovery.

This is the balance problem Blizzard must solve. Make Doctrine too strong, and she will dominate the meta. Make her too weak, and no one will play her.

Comparison With Existing Supports

Let's place Doctrine alongside current supports:

• Moira: Also has a life-drain mechanic, but Moira heals through a limited resource (healing orb and primary fire). Doctrine appears more flexible thanks to Infuse.
• Brigitte: Has self-healing and damage capabilities, but at close range. Doctrine appears to have a wider range of influence.
• Kiriko: Has mobility and teammate invulnerability, but no self-healing through damage.

Doctrine's biggest difference is ability amplification. In Overwatch, very few heroes have mechanics where abilities interact in this way. This is a "combo" design - players must think about the order in which they use abilities, not just use them when off cooldown.

When I compared Doctrine to existing supports, I noticed something interesting: Blizzard seems to be trying to create a support that can operate independently, rather than depending on team structure. This is a notable change in design philosophy.

Meta Impact

If Doctrine works as designed, she could change how teams approach the support role. Instead of choosing a "main healer" and a "flex support," teams could choose two self-sustaining supports. This would change how compositions are built in professional matches.

But I need to emphasize: we have no data to confirm anything. No win rate, no pick rate, no PTR analysis. Every current conclusion is only an informed guess.

In Overwatch's history, many heroes were said to "change the meta" but ultimately became only situational picks. Baptiste, Lifeweaver, and even Echo all went through this phase. The important thing is not to overestimate or underestimate a hero before real data exists.

Contrarian Angle: When Hype Exceeds Reality

This is the section where I want to talk about what the original article did not say.

In the game media industry, there is a familiar pattern: every time a new hero is announced, a wave of articles appears. They describe the kit, praise the design, and predict meta impact. Most forget one thing: new heroes are usually not as strong as advertised.

Overwatch's history is full of examples. Baptiste was praised as the "perfect support" at launch but took months to find his place in the meta. Lifeweaver was initially seen as weak and needed multiple buffs to become viable. Sojourn was considered a "balanced DPS" at launch, then became a dominant hero.

This leads to a question: does Doctrine actually solve the support role's problems, or is it just a marketing solution?

Look at the numbers. According to Overwatch 2 data, the support role typically has the lowest pick rate in ranked matches. Players don't want to play support because they feel a lack of control. A hero with self-healing could attract new players, but does it solve the root problem?

The root problem is not that support is weak. The root problem is that support cannot create decisive moments. In a match, DPS can create highlights with a headshot. Tank can create highlights with an ultimate that tears apart a formation. Support can only... heal. And healing does not create highlights.

Doctrine could change that. With life-drain and ability amplification, she has the potential to create "clutch" moments - surviving a 1v2, healing a teammate at the last second, dealing enough damage to change the situation. But that depends on whether the design is bold enough.

And here is my contrarian view: perhaps Doctrine is not a hero, but a statement about design philosophy. Blizzard may be trying to change how players feel about the support role. They don't just want to add a new hero. They want to change the rhythm of an entire role.

Will they succeed? I don't know. But I will be watching.

There is one more thing I want to say about the information source problem. In my years as a sports documentary writer, I have learned that truth does not lie in flowery statements. It lies in small details that can be verified and cross-checked. The Doctrine article I read lacked those details. This does not mean we should ignore Doctrine. But it does mean we should approach it with healthy skepticism.

Conclusion: The Rhythm Has Not Stopped

I enter the archive like an archaeologist; when I leave, I am a storyteller. And the story of Doctrine - even with murky information - is a story worth telling. It speaks of a game trying to change, of a role searching for a new identity, and of a community of players always hungry for new experiences.

Every reel has a breath, and in Overwatch that breath puts a question to me: are we evaluating the support role correctly? Are we looking at their running rhythm, instead of only the final result?

Korir did not explode in Tokyo. Tokyo merely happened to stand near a fever that was brewing. And perhaps Doctrine is the same - perhaps she is not a hero that changes the game immediately. But if her design philosophy is correct, its impact will come later, but deeper.

When Doctrine launches, I will be there, watching every step. Not to see whether she is strong or weak. But to see whether she can change the rhythm of the game.

And if she can, then perhaps - only perhaps - we will have to rewrite how we tell the story of the quiet heroes.