Kansas City Chiefs: Seven most disappointing players in 2020 season

KANSAS CITY, MISSOURI - JANUARY 03: Nick Keizer #48 of the Kansas City Chiefs celebrates after a touchdown during the 1st half of the game against the Los Angeles Chargers at Arrowhead Stadium on January 03, 2021 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images)
KANSAS CITY, MISSOURI - JANUARY 03: Nick Keizer #48 of the Kansas City Chiefs celebrates after a touchdown during the 1st half of the game against the Los Angeles Chargers at Arrowhead Stadium on January 03, 2021 in Kansas City, Missouri. (Photo by Jamie Squire/Getty Images) /
facebooktwitterreddit
Prev
4 of 5
Next
KC Chiefs Kansas City Chiefs Le'Veon Bell
Le’Veon Bell #26 of the Kansas City Chiefs (Photo by Dustin Bradford/Getty Images) /

Most disappointing Kansas City Chiefs – No. 2: Le’Veon Bell

This might not be fair since Le’Veon Bell didn’t spend the entire season with the Chiefs, but I don’t care, I’m including him anyway.

Chiefs fans were ecstatic when the team signed Bell after the Jets released him. Turns out, there was a reason the Jets felt comfortable releasing Bell and that’s because he doesn’t have it anymore. Chiefs fans saw this firsthand, as Bell did very little in his time in Kansas City.

In nine games with the Chiefs, Bell had just 254 yards and two touchdowns with another 99 receiving yards. He didn’t play in the AFC Championship Game or the Super Bowl either, so the Chiefs ended up getting next to nothing out of him.

The Chiefs weren’t a running team and getting Bell was supposed to change that, but it didn’t. He was passed by Darrel Williams on the depth chart and not even playing in Super Bowl LV was proof that the Chiefs wasted money by bringing Bell in.

We saw this same situation transpire with LeSean McCoy last year and it ended in a similar fashion. No more signing older running backs, please.