First, let me say that I didn't see the game. Wish I had! I was following it on that ESPN Gamecast thing, and I was sharing the frustration over the running game.
Not having seen it, I can't say anything specific. I certainly have nothing either encouraging or discouraging to say about what we did rushing on Sunday.
I will, however, simply point out that, in the NFL, blocking the run is far more about where people are than how much force the OL can exert. If you look closely at a run, it's rarely a matter of blowing the DL off the LOS.
It's rather a matter of 1) sealing off moving DL and 2) either sealing or freezing a scraping or penetrating LB or DB. It's also a matter of synching the RB's cuts with the timing AND the ever-so-brief appearance and disappearance of lanes. It's very intricate stuff.
It is actually understandable to me that the running game would lag in a brand new offense with a 1st team unit that got very little PS work. That makes sense to me.
Now, guys talk about Gurley. I dunno about that. Can't comment, not having seen these plays. There may be an issue there.
But for the rest, I'd just suggest that we keep a few things in mind:
- Resist the instinct of blaming everything on the OL.
- Understand that a good running game in the NFL is generally a matter of the OL and RB being in synch ...
- Within a scheme that is well designed to deal with the defense's scheme.
- I think it makes sense to have some trust that McVay will keep working on the scheme until he figures wqhat works for this perssonel.
Well, I hope they figure it out. I'm an old run blocker and NOTHING pleases me like a relentless running game.
