Redskins should start Dwayne Haskins in Week 9 vs. Buffalo

EAST RUTHERFORD, NEW JERSEY - SEPTEMBER 29: Dwayne Haskins Jr. #7 of the Washington Redskins walks off the field after the game against the New York Giants at MetLife Stadium on September 29, 2019 in East Rutherford, New Jersey. (Photo by Elsa/Getty Images)
EAST RUTHERFORD, NEW JERSEY - SEPTEMBER 29: Dwayne Haskins Jr. #7 of the Washington Redskins walks off the field after the game against the New York Giants at MetLife Stadium on September 29, 2019 in East Rutherford, New Jersey. (Photo by Elsa/Getty Images) /
facebooktwitterreddit

The Redskins endured another unforgivingly middling effort from Case Keenum on Sunday, and the time for a change at quarterback might be drawing near.

Case Keenum was far from the only reason that the Washington Redskins passing offense stalled in the team’s 9-0 loss to the San Francisco 49ers, but he shouldn’t be absolved of blame for the circumstances alone.

On fifteen drop backs, Keenum completed nine of 12 passes for 77 yards. He was sacked three times, on twenty percent of his drop backs, and he failed to give the Redskins offense the same boost that Jimmy Garoppolo gave the 49ers in the second half.

Keenum started out fairly well for the Redskins, but since his three-touchdown performance in Week 1, he’s been borderline replaceable. Per Football Outsiders, as of Week 6, he had a DVOA (Defense-adjusted Value Over Average) of -2.4. He also has an ALEX rating (difference between air yards and yards needed for a first down) of -1.5, which is second-lowest in the NFL. Most of Keenum’s positive statistical production has come in garbage time, when the games were already out of reach.

Other statistics don’t paint Keenum in a favorable light either. Per Player Profiler, despite having a decent overall protection rate of 85.6 percent, which ranks No. 13 in the NFL, and despite having receivers who rank second in the league in overall target separation, Keenum has the No. 32-ranked accuracy rating among qualifying quarterbacks, and he’s ranked No. 26 in overall deep ball attempts.

Simply put, Keenum was originally given the starting job because he gave the Redskins the best chance to win, in the eyes of the coaches. But if anything, he’s played a part in hindering their ability to succeed.

If Keenum, who is 1-5 on the year with his only win being against the lowly Dolphins, is generating these subpar efficiency numbers, and if Dwayne Haskins is progressing as reports have suggested, then there’s no reason to keep withholding opportunities from Dwayne Haskins.

The win-now factor entailing Keenum is no longer relevant, or even correct, and given the promising efficiency numbers from other facets of the Redskins offense, such as the offensive line and the receiving core, the Redskins should aim to start Dwayne Haskins as soon as responsibly possible.

Starting Haskins in Week 8 wouldn’t be responsible, as the Redskins have a short week ahead of a Thursday night showdown with Kirk Cousins and the 5-2 Minnesota Vikings. But after the Vikings game, the Redskins have a week and a half to prepare for the Buffalo Bills in Week 9. Then, after the Bills game, they have a bye week to recover and reflect, ahead of a matchup with the New York Jets.

Week 9, against the Bills, is the perfect opportunity to start Dwayne Haskins. The Bills defense is a stout unit, but Haskins will have extra time to prepare, and even more time afterward to contextualize the experience gained on the field, learn from it, and apply that knowledge in the second half of the season.

Next. Redskins studs and duds from Week 7 loss to 49ers. dark

The time to turn the page to rookie development is nearing, and when the time is right, the Redskins shouldn’t hesitate to make the transition from Keenum to Haskins. Keenum is a known quantity, while Haskins is an investment and an asset, waiting to be developed. After the Vikings game, Haskins should be given the keys to the offense. And this time, the role should remain his.