I didn't notice anything, this was straight out of the script for every Tech v. Kansas State game from when this streak started until the end of time, and, honestly, I expect more creativity next time.
Elements of the "Tech v. KSU Script..."
I don't really feel like discussing a game we've all seen 15 times, so let's get to the film.
This first play is a pretty good encapsulation of the difference in the offense from the win streak last season to the frustration of this season. The idea is there, I guess, the formation/motion gives Morton a pretty easy read; is it a 1v1 up top? Do I have numbers on the bottom? The problem is, nothing about this really stresses the defense at all, watch how comfortable the K State defense is the entire time, no conflict, no choices, no panic, everything is covered. Since everything is covered, the Red Raiders must win individual matchups to create success, and no one does. Eakin and Cupp totally whiff on their blocks, horrible Morton throw, drop by McCray. Punt. Not a great way to start versus a KState team who just drove the ball pretty easily.
The next one is the play that, I think it's safe to assume, lost the game, and possibly the season. This is the play that led to the hit that knocked Morton out of the game. The frustrating part, is that it was avoidable. From the snap, Morton is looking Eakin's way, and based off the way the defense switches them, I'm not sure why he leaves that route, it's open for a first down. He does, and is forced to leave the pocket where, he appears to be staring right at a wide open Price for a first down. He does not pull the trigger, is forced to run, and is hit... pretty dirtily, honestly, but of course that isn't going to be called. It's time to start questioning why none of our QBs appear to be able to read a defense, and why we keep asking them to do it.
Third play is case in point, I don't think anyone knows what Jake Strong sees here, and absolutely no one knows why he throws this ball. I don't want to harp too much on Strong, his performance is not really his fault, although I am left questioning a lot of his mechanics, once Kittley sees this, there really can't be any more multi-read dropbacks. Especially since the previous scoring drive was made with quick passes and runs, KState is giving Tech the quick screen at the snap! Which I guess leads to the ultimate question of the season, offensively, why do we keep asking people to do things they cannot do? Kansas State has made a program on scheme and execution, and that comes from having guys that simply do their jobs. We seemed to be doing that during the winning streak last year, what's changed? Why can we not evaluate our own roster? I don't really have answers for these questions, but the staff needs to find them, and quickly.
I have no information, but we cannot go into Provo with Morton who is a hit away from not playing and Jake Strong, I need to see supreme creativity from this offensive staff, I'm talking, wildcat, with multiple quarterbacks and formations, trick plays, use of tempo (huddle, sugar huddle, etc.), and putting, whoever is playing QB, in a position to succeed. Take a note from Kansas State.
Unfortunately, the defense wasn't much better. I had the same feeling I had sitting in that stadium against Baylor a year ago, they figured out something Tech could not defend, and they did not let up. The worst part, similar to the offense, is we just look underprepared. Poor gap integrity, poor reads, poor tackling, poor situation awareness, and zero adjustment... it just got worse.
This play was run several times, and one Kittley needs to add to the playbook this week, and, while there are a lot of moving parts, this is a pretty straightforward QB Power. To stop it you need some defensive lineman to win their matchups (didn't happen), stay gap sound (didn't happen), and have linebackers read and fill gaps (didn't happen). Going 0-3 in those categories is going to result in a successful play for the offense every time. I will say Linton does an ok job at first of filling a gap, but gets washed down. Banks ends up doing the job of an OLB or Defensive end, and forces Johnson to go outside, but Pierre reads that wrong and is not there to make a play. To prove that it can be done, I put the next play in this clip, but in typical KState v. Tech fashion, a negative play turns into a big gain thanks to a penalty.
In football, you often hear the term "seeing ghosts" in relation to a QB being confused about what he's seeing a defense do, I think it's fair to use that to describe what Kansas State did to the Red Raider defense. KState runs QB counter, one of my favorite plays, where the backside guard and tackle pull for the QB, while the running back runs against the pull. The QB reads the backside end, like a zone read, and when the Dend crashes, the QB lets the RB take it. One of those linebackers is responsible for being in that gap, but because Johnson had killed them all night, it's easy to see why they both jumped that direction. Pierre's first two steps make no sense to me, unless he is trying to get blocked. Either one of them make the right read and Tech has a chance to stop it. KState really is the master of this stuff, if everyone is not doing what they are supposed to do, they will make you pay.
The next one is the play that killed me because it's not complicated, there are no misdirections, it's just a QB sweep. Everyone block down, uncovered lineman pull, be patient, and find a seam. It's not great by the DLine, but at least they allows the LBs to potentially make the play. Jordan and Pierre kill the Red Raiders here. Kind of like with Strong, I don't want to really harp on Jordan, being a true freshman, but, man, where are you going? You could also ask why are we asking him to play this? Is he really all we have? It was pretty obvious KState knew where he was on every play, they were going after him.
The last play in concerning because everyone in your front 7 is blocked, I mean, cmon. I think if anything shows the state of this program it's this play. We are getting to where we need to go, but we absolutely are not there yet. Expectations got out of whack this offseason, which has made everyone insane, but this roster is not where it needs to be yet. I believe it's getting there, and that we are headed in the right direction. Try to remember how hopeless things felt this time two years ago, under what circumstance would that program be competing for a conference championship in two years?! Zero. None circumstances. Especially when you add that this staff has been dealt unbelievably bad QB injury luck, 3 starters in back to back years is insane. I am not saying that I am not extremely worried about the offense and that these things excuse the fact this team appears to be very situationally stupid, wasteful, and, at times, underprepared, but sometimes you need to take a step back to appreciate the overall direction of the program. We are still in good hands moving forward. This is not Kliff, this is not Wells, I know no one wants to hear it, so roast me as you wish, but we're gonna be fine.
Elements of the "Tech v. KSU Script..."
- Slow start for the Red Raiders: starting with this horse who seems to have unlimited problems, and ending with the first Kansas State drive that should have ended 3 separate times, but instead, resulted in points.
- Red Raiders completely forgetting what has made them successful: Tahj Brooks? Quick game? Isolating favorable matchups? Play action?
- Seemingly unsustainable, yet sustainable, backup QB success: Remember when Riko Jeffers knocked Skyler Thompson out of the game? Yeah it didn't impact the outcome.
- Texas Tech was out-coached, out-executed, and out-played: Kansas state had a better plan, executed it better, and played harder. Tech never really had a chance
- It was a blackout night game: Why even waste our time playing these anymore? Just mark them as losses and move on
- Texas Tech special teams were worse than usual, Kansas State's were better: Hey, Cam Watts, the returner doesn't have to tell the truth when he points. Hey, Drae McCray, I know we can't seem to get you the ball, but please stop wasting yardage on kick off returns.
- Texas Tech providing drive extending penalties: Finally stopped their full house backfield play on 3rd and short... oh there's an unnecessary facemask grab from Steve Linton
- Tech not capitalizing on KSU turnover worthy plays: Rayshad Williams drops a ball thrown right to him on 3rd down on the drive after the miraculous Strong led TD drive, KState goes on to score and never look back.
- Kansas State putting on a coaching clinic: two true freshman qbs played Saturday night, which one looked like it?
- KState has guys step up, Tech has guys disappear: The questionable KState corners played their best game. All the guys we've been excited about the past few weeks... where did they go?
I don't really feel like discussing a game we've all seen 15 times, so let's get to the film.
This first play is a pretty good encapsulation of the difference in the offense from the win streak last season to the frustration of this season. The idea is there, I guess, the formation/motion gives Morton a pretty easy read; is it a 1v1 up top? Do I have numbers on the bottom? The problem is, nothing about this really stresses the defense at all, watch how comfortable the K State defense is the entire time, no conflict, no choices, no panic, everything is covered. Since everything is covered, the Red Raiders must win individual matchups to create success, and no one does. Eakin and Cupp totally whiff on their blocks, horrible Morton throw, drop by McCray. Punt. Not a great way to start versus a KState team who just drove the ball pretty easily.
The next one is the play that, I think it's safe to assume, lost the game, and possibly the season. This is the play that led to the hit that knocked Morton out of the game. The frustrating part, is that it was avoidable. From the snap, Morton is looking Eakin's way, and based off the way the defense switches them, I'm not sure why he leaves that route, it's open for a first down. He does, and is forced to leave the pocket where, he appears to be staring right at a wide open Price for a first down. He does not pull the trigger, is forced to run, and is hit... pretty dirtily, honestly, but of course that isn't going to be called. It's time to start questioning why none of our QBs appear to be able to read a defense, and why we keep asking them to do it.
Third play is case in point, I don't think anyone knows what Jake Strong sees here, and absolutely no one knows why he throws this ball. I don't want to harp too much on Strong, his performance is not really his fault, although I am left questioning a lot of his mechanics, once Kittley sees this, there really can't be any more multi-read dropbacks. Especially since the previous scoring drive was made with quick passes and runs, KState is giving Tech the quick screen at the snap! Which I guess leads to the ultimate question of the season, offensively, why do we keep asking people to do things they cannot do? Kansas State has made a program on scheme and execution, and that comes from having guys that simply do their jobs. We seemed to be doing that during the winning streak last year, what's changed? Why can we not evaluate our own roster? I don't really have answers for these questions, but the staff needs to find them, and quickly.
I have no information, but we cannot go into Provo with Morton who is a hit away from not playing and Jake Strong, I need to see supreme creativity from this offensive staff, I'm talking, wildcat, with multiple quarterbacks and formations, trick plays, use of tempo (huddle, sugar huddle, etc.), and putting, whoever is playing QB, in a position to succeed. Take a note from Kansas State.
Unfortunately, the defense wasn't much better. I had the same feeling I had sitting in that stadium against Baylor a year ago, they figured out something Tech could not defend, and they did not let up. The worst part, similar to the offense, is we just look underprepared. Poor gap integrity, poor reads, poor tackling, poor situation awareness, and zero adjustment... it just got worse.
This play was run several times, and one Kittley needs to add to the playbook this week, and, while there are a lot of moving parts, this is a pretty straightforward QB Power. To stop it you need some defensive lineman to win their matchups (didn't happen), stay gap sound (didn't happen), and have linebackers read and fill gaps (didn't happen). Going 0-3 in those categories is going to result in a successful play for the offense every time. I will say Linton does an ok job at first of filling a gap, but gets washed down. Banks ends up doing the job of an OLB or Defensive end, and forces Johnson to go outside, but Pierre reads that wrong and is not there to make a play. To prove that it can be done, I put the next play in this clip, but in typical KState v. Tech fashion, a negative play turns into a big gain thanks to a penalty.
In football, you often hear the term "seeing ghosts" in relation to a QB being confused about what he's seeing a defense do, I think it's fair to use that to describe what Kansas State did to the Red Raider defense. KState runs QB counter, one of my favorite plays, where the backside guard and tackle pull for the QB, while the running back runs against the pull. The QB reads the backside end, like a zone read, and when the Dend crashes, the QB lets the RB take it. One of those linebackers is responsible for being in that gap, but because Johnson had killed them all night, it's easy to see why they both jumped that direction. Pierre's first two steps make no sense to me, unless he is trying to get blocked. Either one of them make the right read and Tech has a chance to stop it. KState really is the master of this stuff, if everyone is not doing what they are supposed to do, they will make you pay.
The next one is the play that killed me because it's not complicated, there are no misdirections, it's just a QB sweep. Everyone block down, uncovered lineman pull, be patient, and find a seam. It's not great by the DLine, but at least they allows the LBs to potentially make the play. Jordan and Pierre kill the Red Raiders here. Kind of like with Strong, I don't want to really harp on Jordan, being a true freshman, but, man, where are you going? You could also ask why are we asking him to play this? Is he really all we have? It was pretty obvious KState knew where he was on every play, they were going after him.
The last play in concerning because everyone in your front 7 is blocked, I mean, cmon. I think if anything shows the state of this program it's this play. We are getting to where we need to go, but we absolutely are not there yet. Expectations got out of whack this offseason, which has made everyone insane, but this roster is not where it needs to be yet. I believe it's getting there, and that we are headed in the right direction. Try to remember how hopeless things felt this time two years ago, under what circumstance would that program be competing for a conference championship in two years?! Zero. None circumstances. Especially when you add that this staff has been dealt unbelievably bad QB injury luck, 3 starters in back to back years is insane. I am not saying that I am not extremely worried about the offense and that these things excuse the fact this team appears to be very situationally stupid, wasteful, and, at times, underprepared, but sometimes you need to take a step back to appreciate the overall direction of the program. We are still in good hands moving forward. This is not Kliff, this is not Wells, I know no one wants to hear it, so roast me as you wish, but we're gonna be fine.
Last edited:
