KCKingdom
Fansided

Kansas City Chiefs: Le’Veon Bell experiment was a major failure

KANSAS CITY, MISSOURI - JANUARY 17: Running back Le'Veon Bell #26 of the Kansas City Chiefs has a pass broken up by outside linebacker Sione Takitaki #44 of the Cleveland Browns during the third quarter of the AFC Divisional Playoff game at Arrowhead Stadium on January 17, 2021 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images)
KANSAS CITY, MISSOURI - JANUARY 17: Running back Le'Veon Bell #26 of the Kansas City Chiefs has a pass broken up by outside linebacker Sione Takitaki #44 of the Cleveland Browns during the third quarter of the AFC Divisional Playoff game at Arrowhead Stadium on January 17, 2021 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images) /
facebooktwitterreddit

Fans were excited about the Kansas City Chiefs signing Le’Veon Bell, but he did next to nothing during his time in KC.

The Jets released running back Le’Veon Bell not even two months into the 2020 regular season and naturally, the Kansas City Chiefs scooped him up and hoped he’d add something to this offense. Bell was once a dominant running back for the Steelers and used to run all over the Chiefs when he was in his prime. Maybe that was why Chiefs fans wanted him in Kansas City so badly.

I was skeptical about bringing Bell in initially and even wrote an article about it. In that post, I brought up how Bell wasn’t going to enough to fix the mess that was the Chiefs run game. Gotta say — I called that one and I knew after just a few weeks that this wasn’t going to end well for Kansas City.

Bell finished his stint with the Chiefs carrying the ball just 63 carries for 254 yards and two touchdowns while also hauling in 13 receptions for 99 yards. He started just two games while appearing in 10 total and didn’t play at all after the Divisional Round win vs Cleveland.

The Kansas City Chiefs didn’t get anything out of Le’Veon Bell.

This was a similar situation that the Chiefs found themselves in literally the year before when they signed LeSean McCoy and he did very little. The difference there was that the Chiefs brought McCoy in prior to the season and he actually was their starting running back for the first chunk of the season. His fumbling issues eventually landed him on the bench and he wasn’t even active in the postseason.

Bell came in not quite halfway through the season but the hope after Clyde Edwards-Helaire was injured was that Bell would be able to step up and show why this team brought him in. That didn’t happen, as Darrel Williams got the majority of the snaps instead.

Hopefully, the Chiefs learned from this and now know not to bring in running backs who appear past their prime. McCoy was the first running back who did nothing for this team and now Bell followed in his footsteps.

Next. Five Things We Learned in Super Bowl LV Loss. dark

We learned that Le’Veon Bell isn’t anywhere close to the player he once was and know the reason the Jets were okay releasing him. Next time, just give the guys on your roster a chance rather than bringing someone else in.