RSOB Chapter 4: The BABS Player Profiling System
New to “Ron Shandler’s Other Book”? Read the Introduction.
The foundation of BABS is a basic accounting concept – the balance sheet. On the left side are your Assets; on the right are your Liabilities.
For batters, your Assets are Power, Speed and Batting Average. For pitchers, your assets are Pitching Effectiveness (a proxy for ERA and WHIP), Strikeouts and Saves. Both sides have Playing Time as an Asset as well.
The major items on the Liabilities side are Health and Experience, or actually “lack of” each. For batters, Batting Average can also be a Liability; for pitchers, Pitching Effectiveness is the comparable negative skills offset. There is also a Miscellaneous category for minor variables like moving to a new team, a significant ballpark change, or advancing age. For these variables, you can neither count on them having an effect nor quantify them, though their impact could be considerable.
Assets
Skill and opportunity have always been the two key elements to every projection, and they form the foundation of our Assets. We look for positive contributions in these categories.
Playing time: It all starts here, an element of the forecasting process with a great amount of variability. As such, players will be rated in BABS based on a broad expectation for their potential for playing time:
BATTERS PITCHERS ----------------- --------------- F Full-time Approx. 500+ PA Approx. 180+ IP M Mid-time Approx. 300+ PA Approx. 100+ IP P Part-time Fewer than 300 PA Fewer than 100 IP
Most reputable touts go through a meticulous process of fitting plate appearances and innings into the available playing time on each team. That’s an admirable effort and vital for accurate fantasy valuations.
But let’s be honest here; the only players for whom these projections are even close to being on target are full-timers who stay healthy all season. Of the full-timers in last year’s Top 300, there were only 148 who stayed healthy all year, and that included 21 relief pitchers broadly defined as “full-timers.” Beyond the Top 300, the number of full-timers drops sharply. Even if we could deem that there were 200-250 healthy full-timers, that’s still less than 20 percent of the entire player pool.
So I opt to project playing time in broad chunks within which we can account for a good measure of volatility. There are full-timers, mid-timers (mostly platoon types) and part-timers. Beyond that, any quest for precision is mostly a waste of time.
Skill: On the skill side, players are not rated on their potential statistical output. I don’t care whether Gerrit Cole will post an ERA of 2.50, 3.00 or 3.50. There are too many variables to know where that number will land. Instead, players are rated against each other, because that’s how it all comes out anyway. Cole could repeat his 2.60 mark, but that 2.60 is far less valuable in a season where everyone and his wife’s cousin’s housekeeper is posting sub-3.00 ERAs. So players are rated against the population mean for each skill:
Extreme Impact Top 10% of players with that skill Significant Impact Top 25% of players with that skill Moderate Impact Top 50% of players with that skill No projectable impact Bottom 50% of players
Here are the codes we will use for each player:
Impact Level Power Speed BatAvg PitchEff Strikeouts ------------ ----- ----- ------ -------- ---------- Extreme P+ S+ ** E+ K+ Significant PW SP AV ER KK Moderate p s a e k
** There is no extreme level for batting average because that stat has way too much variability. If truth be told, the only player who I’d be comfortable assigning a rating of A+ would be Miguel Cabrera.
Those in the bottom 50% for each skill are assigned no rating. Their contribution is typically not enough to substantively move a team in that category’s standings, or at least not at a level that you can project. In mixed leagues, these players are usually easily replaceable. They might be more important in AL/NL-only leagues, but that does not make them any more projectable. You’re still going to want to target players with at least Moderate skill to move the needle.
The skill ratings for each player represent his true, underlying talent regardless of opportunity for playing time, level of experience or injury history. The latter two variables are accounted for on the Liabilities side of the balance sheet.
For the assessment of each of the skills categories, I return to my roots with the Baseball Forecaster and BaseballHQ.com metrics. For a fuller explanation of these gauges and complete data for every player going back many years, those are the places to go.
Power: I rely mostly on Expected Linear Weighted Power Index here. This combines weighted levels of hard-hit line drives and hard hit fly balls as a percentage of all balls put into play. So this is pure power, not colored by a hitter’s propensity to strike out.
Speed: Here I rely on Statistically Scouted Speed, which looks at run-scoring, triples, infield hits and body mass index. I also look at each runner’s track record of how often he’s been given a green light along with his stolen base success rate.
Batting Average: I use Expected Batting Average here, which looks at a batter’s contact rate and odds that a batted ball will fall for a hit, which is a product of the speed of the ball, distance it is hit and speed of the batter.
Pitching Effectiveness: Here I use Expected Earned Run Average, which approximates ERA while using only situation-independent, skills-based metrics, like strikeouts, walks and ground balls. This is similar to xFIP (Fielding Independent Pitching).
Strikeouts: I combine several metrics for this assessment – strikeout rate, swinging strike rate and first pitch strike rate (which correlates more with walks but provides some nice color).
The Assets section of the pitcher balance sheet also has a column for Saves. This is an opportunity-driven statistic but can be pared down to three levels, similar to what we do in Mayberry:
Significant SV Likely to get 30+ saves Moderate sv- Likely to get 10-29 saves
These seem like wide ranges – okay, they are – but we need to cast a wide net in this category. The Significant saves sources are pretty much guaranteed a frontline shot at 9th inning work. The arms classified as Moderate all have some risk associated with them, from uncertain bullpen depth charts to spotty track records in a closing role. By filtering out anyone projected for fewer than 10 saves, we’re essentially saying that those guys are not projectable enough. My advice is always to speculate on relief pitcher skills and be grateful if you back into saves.
Miscellaneous: This is for any positive variables that might have a legitimate impact and are not captured in the other categories. Guess what the key word is in that last sentence?
Legitimate? Positive? The?
Close. It’s “might.” These are variables that need to be on our radar. Most analysts will build them into their statistical projection. I prefer to just identify them and let you know they might be a factor. Or not. It’s your call how important they are.
There is not much I can think of that fits here:
Pk (Positive park effect)
As noted in Chapter 2, park dimensions might have an impact on output, but changes are neither guaranteed nor can be absolutely attributable to a particular change in venue. The only players who will be noted at all are those moving to one of the more extreme hitter parks from one of the more extreme pitcher parks. The hitter parks, based on 3-year data, are Colorado, Baltimore, Houston, Yankee Stadium, Toronto, Cincy and Milwaukee. The pitcher parks are Seattle, Dodger Stadium, CitiField and San Francisco. Any other movement is ignored. Always remember The Nelson Cruz Experience – his counterintuitive improvement moving from Baltimore to Seattle last year – as evidence that this is not foolproof.
Rg (Positive regression)
There are a few players who had really bad 2015 performances, sometimes driven by no more than random statistical volatility. Odds are “last year’s bums” might see some rebound just by virtue of the planets realigning. In any case, it’s important to identify them because this is one of our few opportunities to engage in a full frontal assault against recency bias.
Liabilities
It’s great to roster a bunch of players who you hope will put up big stats. But what separates the winners from the losers is the ability to build risk into the process. Every player provides certain assets but many also have a unique set of liabilities that influence their potential to provide a fair return on your investment.
Here are the ratings we use on the Dark Side of BABS (no storm troopers allowed).
Negative Skill: The core ratio categories in Rotisserie are batting average and ERA/WHIP, and for these, a bad player can do great damage. So, rather than provide a negative rating on the asset side, we have a column on the Dark Side for players with the red lightsabers.
-AV: Bottom 25% of batting average skill
-ER: Bottom 25% of pitching effectiveness skill
Injuries: Every year, this is the one variable that wreaks havoc with our chance at success. Disabled list stays have ranged between 25,000 and 30,000 days lost in each of the past five years, so this is no small variable.
I’ve decided to take a different approach to injuries with BABS. We already know up front that about 40 percent of the top-ranked players are going to spend some time on the DL. We cannot project which players are going to pull up lame at any time, so we have to attach some injury risk to pretty much everyone.
As such, I’ve set a starting point for the health of each player. Everyone has a minimum baseline of a 25% chance to spend some time on the DL. To that, I’ll add greater odds to those players with an injury history (based on days spent on the DL over the past two years) or current health concerns.
The codes will look like this:
INJ
Players who spent more than 50 days on the DL in 2015, spent more than 30 days on the DL in consecutive seasons, or are currently hurt with an uncertain or negative prognosis for 2016. I give them over 50% odds of missing significant time in 2016.
inj-
Players who spent more than 20 days on the DL in 2015 or are currently hurt with a positive prognosis for 2016. I give them 26-50% odds of missing significant time in 2016.
I classify “significant time” as enough missed games that it hurts. If Mike Pelfrey goes down for two weeks with a hangnail and you replace him with Brett Oberholtzer, that’s not significant. And if this is a real move you need to make, you have a lot more problems than worrying about injuries.
Experience: Okay, I’ll say it – Mike Trout is a god. He is among a small class of players who hit the ground running upon promotion and never let up. (Though, if truth be told, his roto earnings for his career have been $54, $47, $38, $35. Just saying.) But most players don’t follow this path.
Patrick Davitt’s research has shown that hitters need at least 800 plate appearances to establish a baseline, or enough experience from which we can legitimately project further growth. Those 800 PAs could mean a big rookie year and a sophomore slump, or a pedestrian first season followed by a growth year, or two consistent performances. But the percentage play is to expect some volatility until that baseline is set.
So as much as we’re ready to anoint Carlos Correa as the next first-ballot Hall of Famer, there is risk, and we need to account for that. I’ve decided to err on the side of caution and increase the benchmark slightly.
On the balance sheet, we’ll identify the young players as such:
Bat SP RP PA IP IP ----- --- --- EX < one full season of MLB experience 500 150 75 e < two full seasons of MLB experience 1,000 300 150 - Established players, veterans, has-beens
About 1,000 plate appearances in the Majors – two full seasons – is a good point to determine legitimacy on the batting side. In assigning ratings, I exercised some latitude here, often giving a pass to some outwardly established players who have PAs in the 900s. It’s a little more fuzzy with pitchers, but we’ll go with 150/300 innings for starters. For relievers, we’ll use 75 and 150 innings.
Essentially, anyone who gets an “EX” or an “e” is not yet a fully formed entity.
Finally, given my opinion about age, I don’t give a flying whoop whether a player reaches these thresholds at age 24, or 27, or 31. Experience is experience at the Major League level, regardless of age.
Miscellaneous: These are the negative variables that could have an impact, might not, probably won’t but can, and are definitely not quantifiable unless they are. That’s about as firm a stance as I’m willing to take. But all of these need to be on our radar because, if David Ortiz bats .230 in 2016, we need to be able to come back to BABS and say, “Aha! He’s old!”
You should really change the heading for this section from Miscellaneous to Rationalizations.
Okay, I’ll give you that.
Any of these could be bad, good or have no effect:
Pk (Negative park effect)
As on the Asset side, we can neither guarantee or absolutely attribute performance changes to park dimensions. If Jose Bautista was traded to San Francisco, he would qualify for this code, but you’d think someone with his skill would be able to hit reasonably well anywhere. So take it for what it’s worth.
Nw (New team)
This goes beyond park effects. Many players have an adjustment period when going to a new team, and especially a new league. I tend to give this more weight than others, but it’s just another variable that might have an impact. Only those players with some baseline of MLB performance are noted.
Ag (Advancing age)
Once a player hits 36, anything can happen. Some batters manage to hang on for longer; some pitchers face a steep cliff at 38. All are essentially geezers at this point. No matter how many artificial supplements some of them might be taking to ward off the fear of premature retirement, I won’t be anywhere near the bidding on players like Marlon Byrd or Bartolo Colon.
Rg (Negative regression)
As much as we want to believe that players like Jake Arrieta and Zack Greinke can sustain last year’s performances, the odds are stacked against them. Players noted here are those who posted performances so far above their historical levels in 2015 that it’s tough to justify their sustainability.
I also use this code for players whose track record has been historically volatile, at least from the perspective of their surface stats. So Alcides Escobar will get nicked here, but so will Chris Davis. Recency bias is already pushing Davis up the draft boards this winter, but do we really know whether we are going to see the 45-.260 version or the 25-.200 version?
Beyond that, feel free to add any other miscellaneous Liabilities as you see fit. If you’re worried that the Rockies will trade one of their outfielders out of Coors, then jot a note on the dark side for Carlos Gonzalez, Charlie Blackmon and Corey Dickerson. If you’re worried about potential suspensions for Aroldis Chapman, Jose Reyes and Yasiel Puig, feel free to ding them here too.
I suppose that also means you can change any of the ratings, on either side of BABS. This is your tool and I have no way of knowing what the heck you’re doing anyway.
I’ll start getting into the balancing of assets and liabilities in the next chapter, but there is basic point to remember: The more a player is lacking on the health and experience scales, and the more of these miscellaneous liabilities he has, the greater the risk of him falling short of realizing his assets. I think that goes without saying, but I said it anyway because… this is my book. But it’s your tool.
That’s it.
Hmm, I dunno. It all seems kinda simplistic and based more on opinion than fact.
Simplistic? Well, it’s simple, for sure. That’s the goal, to keep it simple but structured. However, the foundation is still based in real data. The Asset and Liability categories are all driven by data; they are just sorted into broad tiers. The secondary categories are more contextual but no less driven by fact.
So how does it work, in practice?
Players with the same asset ratings are pretty much interchangeable. However, not all players will be exactly the same; some will have more risk factors. In your roster-planning process, you’ll be making decisions as to how much risk you’d be willing to tolerate.
An example, please?
Okay. In nearly all leagues, Cy Young winner Dallas Keuchel will likely get drafted ahead of Sonny Gray (both pictured above). In the National Fantasy Baseball Championship (NFBC) ADPs as of January 1, Keuchel was going #42 while Gray was going #62. This is likely driven by their relative 2015 performances (beware recency bias) and respective team environments (which I discounted back in Chapter 2).
But here’s the thing… on a broad skills basis, both have essentially the same assets. Both have projected ERAs right around 3.00. Over the past three years, both have struck out about 7-8 batters and walked about 2-3 batters per 9 IP. If anything, Gray is more consistent than Keuchel.
So, in evaluating their respective assets, BABS gives them identical ratings. Both have significant effectiveness “ER” and moderate strikeout ability “k”. We’ll begin notating these as (ER,k). If there are Liabilities, they will be shown like this: (Er,k | INJ).
But players cannot be evaluated based on their assets alone. Keuchel also owns a potential Liability – the possibility of significant regression off of 2015’s extreme numbers. If you have to choose between the two, you might opt for Gray since his Liability record is clean and his potential acquisition cost will likely be lower.
You have full control over those decisions. BABS lays out all the facts in front of you.
Hmm. Keuchel/Grey. Blackmon/Marte. What other players are more “interchangeable” than we’d normally perceive?
Tons of them. Within the wide ranges of skills metrics and wide error bars in projections, players are not all that different. So, while they might not outwardly seem similar, Chris Davis, Lucas Duda and Matt Kemp all have the same asset ratings of (P+, a). Gregory Polanco, Angel Pagan and Francisco Lindor are all (s,a), however, each has his own injury and experience liabilities.
Yeah, but I still don’t see those groups as equivalent. Lindor is coming off a .313 season. Polanco has never batted over .260. Duda has never hit more than 30 HRs while Davis has hit more than 45 twice. Not the same.
But from a skills standpoint, the variances are not statistically significant. Duda hit more HRs than Davis in 2014. Lindor has only 390 ABs at the Major League level so you can’t consider his .313 average as a real baseline (because batting average does not stabilize until 910 ABs, remember?).
Okay, then once again, how am I going to be able to rank the players, especially without numbers?
BABS assigns each player to tiers based on:
a. Expected playing time
b. Primary assets (power, batting average, pitching effectiveness) with minimal risk
c. Secondary assets (speed, strikeouts) with increasing risk
d. Decreasing assets with increasing risk
I’ll handle the details for you once we get to the rankings sections.
But first, let’s get into the draft planning process.
Chapter 5: BABS Draft Planning – next Friday, January 29
I like what you’re doing with this.
How might you modify the assets and liabilities for a Scoresheet draft?
I don’t think I’d change too much for Scoresheet. The Saves category becomes superfluous, obviously. I might try to find a better way to incorporate more on-base skills for batters. Defense is missing, which is the case for most non-sim games. But the other skills and liabilities are just as relevant in a sim game.
I noticed you picked dee gordon ahead of altuve in the fsta. I actually like that pick.
Still, it did go against the ‘tide’, so I was wondering what your thinking was at this time in the draft?
thx
Martin
First of all, Altuve’s underlying skills metrics are not as good as his stats would lead you to believe. Second – and I’ll be writing about this in future chapters – you want to give yourself room to make mistakes later in the draft. Rostering players with extreme skill – like Gordon’s SBs – gives you flexibility later on to pass on a speed guy with a bad batting average, for example, and opt for another skill set.
Thoroughly enjoying RSOB. It’s going to be a long week waiting for the next chapter on 1/29. Does the notation for Experience seem to be at least inconsistent with, if not inverted in comparison to, the notation for other factors? Would the notation for Experience described below be more consistent with the rest of the model and make for an easier read?
** (similar to AVG, there’s no “Extreme Experience”)
XP Established players, veterans, has-beens (comparable to “Significant Experience”)
x < two full seasons of MLB experience (comparable to "Moderate Experience")
-x < one full season of MLB experience
Regards,
Chris
I think there should be an A+ rating for batting average. It may be a rare skill these days but it does exist. We’ve seen enough players with the extreme batting average skill that it is worth noting when a player has it. Miguel Cabrera right now, a few years back Ichiro, Tony Gwynn and Wade Boggs just to name a few. I would love to know that a player has a skill that few others own when putting together rankings and while drafting.
I’d love if you could elaborate a bit more on the skill differences you see between Dee Gordon and Jose Altuve, is your selection not just more recency bias?
This is interesting. We could position experience – and health too – as positives/assets. I’ve positioned both as liabilities because I think it’s easier to identify players as having not enough experience, or as being injury risks. In the next chapter, when we start setting down HOW MANY of each asset and liability you need to budget, I think it’s easier to say “roster no more than x number of inexperienced players” rather than “roster at least x number of experienced players.” I might be splitting hairs here, but I think the concept of the balance sheet – where you have positives and negatives that you have to balance – is easier to follow during a draft. But the nice thing about publishing this book online is that it becomes a living document. If many others think all the elements of BABS should be presented as positives to achieve, I’ll modify the model. Thanks!
Yeah, I really mulled this for awhile. But there are so few players who are consistent .300 hitters that there would be only a few A+ ratings. Right now, I’m running into the same situation on the pitching side. There are only a handful of E+ ratings, and only one starting pitcher – Kershaw. I might have to rethink this, but the error bar for batting average is so wide that it’s tough to commit to saying that someone deserves an A+. Except for Miggy.
As for the Gordon/Altuve question, Gordon is (S+,AV) while Altuve is (SB,AV). Altuve’s power does not register as an above average skill and could regress. If not, it’s possible he could follow the Brett Gardner path, which makes him less valuable as well. In any case, Gordon’s extreme speed skill was what I was looking for in the FSTA draft.
I wasn’t thinking on that level (you took it one step further, naturally ;-). I was simply thinking in terms of keeping the notation consistent to make it easier to interpret. With speeds, power, etc, the notation is (where A is a letter)
Extreme: A+
Significant: AA
Moderate: a
Liability: -AA (or -a)
Currently, power, speed, average, pitching efficiency follow that notation. Experience though appears inverted by comparison. EX looks like it would be “significant” – an asset/positive – because it is in AA format; however, EX is a liability instead; “e” appears to be moderate etc.
I do agree that it’s easier to say “roster no more than x number of inexperienced players”… Perhaps the scale becomes – to avoid clutter on the balance sheet –
” ” : No notation for established players
xp : < two full seasons of MLB experience (comparable to "Moderate Experience")
-xp : < one full season of MLB experience
Thanks!
The extreme factors all have a “+” sign. The significant factors all are in CAPS. The moderate factors are all in lower case. So “EX” is significant risk; “e” is moderate risk. It may be less intuitive because the variabilities on the Liabilities side are inverted. With BA and ERA liabilities, I added a minus sign just to separate it from the Assets but both are significant Liabilities. Does that make more sense?
For 4×4 leagues, would you include strikeouts as a skill? They’re already baked into xERA, so I’d be inclined to say no, but to me, they’re a pitcher’s most important skill, so I don’t mind emphasizing strikeout pitchers in a league where K’s are not a stat.
BABS is all about skill. While the codes used are loosely tied to roto categories, in the end you just want to know which are the most-skilled players. I would use all BABS categories for whatever format you use.
I can see leaving out BA but what about OBP for those of us who play in those types of leagues; do you see that as a stable enough skill?
I do. It’s tough to incorporate every variant format. I’d identify the subset of players who are significant OBP contributors and just note them on the ranking lists.
I agree with Nathan’s post above. BA is not a good indicator. You’ve said that yourself a number of times. I use OBP and OPS as primary ratio indicators for batters.
Agreed, but it’s not straight batting average. As noted: “I use Expected Batting Average here, which looks at a batter’s contact rate and odds that a batted ball will fall for a hit, which is a product of the speed of the ball, distance it is hit and speed of the batter.” Combined with the power metric makes for a decent proxy for OPS. I agree that we’re missing an element that accounts for walks.
I’m trying to understand this within the context of prior drafting strategies. It seems that, at least loosely, this approach may be comparable to drafting with Mayberry Method using 3035/0335 CBC as a minimum; any players above that are draftable. Certainly, there’s perhaps additional nuances to the balance sheet approach, but at the core is that accurate?
I wouldn’t call that the “core” but it’s certainly an element. BABS is a natural progression from Mayberry but it’s not just a player rating methodology. The next few chapters show how it works.
How would OBP compare to batting average as a skill. Are the extra components of walk rate included already? A player like Joc Pederson is widely disparate from BA to OPS while a Votto would be an OPS+ ?
Walks are not a component of the skills gauges on the batting side. Perhaps it’s something that I’ll need to consider for BABS 2.0.
Are you looking at each players career (including minors) or just what they did in 2015 to make your determination? If this is answered already I apologize.
Last 5 years, including minors, AA and above.
Inexperience is deemed a liability which I understand. But how you do you account for the fact that those players still have room to develop skills which they may not currently have credit for? For example, Rougned Odor is not credited with any form of power but did hit 16 HR’s last year and is still young enough to develop more of a power hitting profile. Obviously this would be more relevant in a keeper league.
Just to quickly add on, is there a way for the system to identify, for example, a player who is more likely to develop a certain skill such as power when they are inexperienced?
It’s an inexact science. By virtue of the fact that a player has a rating that includes experience risk, that denotes the even larger variability in his expectations. I’ll go into that more in the column on keeper leagues planned for next month.
Ron,
I recently came back to this and continue to be impressed with and pleased by the BABS concept. I used it for one of my drafts this year and at this point will likely be doing so again. I do have a few methodological questions about how you determine your skills ratings for players in the pre-season.
1) When you are gauging the top 10%, 25%, 50% and the bottom 25% for a skill – what population are you pulling from? Specifically – is this all potentially relevant players, or is the pool smaller when setting the levels – such as those expected to be drafted in a 12 (or 15) team league?
2) Why are there so few players that merit the inclusion in the top 10% for AVG and Pitching Effectiveness? It would seem that by definition the top 10% would be the same number of players as for the other skill indicators… I am left to assume that you used your own judgment to determine that players outside of Cabrera and the select few among the pitching elite better fit within the significant group despite technically being among the top 10% in the skill.
1) The population is the entire database of current MLB players.
2) The percentages do not represent players but skill levels. For instance, if we determined that the range of a certain skill is from 0 to 100 and the top 10% would be those players who achieved 90-100, then any number of players might fit that range.