Over the past several seasons, there have been quite a few very popular articles that look at an interesting approach to building a fantasy team with late value picks. Based on the theory of using both Strength of Schedule ("SOS") and taking two players as a combination to build one very good starting duo, a Defensive Team by Committee ("DTBC") can be built as a standard fantasy league strategy. In general, this is usually a wise move because defensive scoring can vary widely on a week-to-week basis depending on matchups, and quite often the teams projected to have the best defenses underperform. Many years it makes a lot of sense to wait as long as possible to secure your fantasy defenses, so there is rarely (if ever) a need to pursue an elite defense in fantasy drafts.
So with this in mind, this article will apply the normal method applied to the other positions (running back, wide receiver, and tight end) for the team defense position. Let's take a look at how to go about building this committee and then we can digest and discuss the results.
HUDDLE UP
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. However, you cannot expect to have every defensive team available. After all, the goal here is to wait at the position and pick up two value picks later in the draft to form our combo and serve as a solid committee. The best plan is to use the following criteria to decide which players to start with for evaluating:
CRITERIA #1 - D/ST11 AND BEYOND
This seems pretty simple. If we want to have a duo that puts up D/ST1 numbers, that means we want D/ST12 or better production - else we would just draft D/ST12 or higher and forget the whole idea. This year there is a slight cheat from the norm (D/ST13 or higher) because of a harder look at both schedules and, more importantly, ADP information. Focusing just outside the Top 10 defenses, both New England (D/ST11, ADP of 181) and Philadelphia (D/ST12, ADP of 199) should be considered, just in case they fall in drafts. Picking an arbitrary line of D/ST13 does not make sense if including D/ST11 or D/ST12 makes the result so much better. Both New England and Philadelphia have favorable schedule segments this year, and their respective ADPs are still quite low (after Round 15), so drafting either of these teams (or both) late is not that much of a reach at all. After all, ADP values tend to go out the window in the back half of most drafts anyway, so it makes a ton of sense to include but the Eagles and the Patriots as possible teams for 2019. So here is the list of teams in consideration for DTBC, listed by their Average Draft Position (ADP):
ADP Rank
|
Team Defense
|
ADP Rank
|
Team Defense
|
D/ST11
|
New England
|
D/ST22
|
San Francisco
|
D/ST12
|
Philadelphia
|
D/ST23
|
Indianapolis
|
D/ST13
|
Kansas City
|
D/ST24
|
Washington
|
D/ST14
|
Buffalo
|
D/ST25
|
Atlanta
|
D/ST15
|
Dallas
|
D/ST26
|
NY Giants
|
D/ST16
|
Pittsburgh
|
D/ST27
|
Carolina
|
D/ST17
|
Oakland
|
D/ST28
|
Detroit
|
D/ST18
|
Seattle
|
D/ST29+
|
Arizona
|
D/ST19
|
NY Jets
|
D/ST29+
|
Cincinnati
|
D/ST20
|
Green Bay
|
D/ST29+
|
Miami
|
D/ST21
|
Tennessee
|
D/ST29+
|
Tampa Bay
|
Table 1: Defensive Teams 11-32 Based on ADP
Going all the way to D/ST32 is an exercise in thoroughness, but odds are that the middle tier of teams is the most likely to comprise the defensive committee for this year. Regardless, Working through the math and considering each and every option ensures that no stone is unturned. With 22 teams under consideration for DTBC, we have a very large pool of options (231 in all), so there had better be a decent pair (or several, we hope) out of all of those couplets. Now, before we go over the method of how to match them up and the results, we need one more rule:
CRITERIA #2 - NO MORE THAN ONE DEFENSE FROM ROUND 15+ AND ONE FROM ROUND 16+
This could get tricky here, but understand the overall goal. The point of DTBC is to free up the first 13-14 rounds of your fantasy draft to pursue all of the other positions for your team. Grabbing 3-4 running backs and 4-5 receivers after grabbing a stud running back or wide receiver in Round 1 sounds like a good idea to me, followed by adding strong depth. This also gives you the flexibility of grabbing a stud tight end, depending on your personal preference, or even to get QB1 if there's a huge value play available before even considering looking towards a defense.
Here is the good news - all of the defensive teams on the list above have ADPs that are Round 16 or higher (later). The interesting part of the defensive team ADP is that only one defense (Chicago) goes before Round 10 (on average), and just the Top 10 are selected by the end of Round 15. Rounds 16-18 see a few teams finally taking a defense with the rest of the Top 12 teams off of the ADP list, which leaves several options for fantasy owners looking for a second defense. Determining when to pull the trigger on your committee options will be key, so monitor everyone's draft (ideally with the Draft Dominator) to see when 8-10 team defenses have gone off the board - then get moving on your committee.
So what is the answer for this year? There is one more thing to consider:
CRITERIA #3 - USE FOOTBALLGUYS' D/ST STRENGTH OF SCHEDULE
This sounds pretty simple, doesn't it? Just take the Team Defense Strength of Schedule to figure out when certain players are more likely to score well. The method here is similar to what the Projections Dominator and Draft Dominator do for you - take the projected fantasy points and slice them up over 17 weeks based on the strength of schedule. which can be called the distributed fantasy points for each defense.
After all 22 team defenses had been calculated with distributed fantasy points on a weekly basis, all that was left was to just compare all of the possible D/ST pairs to find the best duos for DTBC. So here we are - time for some results.
Rank
|
Team Defense 1
|
Team Defense 2
|
Value
|
1
|
Buffalo
|
Pittsburgh
|
144
|
2
|
Buffalo
|
Atlanta
|
143.2
|
3
|
Buffalo
|
New England
|
142.5
|
4
|
Buffalo
|
Tennessee
|
140.5
|
5
|
Buffalo
|
Dallas
|
140.4
|
6
|
Buffalo
|
Carolina
|
140.4
|
7
|
Buffalo
|
Arizona
|
139.4
|
8
|
Buffalo
|
Philadelphia
|
139.4
|
9
|
Buffalo
|
Seattle
|
139.2
|
10
|
Buffalo
|
Washington
|
138.6
|
11
|
Pittsburgh
|
Dallas
|
138.5
|
12
|
Pittsburgh
|
Atlanta
|
138.5
|
13
|
Pittsburgh
|
New England
|
138
|
14
|
Buffalo
|
Kansas City
|
137.7
|
15
|
Dallas
|
Tennessee
|
137.6
|
16
|
Pittsburgh
|
Indianapolis
|
137.6
|
17
|
Indianapolis
|
Carolina
|
137.4
|
18
|
Pittsburgh
|
Seattle
|
137.2
|
19
|
Philadelphia
|
Indianapolis
|
137.1
|
20
|
Pittsburgh
|
Philadelphia
|
136.7
|
21
|
Pittsburgh
|
Arizona
|
136.4
|
22
|
Buffalo
|
Green Bay
|
136.4
|
23
|
Dallas
|
Atlanta
|
136.4
|
24
|
Dallas
|
New England
|
135.9
|
25
|
Philadelphia
|
Dallas
|
135.7
|
26
|
Pittsburgh
|
Tennessee
|
135.5
|
27
|
Buffalo
|
Indianapolis
|
135.4
|
28
|
Buffalo
|
Detroit
|
135.2
|
29
|
Dallas
|
Seattle
|
134.9
|
30
|
Indianapolis
|
Atlanta
|
134.7
|
31
|
Pittsburgh
|
San Francisco
|
134.5
|
32
|
Pittsburgh
|
Detroit
|
134.3
|
33
|
Pittsburgh
|
Kansas City
|
134.3
|
34
|
Dallas
|
Carolina
|
134.1
|
35
|
Buffalo
|
Miami
|
134.1
|
36
|
Carolina
|
Seattle
|
133.8
|
37
|
Buffalo
|
NY Giants
|
133.8
|
38
|
New England
|
Indianapolis
|
133.8
|
39
|
New England
|
Tennessee
|
133.7
|
40
|
Tennessee
|
Indianapolis
|
133.7
|
41
|
Tennessee
|
Atlanta
|
133.7
|
42
|
Pittsburgh
|
Washington
|
133.6
|
43
|
Dallas
|
Indianapolis
|
133.5
|
44
|
Philadelphia
|
Arizona
|
133.5
|
45
|
Buffalo
|
San Francisco
|
133.4
|
46
|
Indianapolis
|
Seattle
|
133.3
|
47
|
Buffalo
|
NY Jets
|
133.1
|
48
|
Dallas
|
Washington
|
133
|
49
|
New England
|
Detroit
|
133
|
50
|
Carolina
|
Atlanta
|
133
|
51
|
Buffalo
|
Tampa Bay
|
132.8
|
52
|
Philadelphia
|
Carolina
|
132.8
|
53
|
Dallas
|
Detroit
|
132.7
|
54
|
Philadelphia
|
Tennessee
|
132.7
|
55
|
Arizona
|
Atlanta
|
132.6
|
56
|
Buffalo
|
Cincinnati
|
132.4
|
57
|
New England
|
Arizona
|
132.3
|
58
|
New England
|
Seattle
|
132.2
|
59
|
Tennessee
|
Kansas City
|
132.2
|
60
|
New England
|
Carolina
|
132
|
61
|
Seattle
|
Atlanta
|
131.9
|
62
|
Tennessee
|
Carolina
|
131.8
|
63
|
Philadelphia
|
Seattle
|
131.8
|
64
|
Indianapolis
|
Washington
|
131.5
|
65
|
Pittsburgh
|
Green Bay
|
131.5
|
66
|
Tennessee
|
Arizona
|
131.1
|
67
|
Indianapolis
|
Kansas City
|
130.9
|
68
|
Carolina
|
Arizona
|
130.5
|
69
|
Indianapolis
|
Detroit
|
130.5
|
70
|
Carolina
|
Detroit
|
130.5
|
71
|
Seattle
|
Detroit
|
130.4
|
72
|
Dallas
|
Kansas City
|
130.4
|
73
|
Philadelphia
|
Kansas City
|
130.2
|
74
|
Philadelphia
|
Atlanta
|
130.2
|
75
|
New England
|
Atlanta
|
129.9
|
76
|
New England
|
Kansas City
|
129.7
|
77
|
Pittsburgh
|
NY Giants
|
129.7
|
78
|
Pittsburgh
|
Miami
|
129.7
|
79
|
Seattle
|
Arizona
|
129.6
|
80
|
Philadelphia
|
Detroit
|
129.5
|
81
|
Pittsburgh
|
Cincinnati
|
129.5
|
82
|
Detroit
|
Atlanta
|
129.3
|
83
|
Dallas
|
Green Bay
|
129.3
|
84
|
Philadelphia
|
New England
|
129.2
|
85
|
Pittsburgh
|
NY Jets
|
129.1
|
86
|
New England
|
San Francisco
|
129
|
87
|
Pittsburgh
|
Carolina
|
128.9
|
88
|
Kansas City
|
Atlanta
|
128.8
|
89
|
Seattle
|
Washington
|
128.7
|
90
|
Carolina
|
Washington
|
128.6
|
91
|
Carolina
|
Kansas City
|
128.6
|
92
|
Dallas
|
Arizona
|
128.5
|
93
|
Philadelphia
|
San Francisco
|
128.3
|
94
|
Dallas
|
NY Giants
|
128.2
|
95
|
Detroit
|
Kansas City
|
128.1
|
96
|
Tennessee
|
Washington
|
128.1
|
97
|
Indianapolis
|
Arizona
|
128
|
98
|
Dallas
|
NY Jets
|
128
|
99
|
Arizona
|
Detroit
|
127.9
|
100
|
New England
|
NY Jets
|
127.9
|
101
|
Washington
|
Atlanta
|
127.7
|
102
|
Tennessee
|
Detroit
|
127.7
|
103
|
Tennessee
|
Seattle
|
127.6
|
104
|
Dallas
|
San Francisco
|
127.6
|
105
|
Carolina
|
San Francisco
|
127.4
|
106
|
Philadelphia
|
NY Jets
|
127.2
|
107
|
Pittsburgh
|
Oakland
|
127.1
|
108
|
Indianapolis
|
Green Bay
|
127
|
109
|
Seattle
|
San Francisco
|
127
|
110
|
New England
|
Green Bay
|
127
|
111
|
Dallas
|
Miami
|
127
|
112
|
Indianapolis
|
San Francisco
|
126.9
|
113
|
Seattle
|
Kansas City
|
126.6
|
114
|
Buffalo
|
126.5
|
Table 2: Defensive Team Committee Pairs
As we can see from Table 2, we have some very good pairs to select from for DTBC. There are 113 pairs that are worth more than the Buffalo defense by their lonesome, and the Bills are projected to produce 126.5 points or D/ST9 overall. Let's also take a look at how often some of these teams show up on the table:
Team Defense
|
Frequency
|
Team Defense
|
Frequency
|
Buffalo
|
21
|
Arizona
|
11
|
Pittsburgh
|
20
|
Kansas City
|
11
|
Dallas
|
18
|
San Francisco
|
8
|
Indianapolis
|
15
|
Washington
|
8
|
New England
|
15
|
Green Bay
|
5
|
Carolina
|
14
|
NY Jets
|
5
|
Philadelphia
|
14
|
Miami
|
3
|
Seattle
|
14
|
NY Giants
|
3
|
Atlanta
|
13
|
Cincinnati
|
2
|
Tennessee
|
13
|
Oakland
|
1
|
Detroit
|
12
|
Tampa Bay
|
1
|
Table 3: Defensive Committee Pair Appearances by Team
As we can see from Table 3, the results have a good number of teams with a dozen or more appearances in Table 2. No less than 11 teams appear at least 12 times in Table 2, which strongly implies that one or two of these teams will likely comprise our DTBC, but we need to do all the math to find out if that is the best option. Using this knowledge of defenses on the list with double-digit appearances, and that information along with Table 2 should make putting a combination of two of the top teams together pretty easy, or even using one of them with a key late pick for our committee. To find out the best strategy, we need to look closer at all of the results.
PUTTING IT ALL TOGETHER
Now that we have 113 possible pairs that are better than Buffao alone, what exactly does that mean? Should the Bills be the basis of our comparison? Of course not. Remember our goal - find a pair of defenses that can combine for D/ST1-type fantasy production. To figure that out we need a better metric, so here are the projections for the Top 12 defenses in standard scoring:
ADP
|
Pos Rank
|
Team Defense
|
FPs
|
92
|
1
|
Chicago Bears
|
151.9
|
120
|
3
|
Los Angeles Rams
|
133.2
|
125
|
2
|
Jacksonville Jaguars
|
138.2
|
141
|
5
|
Minnesota Vikings
|
131.1
|
142
|
6
|
Los Angeles Chargers
|
128.3
|
148
|
4
|
Baltimore Ravens
|
130.1
|
163
|
8
|
Houston Texans
|
126.4
|
164
|
7
|
New Orleans Saints
|
126.8
|
177
|
11
|
Denver Broncos
|
121.5
|
179
|
12
|
Cleveland Brown
|
119.1
|
181
|
15
|
New England Patriots
|
118.4
|
199
|
13
|
Philadelphia Eagles
|
118
|
208
|
9
|
Buffalo Bills
|
126.5
|
210
|
14
|
Dallas Cowboys
|
118.9
|
213
|
10
|
Pittsburgh Steelers
|
122.6
|
Table 4: Projected Fantasy Points for Top 12+ ADP Defenses
Based on Table 4, we see that the Top 8 defensive teams are reasonably well defined heading into 2019, but after that things get rather unclear for teams outside of those first group of defenses. That makes things interesting for the DTBC approach, as a strong pair of secondary defensive teams should compare favorably to one or more of the teams in the first group. To compare apples to apples, we need to adjust how we view Table 4 and the committee choices in Table 2. The committees represent 17 full weeks of play, while the individual players in Table 4 all have a bye week - so we have to add a correction to make the comparison more even. A reasonable number for a bye week fantasy starting quarterback would be 5-8 fantasy points, so if we take a baseline of the lowest projected team in the Top 8 (the Houston Texans with 126.4 projected points) from Table 4 and add 5-8 more points, we have 131.4-134.4 points. The Top 31 choices for DTBC from Table 2 are right in that range, which means that choosing the correct pair can give us the result we wanted - D/ST1 production on the cheap.
Considering all of the results in Table 2, the DTBC recipe for 2019 can go a number of ways, but after considering the Defensive Team Strength of Schedule two teams have at least six favorable matchups (highlighted in blue on the SOS page) - Dallas and Philadelphia. Digging deeper, both teams have a similar schedule with matchups within the division with Washington and the Giants twice each, plus six combined games with the AFC East teams that are not perennial Super Bowl contenders - Miami, Buffalo and the Jets. Combining both strengths of schedule and the Eagles and Cowboys only have one week (Week 4) where both have bad matchups. So the data points to taking the two playoff teams from the NFC East from last season - Dallas and Philadelphia. Both teams are available in Round 17 or later (the ADP for the Eagles is 199 - Round 17, while the Cowboys' 210 ADP puts them in Round 18). Select the Eagles after 7-9 defenses are selected, likely around Round 15-17, and then take Dallas one round later.
An example schedule is provided in Tables 5 for the Eagles-Cowboys DTBC option this season:
Week
|
Suggested Starter
|
Opponent
|
Alternate Starter
|
Opponent
|
1
|
Philadelphia
|
Washington
|
Dallas
|
NY Giants
|
2
|
Dallas
|
at Washington
|
||
3
|
Dallas
|
Miami
|
||
4
|
Philadelphia
|
at Green Bay
|
Dallas
|
at New Orleans
|
5
|
Philadelphia
|
NY Jets
|
Dallas
|
Green Bay
|
6
|
Dallas
|
at NY Jets
|
||
7
|
Dallas
|
Philadelphia
|
||
8
|
Philadelphia
|
at Buffalo
|
||
9
|
Philadelphia
|
Chicago
|
||
10
|
Dallas
|
Minnesota
|
||
11
|
Dallas
|
at Detroit
|
||
12
|
Philadelphia
|
Seattle
|
||
13
|
Philadelphia
|
at Miami
|
Dallas
|
Buffalo
|
14
|
Dallas
|
at Chicago
|
Philadelphia
|
NY Giants
|
15
|
Philadelphia
|
at Washington
|
Dallas
|
LA Rams
|
16
|
Dallas
|
at Philadelphia
|
||
17
|
Dallas
|
Washington
|
Table 5: Suggested DTBC Schedule Plan - Dallas and Philadelphia
The committee approach is not a perfect one, but having this knowledge prior to your fantasy draft can prove to be invaluable if you decide to adopt this approach. If all the players on your starter list are gone, going with a committee can save your team and help you deal with the loss of bigger names. The method is also a big help in "Best Ball" leagues, where lineup decisions are not necessary every week. That's exactly where a committee can do the best, as either player can count for you each week.
Questions, suggestions, and comments are always welcome to pasquino@footballguys.com.