The Kansas City Chiefs' defensive backfield took huge blow after huge blow to begin free agency. They traded Trent McDuffie to the Los Angeles Rams, watched Jaylen Watson sign with that same team, and then, if that wasn't bad enough, the Cincinnati Bengals signed Bryan Cook.
Watson and McDuffie may have a legitimate shot at coming out of the NFC to win a Super Bowl. As for Cook, he's going to find out that the grass isn't always greener elsewhere after just a couple of months in Cincinnati.
Bryan Cook Made a Mistake by Signing with Bengals
First of all, joining one of the Chiefs' fiercest rivals has made Cook go from hero to villain in the blink of an eye. He got a three-year deal worth $40.25 million with $14 million guaranteed, per Spotrac, so at least he got great value.
Other than that, though, there won't be many positive things to say about his new situation.
The Bengals are infamous for their slow starts under head coach Zac Taylor's tutelage. He's likely to enter the season on the hot seat, as well, putting even more pressure on the team to win right away. If not, Cincinnati could quickly sell off pieces before the trade deadline, which could put Cook on the move again. Even if he stays, Taylor's replacement might not be someone he sees eye to eye with.
Meanwhile, job security will never be an issue for Andy Reid in Kansas City, giving anyone on the roster a potential long-term head coach to work with.
Cook left a tough division for another one. The AFC North is up for grabs with three new head coaches and one that may not make it to the trade deadline, all while the Chiefs are making moves to return to the mountaintop and go back to Super Bowl contention.
Additionally, Cook could be exposed when he faces the Chiefs next season, allowing his former team to further cause him to regret his decision.
Also, the Bengals' defense has been infamously bad over the past three years or so. Cook is one of the best safeties in the game — he drew the fourth-highest Pro Football Focus grade among safeties last season — but they're still a ways away from being anything close to decent after giving up the second-most total yards per game (392.6), the most rushing yards per game (147.1), and the third-most points per game (28.9).
Adding Cook to the mix will help, but he's only one man. Asking him to do too much, too soon, could be a recipe to torpedo the budding relationship.
Granted, there's some uncertainty in Kansas City regarding Patrick Mahomes' health, and Cook wasn't going to get that type of money to stay with Steve Spagnuolo's defense. Then again, of all the teams he could've chosen, he chose one of the Chiefs' most hated rivals in recent years. The Bengals aren't even a lock to make the playoffs, and Joe Burrow is always a snap away from missing time, so good luck with that.
Needless to say, it likely won't be long until Cook — like many ex-Cheifs — will regret leaving Kansas City.