The Kirk Cousins Experience – Week 2

Kirk Cousins2

Welcome back to the Kirk Cousins experience, my season-long chronicle of a late-round QB team in a two-quarterback league.

Play on the site that offers a larger PayoutZone, which means more chances for you to win.

In this series I share each week’s highs and lows as I guide a team through a ten-team 2QB league.

In the auction draft, I went heavy on WR and paid only $1 each for my QB2 and QB3. From the beginning, my plan has been to stream the QB2 position. The fundamental premise at play here is that by waiting on quarterback — a reliable, high floor position — you can gain an advantage at the other, more volatile positions.

My hope is that this series will provide an informative example of waiting on quarterback in a 2QB league and some insight into the weekly decisions when you’re starting quarterbacks worse than any that would even be in “streaming” consideration in a traditional one-quarterback league.

For reference, this league has ten teams and uses standard, non-PPR scoring. The only scoring quirk for quarterbacks is a one-point bonus if they break 300 yards passing.

Last Week

After losing Dez Bryant in Week 1, I knew I’d be in for a struggle. I was thrilled to see Steve Smith dropped to waivers, so I added him as this week’s WR3 even though he isn’t a true Dez Bryant replacement.

Last week my starting lineup looked like this:

QB Matt Ryan
QB Ryan Fitzpatrick
RB Mark Ingram
RB Justin Forsett
WR Julio Jones
WR Stevie Johnson
WR Steve Smith
TE Travis Kelce
K Cody Parkey
D/ST St. Louis

 

I highlight Ryan Fitzpatrick, because in last week’s article I left open the question of who to start in that QB2 slot. I chose Fitzpatrick over Kirk Cousins, Johnny Manziel, and Ryan Mallett, and it turned out not to matter.

I lost this week in very convincing fashion, falling well short of my opponent, the week’s highest scorer. My streaming defense, St. Louis, disappointed, and no one had an elite week. Steve Smith was a fine Dez Bryant fill-in for the week, but I am not convinced he stays that way all year. I am also worried with Lamar Miller banged up and Justin Forsett losing touches (including a touchdown) to Lorenzo Taliaferro. I am now 1-1, 6th out of 10 overall based on record and points scored.

Although it didn’t matter, the process of choosing my QB2 is still worth review. Fitzpatrick had a good, if not great, matchup against Indianapolis, and he did fine in that game. He was QB21 on the week, edging out Kirk Cousins and Johnny Manziel, whom I also considered. Ryan Mallett would have been a better start off the waiver wire, finishing Week 2 as QB19.

Given that I am literally playing for free at QB2, I am happy to have a QB21 performance this week. That wasn’t the reason for my loss, because it fits right in the range of expectation. If I can manage low-end QB2 numbers each week out of the position, I will be happy. Now, I just need to figure out what I’m doing at RB and WR.

I’ll open the floor to comment. What would you look for if you had my roster? This week I had Dez, Kirk Cousins, Greg Olsen, Lamar Miller, and Brandon Coleman on my bench.

Week 3

This week I have several options at quarterback, beginning with the two on my roster: Ryan Fitzpatrick (vs PHI) and Kirk Cousins (at NYG). Additionally, Johnny Manziel (vs TEN), Ryan Mallett (at CAR), Brandon Weeden (vs ATL), and Jimmy Clausen (at SEA) are all available on waivers.

Here is how my team currently looks for Week 3. Note that I stream defenses, so I will be adding one off free agency on Thursday.

 

QB Matt Ryan
QB ???
RB Mark Ingram
RB Justin Forsett
WR Julio Jones
WR Stevie Johnson
WR Steve Smith
TE Travis Kelce
K Cody Parkey
D/ST

 

I write elsewhere about my approach to streaming quarterbacks, so each week I won’t dig into the analysis behind my choice at QB2. Illustration is my goal in this series, rather than a how-to guide. So once again, I won’t disclose my QB2 pick. Instead, leave a comment telling me who you would start if you were in my shoes.

And if you are in a similar position, streaming bad quarterbacks in a 2QB/Superflex league, share your situation in the comments or give me a shout on Twitter. Let’s learn from each other’s experiences.

5 Comments

  1. Romeo Ramirez

    September 22, 2015 at 8:52 am

    Out of that lot, I would stay with Fitzpatrick. I saw a poised QB on Monday night and he made some accurate throws. The Jets D will keep it close and Fitzpatrick can be a solid game manager without too much risk. Should be easier sledding for Ivory against the Eagles which will help as well.

    • Joshua Lake

      September 22, 2015 at 10:06 am

      I have to say I agree with your analysis of Fitzpatrick. He doesn’t seem to be an excellent deep passer, but he looked poised and in command in the spotlight.

  2. Arty

    September 22, 2015 at 9:21 pm

    I’d also roll Fitzmagic, thought he looked solid against my Colts. I’m also streaming in a 10 team 2 QB league, I have Dalton, Mariota, and Tygod (Also King DGAF but dropping Cutler). Any suggestions on which 2 to start? 6 pt passing TD.

    • Joshua Lake

      September 23, 2015 at 4:47 am

      Arty, I’d personally go Mariota, although they’re all close together. In our combined 2QB rankings for Week 3, which came out after your comment, Dalton has the edge.

  3. bayareascott

    September 23, 2015 at 7:56 pm

    You can only start one TE right? Have you been thinking of shopping Olsen?

    I am also 2QB 10 team PPR. Been starting Bridge/Cutler. I’m not dropping Cutler but now have to use either ASmith or Bortles, with Manziel back on the bench. Leaning Bortles this week.

    So far I’m fortunate to be 2-0 with only outscoring my opponents by 7.44 points combined. Almost cost myself this week by benching ARobinson for Moncrief, but Donte did just enough.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>