Brady Quinn: Turning to Backup QB Puts Chiefs in a Lose-Lose Situation

Ian Hanford@Ian_HanfordFeatured ColumnistNovember 18, 2012

KANSAS CITY, MO - NOVEMBER 18:  Quarterback Brady Quinn #9 of the Kansas City Chiefs drops back to pass against the Cincinnati Bengals during the second half on November 18, 2012 at Arrowhead Stadium in Kansas City, Missouri.  Cincinnati defeated Kansas City 28-6.  (Photo by Peter Aiken/Getty Images)
Peter Aiken/Getty Images

No one enjoys picking the lesser of two evils, but sometimes, it's unavoidable. 

Just ask the Kansas City Chiefs.

Unless you consider Matt Cassel or Brady Quinn to be a competent NFL starting quarterback, you realize that this team cannot win with its current situation behind center.

That's not this team's only problem, but it would be a fatal issue for any team that has other weaknesses to deal with as well.

Quinn replaced Cassel in Sunday's 28-6 loss to the Cincinnati Bengals. He hadn't played since suffering a concussion November 7 against the Baltimore Ravens, but Cassel is just that bad. He's thrown seven interceptions in the last four weeks, and that won't cut it for anyone.

UPDATE: Wednesday, November 21 at 11:56 a.m. ET

Chiefs head coach Romeo Crennel confirmed that Brady Quinn will start Sunday in place of Matt Cassel, according to CBS Sports on Twitter.

Romeo Crennel just announced that Brady Quinn, not Matt Cassel will start. So much for a slow news day.

— Eye on Football (@EyeOnNFL) November 21, 2012

---End of Update---

Turning to Quinn was inevitable, but it's not encouraging. He's a marginal talent. He was buried on Cleveland's depth chart prior to joining Kansas City. He's never lived up to any sort of hype he had after leaving Notre Dame, and he's past the point of reversing his fortune.

Quinn went 9-of-14 for 95 yards after replacing Cassel. Sure, it could be worse, but it could be a lot better. Avoiding interceptions is nice and all, but it doesn't justify the inability to matriculate the ball down the field. 

Look at this way. Quinn has now played in five games this season. He's only thrown three interceptions, but he hasn't thrown a single touchdown. There's not a huge sample size, but he hasn't thrown for one score in 58 pass attempts this year.

That's ugly. Only a 1-9 team would put up with this caliber of play behind center, yet it's also a main reason that it's 1-9. 

Some may say Quinn isn't that bad. Well, neither is Kyle Orton or Shaun Hill, and they've both thrown, at least one touchdown this season. Would you want either one of them as your starting quarterback? Not if you want to win you don't. 

Cassel shouldn't be a No. 1 signal-caller for anyone, and neither should Quinn. That's the horrible dilemma the Chiefs face every week as they sink further and further into NFL purgatory.

At this point, playing Quinn probably makes more sense, but not for anything he's done. Cassel's shortcomings just can't be justified anymore, making Quinn the automatic starter.

Both are bad. The Chiefs won't win with either, but sometimes, the lesser of two evils is an unavoidable scenario.