One Inning, Two Defensible Bunts
Although the “bunt wars” may not rage on, they are at least still simmering. The older, stale debates about whether sacrifice bunts are good strategy or the wastes of outs often miss the point by leaving aside game situation, game theory, the skill of the bunter, and other considerations. Even when such things are taken into account, discussions can get a bit abstract. Concrete examples of bunts and the situations around them can illustrate what complexities are involved in deciding whether a bunt is the right call. So let’s make it concrete: the sixth inning of the Red Sox-Royals game on Saturday provided two bunts worth closer consideration.
With the Royals leading 1-0 in the top of the sixth with none out and a runner on second, the Royals’ Alcides Escobar sacrificed the runner, Alex Gordon, to third base. In the bottom half of the inning, with the score the same, none out, and Jacoby Ellsbury on first base, Shane Victorino bunted him over to second base. We do have some tools that tell us much both the run expectancy given the base/out state (RE24) and Win Probability (WPA) given the overall game state (inning and relative score) changed. These do so at the time the play happens, so they are helpful for these sorts of inquires, which are attempts to evaluate the decision-making process at the time without respect to what happened later. For both bunts, run expectancy and win expectancy went down. On that basis, one might understandably conclude that both bunts, considered in themselves aside from eventual outcome (the Red Sox ended up tying the game that inning, and went on to win), were bad ideas.
Judging from Twitter (scientific survey!), many people thought the same about the bunts. It is easy to understand that side of things, especially since scoring went on beyond the bunts, making the one-run strategies look retrospectively silly. Without providing a definitive answer as to whether one, both, or neither bunts were the right decision, I want to introduce some considerations for each bunt that I hope will make thing a bit more ambiguous.
Escobar’s bunt at the top of the inning might have initially been more infuriating to some, given that there were no outs, Gordon was on second, and the Royals had their two, three and four hitters coming up. Actually, the Royals’ RE24 and WPA were both hurt less by the sacrifice than Victorino’s, but yes, they still went down (Escobar’s bunt was fairly close to even, although still negative: -.014 WPA, -0.21 RE24).
It is important to remember that both WPA and RE24 are relative to the average plate appearance. While Escobar has been about an average hitter since the beginning of last season, given his prior performance and peripherals, both ZiPS and Steamer see his true talent as closer to a .300 wOBA. In addition, he was facing Clay Buchholz, a right-handed pitcher, thus reducing Escobar’s chances for avoiding an out due to platoon considerations. In other words, there were reasons to think that Escobar was not going to have an average or better range of outcomes given typical plate appearance.
While one run is just one run, even late in the game, the Royals had James Shields going well. It might have been a good idea to pull him earlier, but I want to focus just on the decision to bunt in itself. The Royals have a very good bullpen (this might have been a bit more difficult to write on Saturday night, but the Kansas City bullpen came through in outstanding fashion in both parts of Sunday’s doubleheader), so the chances that extending the lead from 1-0 to 2-0 would be more likely to secure win probability than the average.
Yes, the Royals did have the “heart of the order” coming up, but as we have seen, Escobar is probably not a good hitter in the normal sense (but more on this below). Their cleanup hitter on Saturday was Eric Hosmer, who has not exactly been lighting things up. The batter hitting behind Escobar, however, was Billy Butler. With one out and a runner on third, Butler, who has good strike zone judgment and good contact skills (and hits it hard on contact) had a good chance to at least make enough solid enough contact to sacrifice Gordon in for a run.
Butler did make good contact when he got the chance, but just had a bit of bad luck in lining it right to the shortstop. Still, if you are going to have a batter up in a situation in which (obviously) a hit would be great, but a sacrifice would work, too, Butler is probably the best choice in the Royals’ lineup. He would be up with one out after the sacrifice. Hosmer, on the other hand, would likely be coming up with two outs, requiring a hit from him, which at this point is not necessarily a great chance to take, strategically speaking.
Finally, this bunt was not a surefire out. Although Alcides Escobar does not project as a good hitter in the usual sense, he has been very good at bunting. Almost 30 percent of Escobar’s career bunts have gone for hits. Last year year, he was second in baseball with 11 bunts for hits (with a success rate over 40 percent). He came pretty close to getting on when the time came. Escobar showed bunt on the first pitch but did not get one down, so the element of surprise was taken away (first baseman Mike Napoli conferred with the pitcher). Even so, when Escobar did get the bunt down, Buchholz barely managed to throw him out at first. The pitcher almost threw it down the line for an error that would have scored Gordon and perhaps even have put Escobar on second with none out.
None of this ended up working out for the Royals. But again, out or no out, the situation and the particular players (hitters, potential relievers, etc.) involved also should to be taken into account beyond simply what generic run expectancy and win expectancy tables might show.
Let’s briefly take a look at Victorino’s bunt with Ellsbury on first and none out. This cost the Red Sox about as much as a typical out in terms of run expectancy (-.24), but not much in terms of WPA (-.032), even it was negative.
Victorino’s bunt was not obviously the right call, but it is not clear to me that it was a bad one, either. Some of the reasons are similar to those given above about Escobar’s bunt. For example: the Royals could bring in a reliever soon and make the run environment even more restrictive; Pedroia and Ortiz are good enough hitters to finally get Ellsbury in (as they did) if he was in scoring position. With Salvador Perez behind the plate, a steal attempt might have been too dangerous, costing not only an out, but the baserunner. Victorino is not as skilled at bunting for a hit as Escobar, but he does bunt competently. Although Victorino’s platoon issues do not really hurt his overall value significantly (I will leave aside the issue of whether he should hit second versus a right-handed starter), he does hit much worse versus right-handed pitching. Making sure he got Ellsbury over with a bunt rather than having nothing to show for the out also makes some sense.
The Royals ended up not scoring in the inning after the bunt. The Red Sox did, although it is not clear the bunt was necessary (though it probably helped). As it turned out, the biggest events in the game were still to come along with a couple of lead changes. Of course, neither team knew what would happen in later innings.
Were one or both bunts the right choice? I don’t know. Both WPA and RE24 say no, and I would not want people to use this post to dismiss those tools. But they are still just tools, and while they can be helpful without player-specific inputs, they are not the whole story. This post is not intended as a vindication of these two bunts. (It is not meant as a comment on John Farrell and Ned Yost’s general strategic and tactical chops, either.) But I do think, taking various additional aspects into account, both bunts are at least defensible.
Matt Klaassen reads and writes obituaries in the Greater Toronto Area. If you can't get enough of him, follow him on Twitter.
don’t you have to take into account the volatility surrounding that expected run outcome? if the batter is a good bunter and can almost certainly advance the runner while also possessing an ability to bunt for a hit, it seems to me that the risk-adjusted run expectancy would be favorable to bunting in many situations. of course, this assumes the hitter in question isn’t a good overall hitter, in which case bunting is seldom a “smart” decision. but you have to adjust for risk.
How about travis hafner bunting to end the game in Toronto yesterday? Also defensible in my mind, even if it didn’t work out.
I think it would be interesting to look at whether it’s better for Escobar to bunt than to hit behind the runner. What’s the range of outcomes for the latter? Does he get on base/drive in the run often enough hitting to the right side to balance out with the hits he gets on bunts?
A big part of the typical traditional middle infield #2 hitter’s job is hitting to the right side when asked, so I’m a little surprised not to see it here.
Your defense of Escobar’s bunt includes the justification that Escobar is a good bunter and is often able to reach first successfully on a bunt. That occurs, of course, when the defense isn’t looking for a bunt. In this case, however, they surely were looking for the bunt — as you implied — by the fact that he was unsuccessful on the first pitch and then Napoli and the pitcher conferred about his likelihood to bunt.
This surely reduced the likelihood that he would reach base successfully on a bunt as the defense was now looking for it and prepared to defend it. It’s unlikely, therefore, that his likelihood of reaching first successfully was a factor at all.
“That occurs, of course, when the defense isn’t looking for a bunt.”
This is not true. Good bunters with speed (as Escobar is) reach base even when the defense is paying attention to the bunt. It definitely reduces the likelihood, but all you have to do is watch the play in question to see that it’s possible to bunt for a hit even if the defense is ready for the bunt.
This also doesn’t take into account the possibility of an error. Again, the play in question shows that, given Escobar’s specific skills, there is a non-zero chance that an error can occur, allowing multiple bases.
Additionally, the question of whether or not Escobar should have been asked to bunt in that situation ignored the question of whether or not the 2-hole hitter should have been asked to bunt in that situation. If a team’s #2 hitter can’t be entrusted to hit, he shouldn’t be hitting #2. Maybe Escobar should have been asked to bunt, but the person hitting 2nd in any major league batting order should not have been.
Actually, though this is still the way most managers fill out their lineups, Tom Tango and MGL showed in The Book that the #2 hitter should be one of the team’s best three hitters. Though the resulting inefficiency is minor, there’s no question that having a relatively poor hitter hit second is less than ideal.
Isn’t it true that a successful sacrifice bunt always decreases the run expectancy of the inning (except for maybe a squeeze)? But remember, you’re not playing for runs in this case, you’re playing for a single run. So shouldn’t we be looking at the change in probability of scoring at least one run instead of the change in probability of scoring runs?
It was only the 6th inning. Run expectancy, as opposed to expectancy of scoring just one run, was very relevant.
I am still against both of the bunt decisions, but reading Matt’s analysis was both enjoyable and enlightening.
To decide weather the sac bunt is a good outcome, you can’t just look at the difference in WPA or RE24, before and after the bunt.
you have to add in the probability that the bunt could have gone for a hit and
any other possibilities.
That total should determine the decision to sac bunt.
No, I think that’s missing the point of the article. WPA and RE24 are based on league averages. Why base your decision on league averages when you know the relative quality of the pitcher on the mound and the hitter at the plate?
I suppose it would be possible for the manager to have a palm pilot with an app to make these decisions, but I’m willing to bet neither manager thought it out that deeply.
Hey man, can I get my Palm Pilot back? You can have this iPad you clearly misplaced.
Great article Matt!
Too often people blindly apply a tool based on large aggregates (like run expectancy) to a specific outcome and don’t adjust accordingly – you detailed these variables out well.
The other part of run expectancy which David commented on above is the specific individual outcomes. Suppose for example a bunt takes the overall run expectancy down, but increases the chances of scoring 1 run (but decreases the chance of multiple runs) – if it’s the 9th inning (or late in the game) that may be a tradeoff that you gladly take.
I’m not familiar with how WPA and RE/24 are calculated so maybe they take into account the individual possible outcomes, but if they are just looking at the old and new run expectancies, then it could be misleading.
What is the chance of a sac bunt resulted in no outs- ie. sac bunt that ends up in a hit or the bunter reaching on an error? For sac bunts done by position players? Is it 5%, 20%, 40%?
Is it a good play to ‘sac bunt for a hit’- to try and lay down a perfect bunt down the foul line. If you bunt it foul it’s just a foul(obviously don’t do it on a 2 strike count) and if you put in play but can’t get the hit you at least advance the runner.
The likelihood of no out on the bunt (or in the PA after 2 strikes) is probably small compared to the likelihood of a double play, especially with the runner on 1st.