Something about Ryan rubs me the wrong way. It's not his injuries - those happen. It's not his physicality - he's naturally as talented as anyone I've watched play the game. So what it is?
It's Ryan's head. As a recovering World of Warcraft player (I know, I know...but I played college ball, too,) I truly find it hard to believe that Ryan could ostensibly be so good at a game that involves so much thinking, planning and strategy. Because he displays NONE of this on the football field.
We don't know a damn thing about Ryan's proclivity for the film room. But it's pretty easy to see how many yards Ryan is leaving on the field by charging headlong into battle with zero regard for where he's going, what he's doing, or his own safety.
Don't believe me? Let's check out the film.
We'll start with week 4 against Kansas City. Ryan's first game back from injury. I watched every single one of Ryan's, and a few stuck out to me. Observe as we jump-cut to the 2nd quarter, as Ryan takes a pitch and heads right.
Ryan's in perfect position for a cut back, with his right foot just about to plant. For some reason, he doesn't. He should gain at least 10 yards, likely more. Instead, he bounces outside right into the arms of Eric Barry. No gain.
So for our running tally, that'll go in the books as -12 yards off his "expected total."
On his very next run, we see why Ryan is so "injury prone." Take a look?
Hopefully, this is what Ryan means when he says he took too much contact last year. Sure this is an impressive display of power, but it's really a pretty meaningless hit that doesn't have to happen.
Next play. Ryan makes a decent run here, going hard off tackle for four yards. Upon closer examination, we can see Ryan left another 6 or so on the field. Rather than absorbing the whole play, here's a quick snapshot of what went wrong.
The green arrow is where Ryan went. The Red arrow is where he should have gone.
Look at the pad placement Vazquez has on the Linebacker, pushing him outside. Check the inside arm Hardwick has on Jackson, walling him inside. This play should have hit the "2" hole, not the "4" where Ryan takes it. Beyond the initial read, the 2 hole gives Ryan an angle to runaway from the DB lurking just outside the frame of this snapshot.
Instead Ryan charges headlong into the D at super duper warp bam bam speed. This leads to him missing a that could have netted him an additional 7-10 yards at least.
So we're at -20 yards, with the added bonus of an avoidable huge hit.
Ryan's not the only one to blame for the sad state of our running game. Take a look at this play. Focus on the pathetic excuse for a fullback.
A real fullback that gets even a glancing hit on the charging linebacker nets Ryan another enormous hole and an additional 7-10 yards.
...we're at -27 yards.
Why is Ryan cutting directly at the Strong Safety when he has a blocker on Eric Berry on the left? If you know the answer to that one, tell me.
Let's call that one -9 yards.
Tally all that up and we have -36 yards that Mathews (and McClain) left on the field. How many did Ryan tally for the game?
61. Those runs were the difference between a 61 yard game, on 12 carries, for a 4.4 yards / carry average.
With the extra 36 yards? He's at 97 yards on 12 carries, for a whopping 8.08 yards per carry.
Time to get his grind on in the film room, right?
I plan on beating this horse into the ground in subsequent posts, but John would kill me if I did 16 straight posts on Ryan Mathews in a row. We'll see how it shakes out...