Doctrine - Overwatch 2's Vampiric Support Hero and the Data Gap After BlizzCon 2026

The presentation at BlizzCon 2026 lasted exactly seventeen minutes. Doctrine appeared at the ninth minute, with two Infuse charges glowing on the ability bar. The mechanic lets her amplify healing or mobility for an ally. Blizzard calls Doctrine a vampiric support. The crowd clapped. I rewound the footage, noted every frame, and stopped at a detail few noticed: nearly every data point in the presentation materials came with no source. That is why I chose to write about Doctrine not as an event, but as a question of trust. In esports, both excitement and sobriety are equally necessary. Context first. Doctrine belongs to Overwatch 2, tied to Season 5 and revealed at BlizzCon 2026. She fits the vampiric support design family - the kind of support that can sustain itself or drain life. Her core mechanic is Infuse, with two charges. When activated, Doctrine can upgrade her own ability or an ally's to a higher tier. The Perk system ships with two notable options: Cost of Life and Transfusion. Positioning-wise, this is Blizzard's attempt to expand the support role - historically the least reinvented role in hero shooters. But most details - cooldowns, healing output, damage, duration - remain unannounced, or are listed with no source. We have a name, a design theme, and very little verifiable data. I will start with a dry observation. Across Overwatch 2's new hero reveals, Doctrine is the case with the lowest rate of sourced information I have recorded. Readers are shown a product, but not the data behind it. Based on my experience tracking matches and hero reveals, this is the signature of a pure product introduction, not a balance document. Design-wise, the two-charge Infuse is worth discussing. It creates a save-or-spend problem: hold a charge for an emergency, or spend it now to apply pressure. Similar designs have appeared on many supports in League of Legends, and history shows they push players toward two extremes - overly conservative or overly reckless. The balance between those extremes is the true skill test of a support. But hold on. Doctrine has two Infuse charges, yet nobody says the cooldown per charge. She has Cost of Life and Transfusion Perks, yet nobody says their concrete effects. BlizzCon 2026 is a future event, and all current information is promotional, not balance data. Put plainly: we are debating the strength of a character who has not yet appeared on the test server. This is where I remember something I once wrote. People think they are reading the match, when in truth the match is reading them. Doctrine is the same. People think they are analyzing a support hero, when in fact they are exposing their own expectations, fears, and herd instinct. Every time a new hero appears, the community splits into two camps: hype and doubt. Both are right, and both lack data. Historically, vampiric support is not new. Blizzard touched it with Moira and Brigitte, but never pushed to pure self-sustain. If Doctrine's description is accurate, this is an attempt to answer an old problem of the support role: over-dependence on teammates. A support that can sustain itself eases the load for the whole team, but also raises a role question - does a healer who also saves herself make other roles fade? Esports history shows that whenever a support gains self-sustain, the meta usually shifts in one of two directions. One: compositions move toward long control play, where fights are measured in minutes, not seconds. Two: a wave of backlash from rival communities triggers repeated balance patches. Both leave traces in pick/ban data. But to measure that, you need data. And that data does not yet exist. I also want to talk about the Perk system. Bringing Perks into new hero design shows Blizzard trying to add depth for competitive players. But Perks also increase balance variables: a hero can be strong in one player's hands and weak in another's, depending on Perk choice. For Doctrine, the two Perks Cost of Life and Transfusion seem to split two play styles: one accepts risk in exchange for power, the other maintains steady survival. If so, this design targets different player types - something some older supports never achieved. Here, I want to argue against myself - and against those who are over-excited. There is a very esports temptation: turning every new hero announcement into a historic event. But history teaches me that most new heroes pass through a hype - adjustment - stabilization cycle. Doctrine will be no exception, no matter how compelling the trailer. The bigger problem lies in sourcing. When most data points are marked no source, the question is not whether Doctrine is weak or strong, but: who is telling this story, and for what purpose? A product introduction is not an analysis. Mixing the two is the fastest way to lose credibility. Nor do I believe in framing vampiric support as a poetic title. A vampire in culture is a creature that drains blood to survive. Naming a support that way is an aesthetic choice, not a balance statement. A sober writer must separate the two. And so must a sober reader. The meta does not die; it metamorphoses into another poem. Doctrine may be the start of a new support lineage, or just a melody that drifts past the season. We will know when the test server opens, when win rates appear, when pro teams start experimenting. For now, what I keep is not a prediction, but a question: when a game introduces a new character through emotion rather than data, what should players believe? I do not predict the future; I only listen to the past whispering.