OPS in baseball statistics

Baseball, perhaps more than any other sport, attempts to quantify how good or bad a player is with statistics. Most baseball statistics only measure a small part of a player’s ability. One statistic that gained popularity in recent decades is On-base Plus Slugging, or OPS. Here’s an explanation of OPS in baseball and what it means.

What is OPS in baseball?

OPS, like its non abbreviated name states, is the sum of on base percentage plus slugging percentage. On base percentage measures the ability of a player to get on base. Slugging percentage measures the ability of a player to hit the ball a long distance.

Modern analysts argue that OPS gives a better measure of a player’s value than traditional baseball statistics.

One of my friends summed up the problem with traditional statistics really well. He was at a Cardinal game, and Mark McGwire came up to the plate. McGwire was in his final season and not exactly tearing up the league due to failing health. “What’s the big deal with this guy?” one of the other attendees asked. “He’s not even hitting .200.”

“Sometimes players who can’t hit .200 can do other things,” my friend said as McGwire launched a baseball high over their heads and into the deck above them. He pointed upward toward the ball. “Like that.”

McGwire’s .187 batting average in his final season understates his value. The same can be said for Babe Ruth’s final season.

OPS helps you find underrated and overrated players

1981 Fleer baseball cards - Nettles error
The statistics to help you find an underrated baseball player weren’t traditionally on the back of a baseball card.

Advanced statisticians love Hal Morris’ 1998 season. He hit .309, a good batting average. He finished second on his team in batting average. But he wasn’t the team’s second best hitter. He got 146 hits that year, but 116 of them were singles. Making matters worse, he only walked 32 times. His OPS was only .731 due to his small number of walks and extra-base hits. The .309 batting average overstated Morris’ production.

In 1974, Gene Tenace had a disappointing year. He only hit .211. But he walked 110 times and hit 26 home runs. His OPS that year was .778. Tenace didn’t hit the ball as much as Morris, but his walks did the team about as much good as Morris’ singles, and they were almost as numerous. When Tenace did hit the ball, it was a double, triple or home run about 40 percent of the time, which gave his team a much better chance of scoring. His batting average was a lot less impressive, but he had a much better year. His .211 batting average really understated Tenace’s production.

Gene Tenace was an underappreciated player in his day. OPS is one of the statistics analysts use to try to identify players like Gene Tenace, who can help your team while being affordable in terms of what it will take to acquire the player and what you’ll have to pay him. This sums up the “Moneyball” approach the Oakland Athletics made famous early in the 21st century.

What is a good OPS in baseball?

A good OPS, generally speaking, is above .800. It’s a crude measure of a crude statistic, but it’s very difficult to compile an OPS of .800 and not be a useful player.

Another trick is to take OPS and divide it by three and compare it to the player’s batting average. If the OPS/3 is higher than the batting average, batting average is understating his value and you have an underrated player. If the OPS/3 is lower than the batting average, you have an overrated player.

Going back to the examples of Hal Morris and Gene Tenace, Morris’ OPS/3 in 1998 was .244. That’s well below his batting average and not the kind of production you look for in a first baseman. Hal Morris was something of a poor man’s Wade Boggs, but Boggs was more valuable because he drew more walks.

Tenace’s OPS/3 in 1974 was .259, which was quite a bit higher than his batting average. He wasn’t great, and I’m sure people questioned why he played every day, but he deserved the playing time he got.

The problem with OPS in baseball

There’s one big, big mathematical problem with OPS in baseball. You’re adding two percentages. But when you express them as fractions, they have different denominators. As a result, you end up double-counting singles, but only single-counting extra-base hits and walks. A single can be better than a walk, but not all the time, and a single isn’t as valuable as a double. But in effect, by counting singles twice, OPS assigns the same value to singles and doubles.

A better statistic would be to take the sum of a player’s total bases, walks, and hit by pitches, and divide that by plate appearances minus sacrifice flies. It’s still an incomplete picture, but it’s mathematically fair, and gives a more complete picture of a player than raw OBP or slugging percentage.

But OPS is easy to calculate and most collections of statistics include both OBP and slugging percentage. So people use it.

Better statistics than OPS

If you want a really nice statistic, look at WAR. WAR stands for Wins Above Replacement. Some people describe replacement-level players as league average. But practically speaking, think of the type of player who gets released in September to open a roster spot for a hot prospect, and some contending team picks him up to see if he has anything left.

WAR estimates how many more games a team would win if they replaced a player like that with a different player.

When you look at Hal Morris in 1998, his WAR was 0.4. He was barely better than Daniel Nava’s 2015 season.

The 1974 Gene Tenace, in spite of having only a slightly better OPS than the 1998 Hal Morris, had a WAR of 5. In spite of his unimpressive individual statistics, his overall value was better than some All Stars. A team that replaced the 1998 Hal Morris in the starting lineup with the 1974 Gene Tenace could expect to win 4-5 more games over the course of a season, which is pretty significant.

The problem with WAR is it’s hard to calculate. You have to know things like how often a player grounded into a double play and kept his team from scoring. But we have the data and we have the algorithms to make computers calculate it for us.

Fun with WAR

Thanks to WAR, we can answer lots of questions. Who was better, Mickey Mantle or Willie Mays? Well, in 1957, Mantle was slightly better than Mays was in his best season, 1965. When both of them were at their best for a single season, Mantle was better.

But Mays put together a stretch from 1962-1965 that was better than any four-year stretch of Mantle’s career. Cherry-pick Mantle’s four best seasons and they still weren’t quite as good as that stretch. We can still argue about raw ability, but if the Yankees had traded Mantle for Mays even up, they would have won a few more games with Mays, especially if they did it after 1957. We have the numbers to prove it.

According to WAR, the three greatest position players of all time, in order, are Babe Ruth, Barry Bonds, and Willie Mays. Before WAR, we knew Willie Mays was great. But greater than Ty Cobb? No one argued that in the ’80s, because Mays never hit .400. Cobb did. Crossing eras can be tricky, but WAR lets us compare better than we used to be able to.

Why use OPS, then?

The problem with WAR is you don’t always have it, especially if you’re at the stadium watching a game in person. Most scoreboards give you OBP and SLG, so you can calculate OPS easily if you don’t have it. It gives you a rough estimate of which team’s first baseman is a better hitter.

And WAR is great for figuring out whether trading one player for another is a good trade, or figuring out who should play more often and who should play less. But it’s not a good situational statistic. When you need to figure out which bench player should pinch hit for a weak hitter late in the game, OPS probably works better. And it’s more readily available to the fans.

Second guessing the managers is a big part of the fun of watching baseball, and OPS is a really good stat for that purpose. That’s why people care about OPS in baseball.

Leave a Reply

%d bloggers like this:
WordPress Appliance - Powered by TurnKey Linux