KC Chiefs: Three reasons why losing Sammy Watkins wouldn’t be a big deal
![Sammy Watkins #14 of the Kansas City Chiefs (Photo by Joe Robbins/Getty Images) Sammy Watkins #14 of the Kansas City Chiefs (Photo by Joe Robbins/Getty Images)](https://images2.minutemediacdn.com/image/upload/c_fill,w_720,ar_16:9,f_auto,q_auto,g_auto/shape/cover/sport/a4774e440619eafef4f886887ba0f685f9be8d821a703f35eed5d5ebc5404ac8.jpg)
1. Injury-prone
After the dust has settled, what most members of Chiefs Kingdom will remember about Sammy Watkins (aside from his heroics in the postseason) is that the guy could not stay healthy. This was by far the most frustrating part about Watkins’ time in Kansas City and it’s not like the Chiefs didn’t know this was a possibility.
Prior to coming to Kansas City, Watkins played in all 16 games just once — his rookie year in 2014. After missing half the 2016 season, Buffalo traded him to the Rams where he played in 15 of their 16 games.
Watkins appeared in 14 games in 2019 (starting 13) and that was his healthiest season with the Chiefs. It showed too, as he put up his best numbers that year (though still not great), but this year saw the Chiefs’ WR2 start just nine games while appearing in one other, not as a starter. He also missed two playoff games and having him healthy in the Super Bowl would have made a difference offensively for sure.
Next. Receivers Who Could Replace Sammy Watkins. dark
Fans are split on their feelings toward Sammy Watkins and while I’m grateful for what he did for the Chiefs, this is one player they shouldn’t re-sign. He proved he can’t stay healthy for an entire season and this is a team that relies on their offensive playmakers to win games.
The Chiefs took a chance on the best wide receiver in the 2018 free-agent class (or one of the best, at least) and it didn’t pan out. Let another team overpay him this time.