no wonder we hired Hunter Lochmann
That is 2,728 pounds—1.24 metric tons—in the box for those weighing at home.
On 1st and 10. MANBRAAAHHHLLL!!!
Before the Minnesota game I tweeted that I'd be perfectly content if Borges debuted a completely new package and used it to beat up on the Gophers at home a la 2011. So here I am, being content.
The unbalanced stuff I'm sure Brian will picture page and Space Coyote and Burgeoning Wolverine Star will peel it apart as well; since they know more about that stuff I'll leave it to them. What I would like to do is look at the heavy formations in the macro: how Big did Michigan actually go, how effective it was on a yards-per-play basis, and whether it matches the personnel.
By "big" I mean fewer receivers in the formation. The lower that number, the more backs and TEs, and thus the "heavier" the formation. How big?
Average Receivers in Formation:
|2013 games 1-4||2.30||2.29|
|2013 Minnesota||1.83 (!)||1.79 (!)|
That is big—like we should all have pronounced brow ridges and live in caves and the equipment sponsor is Mousterian big. I counted Funchess as a WR when he was in a 2-point stance; if you file him as a half tight end (you shouldn't) it gets even heavier. A lot of the three-wide was on the time-sensitive last drive of the 1st half—that you should count.
Did it work? Did it work better than the stuff Michigan has been doing until now? Did they always run to the side they unbalanced? We see after the jump.
10/5/2013 – Michigan 42, Minnesota 13 – 5-0, 1-0 Big Ten
Jon Falk has a compatriot at Minnesota. He's probably had a dozen over his 40 years as Michigan's equipment manager. Some guy who comes in with the latest Gopher coaching staff, wonders what it's like to hold the jug in his meaty palm, and maybe once gets to shepherd it for a year. Since Falk arrived at Michigan a fresh-faced young thing four years into Bo's career, his opposite number has had this experience three times.
In proof lingo, this means that beating Minnesota—beating up on Minnesota, usually—is a necessary but not sufficient property of Michigan teams that want to do anything with their seasons. Sometimes you can retain the Jug despite not being very good; sometimes you can retain the jug despite being headed for 3-9 because Nick Sheridan has an out-of-body experience. When you're headed for 3-9 you get a little misty about the Jug coming out. When you're not the worst team in Ann Arbor since the 1930s it's a checkbox to fill out.
Michigan did so in perfunctory style, grinding out a second half in which they went from vaguely threatened to bored. Since this came on the heels of narrow escapes against teams that lost 43-3 to Ohio on Saturday and 41-12 to Buffalo last week, it's progress. How much is unknown.
This game settled into a grim fugue state almost from the drop, as Michigan manballed its way into the endzone on a Statement Drive to start the game. Unfortunately, that Statement was "by putting Taylor Lewan next to Michael Schofield we can bull our way down the field against Minnesota." That statement is unlikely to apply to many teams on the schedule. But, hey, progress.
Then Minnesota donned turbans and embarked on the Ishtar Drive. An epic production galaxy-spanning in its dullness that arrived at its destination two hours too late and failed to have the desired impact, it ate up the rest of the quarter. Michigan left it without having attempted a pass.
This was a little dull.
It was the kind of dull that had Space Coyote, the Michigan's blogosphere's resident instant analysis savant, pleading with the masses that the intricacies of a well-blocked power play were just as appealing as, say, watching 175-pound Venric Mark activate his truck stick on an Ohio State safety. I can't imagine there's another Michigan fan in the world more receptive to that argument than yours truly and even I wasn't buying that as the secondary effect of all that manball kicked in: punt, commercial, play, end of quarter, commercial, play play, punt, commercial. Touchdown, commercial, kickoff, commercial—the NFL special. As the teams' attempt to blow through this game in record time was thwarted by the networks, being in Michigan Stadium became the worst concert of all time interrupted by bouts of football-related activity.
It was the kind of thing that made you consider what the purpose of your fandom was. Am I only here to see Michigan end a game with a larger number on the scoreboard than Opponent? Is there any valid goal outside of this? Am I a bad fan for wishing something interesting would happen? Do the people on twitter who scorn you for having feelings other than Go Team have a point? What is the point of any of this, and why can't they make the wifi work?
At halftime, the guys in front of me discussed whether they would bolt for Frazer's, and two did. I'm usually a guy who thinks leaving an athletic event before it's decided is a mortal sin, but I kind of envied the guy in the home-made muscle shirt screwing off to a place where he could get a beer and not hear "Build Me Up, Buttercup." At any other time, I would have thought this man's attendance at Michigan Stadium was a necessary property of a fan that he had just shown was not sufficient by leaving a touchdown game at halftime like he was a sorority girl about to blow a .341. On Saturday, I was with him in spirit.
This is a fearful development. I don't want to think like that. I want to be forever ten years old, excited by everything. On Saturday I had a long look down the elevator shaft.
It'll pass like the moment above did. Someone will do something interesting, and there will be something at stake other than a piece of crockery that just means you're not horrible, and sometimes not even that. I had a bad day, I was pissed at Dave Brandon when I discovered I was thirsty but knew I couldn't do anything about it without missing a large chunk of the game I was there to see even if it was narcoleptic, I was emo after the last few weeks of expectation-depressing terror. It'll pass, and the doors will close on the moment where I reached out and felt the slight outlines of a limit to my fandom.
Michigan won by a lot, eventually.
Completely one-sided highlights:
Brady Hoke Epic Double Point Of The Week. Has to be Michigan's new favorite worst nightmare at wide receiver: Devin Funchess. Relieved of many blocking duties and deployed on the outside, Funchess displayed fantastic hands on a couple of catches outside of his body, ran routes that got him tons of separation, and went right by a Minnesota cornerback(!) on a straight-up fly route(!) to prove himself Michigan's best deep threat(?). By the end of the game he had newspaper types plumbing the statistical depths for completely invalid comparisons to Jim Mandich, who was a tight end, which Devin Funchess is not.
Honorable mention: No Turnovers, which may be Devin Gardner's temporary name until such point as he turns it over. Schofield and Lewan were mashing as tackle brothers. Blake Countess did have a pick six, albeit one of no importance. James Ross and Desmond Morgan had lots of tackles, usually at the LOS when not facing spread formations.
Epic Double Point Standings.
1.0: Devin Gardner (ND), Jeremy Gallon (ND), Desmond Morgan(UConn), Devin Funchess(Minnesota)
0.5: Cam Gordon (CMU), Brennen Beyer (CMU)
I guess? [Upchurch]
Brady Hoke Epic Double Fist-Pump Of The Week. Wow. Are we at a loss here? We might be at a loss here. Countess's interception was after the game was decided, as was the long Funchess fly route thing. Michigan's longest run went for not many yards. I guess we're going with Fitzgerald Toussaint scoring an easy ten-yard touchdown, as it hinted that Michigan may be able to run the ball forward? Yeah, okay.
Honorable mention: Funchess reception, pick one. Countess pick. Black FF.
Epic Double Fist-Pumps Past.
8/31/2013: Dymonte Thomas introduces himself by blocking a punt.
9/7/2013: Jeremy Gallon spins through four Notre Dame defenders for a 61-yard touchdown.
9/14/2013: Michigan does not lose to Akron. Thanks, Thomas Gordon.
9/21/2013: Desmond Morgan's leaping one-handed spear INT saves Michigan's bacon against UConn.
10/5/2013: Fitzgerald Toussaint runs for ten yards, gets touchdown rather easily.
[After THE JUMP: actual game analysis instead of pathetic emo self-pity mooning!]
In re: "who are you optioning?"
This is a weird formation, right? Lewan is eligible receiver, Kwiatkowski is not?
It's a little weird. Neither Lewan or Kwiatkowski are eligible in that formation. Lewan wears an ineligible number; Kwiatkowski is covered up by a receiver outside of him. I call these formations "unbalanced" when I talk about them.
They're not that weird, though. Teams do it to screw with the defense's alignment, test various things, etc. If the play ends up being a pass you've declared that you've only got four receivers, but since the tight end can pass block you're still playing 11 on 11.
Occasionally you'll see Michigan line up with two receivers on the line of scrimmage to the same side. This drives me nuts since the slot guy may as well not exist. This was more common under Rodriguez but IIRC Borges did do it a couple times last year. These are always runs, and usually short ones if the defense notices the alignment, which it seems like they always do.
Why do coaches do this? They're trying to mess up a defense's alignment keys and get easy yards. It's the same principle at work whenever a wide receiver lines up at fullback and motions out to the flank, or when a running back ends up lined up way on the outside.
Join our flaming crater!
What effect do you think the 'Bama game will have on recruiting? Much to my surprise many fans think neutral or positive.
I don't think it will have much, if any. Michigan's down to a couple of scholarships in the next class. By the time the 2014 kids start committing in numbers, Michigan will have played 12-13 additional games and the Alabama debacle will be a lot less relevant than it seems right now.
If it's going to hurt, it'll be with Derrick Green and LaQuon Treadwell. I don't think anyone was optimistic about Green after Auburn popped up even before Saturday; Treadwell is more of a mystery. We'll see.
In general, short-term results are not the be all and end-all in recruiting. See Charlie Weis, Ron Zook, etc. You either have it until such point as your job is under threat or you're at Kansas, or you don't.
An update on the Stubhub thing.
Just a quick heads up that UM still appears to have their relationship in place with StubHub. I received an email on Friday from the Michigan Ticket Office proclaiming, “Don't forget to use our online Marketplace (in its second successful year in service) to easily resell your tickets electronically.” I know you mused about whether this relationship was still in place after StubHub referred to UM as a former partner, so I wanted to pass along.
False alarm. Still amazed at that MBA who managed to make counterfeit tickets incredibly easy to manufacture unless you were selling through Stubhub. Probably laughing moooooohahahahaha right now in a lair somewhere.
Inversion. Also, this section sponsored by Slanty the Gecko, inexplicably the first hit in Google Images for "line slant football," or at least it was a year ago.
Steve Sharik, a former high school who you may remember posting some great diaries a couple years back, sent me an email about what happened to the defense; I responded with a question, and he answered. So let's put me in a yellow box:
It looks like Michigan is slanting the DL a lot to get their guys in gaps between the massive OL and set up an obvious cutback lane in which the LBs are supposed to be 2v1, but rarely do both of them get there. It's so consistent that it almost seems like I have to be wrong. I want the LBs to absolutely tear ass for the gap behind the slanting DT (usually they leave the DE to contain the backside). Instead they check up for cutbacks constantly that seem like the DL's job. Am I crazy?
Slanting does two things to zone blocking:
- If I'm an OL zone blocking to the right, and the guy on my outside who I'm supposed to block goes left, there is a natural tendency to go after my guy.
- More importantly, slanting the DL gets penetration, which wreaks havoc on zone blocking.
Recall how effectively OSU slanted against us in 2007 (yes, that screen shot).
the most infamous
What would continually happen was the ball would show in a hole a LB was supposed to fill, which was done fine, but the hole was created so well that there essentially are two gaps where there was once one: there is space on both sides of the lead blocker, so the filling LB has to pick one, meaning the extra LB/S/C has to fill the other one. Consistently this second, unblocked defender was late and too far away, creating a seam in the run defense.
[ED: This came up last year too. I complained about Brandin Hawthorne not getting past a blocker against EMU. Michigan has been short on free hitters.]
BONUS: we also had a discussion on that seam route Alabama hit early and Floyd tackled immediately on. I am still in a yellow box.
Sharik: Even the normally reliable Kovacs was bad. Demens was in the wrong gap a few times, Morgan doesn't have a great feel for when to attack now or where to fit, and Kovacs and JT Floyd were very tentative. In other words, our extra run defender (when the QB is turning around and handing it off, they're playing 10 v. 11, so we should have an extra, unblocked defender vs. the run) was late to the party or in the wrong gap, creating the huge seams you saw. Even vs. the pass, on their conversion on a 3rd and long, Kovacs went to wide and too aggressively to re-route a seam, and ended up being outside the numbers and too close to the LOS, thereby giving up the seam right behind him.
I caught that Kovacs thing, but thought the problem there was a crappy chuck on the guy. If he really jams him there the blitz should have time to get there or Floyd has time to get over. yes/no?
Against the pass, the defender responsible for the seam must stay on that seam--reroute the receiver off the seam. You do this with both your horizontal and vertical position. When Kovacs was so aggressive he took himself outside of the seam and stayed too close to the LOS, creating an open window for the seam. The technique is to not gear up to hit the guy, but to shock, catch, and run. If a guy is running in the seam, it almost looks like man coverage if the defender is playing his technique correctly. (Actually it does look like man, the way to tell man or zone is by what other defenders are doing.) Also, Floyd can't come over b/c he has deep 1/3 and the outside receiver was running a go route.
If Kovacs stays in the seam window, he doesn't have to take his eyes off the QB and he can eliminate the possibility of a throw without touching the WR. And if their QB holds the ball b/c the seam isn't open, the blitz gets home (or at least has a better chance).
Actually, I think the designed route was an inside skinny; designed to be behind the Mike and in front of the Free. The WRs job is to clear the seam defender, then post to the middle at about 10-15. (Different coaches teach different depths, and different defenses command slightly different depths, as well as the drop of the QB--3, 5, 7 step.)
I am now out of a yellow box. When Steve mentioned that the slot defender on the seam often looks like man coverage, it made me think back to Courtney Avery consistently carrying receivers deep on similar routes, and wondering if that was what the intent was. We eventually figured it was—this was a BWS debate—and then last year Mattison flat out said so after Avery carried a seam route deep and Iowa got a 44-yard gain out of a simple crossing route; we asked what happened there and he said Countess got out of position.
Thanks to Steve for the input. Long way to go.