Our friends at USA TODAY added a smart twist to their analysis of the work the Buffalo Bills did at the 2022 NFL draft.
With their top selection, Buffalo took Florida cornerback Kaiir Elam. Heading into the draft that was a clear need for the team because of two reasons.
First, last year’s starter in Levi Wallace signed with the Pittsburgh Steelers during free agency. Plus many know Tre’Davious White is currently dealing with a knee injury.
White will probably want to be out there on the field as soon as possible next season. However, Elam’s addition was praised by USAT because now White likely feels less pressure to do just that.
First, here’s the breakdown:
Buffalo Bills (A): A team that may enter the 2022 season as the prohibitive AFC favorites didn’t necessarily have a lot of needs but came away with really good players who should pay immediate dividends. First-round CB Kaiir Elam has ideal physical traits (size, speed) for the position, and his presence could ease any pressure on Pro Bowler Tre’Davious White to return too quickly amid his recovery from an ACL tear. Second-round RB James Cook will bring needed juice to the ground game and maybe reduce some of that load on QB Josh Allen. Even fifth-round WR Khalil Shakir might soften the departure of slot WR Cole Beasley. The Round 6 choice spent on Matt “Punt God” Araiza, whose booming leg will cut through those Lake Erie winds, was the cherry on top.
The Bills will make Elam earn his playing time. But it’s hard to argue that anyone but him and Dane Jackson will be the opening-day starters once September rolls around. At least with the way the roster currently stands.
Many have looked at White’s injury as a reason for Elam’s addition–but sometimes it’s hard to see the human side of things.
A large monkey is probably off White’s back in terms of his rehab. Hopefully if he takes his time with his return, While won’t miss a beat.
While that might be hard in the short term… the longer results of that could pay dividends for the Bills.
from WordPress https://ift.tt/lah1V2g
via IFTTT
No comments:
Post a Comment