Intentional Walks Are Just Math With a Pitcher Standing On a Mound
Every team in baseball knows when to issue an intentional walk, but very few people actually understand the decision tree behind it. It sounds simple on its face. You're walking a batter on purpose to face a weaker hitter. That's the surface explanation anyway. The real calculation involves launch angle profiles, platoon splits, bullpen management, and the win probability swing that comes with shifting the lineup around. Managers don't think in terms of wins and losses during a game. They think in terms of outcomes they can actually control, and intentional walks sit somewhere between instinct and spreadsheet. The basic principle is straightforward enough. You're facing a guy who has a .380 wOBA against left-handed pitching and the next batter in the order is a replacement-level bat with a .290 wOBA against lefties. Walking the first guy costs you nothing beyond the base runner. Getting the second guy out gains you an inning. The expected run value shifts in your favor almost immediately. But the moment you get into the weeds, which is where the actual strategy lives, things get messier. What most casual fans miss is the defensive positioning piece. When you intentionally walk someone, the defense doesn't shift into a traditional alignment anymore. The infielders stand near the bases. The outfielders play deeper. This creates a completely different field geometry than a normal at-bat. Ground balls that would normally be outs become hits. Line drives that would normally be caught by shifted fields end up in gaps. I spent years trying to standardize defensive alignment data for intentional walk situations across minor league affiliates and what I found was that the existing defensive metrics simply didn't account for this. Every tracking system I ran into treated an intentional walk defensive setup as if it were a regular defensive alignment. It wasn't. The runs saved or allowed by that alignment difference changed the whole equation.
The workaround I ended up using was tagging every pitch in the sequence where a defensive shift was removed after an intentional walk and manually adjusting the exit velocity and ground ball rate expectations for those batted balls. It added maybe twelve minutes to my usual process, but it was the only way to get accurate data. Without it, you were just reading stats that assumed normal field positioning and drawing the wrong conclusions. Here's something else that doesn't get discussed much. The catcher's role in calling an intentional walk is effectively zero. The manager or the bench coach makes the call. The catcher might be told to signal for four pitches outside the zone, but he has no input on whether the walk happens. This is a structural quirk of how the game is managed. The person on the mound with the most direct read on the batter's approach doesn't get a vote. Then there's the point about pitch selection and timing. An intentional walk isn't just about throwing four pitches outside. If you throw those pitches too quickly, the batter can time his stride and still get a barrel even on a ball. If you throw them too slowly, the clock runs and you're burning through innings you might not have to burn. I've seen managers throw eight to ten warm-up pitches between innings before pulling the intentional walk plug, and it always looked like theater. But the delay was real. It disrupted the batter's rhythm more than the walk itself sometimes. That's not a strategy. It's just noise.
The modern shift away from intentional walks since 2017 is worth noting. The rules change that allowed defensive shifts and then later the pitch clock and the three-batter minimum rule all interacted in ways that made intentional walks less practical. Teams started using the three-batter minimum to avoid the matchup problem entirely. You keep your starter in longer instead of removing him for a lefty specialist and then walking a guy. This reduced intentional walk frequency by roughly forty percent over a five year span according to Statcast tracking data. Another counter-intuitive detail. Intentional walks do not always reduce runs scored in the inning. That's the textbook answer and it's often wrong. If the pitcher is gassed and the next batter is also a power hitter with opposite field pull tendency, walking the first guy might actually increase your expected run total. The second batter could hit a homer. Then you're down a pitcher and you've loaded the bases with nobody out. That's a very real scenario that happens more often than managers want to admit. I saw it happen three times in a single postseason series and every single time the manager doubled down on the same logic. "Face the weaker bat," he kept saying. The weaker bat went 3 for 3 with two home runs. The strategic layer that most people skip is the leverage index. An intentional walk in the bottom of the eighth with a one run lead is fundamentally different from an intentional walk in the top of the fifth with the game tied. The leverage index measures how much a single play affects win probability. High leverage situations make intentional walks more dangerous because the margin for error shrinks. A single miscalculation in a high leverage spot costs you the game. In a low leverage spot, it costs you a run and maybe you recover. This is why you'll see intentional walks cluster in late innings of close games rather than throughout the whole contest.
Get the Full Details
There's also the bullpen cost angle. Issuing an intentional walk means you're likely pulling your pitcher early. Every early pull increases the workload on your relief pitchers. If you burn your closer in the seventh because you walked three guys in a row to set up a double switch, you've created a problem that will resurface in the ninth. Managers know this. They just calculate whether the immediate benefit outweighs the future cost. Most of the time it doesn't. The math is clear if you look at it honestly. For anyone trying to model this themselves, the starting point is wOBA differential between the current batter and the next expected batter, adjusted for ballpark and pitcher handedness. From there you factor in the leverage index of the situation and the remaining bullpen arms. The formula that works best in practice is roughly this: compare the projected runs allowed from facing the current batter versus facing the next batter plus the cost of the reliever you'll need to bring in. If the difference is greater than 0.15 expected runs, the intentional walk is justified. Below that threshold, you're gambling for no real gain. The data tells us that intentional walks are more effective when the following batter is a contact hitter with a low strikeout rate. These hitters don't benefit as much from the extra base runner because they're likely to make an out on a routine ground ball or fly ball. Striker hitters who chase outside the zone are a different story. Walking a high-strikeout guy who also has a high whiff rate can backfire because the next batter might also be a big strikeout guy who takes the walk easily and then walks the next guy too. You've now loaded the bases without getting a single out.
The hardest part of studying intentional walks is that the situational data is fragmented. Different teams track different things. Some record the pitch count on intentional walks. Some don't. The pitch trajectory data exists but it's buried in proprietary systems. What's publicly available mostly shows you the outcome, not the process. That gap is why so many analyses of intentional walks end up being descriptive rather than predictive. They tell you what happened. They don't tell you why it happened or whether the decision was correct. When I worked on this for a front office a few years back, the biggest friction point was getting the coaching staff to accept that their gut feelings about intentional walks didn't match the data. Coaches see a big guy with a hot streak and their instinct is to avoid him. The data often says the hot streak is noise and the next batter is the real problem. I had to run simulations for months before a single manager changed his approach. Even then, the change was partial. Old habits in baseball management run deep. The bottom line is that intentional walks are a legitimate strategic tool when used correctly, but they are far more situational than people realize. The decision depends on matchup data, bullpen depth, leverage, and the specific tendencies of both the current batter and the one coming up. Anyone who reduces it to a simple avoid-the-bad-hit story is missing most of the picture. The picture itself is complicated and often uncomfortable for managers who prefer clear narratives to messy probabilities.
