Zone read rushes

[CRA]

Per the article in the Observer...

We ran 128 zone read rushes last year for 767 yards.

That is an average of 5.9 yards per zone read rush.

[Cape Fear Cat]

5.9 per? I'll sure take that.

[panther4life]

I'd like to know how they are figuring that...

 

Cam himself rushed 127 times for 741 yards... So I assume the biggest chunk of that Data is derived from him running out of it. We all know he can scramble and take off as good as anyone. However it puts the running backs and the line at a huge disadvantage when we hand it off.

 

 

[jtnc]

I'd like to know how they are figuring that...

Cam himself rushed 127 times for 741 yards... So I assume the biggest chunk of that Data is derived from him running out of it. We all know he can scramble and take off as good as anyone. However it puts the running backs and the line at a huge disadvantage when we hand it off.

Our line isn't at a "huge disadvantage", they just don't know how to fuging block. Look at our read-options vs SF and the difference is blocking.

[L-TownCat]

Our line isn't at a "huge disadvantage", they just don't know how to fuging block. Look at our read-options vs SF and the difference is blocking.

Not really a fair comparison a SF has one of if not the best o-line in the league.

[panther4life]

Our line isn't at a "huge disadvantage", they just don't know how to fuging block. Look at our read-options vs SF and the difference is blocking.

Any offensive line would prefer to know whether its going to be a pass or a run so they can block properly. Their line is better than ours overall but even their great line is at more of a disadvantage when blocking without knowing whats going on behind them just as much as ours or any o-line in the league would be. Sure their talent level mask it better but its still not ideal way of blocking for any lineman.

 

Here's a simple way to think of it....

 

Pass blocking is all about creating pocket.

Run blocking is all about paving a path.

 

Zone read blocking is full of what the fug is going on behind me?? They don't know if the qb decided to hand it off, drop back and make a pass or run it himself. Meanwhile the D is just following the ball.

 

So yes we know the shortcomings of our o-line and there is no need to amplify this problem with play calling that makes it worse. Coaches have to be able to scheme around the weaknesses of their teams not make them worse. 

[AceBoogie]

Not really a fair comparison a SF has one of if not the best o-line in the league.

THE best didn't really matter who played qb behind that line.

[jtnc]

Not really a fair comparison a SF has one of if not the best o-line in the league.

Redskins also did much better with it than us too.

[Frizzy350]

Our line isn't at a "huge disadvantage", they just don't know how to fuging block. Look at our read-options vs SF and the difference is blocking.

 

SF, Wash, and Sea rarely run the true read option, they usually run a pre-determined play action qb bootleg or a regular hand off and there isn't an actual read from the QB.  Notice how often all those teams use the pistol for their "option" offense.  With the running back behind the QB, you really can't do a read and it's usually a vertical (straight up the gut) run, whereas the read option we typically run is usually a run meant to hit the edges.  In the pre-determined "read" plays however, the line knows exactly where the ball is going and the play develops much quicker in the backfield.

 

The biggest issue with our zone-read (at least last year) was the robotic and unrealistic nature of some of our blocking schemes.  For instance against Denver, often times Greg Olson was expected to go 1 on 1 with Von Miller on read-option plays, Miller obviously beat Greg like a drum.  Also our zone-read had bad timing written all over it when it was called.  The way we run it we either break off a huge chunk of yards, but it was just as likely to get stuffed in the backfield for a loss.  So while the avg net yards is a staggering amount, it's not like we were getting 6 yards per zone read - oftentimes it would lead to 3rd and a mile killing our drive.

[panthers55]

Per the article in the Observer...

We ran 128 zone read rushes last year for 767 yards.

That is an average of 5.9 yards per zone read rush.

So if we have 20 runs which account for 500 of those yards and the other 100 account for 250 with 50 being for negative yards, is that still great??  

 

Where we struggled often was losing yards or gaining a yard or two and being in too many 3rd and longs.  It was great when we broke a big play but it isn't a bread and butter play, it is a change of pace play that we should run 3 or 4 times a game not half of our running plays.

[CRA]

So if we have 20 runs which account for 500 of those yards and the other 100 account for 250 with 50 being for negative yards, is that still great??

Where we struggled often was losing yards or gaining a yard or two and being in too many 3rd and longs. It was great when we broke a big play but it isn't a bread and butter play, it is a change of pace play that we should run 3 or 4 times a game not half of our running plays.

Well the RBs struggled no matter how we ran....blown up either way for negative plays too often last year.

Read option wasnt are issue.....you can apply your statement to both ways we ran last year. Early and late. OL couldn't block consistant and both ways got blown up. We didn't run better later in the year.....we merely finished the season against NO.

Are RBs had the same success last year regardless of what we did....they did not run better when we reduced the zone reads

[PantherBrew]

Lineman are only taught one way to block the zone read, and the way is with the assumption that the running back is going to carry the ball.  

 

In the basic zone read, the QB "reads" the 5 tech, usually on the weak side.  If the 5 crashed down to stop the RB, then the QB has an "option" to pull the ball and run it to the vacated area of the 5.  

 

Lineman know how to block the play, for them it is essentially easier to block because they dont have to account for one of the Defensive lineman.  

 

The two reasons the play can be unsucessful are because either the line didn't block for the RBs path and the give gave him the ball.  Or the QB makes a bad "read" and keeps it and gets tackled by the read man. 

 

I know many know these basics, but a lot of guys yell about the zone read without knowing how it works. 

[Navy_football]

Cam is not an NFL read option QB. I think he's too big and lacks the acceleration to run the read option in the NFL. How many times was he caught from behind by DEs, LBs and even DTs. Cam has long speed, which takes time to develop. Kap and RG3 can run away from most DEs and DTs in a few steps. Cam can run away from some, but not the more athletic ones. 

 

Love Cam and he's an exceptional runner. But I've always been more impressed with that cannon on his right shoulder than his ability to run. I think the team is better served using him as a passer that can make plays with his legs when the play breaks down. And of course short yardage plays are a must for any QB his size and strength. Let the RBs be RBs and the QB be a QB.

[teeray]

The more I read people in the media talking about the read option the more it convinces me they don't know what the fug they are talking about.

For instance, did they know that just because a defender was not left unblocked and the QB didn't make a read after the snap that does not mean the offense did not run the read option?

Or that a zone read option is only one type of several variations of the read option?

Be careful what u read on the read option because most of these people, including some football people, don't seem to know what they are talking about.