It seems that the newest “Moneyball” craze in the majors this season is the defensive shift. Usually used only against left handed hitters, it is being implemented by more and more teams against more and more players. Today, I am going to look at the fantasy implications of the shift.
First, there is little to no information available on what extent the shift is currently being used and against who. Without going back and looking at every game played, I decided to see how the shift was effecting a handful of players. I asked the “great” “minds” here at Fangraphs for 10 players who they see get shifted regularly. Here is the list they came up with:
One important note first. I have noticed that writers are identifying players to shift by their overall pull percentages. This is not the right way to look at it. First, it is only the infielders who are being shifted, so only ground balls and line drive data should be examined. Second, when a player is shifted, the defense puts 3 players close to one side of the field. This setup allows good coverage of the middle part of the field by the defense. It is actually better to look for a low percentage of ground balls and line drives hit to the opposite field to identify shift candidates (see Appendix at end of article for a method to get the percentage of batted balls to different zones of the field).
For reference, here are the career pull and opposite percentages for the above players and the average, high and low values for all of them:
|Ground Balls||Line Drives|
|Name||Pull %||Opposite %||Pull %||Opposite %|
If a person looks at the Pull % on ground balls, the range is 20 percentage points. Instead, if the Opposite % on ground balls is used, the range drops to 10 percentage points. The variation on the line drives shows the same pattern with the opposite field numbers being grouped closer together.
To get an idea of the effects of the shift against players, I calculated the difference in the players’ BABIP and xBABIP for 2011 and 2012. I only looked at these two seasons because that is when teams began to deploy the shift more and more. I subtracted each player’s BABIP from their xBABIP. To get the final value, I weighted the difference in BABIPs by the players’ plate appearance for that season. Here are the final numbers:
|Name||2011 PA||2011 BABIP||2011 xBABIP||Diff||2012 PA||2012 BABIP||2012 xBABIP||Diff|
|Weighted Average Difference =||-0.009||Weighted Average Difference =||-0.041|
With this small sample size, the effect on a player’s BABIP this season is a decent amount (-0.041). It is 4 times the the value for 2011 (-0.009).
This methodology is not a perfect way to determine the exact effect of the shift, but it does show that the shift does seem to be dragging down a hitter’s BABIP. Also, it gives a possible starting off value to show the average change in BABIP because of the shift. To put these numbers into perspective for fantasy owners, here is an example.
Consider the following player:
90 K (15% K%)
The player would end up getting 180 Hits with those stats for a 0.300 AVG. If a shift is able to drop his BABIP to 0.280, the player’s hits would drop to 160 and their average to 0.267. Using these numbers as a reference, a player who is shifted will like see a significant drop in their AVG.
For fantasy owners looking for buy low candidates with their xBABIP exceeding their BABIP, they should know that those hitters who are seeing a shift put on them quite often may have their BABIP suppressed by around 40 points.
Appendix: To figure out how much a player hits to various zones on the field, first go to:
Select the following:
Select Hitter to examine
Infield Distance: 550 (This puts all the batted balls into 3 bins and makes the OF Zone selection irrelevant).
Number of angle zones to split the field into: 3
Select Hit Type: Grounds and/or Line
Start and Stop Date: User used
Pitch Type: Leave Blank
The output should appear with the negative numbers showing hits to left field and positive numbers to right field.