Kansas City Chiefs: Potential reasons why John Dorsey was fired

POWER STRUGGLE

The biggest story floating around out there is that Andy Reid is why John Dorsey got fired. Now this could be a combination of the reasons listed above or just a few or none, but it seems all too likely after the past few months.

If the Mahomes pick angered one of the two, that likely caused a rift. From there, Jeremy Maclin was let go and that irritated Reid, who considered that to be the final straw. Now that’s just my opinion, but all of this seems even more likely when you consider that Reid was given an extension not even an hour before Dorsey was let go.

Reid has been in the NFL for a long time and is well respected throughout the league. He handled both head coaching and general manager duties during his time in Philadelphia and it’s possible that he and Dorsey butted heads frequently over the past four years.

While we were all led to believe that all decisions were made and everyone was happy afterwards, clearly that wasn’t the case or this move wouldn’t have occurred.

If Reid was really the cause for why Dorsey is out in Kansas City, then it might be tough finding a general manager to take over and essentially “take a backseat” to whatever Reid wants. Reid is the head honcho for the Kansas City Chiefs, that much is clear. Most general managers want to be able to make their own decisions and not have to share a role with the head coach.

An update that hit the Twitter-sphere as I was writing this post is that Dorsey hadn’t been getting along with owner Clark Hunt. If that were the case, then him being dismissed from the team makes perfect sense. The owner holds the cards and if he and the head coach were both having issues with Dorsey, then this move might have been for the best.