Kansas City Chiefs: Potential reasons why John Dorsey was fired
MONEY, MONEY, MONEY
When push came to shove, John Dorsey wasn’t the best at locking down the key players. Sure, he made a smart move in extending Travis Kelce, but that was a no-brainer. When it came to players like Justin Houston and Eric Berry, Dorsey took his sweet time and that wound up costing the team more money than what would have been necessary had it been done earlier.
Among issues I've heard #Chiefs brass had with John Dorsey: Didn't get some big deals done early (e.g. Houston, Berry). Cost them more later
— Tom Pelissero (@TomPelissero) June 22, 2017
Some of the deals Dorsey did, however, weren’t the best. When he first got to town, he signed Dwayne Bowe to a ridiculous contract that the receiver never lived up to. In 2014, Dorsey inked Justin Houston to a $101 million, which was a smart move at the time, but the linebacker’s injuries have been mishandled and he’s barely played over the last two seasons.
There’s the Jeremy Maclin contract as well, who was signed to a five-year deal worth $55 million and didn’t play to that deal at all in year two. While fans were pumped for the re-signing of Eric Berry, it’s tough to be super optimistic about it with how badly some of Dorsey’s deals have gone.
This might have made more sense as to why Dorsey was fired especially with the Maclin drama. A general manager has to be able to pay the big time players and know when to let guys walk. We all thought Dorsey did a good job of that for the most part, but apparently not good enough.