Something sure is wrong with Johnson, who is averaging 43.1 rushing yards per game. Subtract the one good game Johnson had (101 yards against the Browns) and that average falls to a Ryan Moats-esque 33.5.
"There's no rhyme or reason to it right now. If there was, I'd let you know," Munchak said after Johnson's latest disaster, a 34-yard outing against a Colts defense that entered the game 31st against the run. "We're just trying to get something fixed that hasn't been as productive as we'd like, and we're not doing anything different . . . We don't feel any different about Chris Johnson. Nothing's changing. Our philosophy hasn't changed."
That's not entirely true. Johnson has scored only one touchdown all season and is now yielding more carries to Javon Ringer. Johnson is not hitting the holes with any authority and is proving to be a bust after signing a $53.5 million contract with $30 million guaranteed. The 35-day holdout Johnson used to get that deal has to be factored into his decline.
Johnson turned 26 in September, so it's not as if he's over the hill. But to hear the coach announce, "C.J. is our starter and nothing has changed," is troublesome. It's also inaccurate.
Things have changed, coach. Johnson is on fantasy benches and his nickname is now CJRB3. This week's challenge is the Bengals, who are ranked second in run defense.
"This is a situation where it can't get no worse, really, so it can't do nothin' but go up," Johnson told the Knoxville News-Sentinel. "I'm always eager to get back on the field and practice after a bad game and try to make it better."
Lord knows he's had plenty of chances to do that this season.
Chris Johnson's miserable game-by-game numbers:
Week 1: vs. Jaguars, 9 carries, 24 yards, 2.7 avg. 0 TD
Week 2: vs. Ravens, 24 carries, 53 attempts, 2.2 avg. 0 TD
