The 2014 Kansas City Chiefs: How To Stop The Bleeding

Sep 7, 2014; Kansas City, MO, USA; Kansas City Chiefs running back Jamaal Charles (25) carries the ball against the Tennessee Titans in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports

Step One: Feed Jamaal Charles The Ball

You can file this step under “duh”.

On a day when the KC offense was a complete disappointment the most dumbfounding part was that Jamaal Charles only touched the ball eleven times. There is no other player on the Chiefs offense that is ANYWHERE near as talented, productive, or capable of making something happen any time they have the ball in their hands as Charles. There isn’t even a discussion or argument to be made otherwise. It’s a fact.

So how in the world can you justify having him only touch the ball eleven times?

Simple, you can’t.

I get that sometimes a team will stop the run early on and then if you fall behind you have to abandon the run for the most part to try and come back via the pass, but here’s the thing…..

JAMAAL CHARLES WAS THE KANSAS CITY CHIEFS LEADING RECEIVER LAST SEASON!!!!!!!!!!!

(sorry I had to go all caps locks and exclamation points on you, but it needed to be done)

If the running game wasn’t working, regardless if it was due to their defense, KC’s offensive line, the game situation, etc. It doesn’t excuse not getting the ball in his hands more. The Chiefs threw a screen pass in the preseason on something like 19 out of every 20 passes (I’m not actually sure that’s factually correct, but it did seem that way) so why on earth couldn’t they throw a few more to him today? Jamaal Charles should touch the ball 20 times in every game unless the Chiefs get such a big lead before he hits that number that you can justify sitting him. Otherwise, get him the ball.

When the Chiefs are struggling to move the ball you have to take advantage of Jamaal Charles abilities, period. To not use the best weapons at your disposal is foolish.

Which brings me to step two……