A Look Back at What Went Wrong: Part I
With a large amount of Tedford bashing this week, I thought I’d play devil’s advocate. I’m still not quite sure whether I want to join the "Tedford isn’t playing to win/Tedford is scared" camp or the "Tedford botched the playcalling this game but he’s still God" camp. After I’m finished doing this analysis I think I will have convinced myself on which side I want to take.
Please keep in mind that the purpose of this post is to bring some arguments to the table to try and justify why Tedford did what he did, why the playcalling maybe wasn’t as bad as it seemed, and to show that maybe some of us are overreacting a little bit. Remember, I’m trying to play devil’s advocate here. I am not advocating these arguments (yet, although by the end of this post I might) but I merely want to try and shed some light on the other side of things. It seems like the Tedford bashers have plenty of ammo on Tedford and being pretty vocal, so I want to balance things out.
Screen Plays
Alright, first of all, I want to talk about screen plays. Why? Because Tedford called a lot of them and they didn’t seem to work very well. First of all, Tedford called 10 screen plays. That’s 10 passes out of Longshore’s 34 attempts that were screen passes (29.4%). Obviously, Tedford wanted screens to be a big part of the game plan. I suppose his thinking here was that UCLA was probably going to come after Longshore with blitzes to try and make him run on his gimpy ankle. Evidence of this was the fact that 4 out of the 10 screens occurred on our 2nd possession and first scoring drive (4 screen plays out of 11 plays during that drive). The other six screen plays were stretched out over the remainder of the game.
How effective were those screens? Well, in order they got +7, +2, +5, 0, +2, +3, 0, >10 & FD (first down), >10 & FD, and +1. So two out of the ten screens got first downs. Eh, not so great. The ones that didn’t get first downs averaged 2.5 yards per play which is pretty darn pitiful. Obviously, either UCLA snuffed them out real good or we executed poorly. I honestly think it was more of the former.
So was calling all these screen plays a bad idea? The devil’s advocate argument here is, NO! The screen plays are relatively safe plays that get the ball out of Longshore’s hands quickly and take advantage of any UCLA defensive aggressiveness! But then actually, let me interject the other side of the argument and my opinion. Yes, I think it wasn’t such a great idea. I like the fact that Tedford called 4 screen plays in the second touchdown scoring drive. I think it’s safe to assume, as I already stated, that Tedford wanted to protect Longshore and just get the ball out of his hands fast. But that stretch of 0, 2, 3, and 0 yard gains made it quite obvious that UCLA was well prepared and aware of our screen plays after the first few. And despite getting 2 and 3 yard gains I think those were really hard fought yards. I know we also did get two first downs off of screens towards the end but I think the first one was luck. The second one was genius. Without the torrent and pictures to show you, the second screen play that went for a first down was a new play I’ve never seen before in the 6 years I’ve been watching Tedford. It’s a deception play. I mean, obviously screens are deception plays but the way that Tedford executed this screen play was innovative and groundbreaking. I hope to see more of those types of screens.
But back to screens in general. We called a lot of ‘em, 10 to be exact. I think in most games we run about 5-6 screens. And upon a quick glance at my Oregon notes, I see 4 screens. We called a lot more than usual. I think this was just a part of the gameplan to get the ball out of the QB’s hands fast. They didn’t work that well and I must admit that the downs might have been better spent on a down-field pass.
Part II and Part III will be posted later today.


