The rub on the release of Jeremy Maclin

HOUSTON, TX - JANUARY 09: Jeremy Maclin
HOUSTON, TX - JANUARY 09: Jeremy Maclin
1 of 5
KANSAS CITY, MO – DECEMBER 27: Jeremy Maclin
KANSAS CITY, MO – DECEMBER 27: Jeremy Maclin

In the wake of Jeremy Maclin’s release, it’s clear that Chiefs Kingdom can be quite forgetful at times.

Over the weekend, the Kansas City Chiefs parted company with nine-year veteran wide receiver Jeremy Maclin. Since then, the narratives surrounding this transaction have been interesting to say the least. My lone takeaway from those watercooler conversations: members of Chiefs Kingdom can be a forgetful bunch.

From the discussions around the blogosphere, you’d come away thinking Maclin was an expendable part of an otherwise formidable offense. The maturation of Chris Conley and the emergence of Tyreek Hill, in an admittedly impressive rookie campaign, made Maclin a forgotten part of a budding, young offensive group. After all, the former Missouri Tiger’s production was down from the year prior. Losing him should only have a negligible effect on head coach Andy Reid and company, right? RIGHT? 

Whether or not you believe the offense can survive without its most accomplished receiver depends entirely upon the premise supporting your argument. I’m okay with anyone who’s concluded that the Chiefs offense can weather the departure of Maclin. The issue, for me, are the flawed premises some have used to arrive at said conclusion. Today, if I could, I’d like to offer a counter perspective to the most popular talking points circulated around the Kingdom the past few days.

Schedule