How to Beat Statcast’s Hitting Metric
One of the more fascinating rollouts from Baseball Savant this season has been xwOBA, a metric that utilizes launch angle and exit velocity to assign a hit value (single, double, triple, home run, or out) to every batted ball and then translates the results to “expected” wOBA. Why does it matter? By stripping out the influence of luck and defense, it gets closer to something like a “deserved” hitting number.
Here’s what the glossary at MLB.com says about the metric:
xwOBA is more indicative of a player’s skill than regular wOBA, as xwOBA removes defense from the equation. Hitters, and likewise pitchers, are able to influence exit velocity and launch angle but have no control over what happens to a batted ball once it is put into play.
For instance, Tigers first baseman Miguel Cabrera produced a .399 wOBA in 2016. But based on the quality of his contact, his xwOBA was .459.
For the most part, those claims make sense. But that’s not to say xwOBA can’t be beaten. To understand how, let’s look a little bit at how wOBA compares to xwOBA. Let’s begin by looking at all players from last season who recorded at least 400 at bats and compared their wOBAs to their xwOBAs. The scatter plot looks like this.
There’s a pretty strong relationship there. Of the 183 players represented above, 150 had a disparity between wOBA and xwOBA under 30 points. That seems pretty conclusive.
So what are we to do with this data? We could look at the outliers on either end, presume that they were either unlucky or lucky when it came to batted balls, and then move on with the analysis. However, before we do that, we might want to look at other reasons for the potential disparity. To that end, I did an eye test of sorts. I took all players with at least 400 at bats in both 2015 and 2016 and looked at their xwOBA minus wOBA in both seasons. If a player had a negative number, he might be considered to have had some good luck. If the numbers were positive, he might have had some bad luck.