What to do with Jeremy Hill and C.J. Anderson?

Published: Sep 29, 2015 at 07:53 AM

Every week Committee Meetings breaks down some top storylines from the league's most head-scratching backfield committees in hopes of gaining some clarity for fantasy owners. If you're wondering about a backfield that's not discussed below, feel free to Tweet @MattFranchise for some additional advice.

The current state of running backs in fantasy football is a tumultuous one. A quick glance at the top 15 runners in fantasy through three weeks includes a couple of the elites, but is mostly a mashup of surprises. Of the top 15 backs below, a mere three of them had first round ADPs in fantasy drafts this season.

Now, we expect this snapshot to change dramatically as the season goes on, but it's still a good reminder of just how unpredicatble fantasy production can be as we navigate our way through the season. Also, how many of the above running backs are members of a committee? I'll count for you, the answer is nine. That means there is still great value to be had from running backs that play in RBBC backfields. So let's get to the Week 3 Committee Meetings recap and do our best to predict what may or may not happen in Week 4.

Jeremy Hill cedes touches to Giovani Bernard

Jeremy Hill | Giovani Bernard | Rex Burkhead // Bengals
On Sunday morning, all whispers out of Cincinnati regarding a backfield timeshare were squashed with reports that Jeremy Hill was set to return to a workhorse roll following a week where he lost two fumbles and was benched for Giovani Bernard. But this was not the case when the Bengals took on the Ravens in Week 3.

The snap count was lopsided in Bernard's favor (66 to 34 percent) and it was basically an even split of carries (Bernard: 13, Hill: 12) while Bernard also caught three passes on the day. Bernard was also more productive with his carries as he rushed for 3.8 YPC compared to Hill's 1.8 YPC. Granted, the Ravens defense has been tough against the run this season, but it was the second straight disappointing week out of Hill from a fantasy perspective. His owners, who likely drafted him in the late first or early second round, are left scratching their heads:

CIN RBs through 3 games:

Gio Bernard 41 rush attempts for 235 yards (5.7 YPC)
Jeremy Hill 41 rush attempts for 123 yards (3.0 YPC)
— Matt Franciscovich (@MattFranchise) September 28, 2015

Despite the gap in production between the running backs, Bengals offensive coordinator Hue Jackson confirmed Tuesday that "Jeremy is our starting tailback and that's not gonna change," which should make fantasy owners breathe a little bit easier. Jackson also said that "He'll get himself going here soon. I'm not concerned about Jeremy," a notion that our fantasy editor and podcast producer Alex Gelhar reiterated via Twitter on Monday. Really, Hill just needs to get into a groove to build his confidence back up and he should be just fine as a fantasy asset.

Whether or not you should bench Hill until he shows us something more, well that's really a matter of who you'd be starting over him. Hill remains the higher ranked running back over Bernard since he is still the starter, but there will obviously be weeks where Bernard is the better fantasy play, especially in PPR formats. In Week 4 the Bengals take on a Chiefs defense that hasn't allowed a running back in the end zone yet this season and has surrendered 248 total rushing yards (82.6 per game).

C.J. Anderson comes up short for third straight week

C.J. Anderson | Ronnie Hillman | Juwan Thompson // Broncos
In a frustrating moment for fantasy owners on Sunday night, C.J. Anderson returned to the sideline (after being in the locker room for concussion tests) just in time to see his teammate, Ronnie Hillman, run one in for a score in the second quarter. It was a fitting circumstance with how things have unfolded for Anderson and his fantasy owners so far this year.

Through three weeks, C.J. Anderson is averaging an appalling 3.46 fantasy points per game. He posted another dud on Sunday night against the Lions. He led the Denver RBs in snaps (35 to 23 for Ronnie Hillman) but Anderson's snap count has decreased each week (52, 42, 35) as have Denver's total rush attempts (24, 21, 18). Add to it that Anderson saw just eight carries while Hillman saw seven, and the picture becomes a bit clearer as to why he hasn't been able to produce.

As coach Gary Kubiak said on Monday morning, Anderson's issue early this season has been his health and inability to stay on the field. For the third straight game, the second-year running back missed playing time to an injury. As you may have heard around fantasy circles, players can't get fantasy points if they're not on the field. #Analysis.

While we're not rushing out to dump Anderson just yet, it makes sense if you're ready to relegate him to your bench until he shows us some production. The Denver running backs do have a decent matchup this week though against a Vikings defense that has allowed 16.47 FPPG to opposing runners so far this season (414 total yards and two rushing TDs).

Dallas RBs put up huge fantasy numbers

Joseph Randle | Lance Dunbar | Darren McFadden // Cowboys
The Cowboys backfield had the breakout game we've been waiting for behind one of the best offensive lines in the league against the Falcons in Week 3. Between Joseph Randle, Darren McFadden and Lance Dunbar, the Dallas running back committee collected 245 yards from scrimmage and four touchdowns on the day, which translates to 39.50 fantasy points in standard leagues. As a group, the three runners averaged an impressive 6.0 yards per carry in the game.

The Dallas star was obviously Randle, who totaled 105 yards and scored three times. Many fantasy owners took a chance on him as early as the fourth round of drafts, and saw their investment come to fruition early as it looked like Randle was set to have a record-breaking day -- his first three runs went for a combined 85 yards and a score. But his insane yardage gains slowed as Randle added just two more rushing yards for the rest of the game. Fantasy owners didn't mind since he scored twice more, but this could be an indicator of his ability to turn nothing into something.

Surprisingly, Randle barely out-snapped Dunbar in this game (22 to 20). Dunbar was involved from early on, getting looks on first and second downs while also operating as a check-down safety blanket for Brandon Weeden (12 of Weeden's 22 completions went to running backs). He finished as the Cowboys' leading receiver with 10 catches on 10 targets for 100 yards and racked up an impressive 81 YAC. As long as Weeden is under center, we expect the Dallas offense to lean heavily on the run game and to keep featuring Dunbar as a short-yardage pass catcher who can turn short passes into longer gains to move the chains. Go scoop him up immediately if you play in a PPR scoring format.

Mathews & Sproles make most of Murray's absence

DeMarco Murray* | Ryan Mathews | Darren Sproles // Eagles
When DeMarco Murray was ruled out on Sunday morning with a hamstring injury, savvy fantasy owners who had Ryan Mathews on their bench were forced to make a tough decision: Start Mathews against a Jets defense that had up to that point allowed just 159 total yards and zero touchdowns to opposing runners? The answer seemed obvious with the Philadelphia backfield in dire straits after totaling negative rushing yards one week prior.

Alas, the Eagles got ahead of the Jets early and relied on Mathews and Sproles the entire game. Mathews collected 125 total yards and a receiving touchdown while Sproles scored on the ground (and on a punt return). The backfield duo combined for 42 offensive touches during the game, while quarterback Sam Bradford completed just 14 passes against the Jets, six of which went to his running backs.

If nothing else, at least we know now that if Murray (who has had durability issues in the past) has to miss more time, Chip Kelly will feed Mathews with some Sproles sprinkled in. There have also been reports that even when Murray gets back to full health, Mathews has earned himself a bigger role regardless. Murray's status needs to be monitored ahead of the Eagles Week 4 matchup against Washington on Sunday. Sproles will be a boom-or-bust flex play going forward and has more value in PPR formats, especially if Murray misses more time.

Karlos Williams outscores LeSean McCoy ... again

LeSean McCoy* | Karlos Williams | Anthony Dixon // Bills
Rookie running back Karlos Williams had another strong game for the Bills and has now outscored LeSean McCoy two out of three weeks. Williams and McCoy basically split carries (12 for Williams, 11 for McCoy) but the rookie was far and away the better runner. He averaged 9.2 YPC and totaled 110 yards with a rushing touchdown while McCoy managed just 26 yards from scrimmage for Buffalo.

A major factor in this committee is the health of McCoy (hamstring) who admittedly hasn't been 100 percent since the season started. Since he's been playing so well, it's hard to say that Williams would be getting less opportunities if McCoy was at full strength, but the argument can be made that McCoy would be more effective with his runs if he was healthy. Through three games, McCoy is averaging 3.4 YPC on 43 attempts while Williams has managed a clip of 7.8 YPC average on his 24 attempts (and three touchdowns).

If Williams is somehow still available in your fantasy league, now is the time to put in a claim for him. He has scored a touchdown in all three games and if he keeps running like this, Buffalo won't be able to take him off the field, even when McCoy gets fully healthy. The Bills take on the Giants in Week 4, and early reports point to McCoy possibly sitting out in order to rest and recover, in which case Williams would have RB1 value.

Patriots backfield remains unpredictable

Dion Lewis | LeGarrette Blount | James White // Patriots
Welp, they done did it again. That's right everyone, after Dion Lewis started the season as fantasy's RB5 through two weeks of solid play, Bill Belichick and his inconsistent ways decided to give LeGarrette Blount 18 carries against the Jaguars. On those 18 carries, Blount fell into the end zone three times. All three scores came in the second half and all of them were from inside the 5-yard line. He totaled 78 rushing yards on the day and finished as Week 3's third-highest scoring fantasy running back (27.20 fantasy points).

Fortunately for owners who started Lewis, he scored a rushing touchdown of his own early in the first quarter. So while there was really no loser here, it would have been nice for Lewis owners if he had gotten some more opportunities. Still, he finished with 67 total yards and the score in what was a demolition of Jacksonville. It seems like Belichick kept him on the sidelines after the game got out of hand to protect him, which in the long run is a great indicator of how much the Patriots like Lewis as their lead runner.

It also makes sense that it took Blount a game to get back into the mix after being suspended for Week 1 (he had just two carries in Week 2). While his usage here is a bit worrisome for Lewis owners, the Patriots offense has proven that it's proficient enough for both backs to have value.

Going forward, Lewis remains the New England running back to start in fantasy and will at worst be a weekly flex play. Blount looks like he'll serve as a short-yardage goal-line vulture and clock-killer in blowouts, which comes with more risk on a weekly basis. New England has a bye in Week 4 so make sure you have other options at running back ready in place of Lewis/Blount.

In the latest episode of the NFL Fantasy LIVE podcast the gang recaps the high-scoring Week 3 fantasy slate, discusses whether or not to panic with struggling RBs, and highlights the top Week 4 waiver targets. Don't forget to subscribe and listen in HERE!

Matt Franciscovich is an associate fantasy editor at NFL.com. He's been listening to the latest Tame Impala record "Currents" at least twice a day in recent weeks. Hit him up on Twitter **@MattFranchise** for music recommendations and fantasy advice.

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.