KCKingdom
Fansided

Kansas City Chiefs: Potential reasons why John Dorsey was fired

Mandatory Credit: Denny Medley-USA TODAY Sports
Mandatory Credit: Denny Medley-USA TODAY Sports /
facebooktwitterreddit
Prev
2 of 7
Next
Former Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: John Rieger-USA TODAY Sports
Former Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: John Rieger-USA TODAY Sports /

MACLIN BACKLASH

Chiefs fans were just as shocked three weeks ago when the KC Chiefs released wide receiver Jeremy Maclin. Several days later, Andy Reid held a press conference and seemed very irritated that Maclin was no longer a part of the team.

No one is entirely sure of why Maclin was cut, but a lot of the speculation pointed to financial issues. Is it possible that the final straw for the Dorsey/Reid duo was the move of releasing Jeremy Maclin?

It does make sense when you think about it. Maclin and Andy Reid go way back, all the way to 2009 when Reid drafted Maclin in the first round when he was with the Eagles. The Chiefs even tampered in free agency to get Maclin, which ended up costing them a third round pick in the 2016 NFL Draft.

Maclin had a bad year in 2016 and Dorsey obviously didn’t see him as being a viable option to keep on the team. Perhaps cutting former Mizzou man Jeremy Maclin is what led to the exit of John Dorsey. Will we find out if this had something to do with Dorsey’s departure?