Picture Pages: Scraping, Bubbling
Picture Pages: you see, Rudy, sometimes you just need to break down a play that's representative of a larger trend. This series picks out a play or two per game that seem significant in the grand scheme of things, Theo, and attempts to explain why. Vanessa.
I brought this up in UFR and wanted to make it clearer so here goes. This is a first and 15 on Michigan's first drive of the day.
Michigan lines up in one of their common sets, a three-wide shotgun look. Here the tight end is lined up as an H-back. Michigan often used the h-back as a pass blocker for Forcier rollouts, but this time he's going to go with the play. Western aligns in a 4-3 look with the nickel back shaded inside of the slot receiver. Michigan will run a zone read, and Western will do a version of a scrape exchange. In brief: in a scrape, the backside defensive end will take off after the tailback instead of maintaining contain. A weakside linebacker or corner will provide QB contain, thus hopefully minimizing or eliminating the quarterback's athleticism edge over the defender he's dealing with.
Below is the handoff point. As Western did basically the whole game, the unblocked backside end takes off after the tailback. Since this is the guy Forcier is reading, he pulls the ball out. A couple points: Michigan has six blockers against six defenders here and should be content to hand the ball off. As we'll see, Brown's going to end up with a lot of room.
A few moments later we see the scraper coming in: he's the corner/LB who was lined up over Grady. He comes flying in and threatens to tackle Forcier in the backfield. The scrape exchange Michigan saw a lot last year saw the WLB head outside; this one is less vulnerable to the veer or other quick-hitting backside plays that exploit the fact that your WLB is flying around the edge. But there's an obvious cost: HOLY GOD LOOK AT THE SLOT RECEIVER.
Forcier is, in fact, looking at a spectacularly open guy on a bubble route. One of the Western safeties is coming up but he's inside of and ten yards away from a guy who's quicker than him. At best he squares up and holds the gain down. If he misses a tackle Grady is born to run.
Also note the line moving to the second level and sealing those defensive tackles. Michigan had three or four plays like this where the tailback shot up to cavernous gaps in the line of scrimmage without the ball. And this isn't a reaction to Forcier's decision to pull the ball yet; only the WLB has seen that. The frames above make it pretty clear that if Michigan had handed the ball off Schilling was going to cut this guy off.
Forcier, unfortunately, decides against the bubble and cuts directly upfield:
Molk has finished burying the playside DT and if Brown had the ball he'd be cruising, as the WLB who peeled off to Forcier was about to get his clock cleaned by Schilling. But Forcier pulled the ball and then made a poor read, so he's got one option:
Four yards.
Takeaways:
- Just because the backside DE is crashing down doesn't mean you have to pull the ball. This would have been a big gainer if Forcier handed it off.
- Scrape exchanges are not a magic pill. They pull defenders out of position and the right play call—or read—can exploit them.
- Forcier is, yes, a freshman. He made a number of mistakes against Western of this variety.
- But even so it's nice to have a guy like Forcier who can turn his mistake into positive yards. Michigan had a lot of screwups in game one but most of them still went forward. That's a huge difference from last year.
September 11th, 2009 at 3:15 PM ^
September 11th, 2009 at 3:37 PM ^
September 11th, 2009 at 3:53 PM ^
September 11th, 2009 at 4:12 PM ^
September 11th, 2009 at 5:05 PM ^
September 11th, 2009 at 7:42 PM ^
September 12th, 2009 at 12:13 AM ^
September 11th, 2009 at 4:23 PM ^
September 11th, 2009 at 3:17 PM ^
September 11th, 2009 at 3:35 PM ^
September 11th, 2009 at 3:48 PM ^
September 11th, 2009 at 3:52 PM ^
September 11th, 2009 at 3:42 PM ^
September 11th, 2009 at 4:25 PM ^
September 11th, 2009 at 3:46 PM ^
September 11th, 2009 at 3:46 PM ^
September 11th, 2009 at 3:51 PM ^
September 11th, 2009 at 4:08 PM ^
September 11th, 2009 at 4:24 PM ^
September 11th, 2009 at 6:09 PM ^
September 11th, 2009 at 4:25 PM ^
September 11th, 2009 at 4:27 PM ^
September 11th, 2009 at 4:39 PM ^
September 11th, 2009 at 10:15 PM ^
September 11th, 2009 at 11:06 PM ^
If that's not his key, then fine.That's essentially what I was saying with this:
They're going to have to come up with a different read and blocking scheme if ND scrapesTate can't just read the DE, because it's going to lead to trouble against teams with better linebackers if they know he'll keep it any time they crash and scrape. As it was, he was lucky to get four yards against a MAC team. Go check out the Smart Football link Brian put at the start of the post, it pretty much says this.
If the offense knows that the defense is shifting to this (a big if), what is the adjustment? Tell the tackle to block the defensive end, and the quarterback to read the linebacker. Often the linebacker will take himself out of the play, and with good blocking, the offense should be able to get a good run play, or a big play if the runner can cut back.FWIW somehow my ability to remember useless information that makes me great at trivia also helped me remember this post. Check out the second video, the first half of it is full of RichRod going over his spread-to-run philosophy and how they look to run any time there are only six defenders in the box. Since he counts the QB as a blocker due to the defense needing to have one of the players in the box (usually the DE, yes) account for him, leaving the five other defenders in the box to get blocked by the five O-linemen. Well, with the scrape exchange it's just the LB getting "blocked" by the QB when he goes out wide, and this means that there should still be enough linemen to have one take care of the crashing DE.
September 12th, 2009 at 12:30 AM ^
September 11th, 2009 at 4:42 PM ^
September 11th, 2009 at 4:34 PM ^
September 11th, 2009 at 4:41 PM ^
September 11th, 2009 at 4:49 PM ^
September 11th, 2009 at 4:54 PM ^
September 11th, 2009 at 6:46 PM ^
September 12th, 2009 at 8:22 AM ^
September 11th, 2009 at 5:57 PM ^
September 11th, 2009 at 6:48 PM ^
September 11th, 2009 at 8:38 PM ^
September 12th, 2009 at 1:13 AM ^
September 11th, 2009 at 6:00 PM ^
September 11th, 2009 at 6:02 PM ^
September 11th, 2009 at 8:05 PM ^
September 11th, 2009 at 6:33 PM ^
September 11th, 2009 at 8:09 PM ^
September 12th, 2009 at 1:19 AM ^
September 12th, 2009 at 8:30 AM ^
September 12th, 2009 at 11:41 AM ^
Comments