I may expand upon any or all of these later, but I wanted to just get them down briefly while eyes are looking:
1. Option to use generic batting platoon splits in current and historical games. Small samples and biased samples (pitcher faced quality, overmatched pitchers pitching around a batter in an implicit acknowledgement that the likely walk is a better outcome than the expected outcome of a straight-up at bat, etc) make raw statistics unreliable and hide invisible prior decision making.
2. Option for initial player rating variation upon game creation, especially for the current season. ZIPS and other projection systems give a probabilistic forecast of stat lines. To take the median value that they provide as a representative line and treat it as a predicted outcome is to use them otherwise than as intended.
3. Scouting with projected stat lines (preferably for splits). When a scout grades a player, it should convey something objective to the general manager. Even if it is just a range of performance, there is an understanding between scout and GM as to what is being reported. Especially with relative ratings and scale shifts, a grade of, say, 40 is hard to evaluate and can mean a greater or lesser distance (in actual statistical performance) from average depending on the average and distribution of quality in the league.
Thanks for reading.
|