Slugging percentage uses the wrong weights
Slugging percentage feels like the honest power stat. Where batting average flattens every hit into the same event, slugging finally pays extra for extra bases: a single is worth one, a double two, a triple three, a home run four, and you divide by at-bats. It looks like someone sat down and weighted the hits by value. But that is exactly the problem. Those weights — one, two, three, four — are not the run values of those hits. They are the number of bases the batter reached, which is a different thing that happens to look rigorous. A home run does not produce four times as many runs as a single, and a double is not worth twice a single. The stat encodes a tidy staircase that the actual scoring of baseball does not follow, and because the staircase looks precise, almost nobody questions whether the steps are the right height.
Where the 1-2-3-4 comes from
The weights in slugging are a counting artifact, not a measurement. Total bases were originally just that: add up how many bases a hitter’s hits were worth by definition, then divide by at-bats to get a rate. A single is one base, a home run is four, so the numbers fall out of the language of the game rather than out of any study of how hits create runs. It is an elegant coincidence that the base counts rise with offensive value — more bases really are better — and that coincidence is why slugging works as well as it does. But working roughly and measuring correctly are not the same. The base-count weights were never calibrated against run scoring; they were inherited from the box score, and they have been quietly standing in for value ever since.
What the hits are actually worth
When analysts measured how many runs each event produces on average — by looking at how the run expectancy of an inning changes before and after each kind of hit — the real weights came out looking nothing like one through four. A single is worth far more than a quarter of a home run; a walk, which slugging ignores entirely, has real value close to a single; a double is not double a single, and a home run, while the most valuable single event, lands well short of four times a single in run terms. The gaps between the hit types are compressed compared to the base-count staircase. Slugging overpays the home run relative to the single and underpays contact that keeps innings alive, because it is counting bases touched rather than runs generated.
The home run gets overpaid
The distortion is largest at the top of the staircase. By awarding four for a homer and one for a single, slugging says a home run is worth four singles, when the run-value ledger puts it closer to two. That fourfold weighting is why slugging systematically flatters pure power hitters and shortchanges high-average, high-on-base hitters who rarely leave the yard. Two players can create nearly identical run value — one through a pile of singles and walks, the other through a smaller number of extra-base hits — and slugging will hand the second a gaudier number, not because he helped his team more but because his hits touched more bases. The metric is not wrong that power is valuable. It is wrong about how much more valuable, and the error all points in the same direction.
The walk that vanishes
Slugging’s other blind spot is that it treats a walk as a non-event. Because the denominator is at-bats, which exclude walks, and the numerator counts only bases on hits, a base on balls simply disappears from the calculation. Yet a walk puts a runner on first with real, measurable value, and a hitter feared enough to be pitched around is displaying a skill that helps his team score. A patient, high-on-base hitter can post a modest slugging figure while contributing significant offense that the stat cannot see, and a free-swinger who rarely walks but occasionally runs into one can post a gaudier mark. Any stat that erases one of the three true outcomes is describing a slice of hitting, not the whole of it.
Why it still looks good next to average
None of this means slugging is useless, and the reason is instructive. Compared with batting average, slugging is a clear improvement, because at least it distinguishes a double from a single and a homer from a bloop, and its weights, while wrong, at least rise in the correct order. That is enough to make it far more correlated with run scoring than average is, which is why it survived into the on-base-plus-slugging era as the power half of the pair. But being better than a genuinely poor stat is a low bar. Slugging clears it while still carrying weights that no measurement of run value would ever produce, and pairing it with on-base does not fix the internal weighting — it just bolts a second flawed rate onto it.
What to read instead
The clean fix is to weight the events by their actual run values instead of their base counts. Linear-weights metrics — the family that includes weighted on-base average and the run-value stats built on it — assign each hit, walk, and out the value it really produces, then express the total on a familiar scale. Those numbers rank hitters the way run scoring actually rewards them, crediting the walk, compressing the home-run premium to its true size, and refusing to erase outcomes. StatLine’s hitting tables carry the components — singles, extra-base hits, walks, and the rate stats built from them — so you can see where a big slugging figure is real thump and where it is the base-count staircase doing the flattering.
The honest read
Slugging percentage is a real measurement of a real thing: bases gained on hits, per at-bat. As a rough index of power it is serviceable, and at the extremes it still separates the sluggers from the slap hitters. But its weights are a counting convenience mistaken for a value scale, and the mistake always tilts the same way — toward the home run, away from the single, and straight past the walk. Read slugging as a power descriptor, useful for what kind of hitter someone is, and stop reading it as a measure of how much offense he created. For that question the bases-touched staircase is the wrong ruler, no matter how precise its four neat steps look on the page.
A worked example
Picture two hitters over the same hundred at-bats. The first collects thirty singles and nothing else; the second hits seven home runs and makes outs the rest of the way. By total bases the second hitter slugs .280 to the first hitter’s .300, so slugging calls them close, with a slight edge to the contact hitter here only because the home-run total is modest — nudge it to ten homers and slugging crowns the power hitter comfortably. But run-value math tells a steadier story: thirty singles put thirty runners on base and turn over the lineup thirty times, while seven solo shots produce seven runs and twenty-one quiet outs. The base-count staircase keeps insisting the four-base hit is four times the one-base hit, and in the run ledger it simply is not. The gap between what slugging says and what scored is the weighting error, made concrete.