Reeling from two straight losses, Kansas heads to Lubbock to face a Texas Tech team that will likely be starting it’s third quarterback of the season. Seth Doege will run coach Mike Leach’s spread offense after an injury to Steven Sheffield and a poor performance by Taylor Potts in last week’s surprising Red Raider rout at the hands of Texas A&M.
While the Jayhawks have their own problems to worry about, the past week has been anything but calm in Lubbock. First, Leach received a lot of publicity for saying his players had apparently been paying more attention to their fat little girlfriends than their coaches over the last week. Every girl with teased hair and skinny jeans in west Texas cried foul.
Then he announced that the red-shirt freshman Doege would probably start at QB instead of Potts. Prior to his playing time the past three weeks, due to injuries, Doege hadn’t actually played in a game in five years.
The last two weeks it’s appeared Todd Reesing hadn’t played in a while as well. His critical first half turnovers have put the Jayhawks in the hole early in both of their losses, but Reesing said he’s not inclined to change anything at this point, he just has to do a better job on his end.
Kansas hasn’t exactly had a lot of luck against Tech. They are just 1-10 in school history, although their only win did come in Lubbock. After facing Oklahoma’s defense last week, the Jayhawks should have an easier time moving the ball against the Red Raiders, but they still need to find the running game that has disappeared from their offense over the last two weeks.
Tech was embarrassed by their loss to A&M last Saturday and you can bet Mike Leach will have his team up for the game. It never seems to matter who the quarterback is, Tech can move the ball and the Jayhawks are still trying to find the right combination of players on the defensive side of the ball.
It will be a surprise if these teams don’t score at least 35 points each in this game. If Kansas wants to stay in the north race they have to find a way to win.

No comments:
Post a Comment