The destructive chain reaction that ended the Kansas City Chiefs’ season

Where Was The Run Game?!

First things first, a big reason K.C. lost this game is due to the fact they completely abandoned the run in the second half.  The Chiefs ran the ball a total of 24 times in the game, but ran it just 8 times in the second half. For a little more salt on the wound, they only ran it 5 times in the 3rd quarter.

In my opinion, that is just not the mindset you want to have entering a half of football up 11 points. I understand the lure of constantly wanting to air it out when you have Patrick Mahomes, but why not set him up for success by establishing the run and getting the defense to stack the box or at least honor the run more? That is why you spend a first-round pick on a running back, right? To be able to run the ball when you want to and chew up game clock? Instead, the Chiefs clearly wanted to come out going for the jugular, but failed to ever realize it was costing them the game.

There was just no mindset to come out in the second half and put together some nice, long, sustainable drives.  You know how I mentioned K.C. ran the ball five times in the third quarter?  Well, that in turn saw them pump out two drives that each averaged out to 2:05 in time of possession.  On top of that, their last drive in the third quarter lasted 23 seconds and ended in a rough interception.

With no run game, the Bengals were able to drop more guys back in coverage. That gave us play after play of Mahomes seemingly running sideline to sideline, trying to make something happen.  Which also lead to some reckless decisions in pivotal game moments.  As far as I am concerned, the Chiefs abandoning the run set off a chain reaction of events that all lead to the culmination of a K.C. defeat.