Best and Worst: MSU

Submitted by bronxblue on

If you are coming here looking for rants, I might have a couple but I’m remarkably, I don’t know, accepting of yesterday’s insanity.  Probably one of those grief stages.  So fair warning (unless you are a referee in this game – for you, I’ll make an exception).

Best:  A Broken Heart Mended

I was 13 when Kordell Stewart ripped UM’s heart out.  For some reason I thought I was younger, but maybe that was just because I was a late convert to UM football in that respect.  I cheered on UM because they crossed the family TV screen most Saturdays, but I was a Pistons (and, honestly, an NBA) fan at my core.  I went to a couple games a year, voraciously read box scores each morning during the season, and consumed as much content as possible about the NBA.  If I had any football fandom in my body, it was for Barry Sanders, tragically dragging the Lions along with his brilliance under a baggy dome. 

College football was just a thing that was on, the white noise machine of fall Saturdays.  I cheered UM because of their ubiquity and prominence locally.  I cheered because of the uniforms, the pageantry during the Tournament of Roses before the Rose Bowl, and the fact that they always seemed to win.  My dad had gone to UM but never wore that connection on his sleeve, and I was still a bit too young to care about academics and job prospects, the objective metrics that led me to attend UM.  Hell, I’m not even sure when we got ESPN on cable (and chances are had I stumbled upon it, it wouldn’t have been football).  No, my relationship with UM football was one of convenience and detachment, where I would cheer because UM was usually winning or losing in conventional manners, and I knew enough about the sport to accept that at face value.

Until that play.  I still remember sitting with my dad on the coach in the living room, just watching it unfold.  My Dad assumed the game was over; it was 70+ yards to the lip of the endzone, and while Stewart had a cannon this was an era before the internet, before on-the-field Statz and talking heads, before constant replays and trips to the video archives between timeouts, so there wasn’t much in the way of foreshadowing.  You knew about the Flutie Miracle, The Miracle in the Meadowlands, and The Band on the Field between Cal and Stanford, but it always felt distant and unimaginable, moments of affliction that deeply wound the participants but are mostly macabre blips in everyone else’s memory.  Those plays happened to them, not us.

So it felt almost like a fait accompli that UM would win the game after Colorado’s last-gasp attempt, with (I’m guessing) most in the stands wondering if Stewart would even be able to get the ball to the endzone.  It seemed impossible to contemplate anything more.  And then the ball sailed from his arm like a rocket, and you could tell even the camera man was caught a bit off guard.  He just kept panning, panning, panning into the endzone, and then a bunch of limbs reached out like a preacher’s chorus praising the gods of football, and the ball caromed into the waiting arms of Michael F’ing Westbrook, and then it was over. 

And at that moment, even though it took a couple of more years for me to fully realize it, I became a UM football fan.  You can’t have your heart broken like that, to see your guys lose a game because of celestial forces and cold physics, and not have that feeling wiggle its way into your rib cage and never leave.  From that day forward, I always made sure to check the box scores every Sunday morning, to track the AP polls, to know how the Wolverines did.  I started to get annoyed with the 8-4 seasons, the seemingly annual underperformance, and then the ascendant ‘97 season hooked me forever.  I was in the stands when Notre Dame nearly drove the field with no timeouts in 1999, unable to catch my breath.  I watched them lose to Purdue and Northwestern in heartbreaking fashion in 2000, and then 2001 with the damn Clockgate against MSU.  And when I graduated and moved away, I still followed the team, yelping uncontrollably after Braylonfest, losing my mind after the New Math game, and giggling myself silly when ND left Gallon all alone in 2011.  The 2006 game against OSU, Horror, everything that transpired under RR and Hoke (including the heartbreaking 2009 loss to MSU), and now this game all fell on the other side of the ledger. 

I know people want to frame this as a curse, some lingering bad juju from the clusterfuck hanging over the program since Bo died, but I don’t think that’s it.  Every game, both in the micro level and in the macro sense, creates fans and keeps them there.  And this element of fandom is a zero-sum game; for every breathtaking win there must be a heartbreaking loss, only the names and faces change.  They come about organically, and sometimes the most fertile soil is littered with shitty outcomes.  But you can’t root for something and be surprised when they don’t come out on top all the time, and while I’m going to try to frame this as a sign of good things to come, of a team that is growing into something special and a future that is brighter today than it was 2 months ago, that’s not going to take the sting away, and it shouldn’t.  But you don’t win all those games without a couple of tough losses, and sometimes you’ve got to wade through some foul stuff in order to come out better on the other side.



Worst:  Leave Blake Alone!

Objectively, that last play was terrible.  It was a series of small disasters that snowballed into an improbably loss.  It was a low-ish snap that O’Neill couldn’t get ahold of, resulting in the ball being bobbled.  UM, knowing his tendency to run to the right before booting the ball, shifted the shield in that direction but left nobody on the back side to handle the 4 MSU rushers from that direction.  Had there even been one blocker extra on that side, I wonder if MSU is able to get to Blake quite that quickly.  Once the ball was snapped, the offensive line started running down the field to cover the punt even though it didn’t appear MSU had anyone returning it, leaving even fewer players back to hold up the rush.  Then, in his attempt to at least get the ball off, O’Neill kicked the ball right into the arms of the MSU defender, who then stumbled his way to the endzone.  As others have noted, O’Neill probably should have fallen on the ball and just given up the field position, since MSU still would have had time for maybe 1 or 2 more plays with about half the field to go.  But in the heat of the moment, it’s hard to fault a kid for trying to make a play.

Ultimately, it was the play that cost UM the win, but it wasn’t because of any single player.  It was just a bit if bad luck at the worst possible time.  And while the vast majority of the fanbase responded positively toward O’Neill, it must be stated again that if you think calling for a kid to be deported or kicked off the team, or sending him Twitter-muscle shade, or anything else that prompted Jim Hackett to send a formal letter to the fans and students to lay off of O’Neill, well…

Best:  Rationalize away Merrill

ST3’s always-excellent column touched on some of these points, but this was a game far closer than the yardage would lead you to believe.  You skim the narrative being put forth by the MSU faithful today, the argument for why MSU won wasn’t because they got the flukiest f*ing play in recent memory but because UM got incredibly lucky because the MSU offense was unstoppable and MSU’s defense was demolishing UM’s attack. 

Now, MSU’s passing game was pretty solid (328 yards, 8.4 ypa, 1:0 TD:INT) in aggregate, but Cook still completed less than 50% of his passes, and 74 of those yards came on a busted play to FB Trevon Pendleton.  Yes that play happened, but it was also an extreme outlier that goosed the numbers a bit.  Throw that out and you have far more pedestrian numbers (254 yards, 6.9 ypa), furthered buoyed by some questionable penalties that kept MSU drives going (the 12 men on the field penalty was correct; the extremely questionable Lewis holding call where the receiver fell into the official that wiped out a pick, the targeting atrocity on Bolden, and the personal foul on Henry for tackling a player before the whistle was blown all felt like missteps) and some great catches by Burbridge.  Some fans will argue that Cook was let down by his other receivers (most notably Kings) due to some drops, but that’s the equivalent of arguing “the computer is cheating” whenever your game of Madden mirrors reality a bit and mediocre WRs drop balls.  To Cook’s credit, though, he made some great throws in tight windows, and while I still wouldn’t trust him to run my NFL franchise, he played well enough against UM.

By comparison, I thought Rudock had a fine game.  He played the game like a QB whose team had the lead for virtually the entire game and knew that the worst thing he could do was give MSU a short field with a bad throw.  He completed 60% of his throws for around 6.7 ypa and kept the sheet clean, while lofting a couple of nice balls to both Darboh and Chesson to come back to for completions.  In fact, 7 of his 15 completions were for 1st downs (to Cook’s credit, he had 13 for first downs as well, but he also threw the ball 14 more times than Rudock).  He continues to struggle throwing the ball deep, jarring in this game due to MSU’s poor corner play, though at some point you have to wonder if there’s a bit Luis Mendoza in his main deep threat, Chesson, who has amazing speed but just has never seemed able to harness it properly as a receiver (obviously he’s had a bit more success on returns and designed runs).  But as Brian and others have said, if this is the Rudock UM gets this season, they should win every game except OSU, and until the last 10 seconds, he did more than enough to get this team the win.

MSU never established the running game (yes they had injuries to the offensive line and Jack Allen was out, but MSU has struggled all year on the ground), with the top 3 backs averaged about 2.7 ypc, which was less than the 3.5 ypc picked up by Smith and Houma, the two leading rushers for UM.  For the game, UM had more and better rushes than MSU, and that includes knocking off 15 yards for O’Neill’s final punt play.  Michigan scored in all 5 of their red zone trips while MSU only scored on 2 of them, missing two FGs and turning the ball over on downs.  In fact, MSU failed to convert 4th downs 4 times in this game, only one of which would be considered required (the seemingly last drive on 4th and 19).  Hell, dad they lost this game, people would have questioned Dantonio’s decision to call a pretty obvious fake punt that was stopped and UM turned into a TD.

As for defensive dominance by MSU, that doesn’t ring all that true either.  MSU scored on 3 of their 12 drives (I’m excluding the end of the half and the last blocked return), while UM scored on 5 of their 13.  UM had 3 sacks for 29 yards, matching MSU, and while UM had two less TFLs, theirs resulted in more lost yardage than those by MSU (7 to 9 TFLs, but 37 yards compared to MSU’s 23).  MSU had one more QB hit, but UM had 10 (!!) pass breakups, including 6 by Lewis.  The teams had basically the same 3rd-down conversion rate (MSU was 3/12, UM 4/15), and UM converted more in the 2nd half (3/10) than MSU (1/6). 

The reason MSU had so many more yards compared to UM had largely to do with special teams decidedly going in UM’s favor (along with MSU’s poor conversion rate), with O’Neill averaging 44.6 yards on 7 punts, highlighted by the field-shifting 80 yarder in the first quarter, and pining MSU inside their own 20 two more times.  By comparison, MSU averaged 37 yards on 5 punts, including one touchback.  And as for returning said kicks, UM pantsed MSU mercilessly, with Peppers and Chesson picking up 154 yards on 7 returns while MSU snagged 54 yards on 4 returns.  It all added up to UM starting on it’s own 38 while MSU had an average starting drive on their own 22 yard line.  So yeah, that’s where your 150-ish difference in yardage mostly came from; UM didn’t need to go as far to score, so they didn’t.

MSU played well enough to win; UM suffered by not converting a couple more of those redzone trips into touchdowns, and that ultimately cost them at the end.  But don’t for a second believe that MSU “deserved” to win this game because the people making the arguments fear basic math.  It was a close game that went against UM due to the most freakish of plays possible, nothing more and nothing less.


Meh:  Offensive Line Expectations Ticked Down

Yes this is MSU, and yes they again appeared to have a jump on a number of snaps (the 3 goal line runs capped off by Houma’s TD in the 3rd quarter all featured MSU players jumping the snap successfully), but I thought the offensive line did struggle at the point of attack, especially in the running game.  MSU’s defensive line is the obvious strength of their unit, and it played well, consistently getting pressure and clogging up the running lanes.  Thomas, who I still think is more a uniform stuffer than an elite talent, was second on the team with 7 tackles and held the edge well when UM (illogically) attacked it.  I’m sure there were bad cuts by Smith that led to some stops, but like in the Utah game, you can see the deficiencies that submarine the rushing attack against elite defensive lines.  Luckily, there aren’t a huge number of those lines left on the schedule, with OSU seemingly being the only sure bet to reproduce this level of disruption.

As for passing downs, it’s harder to tell because Rudock seemed willing to take a couple of sacks instead of throwing the ball downfield.  Calhoun was consistently getting pressure and MSU got a couple free runs from their LBs, but it wasn’t the demolition we’ve seen in years past.  Rudock appears to have all of his ribs and soul intact, which is a marked improvement for UM signal callers in this rivalry.  And as noted above, the passing game was reasonably efficient even though the screen game, which might have loosened up the pressure a bit, was lacking.  Overall, it felt like a decent performance by an average line but perhaps not the step forward fans had hoped for coming into the game.  At the same time, it wasn’t a huge setback, it was just a reality check that this year’s rushing attack won’t approach the best units under Harbaugh’s various regimes.


Best:  Jourdan MF Lewis

Nothing was more entertaining than seeing MSU fans complain about Lewis “mugging” Burbridge throughout the game on his way to 6 pass breakups and a pretty decent effort against MSU’s sole real passing threat.  Lewis, of course, is just playing the same type of physical, grabby defense MSU introduced to the conference some years back, just perhaps at a better level than either Waynes or Dennard every did.  Being a shutdown corner doesn’t necessarily mean that the guy you cover never catches a ball, especially when the opponent doggedly targets him because they literally had no other competent options (Burbridge was targeted 19 times in this game). 

Instead, it means making it as difficult as possible for the offense to consistently complete passes to your side and limiting the damage when they do, and Lewis did that in spades.  Even though Burbirdge finished with 9 catches for 132 yards, he only had 3 catches after halftime, and at least two of them were just great plays by him despite great coverage by Lewis.  Lewis was also the victim of a pick play in the 2nd quarter (I believe) that Brandstatter called out immediately when it happened.  Overall, he played like the All-American he’s being touted as and performed well in a tough matchup against a good receiver.


Best:  Defensive Line Expectations Ticked Up

I know MSU had some injuries on the line, but I thought the defensive  line, in particular Wormley and Henry, were great in this game.  The front 4 recorded 3 sacks, held MSU’s rushing attack in check, got consistent pressure on Cook even when the Spartans left extra blockers in, and generally played like the dominating unit they’ve seen this whole year.  They were also active in the passing lanes, with both Wormley and Henry recording pass breakups as well.  I await Glasgow’s score in the UFR, but he seemed to hold up decently against a solid MSU interior, and both Jenkins-Stone and Hurst had some nice TFLs in there as well. 

Will OSU give them problems?  Probably, but even then I’m not sure we’re going to see Elliott plowing past them like he has against most other units.  This remains a terrifyingly-good unit, and one that you hope will largely return next year to go along with the return of Mone and (fingers crossed) some high-end defensive tackle recruits.  I’m certainly intrigued about next year under this coaching staff.

Best:  Peppers Army Knife

Peppers was deployed everywhere possible in this game, and he excelled at all of them.  He flipped the field with some great punt returns, had a great 28-yard pass/run play to set up a TD, and did well the couple of times MSU challenged him.  He’s obviously still not a finished product, but the strides he’s made in these six games definitely give some credence to the “Woodson” comparisons that seemed a little far-fetched at the start of the year.


Worstest:  These F*ing Guys

By the time they went to the review booth for the third time on UM’s goal line run, you could hear the announcers lose their patience (and for the record, I could understand the argument that Houma’s momentum was stopped, but he played to the whistle, which allowed him to score).  And even at that point, the refs had a handful more dubious calls to make (Henry’s drive-extending PF, Jake Butt’s probably-a-catch that would have kept a late UM drive alive, Shelton’s “two guys are saying he’s out, but let’s trust the idiots in the booth” catch along the sidelines).  The Bolden ejection was terrible in real-time and looked even worse on the numerous replays, as the refs initially tried to frame it as Morgan head-hunting when in fact Cook baseball slid in, then compounded the error by ignoring Conklin clearly throwing Bolden down on top of him.  It was a terrible call, an inexcusable call, and yet not all that surprising given how the season has gone in terms of referee miscues.

I understand that being a referee is a thankless job; jagoffs like me freak out every time you screw up and don’t recognize when you get it right.  But at the same time, you can’t make a series of illogical calls throughout a game and just chalk it up to “human error” and whatnot when you ALSO try to correct every possible call using video replay.  In a game like this between two evenly-matched teams, one team losing its leading tackler due to a dubious call while the other received a fifth of their first downs by penalties is insane, especially when neither team is particularly known for being penalty-prone.  And the thing is, this isn’t a Kings-Lakers situation where there might have been actual bias involved; it was just a series of terrible calls without reprieve.  And as grown-ass adults who are tasked with calling a game as well as possible, this officiating crew failed, and it failed hard.  It didn’t cost UM the game; that’s a fool’s argument to make, especially given how the final play turned out.  But it doesn’t make the clown show we all watched any more palpable.


Best:  A Week Off

On the one hand it sucks that UM is going to have to wait 2 weeks to wash the taste of this loss from their mouths, but on the other hand it should mitigate any hangover that could linger against the Gophers.  UM played like the top-15 team they have shown thus far, and while they certainly shouldn’t have been in any national title talk, they looked a hell of a lot closer to MSU than they had coming into the year.  That’s progress I’ll take.

I’m not sure about next week.  I might do a mid-season recap, take a break, or something in between.  But in a blink of an eye, there are only 5 more games left on the schedule, with the bowl game being the 6th.  And I’m going to try to enjoy the last couple weeks as best as possible.

Comments

Michigan4Life

October 18th, 2015 at 11:28 PM ^

is not true. Connor Cook was fantastic in this game and was dropping dimes. His completion percentage won't reflect it but NFL scouts have him at 75% accuracy rate (talked to a couple who were scouting the game) which is phenomenal considering he's been throwing downfield.  His WRs dropped easy passes that should've been caught which skews his percentage.

Jourdan Lewis had an okay game. He won some battles, but ultimately Burbridge won the matchup. Burbridge gave him ton of trouble and Lewis never once turned his head around to find the ball. That's a weakness that will be harped on by the NFL scouts.

I'm not sure why you think Michigan DL had a good game rushing the passer. Only time they had pressure from rushing 3/4 came from final drive when Henry abused the 3rd string RT. They had pressure via blitz from LB or DB but otherwise, DL didn't do much in pass rush. However, they have been great against the run.

bronxblue

October 18th, 2015 at 11:34 PM ^

I'll trust your unnamed scouts who loved Cook's game; to me, he's a sub 60% completion guy who gets some big throws but also hasn't been incredibly sharp in any game save Rutgers.  He had one long completion on a broken play and a couple of nice throws to Burbridge, but  He does throw the ball downfield, but I continue to see a stronger-armed Kirk Cousins, which is fine for college but not someone who is a first-round draft pick.  But again, you are entitled to your opinion.

Burbridge had a good game, but Lewis also played well and made him work for each of those catches.  Again, Burbirdge was targetted 19 times in this game and according to PFF only caught 7 against Lewis for about 100 yards, many of those earlier in the game.  Maybe I was slightly effusive about Lewis, but he played very well without much additional support in the secondary.  Scouts are going to harp on his size more than anything else; he played the ball well and had a good number of breakups.  

The defensive line held MSU's rushing in check, and were instrumental in getting pressure on Cook along with additional blitzing.  Yes that last drive featured both of Henry's sacks, but I also saw MSU get the ball out quickly, and I think part of the reason they didn't threaten down the field that much was because Cook was under duress moreso than he was used to.  Also, because they could get some consistent pressure, if not sacks, they were able to leave more guys in the middle of the field, which helped slow down MSU's passing game.  And again, this was supposed to be one of the best offensive lines in the conference, and UM held their own.  I'll take that.

 

alum96

October 19th, 2015 at 12:15 AM ^

I dont agree with all of MI4Life's comments but I agree the DL pash rush (to me) graded lower than you have it.  I as well will be curious how Brian UFrs them.  I felt like they did not get as much pressure as MSU even if the stats bear out it was relatively close.  Maybe because Jake holds the ball longer then Cook.  I felt most of our pressure came out of blitz while MSU was able to get by our OL without selling out.

MSU I assume also had more plays so when team A and team B get similar sacks and TFL but one team runs 15% more plays its not as equal on a % basis ie. what % of plays did the DL get pressure.  (edit - I just counted, MSU had 72 plays to UMs 61 so UM D had 11 more plays to rack up statistics)

Last, we threw far less than they did so they had far fewer chances for sacks etc.  They threw 39x, we threw 25.  So if they get 3 sacks and 3 TFL on 25 attempts and we got 3 each on 39 - one teams DL played far better.

You also stated this was one of the best OL in the conf; well not this version.  Take Molk off UM 2011 and you have a diff line.  That is Jack Allen.  Conklin maybe was 70-90%, who knows.  Kielier was hurt, looked hurt last week, and got hurt in 1st series again.  As you stated Henry teed off on a backup not the guy who stymied him (and others) all day.  That was a line with 1 of best 2 players out, the other hurt to some degree and the other tackle seemingly 60-75%.    If MSU would have had their 5 guys healthy on OL it would have made me really worried based on what I saw yest with a patchwork line.

I just didnt "feel" the pressure from the DL and I dont buy the Cook got the ball out quick all game and thats the main reason.  There were downfield throws to Burbridge and Kings (which he thankfully dropped mostly) so you cannot concurrently be getting rid of the ball immediately yet targeting Lewis 20+ yds down the field often. 

We sorely lack a Calhoun type. 3.5 TFL/2 sacks among constant activiy and pressure that doesnt show on stat line.  Henry had the same line but 70% of it came on 1 drive. 'Crooting misses at DE have hurt.  I felt like McDowell and Calhoun and Thomas did much more damage even in non TFL or sack dept but just changing the line of scrimmage routinely than we did but we dont have a MSU UFr to check.

And I thought Durkin was conservative - I felt like almost every blitz Cook made an error or misthrow.  Didnt need to blitz 7 guys, but 1 additional more often would have helped Lewis.  A fraction of a second is all it takes and you defeat good QBs with pressure.  Lowly rutgers did it for 3 quarters.  The 1 quarter they went away from it, MSU scored 14.  And we have better dbs then rutgers.  So I dont get the strategy of bend dont break.  You try to break Cook.

Agree on rush D - it was excellent. 

 

Pinky

October 19th, 2015 at 2:25 AM ^

What a horseshit analysis.  Once again, you go out of way to diminish UM's accomplishments and talk up MSU while construing the stats in a way that fits your narrative (and ignoring other stats in favor of what you "feel").  What a surprise.  Let's take a look at this gem:

"That was a line with 1 of best 2 players out, the other hurt to some degree and the other tackle seemingly 60-75%.    If MSU would have had their 5 guys healthy on OL it would have made me really worried based on what I saw yest with a patchwork line."

To what degree was Conklin hurt?  Did you see any noticeable difference in his play, because I sure didn't.  Do you even know what his injury was?  And from what part of your ass are you pulling that 60-75% number?  Kieler looked absolutely fine save literally one play.  And why didn't you mention our D line injuries?  And why did you use discrepancy in passing attempts in your discussion of TFLs? And why do Henry's stats count less because they came on one drive?

I'm too tired to get into the rest of how bad your post is, but God I wish you would just shut the hell up sometimes.

TheGhostofFerbert

October 19th, 2015 at 1:56 AM ^

1. "Maybe because Jake holds the ball longer then Cook."

Three paragraphs later...

  "I dont buy the Cook got the ball out quick all game and thats the main      reason."

2. "Conklin maybe was 70-90%, who knows."

Two sentences later...

"the other hurt to some degree"

 

I mean come on man.

bronxblue

October 19th, 2015 at 10:00 AM ^

I saw the defensive line get more push than I expected, and it did seem at times that Durkin wasn't willing to sell out.  Yes, UM lacks a dominant pass rusher like MSU's and I expect that to be fixed, but I don't completely buy the injury arguments on the line.  Conklin was in the game after missing last week, and at this point nobody is 100%.  Allen being out was a big loss, but they've had injuries all year.  Kieler played a decent amount of the game unless I missed something, even though he went out with a hand injury at some point.  I think the difference is Cook was quicker to get rid of the ball/throw it.  He also picked up a couple of yards on scrambles while Rudock would get tackled for a short loss, it seemed, which is how you get a lot of the TFL difference from a numbers perspective. I mean, Calhoun had a sack for 1 yard, which I remember being a tick and run that got tripped up at the line after Rudock held the ball a bit. Calhoun played very well in this game, but I'm surprised UM didn't try to rush at him more, as that is clearly his weaker element.  McDowell played very well in addition; I continue to see Thomas as an athlete more than a great football player, but that's more of a feelingsball thing.  The percentage opportunities on defense are there, but UM had fewer TFLs but more yards, which mitigates that argument somewhat.  And as a counter to Henry getting his stats at the end, it was also the drive that shut down MSU on their final chance, and seemed like the first time Durkin really unleashed the rush in a bit. I think this game was all in eye of the beholder. The line was not as good against the pass as in the past, but Cook never seemed as comfortable and did have to move around a bit, and his downfield targets were closer to 10 yards than 20. And once Bolden went out, it seemed like the focus returned a bit to holding down running lanes because I'm guessing the staff wasn't as confident in Ross and Gedeon without a backup. I think the UFR will be very interesting.

Michigan4Life

October 19th, 2015 at 12:06 AM ^

Cook had an accuracy rate of 75% against Michigan. He was accurate and was viticmized by drops by Kings, Burbridge, etc. Scouts count passes that are dropped yet accurate as a "completion rate" to their accuracy rating.

FWIW, Connor Cook will not fall past top 15. I've heard almost every single NFL scouts have him at top 10, possibly #1 overall. He's a lot better than Kirk Cousins who would never have make the throws that Cook can make. 

Anytime you give up 100 yards, you lost the battle. Yes, Lewis had his moments, but he was often grabby and didn't turn his head around to find the ball which allows Burbridge to make the play on the ball.  I've heard rumblings that Lewis is indeed looking to declare after this season. His name has been on the rise.  Size isn't a big issue since Hargreaves is essentially the same size as Lewis and is regarded as one of the best CB in the draft. 

Cook was under duress more than he was used to via blitzing, but he stood tall and delievered the ball on time and accurately.

Michigan4Life

October 19th, 2015 at 9:11 AM ^

by how accurate the ball is. If it's on time and right on the numbers or WR's hands without WRs have to extert effort to get the ball, it's accurate. It's pretty much self explanatory.  NFL scouts do not go by completion percentage because in today's spread offense, any QB can complete 70% of his passes with short passes and screen passes. 

Objectively, Cook had a great game. I'm not blowing him.  I'm simply being objective.

bronxblue

October 19th, 2015 at 10:53 AM ^

I am sure that NFL scouts have their definition of "accurate", but you can't say "Cook had a great game objectively" and then rely on a metric that is "hits the guy in the hands/numbers AND he didn't need to strain too much in my opinion".  

Regardless, I don't know how many balls he threw downfield to be considered in that accuracy metric; was it every throw?  If so, then he also had 3-4 short screens to WRs that didn't amount to much.  Was it throws down the field beyond X yards?  Fine, he threw some nice balls, but Burbirdge had to go up for a couple of them right along the sideline, Shelton had that toe-touch catch because Cook threw it too outside, and probably a couple more.  His one TD to Kings was helped immensely by, I believe, Clark slipping and no safeties coming over the top.  And I'm tired of the drops argument; MSU didn't drop 20 passes in this game; they probably dropped 3-4 at most depending on how accurate you think the play was, and that's a problem literally every QB has to deal with.  

Again, Cook had a fine game, but I've yet to see anything other than a specious "accuracy rate" to cover up his sub-50% completion percentage in this game and the rest of the buzz around him.  And on the season, Cook has good-but-not-elite numbers even with all the caveats you want to throw at him.  8.2 ypa.  57% completion percentage playing basically no competent defenses until UM.  He's very good at not throwing picks (or having the other team drop them/get reversed due to a bad call), and that's certainly helped his passer rating.  To me, he's basically Chad Henne without the senior-year injuries, and that's fine.  But Chad Henne is the definition of replacement-level QB, not the top-15, #1 QB in the country argument I keep reading.  If you draft him in the 2nd/3rd round, and he develops a bit with his accuracy and shows he can handle pressure consistently, then maybe he makes it as a starter in the NFL.  But he doesn't have a great arm, he doesn't have elite mobility, and he puts up competent numbers on a team where (until this year) he wasn't asked to really push the ball downfield.  

bronxblue

October 19th, 2015 at 7:25 AM ^

By all means fight whatever fight you want for Cook and his downfield accuracy rate, but he's under 60% in actual passes for the year; under 50 in this game. I'm sure he's had some drops, but that's true for virtually every other QB in the country and they survive with better completion numbers. I think Cook is a fine college QB, but the hype around him as a pro doesn't mesh with the guy I see in games.

UMForLife

October 19th, 2015 at 7:38 AM ^

In the first half, yes. Not in the second half. Lewis was better. When you miss four throws in a row in the fourth quarter, I believe he did, you cannot be the best Sr QB who is expected to go in the first round. I don't know if he is that good. We will see. But when he has played in big games, which is few and far between in B1G, he has not performed well. He did well in the last bowl game, but I am not sure if he was that good the whole game. He stunk it up in the last OSU game, he didn't do that great against UM this year. Let us see how he does against PSU and OSU before we declare him top 15. NFL scouts like size and measurable. He got that. What you can't see is how well you play against good D and how well you adjust. Jury is still out on him. He is definitely a NFL player. Just don't know how high.

Michigan4Life

October 19th, 2015 at 9:24 AM ^

Actually, Cook played a lot better in bigger games. It's just that he has a tendency to play down to the competition level.

I'm not declaring him top 15. It's the NFL scouts who thinks he's top 15, possibly #1 overall.

Cook had a great game against Michigan. Saying otherwise are not objective



Sent from MGoBlog HD for iPhone & iPad

bronxblue

October 19th, 2015 at 10:56 AM ^

Ah yes, because NFL scouts have been GREAT at drafting QBs in the first round.  Connor Cook might get drafted in the first round because of a dearth of quality options; he did nothing in this game to make me believe that he'll be a good NFL QB.  

That said, I'm done arguing this point with people.  It's my opinion.  You have yours.  By all means stick with it.  But I'm not going to keep arguing with these strawmen scouts and their ill-defined metrics.

 

bronxblue

October 19th, 2015 at 11:40 AM ^

I think their job is to provide adequate information to their GMs to make decisions off of.  I'm sure there are instances where the GM ignores their suggestions (see Manziel in Cleveland, apparently), but if YOUR argument is that every NFL GMs typically go off the beaten path and ignores what his scouts say, especially on first-round selections, which seems to be what you are insinuating, I'm not sure if we are even speaking the same language.

 

Michigan4Life

October 19th, 2015 at 12:16 PM ^

Yes their job is to provide info to the GMs but the final decision ultimately comes down to GM on drafting players. I've heard several instance where scouts hated QB prospects but GM went and pick him bc he's a shiny toy that could make a difference to their franchise. Johnny Football is a great example. Another example is Jake Locker who was drafted by the Titans. There are some who gave him UDFA grade yet the GM drafted him at 1st round. Ditto with EJ Manuel



Sent from MGoBlog HD for iPhone & iPad

2manylincs

October 19th, 2015 at 12:26 AM ^

Im definitely waiting for the ufr on this one. Ive rewatched this game for some reason and did not see one of those 19 targets where burbridge had more than a half step on lewis. Cook earned every completion that he had to burbridge, not the other way around. Thats all that you can ask of a corner. Cook was by far the best player on the field and he kept state close enough to win. My hat goes off to him.

Bill Bafferty

October 18th, 2015 at 11:37 PM ^

We must have watched different games. Cook had a couple of good throws but most were armpunts that Burbridge made great plays to catch. And I don't understand the argument from Staee fans that since they had more yards they deserved to win. Didn't one of the MAC teams they played have more yards they them? It took a once-in-a-millennium play for them to win but they are acting like they won 49-0.

Bill Bafferty

October 19th, 2015 at 12:40 AM ^

Yes armpunts. His many back shoulder throws did he have when not needed? He had a few strikes on intermediate routes but the downfield stuff were all back shoulder prayers. He even hit Lewis in the back of the head with one. When did this board become a Cook hype machine? Even the guys on RCMB are unhappy with his play this year save the 4th quarter of the Rutgers game. As far as Rudock, calling that an armpunt is a compliment. His deep throws this season have been atrocious.

ST3

October 19th, 2015 at 12:09 AM ^

Interesting that you and I both wrote about past heartbreaking defeats, the Desmond Howard game for me and the Kordell game for you. I suppose it is a sub-conscious coping mechanism. "Hey, I survived that; I can survive this, too." I didn't write much about the yardage discrepancy. Frankly, I was really surprised to see that it was so large. State fans pointing to that as some sign they deserved to win must not have watched the game.

bronxblue

October 19th, 2015 at 7:19 AM ^

Yeah, it's sadly a part of any fan's DNA to be hurt by unexpected outcomes, and you want to keep coming back to heal it/get revenge. I noticed a couple people at TOC claim that was proof UM didn't deserve to win, and then I noticed in your post about the starting field difference. But yeah, it was a weird argument to see.

Erik_in_Dayton

October 19th, 2015 at 12:47 AM ^

My parents went to Michigan, and I liked Michigan for that reason before I'd ever even watched a game. But what got me hooked was the Notre Dame game in which Rocket Ismail ran back two kickoffs for scores. It was so exciting and frustrating all at the same time. I had to come back for more. I had to see the team win one of those games. I'm not sure I would have been so pulled to U if M football if, say, Michigan had dominated ND that day. As you've pointed out before, it's a bit of a fiction that the normal season for Michigan has mostly been competing for the national championship. I grew up thinking of Michigan as the team that Notre Dame, Miami, USC, Florida State, etc. beat on their way to a national championship or bowl championship. Yesterday was unique in its painfulness, but it's no more or less than a game to place in our Hall of Bad Memories with the 1990 MSU game, the Colorado game, the Webber timeout game, and the Horror (still the worst in my book). It will take something other than heartbreak to beat down long-time Michigan fans. We know it well and have rebounded from it before. PS: kudos for being able to write this. Despite what I said above, I don't think I'd be up for such a thing yet.

westwardwolverine

October 19th, 2015 at 9:06 AM ^

You know what the worst part about this loss is when compared to other miracle finishes? That the team that ended up winning didn't even do anything miraculous to win it. That's the part that gets me: Sparty didn't have to do a damn thing. Everything just fell right into their lap.

If they block the kick and return it, fine. If they have a miraculous punt return, fine. If they get one second and win on a hail mary, fine. But of course it was none of those. No, it was our punter fumbling the snap and then throw/kicking it right into one of their players who had 3/4 blockers and forward momentum on his way to the endzone because its a punt. They did nothing. 

That's the worst for me. 

tedheadfred

October 19th, 2015 at 11:18 AM ^

What happens to the clock if we do recover (or even just run the ball one more time)?

If it runs, I can't imagine a scenario where they can get a team on the field to try a pass.  If it doesn't run, can someone indicate why it doesn't run?  I haven't seen anything in the rules that indicates that it should stop on a turnover.

I know, salt on the wound and all that.  Just want to understand the game a bit more.

You Only Live Twice

October 19th, 2015 at 9:54 AM ^

Is having good content to read this morning.

Office Sparties are more obnoxious than expected - and the one bragging the loudest didn't even watch the game.

unWavering

October 19th, 2015 at 10:02 AM ^

I disagree that the defensive line was great, at least in the pass rush. Cook had way too much time on the majority of his throws, particularly against a banged up offensive line. They did do well against the rush, and did record three sacks, but the amount of time Cook had was too much for what we were hoping would be the beer 1 defensive line in college football.

SituationSoap

October 19th, 2015 at 10:46 AM ^

Just to touch on your first point about broken hearts creating fandom - yesterday afternoon, my five year old daughter told me that she really hoped the Lions won because she was still disappointed from Michigan's loss Saturday. I didn't counsel her at that point on the wisdom of using the Lions as an emotional backstop for Michigan losses, but it was the first time that she'd noted having an emotional attachment to Michigan football.

 

If that's what Saturday's loss - which hurt, a lot - gives me, it's worth it. I'll be toasting Blake and his One Bad Punt for a long time as we enjoy games together. 

The Source

October 19th, 2015 at 11:04 AM ^

I'm curious if anyone noticed the 12 man on field exchange with Durkin and the Ref.  He appears to say after the penalty to the Ref "now they have twelve" pointing to MSU on the field.  This exchange is immediately followed by MSU o-line guy going down with "wrist" injury.  Anyone get a handle on what was going on there?  That injury looked dubious enough that Spielman was wary of it.  It was interesting to me that Durkin seemed to see something on the field directly before that he was pointing out to referee.