Recaps
Week 8 final: trust the work, own the Dobbins miss
Stevenson delivered usable work, Dobbins missed and Coleman made his case. Gibbs and Tampa Bay offer very different lessons for Week 9.
FHFantasy Homepage desk · · 2 min read
Week 8 is complete. Before you chase the biggest score, separate a useful workload from a result you won't get to repeat. Detroit's running game reinforced an established starter. Denver challenged our pre-game confidence. Tampa Bay produced the sort of passing line that needs its weather attached.
The immediate jobs for Week 9 are practical: check running-back cover, revisit Denver's pecking order and avoid making a permanent judgement from one extreme game.
Our Sunday calls: Stevenson worked, Dobbins didn't
Our Sunday start/sit article preferred Rhamondre Stevenson and J.K. Dobbins to gambling on Seattle's unsettled backfield.
Stevenson gave managers 19 carries for 82 yards plus three catches for eight yards. He didn't score, but the workload was useful. That supports the reasoning behind the start without pretending it was a week-winning performance. His next decision still depends on New England's available runners.
Dobbins was the miss. Seven carries for 13 yards were not the return we wanted from that recommendation. Jonah Coleman instead produced 104 scrimmage yards and scored the winning touchdown against Kansas City. We identified him as a stash before the game; the later waiver article moved him up the list. That doesn't rescue the separate Dobbins call.
For the next lineup, require stronger evidence before treating Dobbins as the comfortable option again. Check Coleman on waivers if he is available. Keep the Denver follow-up beside the next practice and coaching updates rather than assuming Sunday's finishing order is a permanent announcement.
Vaki's work didn't take Gibbs away
Jahmyr Gibbs ran for 153 yards in Detroit's win over Minnesota. Sione Vaki added 65. Both contributed to the ground game that set up the winning score.
A productive second runner doesn't automatically make the first runner a problem. Keep Gibbs in your starting plans. Vaki is a deeper-bench consideration for managers who can afford to wait, rather than a reason to remove an established producer.
The question for Vaki is whether useful work continues across different games. One productive supporting performance earns attention; repeated opportunity would earn greater confidence.
Tampa Bay's zero needs the rain beside it
Baker Mayfield finished without a completion on three attempts as Tampa Bay beat Atlanta 16–0 in a torrential downpour. Bucky Irving ran for 170 yards and Kenny Gainwell for 140.
Don't project that passing volume into an ordinary week. Equally, don't assume two runners can keep receiving that much work together once the game asks Tampa Bay to throw. Keep Irving in your plans and reassess Gainwell against the role and conditions of the next game.
For the receiving group, a zero in this setting is weak evidence for a permanent change of opinion. Use the next injury report and matchup to decide the lineup rather than letting a highly unusual afternoon make the decision alone.
The next moves are roster moves
If your bench has a speculative receiver you never start, a back with a plausible near-term job may help more. If your starters are settled, don't create a hole elsewhere just to claim this week's interesting name.
Review the current redraft board alongside your own lineup. The useful follow-through is choosing who can help your team next, while keeping this week's right and wrong calls visible.
By win window
New injury reports and confirmed role changes can change the next lineup. One touchdown total, one supporting breakout or one rain-soaked box score should not make that decision by itself.
Sources: Patriots: Miami box score, Broncos: Chiefs game recap, Broncos: game centre box score, Lions: Vikings game recap, Buccaneers: Falcons game recap.