ChiefsPlanet

ChiefsPlanet (https://chiefsplanet.com/BB/index.php)
-   Nzoner's Game Room (https://chiefsplanet.com/BB/forumdisplay.php?f=1)
-   -   Chiefs Would drafting a QB in the first round renew your excitement for the Chiefs? (https://chiefsplanet.com/BB/showthread.php?t=295641)

chiefzilla1501 10-29-2015 03:09 PM

Quote:

Originally Posted by Sandy Cheeks (Post 11846979)
You speak of these endeavors as if they are based on individual ones and not team ones.

If it's 3rd and 10, and Alex throws a screen pass that nets 8... is the QB to blame?

If it's 3rd and 10, and Andy draws up a quick, short pass... the ball is caught by Albert for 6, but he only gets 2 yds YAC.. is the QB to blame?

If it's 3rd and 10, and the 12 yard pass is dropped, is the QB to blame?

If it's 3rd and 3, and the called run play goes for 2 yds, is the QB to blame?


If the offense is forced to take back a lead with under two minutes to go... needing to go 80 yards... with this OL... how much blame should the QB really get?



There are times when this QB is to blame for a failed conversion or game-ending, failed drive... but I would easily expect that his individual blame is not as grand as you want to make it out to be.

It's a shared fail. I acknowledge that some of the above led to third down fails probably more than many QBs. I also acknowledge there were 3 or 4 games including the playoff game, where Smith did his job on his final scoring opportunity but either the receiver or defense failed him.

But when you're hovering around 30% on third downs, that's more than low enough to say the QB has just as much to blame for that. And when you go 3 years without a single game-winning drive, he's had more than enough opportunities on both to at least make those 2 things respectable. And apart from one year in SF where he did well on 4Q comebacks, his record as a 3rd down and 4Q QB in SF was also bad so it's not just KC. Anyone doing the eyeball test sees too many situations where Smith checks down before the sticks (nothing to do with playcalling) and where he was easily the goat on a winning/tying drive. He's had so many opportunities on both to be able to somewhat neutralize the failures of his receivers and coach.

KCTitus 10-30-2015 07:46 AM

Quote:

Originally Posted by Sandy Cheeks (Post 11846979)
You speak of these endeavors as if they are based on individual ones and not team ones.

If it's 3rd and 10, and Alex throws a screen pass that nets 8... is the QB to blame?

If it's 3rd and 10, and Andy draws up a quick, short pass... the ball is caught by Albert for 6, but he only gets 2 yds YAC.. is the QB to blame?

If it's 3rd and 10, and the 12 yard pass is dropped, is the QB to blame?

If it's 3rd and 3, and the called run play goes for 2 yds, is the QB to blame?

That's quite an interesting argument, it's so...what should I call it....binary? I really dont think it's an either or scenario. Football is a team game and there are 22 players on the field during each snap.

There's more to the game, and a play than the way you have framed your examples.

For any of the above examples, provide me some context.

What play did the offense call in the huddle? What kind of defense was being shown, what actually occured, was it zone or man/man? Was there a line stunt involved? Did the QB audible out of the initial call because of a blitz? What was the audible play?

Knowing all of that information, then watching the play from the "all 22" cameras, we might be able to determine exactly who failed and when.

Since we do not have any of that information, we have to go with what we see on the television (I dont mean to assume that you DONT have access to the Game Films, but I think it's an educated guess).

Alex does not like to throw the ball down the field. It's born out in the stats that show him with the smallest average distance for passes travelled in the air. That certainly doesnt bode well on 3rd and 10 regardless the situation.


All times are GMT -6. The time now is 02:59 AM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.