Over the past few years, there have been several very popular articles written by myself and our very own Chase Stuart that look at an interesting approach to building a fantasy team with late value picks. Based upon the theory of using both Strength of Schedule ("SOS") and taking two players as a combination to build one very good player, Chase has discussed both Team Defense by Committee ("TDBC") and Quarterback by Committee ("QBBC") as a general fantasy league strategy. In general, I think that this is a wise move because very early on in fantasy drafts there are a ton of running back and wide receiver prospects to go after to build a great team. While there are a few studs at quarterback and also a few choice defenses, I do not see a huge need in leagues to pursue either too hard in the beginning stages of a fantasy draft.
So with this in mind, I started to think about what else can be done with the committee approach. Tight end? Perhaps. Wide receiver? A possibility, but it might be better to look at third wide receiver options than any other option. What about running back? Hmmm, that's really intriguing. What if you could grab two running backs later in the draft that could combine to perform on an RB2 - or even RB1 - level, based solely on their current projections and their schedule? Now we're talking. This really got my attention, so I went after this one first. Let's take a look at how I went about this and then we can digest and discuss the results.
THE GROUND(GAME) RULES
So how to begin? Defenses and quarterbacks are relatively easy to committee together. There's usually only one quarterback and certainly only one team defense per NFL club, so the approach is pretty simple as far as picking out which players/teams to try and pair up. When it comes to running backs, the line is not quite so easy to draw, but I needed some basis to pick which players it made sense to try and combine for a decent committee. I decided that I would use the following criteria to decide which players to start with for evaluating:
CRITERIA #1 - RB25 AND BEYOND
This seems pretty simple. If we want to have a duo that puts up RB2 numbers, that means we want RB24 or better production - else we would just draft RB24 or higher and forget the whole idea. So here is the list of players with which I started, based on their Average Draft Position (ADP):
ADP Rank
|
Running Back
|
ADP Rank
|
Running Back
|
RB25
|
RB38
|
||
RB26
|
RB39
|
||
RB27
|
RB40
|
||
RB28
|
RB41
|
||
RB29
|
RB42
|
||
RB30
|
RB43
|
D'Onta Foreman
|
|
RB31
|
RB44
|
||
RB32
|
RB45
|
Ty Montgomery
|
|
RB33
|
RB46
|
||
RB34
|
RB47
|
||
RB35
|
RB48
|
||
RB36
|
RB49
|
||
RB37
|
RB50
|
Table 1: Running Backs RB25-RB50 Based on ADP
Great, now we have 26 guys to pair up and see how they do. That makes 325 potential committees, so there had better be a decent one (or several, we hope) out of all of those couplets. Now, before I go over the method of how to pair them up and the results, we need one more rule:
CRITERIA #2 - NO MORE THAN ONE RB FROM ROUND 5 AND ONE FROM ROUND 6
This could get tricky here, but understand the overall goal. The point of RB2BC is to free up the first four rounds of your fantasy draft to pursue three receivers after grabbing a stud running back in Round 1. This also gives you the flexibility of grabbing two receivers and a stud quarterback or tight end, depending on your personal preference, or even to get RB2 and have the RB2BC be your RB3. Flexibility is the name of the game here. We all want value in our drafts, and having the ability to grab two running backs in Rounds 5 and 6 to act as our RB2BC gives us that ability.
Here is the good news - nearly all the running backs on the list above has an ADP that is Round 6 or higher (later), but several backs fall in the Round 5-6 range that will be of interest. We will have to keep that in mind when we look at the results because it would not make sense to expect to get two Round 5 or Round 6 running backs in one of these combinations based on their ADP.
So what do we do now to figure out some running back pairs?
CRITERIA #3 - USE FOOTBALLGUYS RB STRENGTH OF SCHEDULE
This sounds pretty simple, doesn't it? Just take the running back strength of schedule to figure out when certain players are more likely to score well. What I did is similar to what the Projections Dominator and Draft Dominator do for you - take the projected fantasy points and slice them up over 16 weeks based on the strength of schedule. I call this result the distributed fantasy points for each back.
After I had all 26 running backs with distributed fantasy points on a weekly basis, I just compared all of the possible running back pairs to find the best duos for RB2BC. So here we are - time for some results.
Rank
|
Running Back 1
|
Running Back 2
|
Value
|
1
|
151.4
|
||
2
|
150.9
|
||
3
|
149.9
|
||
4
|
149.6
|
||
5
|
149.2
|
||
6
|
148.6
|
||
7
|
148.1
|
||
8
|
147.3
|
||
9
|
147.3
|
||
10
|
147.0
|
||
11
|
147.0
|
||
12
|
146.7
|
||
13
|
146.1
|
||
14
|
146.0
|
||
15
|
145.6
|
||
16
|
145.4
|
||
17
|
145.2
|
||
18
|
144.9
|
||
19
|
144.5
|
||
20
|
144.5
|
||
21
|
144.4
|
||
22
|
144.3
|
||
23
|
144.3
|
||
24
|
144.3
|
||
25
|
144.2
|
||
26
|
144.0
|
||
27
|
144.0
|
||
28
|
144.0
|
||
29
|
143.9
|
||
30
|
143.6
|
||
31
|
143.4
|
||
32
|
143.4
|
||
33
|
142.7
|
||
34
|
142.6
|
||
35
|
142.4
|
||
36
|
142.0
|
||
37
|
142.0
|
||
38
|
142.0
|
||
39
|
141.7
|
||
40
|
141.6
|
||
41
|
141.6
|
||
42
|
141.6
|
||
43
|
141.5
|
||
44
|
141.5
|
||
45
|
140.8
|
||
46
|
140.8
|
||
47
|
140.8
|
||
48
|
140.7
|
||
49
|
140.7
|
||
50
|
140.7
|
||
51
|
140.6
|
||
52
|
140.5
|
||
53
|
140.4
|
||
54
|
140.4
|
||
55
|
Ty Montgomery
|
140.2
|
|
56
|
140.2
|
||
57
|
140.1
|
||
58
|
D'Onta Foreman
|
140.1
|
|
59
|
140.1
|
||
60
|
140.0
|
||
61
|
140.0
|
||
62
|
D'Onta Foreman
|
139.8
|
|
63
|
139.7
|
||
64
|
139.6
|
||
65
|
139.5
|
||
66
|
139.4
|
||
67
|
139.4
|
||
68
|
139.4
|
||
69
|
139.3
|
||
70
|
139.2
|
||
71
|
139.2
|
||
72
|
139.2
|
||
73
|
139.1
|
||
74
|
139.1
|
||
75
|
Ty Montgomery
|
139.0
|
|
76
|
138.9
|
||
77
|
138.9
|
||
78
|
138.8
|
||
79
|
138.7
|
||
80
|
138.6
|
||
81
|
D'Onta Foreman
|
138.5
|
|
82
|
138.5
|
||
83
|
138.4
|
||
84
|
138.4
|
||
85
|
138.4
|
||
86
|
138.3
|
||
87
|
138.1
|
||
88
|
D'Onta Foreman
|
137.9
|
|
89
|
137.6
|
||
90
|
137.6
|
||
91
|
137.4
|
||
92
|
137.2
|
||
93
|
137.0
|
||
94
|
136.8
|
||
95
|
136.8
|
||
96
|
136.8
|
||
97
|
136.7
|
||
98
|
136.6
|
||
99
|
136.5
|
||
100
|
136.4
|
||
101
|
136.3
|
||
102
|
136.2
|
||
103
|
Ty Montgomery
|
135.9
|
|
104
|
135.8
|
||
105
|
135.8
|
||
106
|
135.7
|
||
107
|
135.0
|
||
108
|
134.9
|
||
109
|
n/a
|
134.7
|
Table 2: Running Back #2 Committee Pairs
I apologize for the lengthy list in Table 2, but as you can imagine, we have a lot of choices this year. That's a good thing, but now we have to trim that list down to get some very good pairs to select from for RB2BC. There are some tricky situations this season with two backs either already suspended for a few games (Mark Ingram of the Saints) or another back who could also be facing disciplinary actions (LeSean McCoy). Both are right near the RB24 ADP spot, and that could impact this study. For now, we will eliminate both as options, but I a may readdress one (or both) later this summer as the start of the season nears and when we might have more clarity towards these situations. With so many options this season, I need to be thorough as the ADPs tend to get very fluid as preseason wears on, and we need to make certain we have the very best pairings in case our draft plans go awry. So digging in, there are 108 pairs that are worth more than or equal to Tampa Bay rookie Ronald Jones II by his lonesome, so it looks like there will be a number of options. Let's also take a look at how often some of these guys show up on the table:
Running Back
|
Frequency
|
Running Back
|
Frequency
|
24
|
5
|
||
23
|
5
|
||
22
|
4
|
||
21
|
4
|
||
12
|
D'Onta Foreman
|
4
|
|
12
|
4
|
||
11
|
4
|
||
10
|
3
|
||
10
|
3
|
||
9
|
3
|
||
7
|
Ty Montgomery
|
3
|
|
7
|
1
|
||
6
|
Table 3: Running Back #2 Committee Pair Appearances by Player
As we can see from Table 3, Frank Gore and Bilal Powell dominate the list with four others appearing four or more times. In fact, as I mentioned earlier, Powell is projected to be worth more on his own than either Christian McCaffrey (ADP of RB16), which means Powell is a huge steal based on projections. This tells us that this tier of RB15-30 is pretty up in the air as far as who will do the best. All the more reason to get a favorable pair when it comes to strength of schedule.
As we can see from Table 3, we have a rather extensive list of options to put together RB2BC this year. Nine different running backs appear 10 or more times on this list, with four of them appearing 22 times or more. Clearly, these are the backs to target for the committee approach this season, but which ones? Some of that will come down to personal preferences of these nine backs, but some of the math in the study can help us out. Keep in mind that these are all based on projections at this time, and a single touchdown can sway the results significantly. With so many backs on this list with such frequency, it tells us that the ADP list in the RB20-RB36 range is pretty up in the air as far as who will do the best. All the more reason to get a favorable pair when it comes to strength of schedule.
PUTTING IT ALL TOGETHER
Now that we have 108 possible pairs that are better than Ronald Jones II, what exactly does that mean? Should Jones be the basis of our comparison? Of course not. Remember our goal - find a pair of running backs that can combine for RB2 (or better) fantasy production. To figure that out we need a better metric, so here are the projections for RB1 through RB24 (and beyond):