In the latest episode of “should the Chiefs get him?”, we say no to any thoughts of adding linebacker Zach Brown to Kansas City’s roster.
The Philadelphia Eagles have released linebacker Zach Brown.
For some, it was a bit of a surprise given how much he’s played for Doug Pederson’s team (and the state of the position given Nigel Bradham’s health), but no matter the reason, Brown is now looking for gainful employment for the rest of the 2019 season.
Given that Brown was a starter on a decent team, it wasn’t surprising to see Chiefs Kingdom begin to ask the question that always emerges when a player is newly available on the market: should the Kansas City Chiefs sign him? To that, we’d like to simply say no.
Brown was a starter for the Eagles in all six games so far this season, which is part of the surprise why the team would set him free just like that. So far this season, Brown has 29 total tackles (2 for a loss) and 2 passes defended. He’s also been a starter for every team who has brought him in, including the Buffalo Bills, Washington Redskins and, his original team, the Tennessee Titans.
Yet therein lies the first piece of a puzzle that largely reads “Not Worth It” for the Chiefs. Brown’s journeyman status doesn’t help him in an instance like this, as the Eagles were quick to give up on a player who they now need to replace (it’s hard to imagine the Eagles won’t look to sign a linebacker soon). The Washington Redskins did the same, allowing Brown to leave despite being graded by Pro Football Focus as their top defender in 2018.
The reality is that Brown had worn out his welcome in the nation’s capital in the locker room with his criticism of the team and its leadership. Poking at the Washington Redskins brass is an easy target these days given the organization’s proven ineptitude from the top down, starting with owner Dan Snyder, but Brown didn’t do himself any favors with his negative quotes to the press and social media posts.
Washington let Brown walk one year after signing him to a three-year, $21 million deal. The Eagles released him just six games into the season, moving on from a starting linebacker out of the blue. It’s easy to blame his recent criticism of Kirk Cousins (and the resulting dominant performance from the Minnesota Vikings quarterback), but it was likely just the final straw for the Eagles.
Zach Brown hastened his exit with his Kirk Cousins comments, but he wasn’t backing up his brash talk. Never played well, dating back to camp. As I reported last week, #Eagles had narrowed down May LB signing to Brown or Jamie Collins. Went with the former.
— Jeff McLane (@Jeff_McLane) October 14, 2019
Oh and if you’re wondering about that Pro Football Focus score for this year? He’s ranked 60th of 88 linebackers.
Here’s the thing: Brown is a decent run defender and tackler and the Chiefs could most certainly use that. But Anthony Hitchens should be returning soon and the Chiefs already have imported so many new linebackers over the last two years that it’s hard to see how another one fits—unless Brett Veach wants to bring aboard one “maybe” for a former “maybe” in Reggie Ragland.
Given the attitude issues, the low level of play in 2018, the Eagles’ willingness to move on despite having no current options to step in, and the history of being asked to leave, the Chiefs could likely find better ways to address their current concerns.