The DC Times

A New Way to Look at the Cowboys, NFL, and Fantasy Football

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 48: Confidence in Drafting

When I wrote Fantasy Football for Smart People: How to Dominate Your Draft, I calculated the year-to-year consistency of each position to help owners acquire a solid understanding of just how easy it is to project points for each player.

Those consistency correlations can also be thought of as confidence ratings—that is, how confident can you be that your projection for a player is spot on? If the strength of correlation for quarterback fantasy points were theoretically 1.00, we’d be able to accurately project each player’s points each and every time. If the correlation were 0.0, as is the case with kickers, projections would be useless—picking a player with a season-to-season consistency correlation of zero is synonymous to playing roulette. There’s no way to beat the house.

Luckily for us, accurate projections are attainable. The degree to which we can predict the play of specific players, however, varies based on a multitude of factors, their position being perhaps the most important of those.

You can buy How to Dominate Your Draft in KindlePDF, or paperback.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 47: Risk Ratings

One of the new features I added to my 2014 draft package is a risk/reward rating for each player. I used a bunch of different data to create those ratings, one of which is a grouping of historical comps for each player, generated by the Similarity Score apps at rotoViz.

Take a look at Marshawn Lynch’s 20 closest comps, for example:

Lynch Comps

Looking at relevant factors, the apps show you the 20 most similar players relative to Lynch in 2013 and how they performed in the subsequent season. The chart above is one of the reasons I’m so low on Lynch, and it’s reflected in my risk rating for him. A lot of players who are very comparable to Lynch have tanked in the past, with just a handful improving upon their numbers. There’s a chance that Lynch has a quality 2014 season, but there’s an even better chance that he plummets. It’s important to quantify the range of potential outcomes to understand the risk associated with each player.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 46: Stacking in Daily Leagues

At 4for4, I posted an article on stacking in daily fantasy football.

“Never think that lack of volatility is stability. Don’t confuse lack of volatility with stability, ever.” - Nassim Nicholas Taleb

This is my second article in less than a week that starts with a Nassim Nicholas Taleb quote. I don’t even really like the guy, to be honest, but his views on low-frequency events and volatility have somewhat altered my decision-making. And they have a lot of relevance to the world of daily fantasy sports—a form of a stock market—so we can use them to potentially exploit inefficiencies.

There’s a general perception that volatility is a bad thing. We seek stability to the point that we’d rather hold onto something that’s familiar, even if it doesn’t make us happy or is detrimental in some other way, over changing. But volatility itself isn’t inherently disadvantageous; actually, because so many people fear it, we can often use it to our advantage.


The easiest way to create volatility in daily fantasy lineups is through stacking—choosing players who play on the same team in an effort to increase your upside. When you pair a quarterback with his receiver (or two of them), that’s stacking. And it can be a really, really powerful tool in your arsenal, assuming you properly utilize the volatility it creates.

I wrote about stacking in my daily fantasy football book Fantasy Football for Smart People: How to Cash in on the Future of the Game:

“Volatility can be a positive. In tournaments, for example, you want to choose a high-variance lineup because you need all of the upside you can get. If you’re in a 2,500-man league that pays out the top 250 owners, there’s no difference between 251st-place and dead last. You don’t want “solid” in a tournament. You want outstanding. By pairing a quarterback with his receivers, you can greatly enhance the ceiling of your team by relying on dependent events; if your quarterback throws for 400 yards and four touchdowns, you can bet his receivers will have monster games as well.

Volatility isn’t always welcomed, though, as we’ve seen in head-to-head leagues. When you’re playing against just one other owner, you don’t want to seek upside at all costs. In many cases, you just want to maximize the “floor” of your lineup, i.e. create a safe group of players. That means it’s probably best to select players whose production isn’t dependent on anyone else in your lineup.”

Check out the full post at 4for4.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 45: How Much Does Speed Matter for WRs?

I got into a Twitter debate on the value of speed for wide receivers, and it reminded me of a chapter from my book Fantasy Football for Smart People: What the Experts Don’t Want You to Know:

Take a look at the top 10 wide receivers in fantasy football in 2012 (standard scoring): Calvin Johnson, Brandon Marshall, Dez Bryant, A.J. Green, Demaryius Thomas, Vincent Jackson, Andre Johnson, Eric Decker, Julio Jones, and Roddy White. Every single one of those players stands at least 6-1 and weighs a minimum of 201 pounds. The average(the average!) is 6-3 and 220 pounds. Some of them ran outstanding 40-yard dashes, but others (Marshall, Bryant, Jackson, Decker, White) didn’t light it up.

Thus, it isn’t that being fast doesn’t help receivers, but rather that the speed “cutoff” isn’t as stringent as it is for running backs. Receivers also need two things to maximize their chances of success in the NFL. The first is size (especially height). The second is at least a moderate amount of speed (ideally under 4.55, but that’s not a necessity). A bunch of big receivers with moderate speed have succeeded of late—Marshall (4.52), Jordy Nelson (4.51), Dwayne Bowe (4.51)—but they’re all very large.

You can buy What the Experts Don’t Want You to Know for Kindle, as a PDF, or in paperback.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 44: Marshawn Lynch Isn’t a Top 10 RB

Last year, I wrote an article on why I won’t own Marshawn Lynch in any leagues. If you substitute “2014″ into that article, it still pretty much sums up my thoughts on Lynch:

There’s been a lot of rotoViz content written on Seahawks running back Marshawn Lynch, but I have him ranked so unimaginably low that I had to chime in on a running back who I think is the most overrated consensus first-rounder that I’ve ever seen. Shawn Siegele has already suggested that Lynch is a strong sell, citing his drop in yards after contact, while Frank DuPont notes that Lynch is overvalued.

There’s Risk, But Where’s the Reward?

What happens if Wilson gets injured? Lynch’s value would instantly plummet; there’s probably not a back in the NFL, save Alfred Morris, whose play is so tied to the health of his quarterback. You already have to worry about running back health as it is, so the fact that Lynch would likely see a dramatic decline in efficiency if Wilson gets injured just makes him a bigger risk.

And then there’s Lynch’s age. He came into the league at a young age, so Lynch is “only” 28, but that’s still pretty over-the-hill for a running back. In my book Fantasy Football for Smart People: What the Experts Don’t Want You to Know, I researched historic running back production by age. Below, I charted the results by fantasy points per touch.

RB Percentage of Peak Production

You can see that running backs are basically as efficient as they’ll be from the moment they step on the field, and it’s a slow decline from there. Total production peaks in the mid-20s (because backs typically see heavier workloads), but again, Lynch’s workload is priced into his ADP.

Because of these numbers, I’m rarely ever higher than the consensus on an older running back. The only time that’s the case is if the back’s situation has changed dramatically and it isn’t properly reflected in his ADP.

I currently have Lynch rated even lower this year in my 2014 Draft Package.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 43: Regression, Randomness, and Running Backs

Today’s tip comes via a sample from my book Fantasy Football for Smart People: How to Dominate Your Draft:

Back in 2008, I had running back Thomas Jones ranked well ahead of most owners. Jones was playing for the Jets and coming off a season in which he ran for 1,119 yards, but averaged just 3.6 yards-per-rush and scored only two total touchdowns. Those two scores represented just 0.59 percent of Jones’ 338 touches in 2007. ESPN had Jones ranked 21st among all running backs. I had him 10th. Why would I possibly rank a then 30-year old running back coming off a season in which he tallied 3.6 yards-per-carry and two total touchdowns in my top 10? Regression toward the mean. Regression toward the mean is a phenomenon wherein “extreme” results tend to end up closer to the average on subsequent measurements. That is, a running back who garners 338 touches and scores only twice is far more likely to improve upon that performance than one who scored 25 touchdowns.

0-16 Detroit Lions: A Coach’s Dream?

Regression toward the mean is the reason the NFL coaches who take over the worst teams are in a far superior position to those who take over quality squads. If I were an NFL coach, there is no team I would prefer to take over more than the 2008 Detroit Lions. Coming off an 0-16 season, the Lions were almost assured improvement in 2009 simply because everything went wrong the previous season. Even though Detroit was a bad team, any coach who took over in 2009 was basically guaranteed to oversee improvement in following years. The same sort of logic is the reason that there are so many first-round “busts” in fantasy football. Players almost always get selected in the first round because they had monster years in the prior season. In effect, most first-rounders are the “outliers” from the prior season’s data, and their play is more likely to regress than improve in the current year. It isn’t that those players are poor picks, but rather that the combination of quality play, health, and other random factors that led to their prior success is unlikely to work out so fortunately again.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 42: How to Draft WRs

Today’s tip comes from my first book Fantasy Football for Smart People: How to Dominate Your Draft :

For years, fantasy owners have been searching for the wrong traits in dominant wide receivers. Here’s what you should covet.


Speed obviously matters for every position, but many owners seem to value long speed for wide receivers way more than they do for running backs. They shouldn’t. From 2005 to 2009, the fastest wide receivers at the Scouting Combine—those who ran in the top third of their class—have been just barely more successful than the receivers in the middle third in terms of approximate value. Compare that to running backs, most of whom simply haven’t produced if they’ve run slower than 4.55.

Instead of emphasizing speed for receivers, concern yourself with size. It’s the tall, physical wide receivers who tend to dominate in today’s NFL. It isn’t that being fast doesn’t help receivers, but rather that the speed “cutoff” isn’t as stringent as it is for running backs.

Receivers need two things to maximize their chances of success in the NFL: size and at least adequate speed (ideally under 4.55). A bunch of big receivers with moderate speed have succeeded of late—Brandon Marshall (4.52), Kenny Britt (4.51), Jordy Nelson (4.51), Dwayne Bowe (4.51), Hakeem Nicks (4.50)—but they’re all very large.

You can buy the book here.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 41: The Value of Hitting on WRs

I was looking over some drafts I did in 2013 and I came across this one with the guys at 4for4.

It was pretty interesting to me because I absolutely tanked my early running back picks with C.J. Spiller and David Wilson. I hit on Gio Bernard, although it’s not like he would normally make up for big misses in two of the first three rounds of drafts last year.

But take a look at my wide receivers. Dez Bryant was arguably my third-best in that league because I hit on Josh Gordon (7th) and Alshon Jeffery (11th). This was a best-ball league, which is why I drafted Gordon so early despite knowing he was suspended. This is an aberration and I’d say 10 percent the result of skill and 90 percent me just getting lucky as shit, but I also landed Pierre Garcon and Marques Colston in this league.

Anyway, the point of this is to show you the value that wide receivers hold, particularly in best-ball formats, because of their week-to-week volatility. I think best-ball formats are a time to emphasize a high ceiling at all costs, opting for “risky” players who might drop, and that’s often the case at the wide receiver position.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 40: This Is How I Draft

Last year, Josh Moore at did an awesome article called “This is how I draft” in which he asked a few fantasy experts to discuss how they go about drafting their fantasy football teams. Here’s my entry:

I’m Jonathan Bales, and this is how I draft:

I really prefer to do live drafts. I like the environment, and I also like to trade picks quite a bit, which you can’t do on a lot of online sites like ESPN. I think trading picks makes drafts fair in that you’re not stuck selecting players you don’t really want; you can trade up or back and create a unique lineup in much the same way as an auction.

Heading into a draft, I typically have five sheets in front of me: one for each position and one that combines any positions that are allowed in the flex. So if there is a RB/WR/TE flex, I have one sheet with all of the running backs, wide receivers, and tight ends listed together.

Otherwise, I keep the positions apart. I’m one of the few who doesn’t use a single big board. The reason is that I think position value shifts so much as the draft unfolds, rendering a single board useless. You should be drafting players based on their position, scarcity, opportunity cost, and relative value as your draft unfolds, not how you ranked them prior to knowing how your particular draft would unfold.

Basically, I use a minimalist approach on draft day. There’s nothing on my boards other than the player name and his projected points. I’ve done all of the research heading into the draft, so I don’t want to be bogged down with information when I’m on the clock. The only other thing I examine is Week 1 matchups. I do that to select my defense (second-to-last round) and kicker (last round), since I stream them based on the opponent.

Jonathan Bales, Daily Fantasy Expert & Author of the Fantasy Football for Smart People series

Check out the rest at 4for4.

By Jonathan Bales

100 Fantasy Football Tips in 100 Days, Day 39: League Timing in Daily Fantasy

In an old post I did at, I broke down how I break up the times of my daily fantasy leagues:


If you plan to enter a Thursday-night league, you need to minimize as much of the inherent variance as possible. That means you must avoid all players with questionable designations. If there’s any doubt at all that a player will suit up on Sunday or Monday, avoid placing him in your Thursday-night lineups. If you can go into the Thursday-night matchup with a 99-plus percent chance of everyone in your lineup playing, then the potential profits far outweigh the very small probability of a late-week injury.

In addition, you might want to consider joining Thursday-night leagues and purposely avoiding the players in the Thursday game. I wrote about why that might be a smart strategy in Fantasy Football for Smart People: How to Cash in on the Future of the Game:

“Below, I’ve listed the potential outcomes for Thursday night games (how the players performed, if you picked them, and how your post-game situation compares to that prior to the game in relation to a novice).

·         Well, Yes – Worse

·         Well, No – Possible slight disadvantage

·         Poorly, Yes – Even at best

·         Poorly, No – Much better

You can see that the best overall scenario is to fade the Thursday-night players and have them play poorly, putting the novices (who are always bullish on Thursday night players) in an early hole. If you select players on Thursday night and they perform relatively well, you could still actually be in a worse position than when you started. If the novices picked the same guys (or arranged a comparable Thursday night lineup), you’ll be in the same boat in terms of points, but instead of having nine players left, you’ll have just eight (or seven, or six), increasing randomness and decreasing your win expectation. On the other hand, if you pick Thursday night players and they perform poorly, you’ll still be even with the fish, and again randomness rears its ugly head.

However, if you fade the Thursday night players and the novices see a handful of them play well, you can still potentially make up the gap; it doesn’t help by any means, but it isn’t a death blow. Thus, the final outcomes for choosing multiple Thursday night players are being in a worse or comparable situation to your opponent(s), while the results of forgoing those players are slightly worse (or possibly even) and much better. Simply put, more good stuff can happen if you generally choose Sunday and Monday players in your Thursday night leagues, especially when your opponent is likely overvaluing them.

The above example is of course an oversimplification of the situation for demonstration purposes; if you have a player in a Thursday night game ranked well ahead of his salary, there’s no reason to bypass him. Further, you can’t expect a league of 20 competitors to all be novices. If the perceived value of the Thursday-night-player-in-question is minimal, however, it might be best to lay off.”