Why We Still Don’t Have a Great Command Metric
To start, we might as well revisit the difference between command and control, or at least the accepted version of that difference: control is the ability to throw the ball into the strike zone, while command is the ability to throw the ball to a particular location. While we can easily measure the first by looking at strike-zone percentage, it’s also immediately apparent that the second skill is more interesting. A pitcher often wants to throw the ball outside of the zone, after all.
We’ve tried to put a number on command many different ways. I’m not sure we’ve succeeded, despite significant and interesting advances.
You could consider strikeout minus walk rate (K-BB%) an attempt, but it also captures way too much “stuff” to be a reliable command metric — a dominant pitch, thrown into the strike zone with no command, could still earn a lot of strikeouts and limit walks.
COMMANDf/x represented a valiant attempt towards solving this problem by tracking how far the catcher’s glove moved from the original target to the actual location at which it acquired the ball. But there were problems with that method of analysis. For one, the stat was never made public. Even if it were, however, catchers don’t all show the target the same way. Chris Iannetta, for example, told me once that his relaxation moment, between showing a target and then trying to frame the ball, was something he had to monitor to become a better framer. Watch him receive this low pitch: does it seem like we could reliably affix the word “target” to one of these moments, and then judge the pitch by how far the glove traveled after that moment?

How about all those times when the catcher is basically just indicating inside vs. outside, and it’s up to the pitcher to determine degree? What happens when the catcher pats the ground to tell him to throw it low, or exaggerates his high target? There are more than a few questions about an approach affixed to a piece of equipment, sometimes haphazardly used.