NFL 2018: One roster cut each team should make, but won't

NFL 2018: One roster cut each team should make, but won’t

By Dan Parzych | Aug 30, 2018

NASHVILLE, TN - AUGUST 27: Kevin White #11 of the Chicago Bears steps out of the endzone after making a catch against Adoree' Jackson #25 of the Tennessee Titans during the first half at Nissan Stadium on August 27, 2017 in Nashville, Tennessee. (Photo by Frederick Breedon/Getty Images) /

17 of 33

(Photo by Otto Greule Jr/Getty Images) /

Kansas City Chiefs: Spencer Ware

Isn’t it crazy how quickly things can change in the NFL for teams when a key player suffers a devastating injury, and ends up losing their starting job as a result due to another player emerging as a star? For the Chiefs, that was exactly the case with Spencer Ware after the running back suffered a devastating knee injury in the preseason last summer, which led to Kareem Hunt filling in as a rookie.

So what happened next? Well, Hunt would go on to lead the NFL in rushing yards as a rookie, and will look to follow up with hopefully a stronger season during his sophomore campaign. Ware may still see carries as the No. 2 running back from time to time, but with the emergence of Hunt, the former starter isn’t as valuable to this offense.

Hunt wasted no time proving just how much of a dangerous threat he can be as both a runner and receiver to show Kansas City earned one of the biggest steals from the draft in 2017. Also, it should be noted there’s no guarantee that Ware will return to his normal ways, so if the Chiefs were to move on, the most important factor is Hunt is still their main guy that will keep them in great shape in the backfield.

Home/NFL