Doctrine and the Infuse Equation: When Overwatch 2 Bets on the Support Player's Mind

Where failures fall, I pick them up and turn them into poetry. And at BlizzCon 2026, what fell was not a defeat — it was a design manifesto. Overwatch 2 has introduced Doctrine, a vampiric support carrying a two-charge Infuse mechanic, and carrying a quiet belief that the game's support players are finally mature enough not to be coddled with linear, predictable, easy-to-press healing. I sat in my usual PC Bang, headphones still echoing the keyboard sounds of last night's match, and I read the leaked Doctrine information three times in a row. Not because I was curious about a new hero. But because I recognized a signal in it: Overwatch 2 is admitting that the support role has been designed for years as a function of combat, rather than as a brain that orchestrates combat. Doctrine is a belated apology, written in the language of resources. This is my analysis of Doctrine — not a hero reveal piece, but a rereading of the design philosophy behind it. PC Bang 2026 — where keyboards strummed songs for destinies. And sometimes, a new mechanic is also a new destiny. The context around Doctrine is more complex than it appears. Overwatch 2 enters Season 5 in a fragile state of balance: the tank role is dominated by heroes with strong self-regeneration, DPS races through short burst-damage windows, and support is stuck between two extremes — either high healing throughput with no decisive impact, or strong utility completely dependent on teammates. In that stuck space, the best support players are doing something the design never anticipated: they are becoming rhythm-setters of combat through reading skill, not through raw healing numbers. Doctrine is introduced exactly when Overwatch 2 needs a support that can prove this role deserves the title of "carry." The Infuse mechanic allows Doctrine to amplify other abilities, turning every use into a strategic decision: are you buffing mobility, or buffing healing output? Two charges, no more. That sounds simple, but it is one of the greediest decision-making structures Overwatch has ever introduced to the support role. I once wrote that a championship is only a shadow; the journey is what illuminates. With Doctrine, the shadow is the total healing number, while the journey is every time you weigh using the last Infuse charge to save a teammate or hold it for the next fight. That is the poetry inside defeat — because every time you choose wrong, you see it immediately, on screen, with nothing to hide behind. Let's begin with the core mechanic. Infuse is not a single ability. It is a resource. This resource exists as two charges, and each charge can be poured into another ability to change that ability's behavior. Technically, this is an "amplifier resource." It differs from a cooldown in that a cooldown is limited by time, while Infuse is limited by situation. You cannot wait for Infuse to recharge by standing still. You must create a situation worth spending it on. This point is extremely important, and I have not seen many people state it clearly. In most traditional support designs, abilities are designed to have value when used correctly, but they still retain basic value when misused. For example, a heal used early still heals, just wastefully. But with Infuse, the value lies in the amplification decision. If you amplify the wrong ability, you lose a resource charge with no substitute value. This is why I call Doctrine a hero with a "decision tax" — a tax levied on decisions that are not yet mature enough. In terms of archetype, Doctrine belongs to the vampiric support family. This is not Overwatch's first attempt at this line — Moira is an older example, but at a different scale, because she could drain to heal yet lacked resource depth. Doctrine is said to push vampiric further: it does not only drain to self-heal, but converts drained resources into amplification for teammates. This is an intelligent design loop: you must approach opponents to gain resources, but you are also a support — meaning you belong to the hero group most likely to die when standing in the wrong position. The paradox of trivial details lives here. In high-level matches, people usually look at KDA, healing per 10 minutes, ultimate economy. But with Doctrine, the most important statistic may be one never shown on the scoreboard: the number of times a player uses Infuse on the right ability at the right time. I have watched hundreds of support matches at the highest level in Korea, and I believe this will be the kind of data analysts must track manually — at least in the early phase. The two-charge Infuse mechanic creates a fairly steep skill curve. At low skill, players will burn both charges immediately upon entering a fight, driven by a "use it to be safe" mentality. The result is that they run out of resources exactly when teammates need them most. At medium skill, players will hold the second charge as insurance, creating a "starving sustain" state — enough healing not to die, but not enough to win. At high skill, players will know the first Infuse charge must be spent in the first window of a fight, when both teams still have full resources, because that window decides the game. And the second charge must be saved for the clean-up phase. I have not seen official confirmation on whether Infuse recharges over time or conditionally. This is an extremely important blind spot, and I must state it clearly: if Infuse recharges over time (say one charge every 12 seconds), Doctrine will be a durable sustain hero suited to area-control metas. If Infuse recharges conditionally (say draining enough health restores a charge), Doctrine will be a hero demanding continuous combat, suited to high-pressure metas. These two scenarios produce two entirely different heroes in terms of power, and the community lacks enough data to distinguish them. This leads me to the contrarian portion of this piece. There is an overly optimistic wave surrounding Doctrine, and I want to place it under a microscope. That wave says Doctrine will be a "complete" support: mobility, healing, self-sustain, and teammate amplification. But Blizzard's hero design history shows a fairly stable rule: when a hero has too many value axes, it will be capped on one axis to avoid creating an exclusive pick. Doctrine will not escape that rule. The right question is not "is Doctrine strong." The right question is "which axis is Doctrine cut on." There are three possibilities. First, it is cut on direct healing — meaning without Infuse, it heals less than the average of its peer supports. Second, it is cut on survivability — meaning to gain vampiric resources, it must risk positioning to a near-suicidal degree in high-burst metas. Third, it is cut on Infuse resources — meaning two charges span an entire match, or the recharge time is so long that every misjudgment costs half a minute of combat. I lean toward the second and third possibilities occurring together. Reason: vampiric support always carries an internal paradox — to drain, you must enter range, and entering range means dying easily. If Blizzard wants Doctrine's drain to be strong enough to be a significant resource, they must give it some safe approach, or some escape. But its mobility is said to depend on Infuse — meaning you must trade a resource for mobility. This is a harsh loop: to live you must spend Infuse on mobility, but spending Infuse on mobility removes healing amplification. Skilled Doctrine players will have to live inside that trade-off all match long. I write in the gap between two fights. And that gap is precisely where Doctrine is designed to live. In that gap, the Doctrine player does not stand still. They read the map, read teammate positions, read enemy cooldowns, and decide where the next Infuse charge should go. This is a far more complex cognitive process than pressing heal repeatedly. And precisely for that reason, I believe Doctrine will create a greater divide between good and average support players than any hero added in the past two years. Consider the Perk system, another piece of information that has surfaced. Two Perks mentioned are "Cost of Life" and "Transfusion." I do not have full mechanic descriptions, but the names say a lot. "Cost of Life" suggests a life-trade mechanism — perhaps consuming own health for an effect. "Transfusion" suggests blood transfer — perhaps transferring drained blood to teammates. If read through that logic, these two Perks shape two entirely different Doctrine playstyles: one that gambles its own life for greater value, and one that converts personal resources into teammate resources. This is the point I want to stress: Overwatch 2's Perk system is not a mere side option. It is a second design layer on top of the base mechanic, and it changes how a hero is played in each specific match. With Doctrine, Perks may be the deciding factor in whether it is a safe hero or a reckless one. If Cost of Life lets Doctrine spend health to boost drain efficiency, it turns Doctrine into a snowball hero — stronger the more it fights, but riskier. If Transfusion lets it share drained blood, it turns Doctrine into a purely team-oriented hero. I once watched an amateur match in Gangnam where a support player picked Moira and tried to play in carry style. He drained well, but his team lost because no one could hold the combat rhythm. That is the lesson about the limits of vampiric support in old design. Doctrine is expected to fix that limit by turning drained resources into a shareable form of amplification. But expectation is not data. And I am always cautious with heroes advertised by expectation. One more thing must be said about the competitive context. Overwatch 2 is in a phase where the support role competes with itself. Existing supports have been optimized over many seasons, and players have built muscle memory around them. Doctrine is a hero that breaks that muscle memory. It does not reward fast reflexes. It rewards pre-judgment. This means that in the early phase, Doctrine will have a systematically low win rate — not because it is weak, but because players have not learned its rhythm. Overwatch history shows heroes with resource mechanics usually have a longer adaptation period than cooldown-mechanic heroes. For example, heroes with resource bars or charge systems typically take three to six weeks for the community to find optimal play. With Doctrine, I predict that period will last longer, because there are two variables at once: which ability to Infuse, and which Perk to pick for which situation. This decision combination is far larger than a hero with only one resource mechanic. There is another aspect I want to address, and one I see rarely discussed: Doctrine's impact on the tank role. In Overwatch 2, the relationship between support and tank is symbiotic. Tank creates space, support maintains space. If Doctrine can amplify healing onto a specific tank, it may change how teams build compositions. For example, if Doctrine can boost survivability for a dive tank, the dive meta could return stronger. If Doctrine can boost healing for a brawl tank, the brawl meta could be reinforced. But this is where I must speak about the limits of available information. I read the Doctrine leaks carefully, and I must admit the origins are not clearly identified. Most information points lack specific sources. And one detail caught my attention: the timing mentioned is BlizzCon 2026, a future marker. This raises questions about the authenticity of the entire content. I do not want to build analysis on an uncertain foundation. So I will state clearly: this piece is analysis based on circulating information, and it is more hypothetical than conclusive. That is why I chose a cautious approach. I do not claim Doctrine will be strong. I do not claim it will be weak. I only point out that its design structure has a clear internal logic, and that logic has predictable consequences. That is what I can do as an analyst. The rest is time, data, patch notes, and thousands of community matches. Speaking of data, I want to address an aspect any Overwatch 2 analyst cares about: Doctrine's pick rate and win rate in the early phase. History shows new heroes often have high pick rates and low win rates in the first week, then pick rate falls and win rate rises as players learn to play them. With Doctrine, I predict this curve will have a different shape. Pick rate may not be as high as new DPS heroes, since support is a role less chosen by younger players. But win rate at high skill may rise faster, because Doctrine rewards players with reading skill. There is an interesting question I want to pose: can Doctrine become a frequently banned hero in high competitive play? This depends on whether it becomes a "must-pick." And that depends on how high its performance ceiling is. If Doctrine can amplify a key teammate ability enough to change fight outcomes, it will be banned. If not, it will be only a situational pick. I think the first possibility is more likely, since the Infuse mechanic is designed to create clear power spikes. A contract is not just a number — it is a confession of love. And hero design is the same. A hero is not just a set of abilities — it is a statement about how developers see players. Doctrine declares that Overwatch 2 believes in support players. Believes they can handle a complex decision-making system. Believes they need not be protected by easy-to-use abilities. This is a respectable statement, but also a risky one, because it bets on an assumption unverified at global scale. In the Overwatch community, there are two streams of opinion on Doctrine. The first holds this is a step in the right direction, because it brings depth to the support role. The second holds this is an unnecessary complication, because support is already complex, and players do not need another decision layer. I lean toward the first, but with a caveat: depth only has value when it leads to visible differences. If good and average players achieve similar results with Doctrine, that depth is decorative. What I want to see in the first weeks after Doctrine's launch is clear differentiation. I want to see that players with good reading skill achieve markedly higher win rates than players with only good mechanics. If that happens, Doctrine has fulfilled its design mission. If not, it will be just another hero on the list, chosen for raw power rather than depth. There is a cultural aspect I want to address. In the Korean esports community, the support role holds a special place. Support players are respected for their ability to endure pressure and read the game. In other regions, support is sometimes seen as a side role. This cultural difference means Doctrine may be received differently across regions. In Korea, I predict Doctrine will be warmly received, because it aligns with the respected philosophy of support play here. In other regions, it may face initial resistance. I write from Seoul, where I have lived for years, and I see this difference clearly in PC Bang practice sessions. Korean players tend to adopt complex mechanics faster, because they are trained in a highly competitive environment from a young age. Doctrine, with its decision-making system, may be a hero Korean players exploit earlier than the rest of the world. This is a potential advantage for Korean teams in the early phase. But I must also speak of the downside. Doctrine's complexity may create an entry barrier for new players. In a game that already has dozens of heroes, adding one that demands many decisions can increase cognitive load. This is a design issue Blizzard must weigh. If Doctrine is too hard to play at a basic level, it will be ignored by most players, and its depth will serve only a small group. That is an undesirable outcome for a hero designed to reshape a role. I think the solution lies in the learning curve. If Doctrine has an accessible floor and a high ceiling, it will serve both player groups. This means its basic abilities must work without Infuse, and Infuse must be an optimization layer for experienced players. If designed that way, Doctrine will be a successful hero. If not, it will be a controversial one. Looking ahead, I see Doctrine as part of a larger trend in competitive game design: a shift from mechanical skill toward cognitive skill. For years, esports was defined by reflex and precision. But as games grow more complex, the deciding factor is gradually shifting toward decision-making under pressure. Doctrine is an expression of that trend. It does not reward the fastest clicker. It rewards the best thinker. This is why I care about Doctrine not only as a hero. I care about it as a signal of esports' future. If games continue in this direction, esports analysts will have to change how they evaluate players. We will not only look at mechanical metrics, but also at decision quality. And that requires new analytical tools, new metrics, and new ways of understanding. I have spent many years watching esports and writing about it. I have seen many heroes born and many heroes vanish. I have seen bold designs fail because the community was not ready, and conservative designs succeed because the community needed stability. Doctrine sits between those poles. It is bold in mechanic but conservative in role. It demands much but does not break structure. That is a delicate balance, and I am curious whether it holds when exposed to millions of players. There are defeats grander than every mediocre victory. And in hero design, there are failures that teach us more than successes. If Doctrine fails — that is, if it does not create the differentiation expected — that failure will be a valuable lesson about the limits of complexity in design. If it succeeds, it will open a new chapter for the support role. Either way, I will be here, writing about it, analyzing it, and finding the poetry in it. Finally, I want to return to what matters most: the players. Every hero analysis is only half the story. The other half lies with players — those who will pick up Doctrine, test it, fail with it, and ultimately shape it. No designer can predict how a community will exploit a hero. Doctrine will be played in ways Blizzard never imagined. And that is the most beautiful thing in esports: community creativity always exceeds developer imagination. So when Doctrine launches, I will not only look at numbers. I will look at moments — the moment a player uses the last Infuse charge to save a teammate from certain death, the moment another player holds it and wins the next fight. Those moments will be poetry. And I will pick them up from where they fall. That is how esports writes its stories. Not with scoreboards. But with small decisions, made in the gap between two fights. Doctrine is a hero born for that gap. And I believe it will find players who know how to fill that gap with their minds. I write in the gap. That is where I live. That is where esports lives. And that is where Doctrine will be defined.