Maybe you were supposed to read one of these guys? [Marc-Grégor Campredon]

Neck Sharpies: Getting Out of a Scrape Comment Count

Seth September 10th, 2019 at 3:00 PM

Last week in this column I talked about how the changes to Michigan's running game under Gattis seemed to be mostly about adding a read to it. One week later, at least among fans who know the first damn thing about Army, we're all grumbling about about how Michigan reversed the gains of their Gattisization by dorfing the reads.

To be sure, there were plenty of plays where Shea (and one where McCaffrey) had a keep read and handed the ball off. It's also pretty evident—despite what Harbaugh said in the presser—that Patterson was playing hurt. Also later in the game Army knew Michigan wanted to avoid passing and started bringing their cornerbacks on blitzes off the edge.

However, on re-watch, I noticed a lot of other plays where the DE crashed but Army was really taking away both options with what's called a "Scrape Exchange." Maybe showing these plays, what Army was doing, and what Michigan could have done in response, will ease some of the whinging?

----------------------------------------

1. What's a Scrape Exchange?

It's a defensive "paper" call to the "rock" of the zone-read option play. Essentially they're flipping the jobs of the two backside guys, having the DE crash inside while an LB loops into the spot the DE formerly occupied.

image

The win for the defense is the green (i.e. the B gap) block in this diagram. The offensive play is designed to get that block accomplished with a tackle releasing on a linebacker. By exchanging jobs, the defense wins the block and can force a read right into it.

I covered this a few years back when we were meeting Don Brown, and again when Iowa adapted to Michigan's Pepcat package (and Microsoft still included their full video editor with Windows). Unfortunately something on our site is breaking the links to old images at the moment, but you can probably get the gist just from the video with the Bear vs. Shark song on it.

[After THE JUMP: We have the technology, but do we trust it?.]

----------------------------------------

2. How Can the Offense Respond?

A scrape exchange is a paper play, and you can always scissors those. FishDuck, one of the first X's and O's guys I got into, has a whole video on scissors plays for the scrape exchange. If you're interested in those, watch it, because I'm going to skip past this after.

To his list I'll add Belly, a zone read where you double the backside DT to blow him out and then truck stick the WLB. Belly is certainly in Michigan's offense, but might have been iffy against Army because of the weird way they align.

Those are great to have in your offense but not very useful once the ball is already snapped on your zone read play and the opponent has a scrape exchange on.

----------------------------------------

3. How Can the Offense Build a Response Into their Zone Read Play?

Fortunately you're not screwed. Double-fortunately, unlike in 2016, Michigan now employs the guy who once gave a coaching clinic on this (HT: Smart Football) while working for the baddies (warning: language NSFW):

The relevant part starts at 22:15, but you can go back to 12:00 and 19:45 to catch the coaching points on a normal zone read (and the part where Ed admits he had to change up his terminology because OSU guys aren't as intelligent as the players he used to coach).

The way Warinner coaches this, the tackle's first step is to read and react to the defense. Meanwhile the quarterback's zone read—just as Rich Rodriguez always said—is reading a zone, not a player. If the DE steps out of that zone, e.g. by scraping inside, the quarterback reads the linebacker stepping into that zone, and that means give. I had a hard time pulling an old example from a game you want to be reminded of, so here's Mark Huyge (the left tackle) doing it on a play that was blocked well for a frontside run until Michael Shaw inexplicably bounced out of the lane the play created.

Sometimes that exchange happens too late because the T has released downfield. He can still stop and execute a Butt Block. I don't have any good clips of this but we can screen grab from the 2016 Iowa clip and pretend. Basically the tackle sees the WLB cross his face, stops, and just walls off the DE like he would on a rebound in basketball. Now you've got the WLB outside, the DE also walled outside, and the QB will see the WLB, hand it off, and send the RB through the butt block.

image

(Relevant to Michigan but not to this play: in the video Warinner notes that he has the T block that LB "for the running back." In other words he wants the block on the linebacker to be good for a handoff, not just a seal in case the QB keeps it. It's harder to execute but better for general use.)

----------------------------------------

4. What Was Different About Army's Defense?

Army ran a bunch of these against Michigan's Arc Read zone, which they correctly identified as the Wolverines' best play. But what Army does is a bit different than your standard 4-3 defense's scrape exchange. Their 404 Tite system is designed not just to get that exchange, but to make the exchange optional depending on how the offense is blocking it, forcing a give, and forcing the back into the teeth of their defense.

image

What was so disappointing from a game theory perspective is that Army's defense more or less wants to play like this. Their 404 Tite was designed specifically to gum up the frontside gaps with DL and put multiple edge defenders in space on the backside to stop spread games. This is what happens when you run zone read against a 404 Tite:

See? It's not a 100% scrape exchange. The Rush end (we'll call him R today) is able to squeeze the read until the WLB comes around behind him, delaying the handoff and ultimately forcing it. The offense then has no angles on the backside, and is forced to run into whatever gaps they can create on the frontside, which won't be the gaps they normally like to run into because there's a thick DE playing over the tackle they want to run behind out there. Also the defense knows this and has the MLB gunning for it.

These exchanges were more like stacks—lining up behind one another—but the result was similar: two guys hanging out there when the quarterback goes to read, and everybody else fighting their way playside to stop the running back.

Army is able to play like this from multiple alignments. Here's an example from Michigan's final 4th quarter drive. Michigan wants to run the ball and kill clock because if you get Army in any kind of passing situation they're dead meat. Army knows this and is stacking eight in the box. Better to give up a touchdown than a field goal with under 2 minutes left. So this is already a Rock/Paper/Scissors loss for Michigan as it's drawn up.

image

You can see what Michigan wants to do: read the backside EDGE defender (R), seal the backside T and WLB inside, and either split zone inside the R if he forms up outside, or arc zone around him if he gets inside. Army is going to gum this up by having the R dive inside and the WLB jump outside. Essentially they've flipped jobs, and McKeon now has to deal with a green guy outside of him.

At the moment of the read Army has not one but two backside guys protecting the edge Michigan wants to arc out of. They're also in position to exchange, but not fully exchanged, and also shuffled at the line of scrimmage rather than upfield where they would be easy to trap block. This would be a very difficult block to get right:

image

Wherever McKeon goes, the LB will go in the other hole, and the R will do the opposite. Either way the backside is closed, and Patterson has to give it to the running back to get what he can frontside. Where Army has that extra defender. Play dead.

5. What About the Corner Blitzes Into This?

The corner blitzes were Army selling out against Michigan's arc read plays, gambling that Michigan was running some kind of zone read run and giving up entirely on the idea of defending any kind of pass to the flat.

If the defense adds a corner blitz to a scrape exchange and catches you on a read play, you're dead meat, especially when he times his blitz so well that he's in the neutral zone at the snap but would have to be named Khaleke Hudson to be called for it. Short of—I dunno, pitching it to Eubanks?—this play call is doomed.

"What are you gonna do, stab me?" –Man who wasn't stabbed for some reason

The Harbaugh offense nerfed those games by play-action passing and putting the ball in the back's hands so fast that the corner blitz was just adding a useless chaser to the backfield. The Gattis offense is supposed to nerf those games by putting the defense in space. Remember that play in the spring game when the running back ran one way on a flare and the quarterback was the pin & pull ballcarrier? That punishes teams that try to pull what Army was pulling most of this game. Michigan threw it to the back in the flat once in the 1st quarter, then forgot about it. Army then got to go balls out against Michigan's backfield without fear of giving a chunk to a play Michigan should be running a lot.

Michigan also tried a lot of unbalanced stuff in this game, covering the tight end on the strong side and having no pass threats on the weak side. Army allowed it, leaving the cornerback to that side as an overhang LB, which was plenty to force Patterson to give. This invited a CB blitz but since that didn't occur, Michigan got to enjoy greater spacing on the frontside a bit and used that for a decent gain.

After that the gimmick was up.

----------------------------------------

5. Well Then How Do You Beat What Army Does?

Get more players to that side than they have and don't flub the read. By putting a slot receiver on the backside here, Michigan has forced the weakside defender into a run/pass quandary. He's got to stay outside, the DE can again be the read guy, and with no more crashing end the give is a good play again:

But you have to still make the read:

Michigan now has their slot receiver on the backside, and Army has responded by shifting the Tite front over to something more like a 4-2-5, except the WLB is now being pulled outside by the slot receiver. Because he doesn't want to get too far outside, Michigan now has flanking numbers to the back side of the formation. They could bubble out to the slot, or just use that to deliver the quarterback to the safety with a WR crack on the WLB. It's there, and Patterson keeps. Booooooo.

This should not have been a give:

I thought this was a clever way to keep the numbers to the intended play side while moving Army to attack the formation's strong side. It works too: their entire front steps toward the bottom of the screen while Ronnie Bell's orbit motion is reversed into a zipper. The DE has shuffled down the line of scrimmage like he was doing all game, and now Shea has both a TE escort and a pitch option versus Army dudes. He hands it off. Booooooo!

You can also just shift the game to the frontside. This also should not have been a give:

Look at the numbers Michigan has in this clip: 1 has to respect the jet; 2 has to play the run and deep safety; 3 is all the way on the hash and has to get around the H-back, Eubanks. The WLB is so far inside he's not even in read position anymore—that's the damn cornerback, who's got a jet to worry about. Keep the ball!

In summary, this game's running woes weren't just about missing keep reads. Most of the quarterbacks' reads were gives forced by how Army plays defense. The frustrating thing is when Gattis gamed up a keep read for big yards, the quarterbacks still gave.

Comments

BBQJeff

September 10th, 2019 at 4:33 PM ^

The arrow is pointing at the WR but the slot receiver was arguably even more open.  A quick toss to the slot and he runs toward the sideline he has the WR there to block the corner.  That's potentially a huge play.  

Plus it's a shorter throw which gives the D less time to react.  

MGoBlue96

September 10th, 2019 at 4:45 PM ^

I mean either a quick route to the outside receiver or a bubble to the slot is the easy thing to do here, but we know Michigan often doesn't like to do things the easy way. This is the epitome of banging your head into the wall when Army was stoning short yardage runs all day.

gbdub

September 10th, 2019 at 8:09 PM ^

I was really, really hoping we'd call a pass, any pass, to the outside on that 4th and 2, because I knew Army was going to sell out to stop a run (because that's what they'd done all day).

Seth's analysis here does explain a bit more what we were seeing, and why it wasn't necessarily dumb by either Gattis or Shea on a game-wide basis.

But this playcall in particular does seem really bad, and hard to excuse.

mgobaran

September 11th, 2019 at 4:03 PM ^

What is your point beyond this being one bad play call or missed audible? I'll preface this by saying running the ball on back to back failed 4th down conversions is too conservative of an approach. On the other hand we would end the game with three goal line TD runs of 3 yards or less, and had converted a 4th down and 1 by running for 3 yards. We were pretty darn good at short yardage run situations until that point. Our only punt of the game was after a 3 and out (1 run, 2 pass plays), so it'd not like we ever got stuffed on third and short before the last two drives in regulation either. 

As you stated, Harbaugh's offenses have taken advantage of these smoke screens for free yards in the past, so we have no reason to believe Harbaugh is the reason we aren't taking advantage of them now. Although he did this from under center instead of a shotgun snap.

With Shea's poor history on screens passes, and his performance in this game (I counted 5 flare passes, Shea was 3/5 for 2.0 YPA), Shea may not be reliable enough of a throwing in those situations for it to be a valid option.

The other reason may be that as an OC calling his 2nd ever game, Gattis simply overlooked the smoke screen as a play we should be audibling to, and we haven't installed it as an option yet. 

Yeah, it sucked in that moment. I wish we would have thrown the ball out there. But does not taking advantage of it in that situation mean this is a Harbaugh Era or season long issue? Let's just wait an see on that I think.

Reggie Dunlop

September 13th, 2019 at 7:17 AM ^

I never said this was an Era issue. I didnt say it coildnt be fixed. 

I'm dumbfounded they didnt do it. This is one screenshot. That corner was off the entire game. You had that whenever you wanted -- both 4th downs. 

Brian posted his UFR last night. I'll bet you wont argue with me now that the boss has come out and blasted them for the same thing. 

I support this staff, but the offensive approach we ran Saturday was criminal. We got away with it because it was against Army. I want to win the Big Ten, and to do that we have to be as smart and ruthless as the rest of the conference. Saturday was a huge blow to my belief that we're there.

skegemogpoint

September 10th, 2019 at 9:23 PM ^

Pretty clear you don’t watch or know a goddam thing about the players i named or college football in general. 

Feel comfortable in saying Becton, Wilson and Slaton would be a massive upgrade over the guys we landed. And oh, btw, Boy Wonder, Filliaga was recruited as an OT but he didn’t pan out there so they moved him to OG.

Jimmy’s and Joe’s over Xs and Os every day of the week. Seems ridiculous to even have to point this out - but that’s the what the mgoblog message board has become...

MGoBlue96

September 11th, 2019 at 1:19 PM ^

On paper the interior line is one of the best in the country, I am not even sure why you are debating that. Runyan when healthy is solid, RT was the only question mark coming into the season and Mayfield according to all reports had the edge at RT over Steuber. So yes I think it is ridiculous to claim it is a jimmy and joes problem with the offense. Like I said it doesn't matter how good your o-line is supposed to be, if you don't have enough bodies for the defenders your trying to block it is going to be a rough go. You can't out talent the numbers game up front.

DualThreat

September 10th, 2019 at 3:48 PM ^

You know, one thing I haven't seen mentioned much recently is how well Shea fakes the give before he pulls.  Remember the MSU game last year?  So, if Shea keeps the ball in the RB's hands a fraction of a second longer, perhaps that would be the key to getting edge guys to commit inside.

Arb lover

September 10th, 2019 at 4:18 PM ^

Lets worry about ball security rather than good fakes (my opinion). I will also go contrarian and say I have faith that they will get this together, and that Shea and co are being asked to do a lot more than normal teams are.

Remember last year when we (only later) found out that the Oline had been given extremely basic concepts to focus on for the first few games, to avoid the overload? I'm guessing Gattis didn't focus on some of the counter plays... I only hope they do practice and get these concepts, and that everyone gets fully healed. Also making the call on the field is tough and deserves appreciation.

Thanks Seth.

reshp1

September 10th, 2019 at 4:27 PM ^

This was one thing I noticed as well. Michigan's mesh point is so quick, they never really force a defender to really commit. Lots of teams have the QB and RB take multiple steps together before the pull or give is made. If anything, Michigan made an adjustment to shorten the mesh point at halftime, presumably to get the RB to the LoS faster.

LKLIII

September 10th, 2019 at 4:44 PM ^

Agreed.

He was god damned magician last year with that stuff--routlinely faked out even the camera men, and yet I haven't seen him be nearly that sly this year.

However, if Shea's injury is an oblique or rib/intercostal injury, that could materially hamper his ability to do that.  I'm not a physical therapist, but I think holding the ball at the mesh point longer before a pull requires the QB to stretch out his arms from his body an extra beat.  I think that kind of motion might directly involve the obliques/side/core of the athlete's body.

MaizeNBlueWizard

September 10th, 2019 at 3:54 PM ^

If Michigan is going to compete in the big ten there’s a lot more they must do on offense to keep opposing defenses honest.  We must stretch the field horizontally and vertically to make defenses defend the entire field. Too often against army and MTSU we witnessed the wolverines only attacking the middle and seldom anywhere else. We need to throw more on early downs. We also need a better snap count bc they go on a clap every time and the fake clap is so easy to discern its comical that we’re running that in big time D1 football. A cadence is much preferred at home and on the road a variation of snap counts would be way better than what we are currently doing. 

If Michigan can’t properly defeat a modified scrape exchange then I have serious reservations about speed in space. Let’s hope the bye week clears up some of this crap because if we play the way we played last Saturday against any big ten team with a pulse we’re in big trouble. 

imafreak1

September 10th, 2019 at 3:56 PM ^

I'm not a smart man. So I want to boil things down to simple terms.

What I got from this nice and in depth analysis is that Army successfully predicted predicted the play that Michigan called over and over in the second half and ran a defense designed to stop that play. Gattis obliged by calling that play over and over. Including on a critical 4th down. Burning downs with the hopes of occasionally fooling the defense for a big play. Hence.

In summary, this game's running woes weren't just about missing keep reads. Most of the quarterbacks' reads were gives forced by how Army plays defense. The frustrating thing is when Gattis gamed up a keep read for big yards, the quarterbacks still gave.

Except the big play never successfully came off. So, Michigan had unsuccessful Al Borges calling plays in the second half? I had hoped for better.

Is burning downs running the exact play the defense is designed to stop a requirement or is the Michigan offense capable of executing more than one play? Are we forever to doomed to the excuse that it may have been obvious but it should have worked?

I am confident that Gattis' best days are ahead of him but this analysis certainly did not make me feel better.

Cmknepfl

September 10th, 2019 at 4:20 PM ^

I agree this didn't make me feel all that much better.  

I think some explanation for a majority of the gives though, not even more lends itself to Shea not keeping because he is hurt.  Whether he was directed to or not, it has to be part of the explanation.  So many times last year he pulled to convert big plays against Wisconsin, PSU, and MSU.  Is it even possible that his reads are that bad?  If they were wouldn't we also be likely to see him keep when he shouldn't because that doesn't seem to happen much. 

(of course we won those games so they aren't big wins.  If we had lost them though, they would be added to 'big games Michigan cant win' list)

 

 

 

 

LKLIII

September 10th, 2019 at 4:53 PM ^

"Is it even possible that his reads are that bad?  If they were wouldn't we also be likely to see him keep when he shouldn't because that doesn't seem to happen much."

I think this is an excellent point.  If it was purely a cognitive inability to make correct reads, we would be expecting him to dorf the reads about equally in each direction.  That is, pull when he shouldn't about 50% of the time, and give when he shouldn't about 50% of the time. I don't have the patience to UFR it, but I don't think that's what happened. 

It seems to me that when he made the "wrong" read, most of the time it was giving when he should have kept.  If true, that tells me that there was another variable to tilt the balance of the "wrong" reads towards the "should have kept, but gave" variety. 

That lends support to the theory that Shea cognitively understood most of the reads, but was either explicitly coached to not pull, or he was purposefully not pulling on his own accord, in order to maximize his health for future games.  If true, that would be much better news, because we'd expect much of that problem to go away once Shea's health improves and/or once we are in a bigger game where Shea/the coaches are more willing to roll the dice on his health.

reshp1

September 10th, 2019 at 4:19 PM ^

I went through and watched all of Patterson's reads and I thought mostly in the context of "what is this optioned guy doing" he made the right reads most of the time. The problem was Army was making those reads that were correct in the context of one player the wrong one in the context of the entire defense. Michigan never seemed to punish that at all and in fact they played right into their hands by motioning eligible receivers in closer to the line, which just allowed them to gum up the works that much more.

BBQJeff

September 10th, 2019 at 4:25 PM ^

Well, the film analysis confirms what I watched last Saturday.  On at least a few occasions the pull has there but Patterson handed off.  

He was very effective pulling last year.   Why he didn't in this game makes no sense.

Gattis confirmed he was hurt.   If the coaches told him not to pull (which I doubt) or he wasn't pulling because he was protecting his injury then he had no business being in the game once we went to a run-heavy set.  

Indiana Blue

September 10th, 2019 at 5:29 PM ^

Last year Shea was a gutsy QB.  He ran when the play was available.  In 2 games this year he has not shown the same control of his skills.  Whether he’s hurt or not, he is simply not the same as last year.  Zero confidence won’t heal over the next 2 weeks .... he appears to be extremely hesitant to take a hit. 

The QB sets the offensive tone and handles the ball every play.  If he plays like week 1 an 2 this offense Is doomed 

Go Blue!

ColoradoBlue

September 10th, 2019 at 5:31 PM ^

I'm sort of geek, so I watched the Warinner video.  Based on his coaching points in the clinic, many of those questionable gives by Shea were probably correct based on the end's play.  He's never really crashing; usually in a position where the tackle or tight end's body would essentially eliminate him as a threat to the RB.  What I got from this video is that the "default" is a give, and the trigger to pull is really a question of whether the defensive end is a threat to the RB, NOT a question of whether the keep has green grass in front of it.  To wit, it's seldom the defensive end tackling the RB, it's everyone else. 

So upon further review, I think Shea is less of the culprit here.  It probably has more to do with Army messing with the keys, and us just not having enough reps with the counter action to feel comfortable risking anything in a game that devolved into that pressure cooker.  I'm confident we will improve just like we did last year.  Will we improve fast enough?  Who knows.

blueday

September 10th, 2019 at 5:39 PM ^

So the coaches didn't know this and exploit? Sad. How much are they paid and how much did my seat cushion cost that frosted my arsch.

LKLIII

September 10th, 2019 at 6:28 PM ^

I'm betting (hoping) that it isn't coaching ineptness, but some (hopefully) temporary conditions:

  1. The team hasn't had the opportunity to fully rep/install all the counters to the offense yet; 
     
  2. Key injuries (mostly Shea, but also Runyan and DPJ),
     
  3. The nature of our opponent (Army's TOP strategy disproportinately punishes turnovers as they represent a higher % of lost scoring opporunities)
     
  4. The nature of our schedul (tempting bye week to heal before a big Wisconsing game)


All contributed to a rational decision by Harbaugh & Gattis to TEMPORARILY bottle up/constrict the offense against Army--especially after the 3 TOs in the first 4 possessions.  

The bye week will improve player health, allow the team to better understand/further install more counters into the offensive game plan, etc.

andrewgr

September 10th, 2019 at 9:16 PM ^

Leaving aside whether the decision to shut down the offense and run the ball was the right one or not, the fact remains that the way they executed that strategy is really concerning.  No amount of rationalization should convince anyone that the only run play they're capable of safely executing is handing off during a zone read, or else handing the ball to the RB and having him run straight ahead  There are lots of other run plays in the playbook, that these players have been executing since they were in high school.

Go back and look at all the posts after Spring ball.  They all consistently said that the blocking schemes are largely unchanged.  That was the part that was supposed to make this a smooth (not painless!) transition.  The formation may look different, the QB has some extra options, maybe the TE is responsible for being a receiver where in the past on the same play he would have been a blocker, but up front, the blocking schemes didn't need to change at all for a lot of the plays.

Those OL (even the backups forced into action) know those blocks, and they've had plenty of experience executing them.  Pounding the ball repetitievly into the middle of the defensive line was not, could not conceivably have been, the only run play the team is capable of executing.  

I don't have an answer as to why they kept doing that, but I don't believe your hypothesis that due to injuries and a transition to a new offense these were the only plays they could call.  In fact, if that is correct, this team is unavoidably screwed for this year, because to not be capable of executing basic running plays, this team would be in worse shape than a competent team is at the beginning of Spring.

lorch_arsonist

September 10th, 2019 at 6:45 PM ^

Seth this is helpful and balanced. A bunch of the plays that looked like keeps weren't that good for keeping. Yet Patterson did give a few times when there were yards to be had if he keeps-- he's not blameless nor deserving of all the blame he has been given. I appreciate the moderation and it makes Gattis' comments make more sense. Cheers! 

MGoStrength

September 10th, 2019 at 7:07 PM ^

I know this is a rhetorical question that can't be answered.  But, won't everyone do this against us now until the QBs prove they can read it correctly?  Further, are we doomed because our QBs are not as good at this as we would like?  Cheers to McSorely for apparently being better than Patterson :/

jabberwock

September 10th, 2019 at 9:32 PM ^

What?  Our QBs may not be so good?!!!

No worries, we have a QB whisperer as a head coach so there'll never be a concern there.
He'll turn middling 3*s into heisman finalists.  Just wait til about year 3 when he gets "his own guys", then you'll REALLY see something.

ColoradoBlue

September 11th, 2019 at 9:49 AM ^

Except for a couple of cases where he clearly missed a pull, the defense was designed to take away *both* options.  

So we don't need need him to "keep it and run" as much as we need counters, and the counters to counters that punish the defense for playing this way. 

Mongo

September 10th, 2019 at 7:16 PM ^

Original game plan was designed for more passing but missing veterans like Runyan and Wilson really showed.  Two blitzed-induced fumbles resulted in a hurt QB with happy feet.  Change in game plan was to turtle up and win with defense.  Army was happy to oblige and make it a slug fest.  

Bottom line we won this game on the backs of the defense and Shea did not get killed.  Mission accomplished.  But OMG do we need Runyan, Wilson and DPJ back in the line-up and Shea's oblique issue to heal up.  Bye week is a godsend.

JHumich

September 11th, 2019 at 12:57 AM ^

Thank you SO much. Big takeaway for me: Gattis knows what he's doing. If the reads are recognized better, fumbles eliminated, drops don't occur, and Patterson is healthy to throw, maybe we win by five or six touchdowns. Tons of ifs there, and what happened is what happened. But so much going forward depends on the ceiling for the Gattis offense, and you've restored the confidence there.

MGoBlue96

September 11th, 2019 at 1:10 PM ^

Ummm, I do not see how you can came to that conclusion. It pretty much says Patterson only missed a couple of obvious reads and the rest was Army gameplanning to take away both options and Gattis and the offense not having effective counters ready for it. Until he shows those counters I am not sure we can say he is the guy we thought he was coming in.

dragonchild

September 11th, 2019 at 6:53 AM ^

One thing I noticed in the "This is what happens when you run zone read against a 404 Tite" clip:  The WLB was shuffling, almost like the DE in an anti-zone read "Rock" defense.  When the DE shuffles it's because he knows he's being read, so he delays the read by not committing.  The WLB is shuffling and he's not even in the zone being read.  But he's in position to react to either plug the B gap or chase a play to the outside.  That takes a WLB with speed, but if he can pull it off then it flips the numbers game back to the defense.  The outside defenders can force any run back inside, and the RB can't get to the gap first out of a shotgun with a delayed mesh.