Kansas City Chiefs: Potential reasons why John Dorsey was fired

GO PACK GO

Months ago rumors were surfacing that a potential reunion between John Dorsey and the Green Bay Packers was in the works. Dorsey had gotten his start in Green Bay and it would have been no surprise to anyone if he took over for Ted Thompson as the acting general manager in the Bay.

While Chiefs fans didn’t want to see this happen, it would have made sense. Chris Ballard was the GM in waiting for Kansas City at that time, so everything seemed like it’d be okay if Dorsey did decide to leave.

Later on, Ballard accepted the GM job with the Indianapolis Colts and that showed that Kansas City felt confident enough in Dorsey staying in town. No further talks occurred after Ballard bolted for Indy.

Now, however, the Chiefs have sent a mixed signal. If they knew Dorsey wasn’t going to be the GM in 2017, then why let Ballard leave? That’s why one of these recent issues had to be what led to this demise.

It’s been reported as of Thursday evening that Dorsey isn’t going to Green Bay, at least not as the GM. Perhaps he’ll wind up there in another role, but more than likely, he’ll find a GM job with another team. Yes, even this late in the offseason.