1. Shaun Wade’s inconsistencies with the Ravens
This wasn’t necessarily the predominant factor, but it did play a role. Let’s get something straight first — Shaun Wade didn’t play poorly during his time in Baltimore.
The Ravens came away convinced that he could play in the NFL, even if he was still a long way away from reaching his ceiling.
But it is fair to say that Wade had his struggles this summer.
The rookie cornerback found himself buried on the depth chart after failing to impress in the spring. And his struggles in camp weren’t exactly a secret, even if they didn’t come as a surprise either.
Jeff Zrebiec of The Athletic detailed Wade’s status on the roster a few weeks ago.
"“There’s been some struggles for Wade, but the Ravens knew when they drafted him that some development was needed. It’s hard to imagine that they’d give up on a rookie fifth-round corner this quickly.”"
That about sums it up perfectly. Wade had an up-and-down training camp and looked inexperienced in his role. But all of that was to be expected.
The Ravens knew that Wade was going to be somewhat of a project. And even Zrebiec insisted that it seemed unlikely that the team would just give up on Wade before allowing him time to develop.
Wade’s struggles played a role in his departure, but they weren’t the predominant reason.