Doctrine in Overwatch 2: Two Infuse Charges and the Gap Between Marketing and Data

BlizzCon 2026. The Doctrine reveal ran less than two minutes, and I rewound it three times. Not for the visuals, but for one line in the ability panel: this support hero has exactly two Infuse charges. Two. Not an open cooldown cycle, not three stored uses like many other supports. For someone who has spent six years logging match data, two charges is a deliberate constraint. And constraints, not raw power, shape player behavior more than anything else. I looked at the two Infuse charges, then looked at the promise of "massive healing" in the reveal, and learned not to trust either. Six years ago, I started my career by logging match data. Since then, I have kept one habit: read the ability panel of a new hero before reading the marketing copy. The reason is simple. Marketing is written to sell. Ability panels are written to function. Between those two things there is always a gap, and most players only see the first half of it. Context: a support hero in an era of players already used to speed Overwatch 2 enters Season 5 with Doctrine, a support hero built on the "vampiric support" archetype. According to information presented at BlizzCon 2026, Doctrine focuses on self-sustain through lifesteal or life-conversion mechanics, rather than depending entirely on teammates. This is a notable design direction, because historically Overwatch support heroes have been rated poorly for self-defense. At the core of Doctrine's kit is Infuse, a stored-resource mechanic. Each Infuse charge lets Doctrine amplify another ability: increasing healing output for allies, or increasing her own mobility. In theory, this is a familiar design in many RPGs and hero shooters. But in Overwatch 2, where match tempo is measured in seconds, limiting activations to two creates a completely different problem. In six years of tracking matches, I have learned one thing: Overwatch support heroes are always evaluated through the wrong lens. People ask "how much can this hero heal", when the right question is "how does this hero force teammates to play differently". Doctrine, with two Infuse charges, is the clearest example of that difference. I work in Busan, where the esports market runs on its own tempo. Korean viewers do not just watch a new hero with their eyes; they watch with spreadsheets. They do not ask whether the hero is fun. They ask how the hero changes team composition structure. In a market where every roster decision is data-driven, a new support hero like Doctrine will be dissected long before it reaches professional play. Infuse: two charges and the save-versus-spend problem Start with the number two. In game design, the charge count of a resource mechanic is not a minor detail. It determines the entire decision-making pattern of the player. With three charges, a player can amplify healing, amplify mobility, and still keep one in reserve. With two charges, the player is forced to choose. And when forced to choose, players fall into one of two patterns: spend immediately to maximize short-term value, or save for the best possible moment. This is what I call the "save-versus-spend problem". In the matches I have analyzed, the best support players are not the ones who use the most abilities. They are the ones who know when to hold an ability. A heal pressed two seconds into a teamfight is worth far less than a heal pressed at the exact moment a teammate is about to die. Doctrine, with two Infuse charges, pushes this skill to a new level: every button press is not just an action, but a decision to give up another option. This is a design pattern that rewards game sense over aim. And in a game where most heroes are designed to reward aim, a support hero like Doctrine is a notable signal about Blizzard's design philosophy. The developer has repeatedly shown it knows how to create heroes with decision depth, and Doctrine, at least on paper, is one of them. But I do not want to move too fast. There is one thing the reveal does not clarify: do the two Infuse charges regenerate independently, or share a single cooldown? This is not a minor detail. If the two charges regenerate independently, Doctrine can achieve high healing output in extended teamfights. If they share a cooldown, her power will be severely limited in fast fights. This difference determines whether Doctrine is an S-tier hero or a B-tier hero. I noted this in my book with a large question mark. In data analysis, the details omitted from a reveal are often more important than the details emphasized. Blizzard emphasizes healing output. It does not emphasize the Infuse charge regeneration mechanic. That is where I will look for answers. The vampiric archetype: does self-sustain really change the game? The "vampiric support" archetype is not new to gaming, but in Overwatch 2 it marks a shift in how Blizzard treats the support role. Previously, Overwatch supports were designed on a "strong but fragile" principle: good healing, poor self-defense, forced dependence on teammates. Doctrine breaks that principle. A lifesteal or life-conversion mechanic means Doctrine can sustain herself in situations where other supports would die. This sounds appealing, but it also raises a balance question: if Doctrine both heals teammates well and sustains herself well, is she still a balanced support? Or is she becoming an "unkillable" hero? I have tracked matches where a new support hero was rated "over-tuned" in its first week, then heavily nerfed in the next patch. Overwatch history is full of such examples. A new hero launching in perfect balance is nearly unthinkable. Doctrine will be no exception. For someone who has been in the industry long enough, I no longer trust hero reveals. I trust PTR data after the hero is tested. And PTR data for Doctrine, at the time I write this, does not yet exist. There is another aspect of the vampiric archetype few mention. In competitive games, lifesteal mechanics often create a special psychological effect. Players feel they are controlling the match, because they see their health bar rise with each attack. But a feeling of control does not equal actual control. In a match where opponents focus fire, Doctrine's self-healing may not keep up with the rate of health loss. I have analyzed many matches where a hero described as "good at self-sustain" ultimately died like any other hero when cornered. Confidence in self-healing can be a double-edged sword. It makes players complacent, and complacency in a professional match is a death sentence. The Perk system: Cost of Life and Transfusion One of the most notable details in the Doctrine reveal is the Perk system. Overwatch 2 already has a Perk system that lets players customize hero abilities during a match, and Doctrine has at least two Perks mentioned: Cost of Life and Transfusion. Cost of Life, as the name suggests, implies a trade-off mechanic: the player sacrifices part of their own health in exchange for a benefit for teammates. This is a familiar design in RPGs, but rare in hero shooters. It creates a moral problem within the match: are you willing to sacrifice yourself to save a teammate? Transfusion, referring to blood transfer or life conversion, may be Doctrine's core healing mechanic. According to the reveal, the original article's author expressed personal preference for this Perk. But I want to separate "personal preference" from "technical analysis". The revealer's preference is not data. Between preference and data there is always a gap. In six years of writing about sports, I have learned that what matters is not what people like, but what they choose under competitive pressure. A Perk loved in a reveal can become a Perk abandoned in professional play, because it does not fit the actual tempo. The Perk system in Overwatch 2 is a complex variable overall. It lets players customize heroes to their personal style, but also creates countless combinations that need verification. Doctrine with multiple Perks will take at least one season for the community to find the optimal build. And the optimal build in ranked play may differ entirely from the optimal build in professional play. Context determines the value of every number There is a line I keep in my book: a number is only correct when its context has not been stolen. With Doctrine, this is especially important. The reveal promises "massive healing", but massive healing in a test room is completely different from healing in a ranked match, where teammates move constantly and opponents apply constant pressure. In one match I tracked, a new support hero launched with healing output rated "the highest in history". But when it entered professional play, actual healing output reached only about 60% of the test room figure, because professional players know how to cut angles, how to pressure positioning, how to force supports to move instead of standing still and healing. Test room data is not match data. And match data is not professional match data. This is why I do not rush to judge Doctrine. I need at least two seasons of data to verify. That is the standard I set myself after a lesson in 2026, when I wanted to write immediately about a new tactical trend but was told to wait. I was frustrated, but eventually understood the value of waiting. In the Korean esports context, where I currently work, cross-verification of data is a mandatory standard. Professional teams do not make roster decisions based on one season. They need at least two, sometimes three. And with a new hero like Doctrine, waiting is not slowness. It is professionalism. What I want to emphasize here is: the healing capability of a support hero cannot be measured by a ceiling figure. It must be measured by actual value in each situation. A hero that heals little but at the right moment can have higher value than a hero that heals a lot but at the wrong moment. Doctrine, with the Infuse mechanic, has the potential to be the second type. But potential is not result. The contrarian angle: the problem is not Doctrine, it is the source At this point, I must say something few analyses mention. Everything I have analyzed is based on a source that is not clearly identified. The original Doctrine article I read does not give specific sources for most information. Many data points are marked "source: none". This creates a serious credibility problem. In my profession, information without a source is not information. It is rumor presented as data. Furthermore, the article mentions "BlizzCon 2026", a future date. This raises the question: is this real information about an upcoming hero, or speculative content, or content with a wrong date? I cannot confirm. And when I cannot confirm, I must note that uncertainty. In data analysis, the most dangerous thing is not lacking data. The most dangerous thing is thinking you have data. The contrarian angle here is: most players will argue about whether Doctrine is strong. But the right question should be: do we have enough reliable information to evaluate Doctrine at all. And the answer, at this moment, is no. This does not mean I deny Doctrine's existence. It means I separate "verifiable information" from "marketing claims". Doctrine may launch. Infuse may work as described. But until Blizzard officially announces and PTR data appears, any conclusion about the hero's power is speculation. There is a concerning trend in esports media: product reveals presented as analysis. They use the language of data but lack data sources. They create a sense of professionalism but have no basis for verification. And readers, already used to the fast tempo of news, often do not stop to ask: where is the source? What will decide whether Doctrine succeeds or fails? If we set aside the sourcing issue and assume all Doctrine information is accurate, three factors will decide whether the hero succeeds or fails. First, the Infuse regeneration mechanic. As I said, if the two charges regenerate independently, Doctrine will be strong in extended teamfights. If they share a cooldown, she will be weak in fast fights. This is the most important factor and also the unconfirmed one. Second, self-sustain capability in actual combat. The vampiric archetype sounds appealing, but in a match where opponents focus fire, self-healing may not be enough to offset health loss. Many heroes have been marketed as "good at self-sustain" but ultimately died like any other support when focused. Third, community reception. A new hero can be strong statistically but not played for feel reasons. In Overwatch, game feel is the deciding factor. A hero can have a high win rate but a low pick rate, and vice versa. A hero's success lies not only in power but in the experience of playing it. These three variables will shape Doctrine's fate for at least two seasons. And I will track all three, not to predict, but to verify. Takeaway: signals to watch in the next cycle What I want to leave is not a conclusion about Doctrine, but a list of signals to watch. Signal one, official announcement from Blizzard. All Doctrine information must be cross-checked against official sources before being trusted. If BlizzCon 2026 actually happens and Doctrine is actually announced, that will be the first milestone. Signal two, PTR data. When Doctrine hits the test server, win rate and pick rate will be the first reliable indicators. If win rate exceeds 55% or drops below 45%, that is a balance signal. Signal three, professional community reaction. If top support players start practicing Doctrine on stream, that is a signal the hero has potential in professional play. Signal four, how professional teams adjust compositions. A new hero can change team composition structure, or it can be only a situational pick. I looked at the two Infuse charges, then looked at the promise of massive healing, and learned not to trust either. I looked at BlizzCon 2026, then looked at the source gap, and understood that the real question is not whether Doctrine is strong or weak. The real question is whether we have enough patience to wait for data before passing judgment. I entered this profession for the numbers, but I stayed for the stories the numbers do not tell. And Doctrine's story, at this moment, is still waiting to be told.