Q6: Appropriate hitting metrics for position?

This post is part of a series – click ‘previous’ or ‘next’ at the bottom of this page for more.

It’s impossible to discuss what it takes to be a D1 caliber hitter without at least factoring in the defensive component. You have to hit to play…but you also have to be able to field a position to justify a roster spot and meaningful playing time..

Different positions carry different expectations from a power/production standpoint. Corner positions [1B/3B/RF/LF] are expected to provide more offensive production, with an expected trade-off of less speed & defensive range.

Up-the-middle positions [C/SS/2B/CF] tend to have more of a defensive emphasis and come with slightly less offensive production expectations.

We discussed low-90’s exit velocity & low-70’s bat speed as a good rule of thumb for D1 caliber high school seniors. So, thinking in terms of relative metrics and being within certain metrics ranges…instead of one-size-fits-all absolute metrics and “magic numbers”…we could assume that a Shortstop would have different metrics expectations than a First-basemen.

For ideal D1 hitting metrics based on your position, at your age (and defensive & running metrics ideals), check out our free position metrics calculator.

Player A vs Player B

Going back to the previous player examples in this series of Player A [5’9 200 HS Sr] and Player B [5’10 145 Soph], let’s assume Player A is a LF/RF or 3B, based on his physically mature frame and limited capacity to add more strength due to height-to-weight differential.

He was already below the metrics curve for his year and size at 68 mph bat speed. Adding additional expectations of a corner position puts him further below the curve.

Player B, as a 5’10 145 Soph already near the metrics curve given his age & his room for physical growth (63 mph bat speed). Let’s assume he’s a SS or CF given his lean frame. That makes his relative metrics even better.

Of course we’re making assumptions about each player’s defensive abilities here, but we’ll tackle that next…

<< Previous | Next >>