| Sign Up | Google+

If Available, Should we Draft Tavon Austin

600x381_medium

via www.trbimg.com

So Percy Harvin is gone, and we now have an additional 1st round pick to play with. It was likely that the Vikings were going to look for a deep threat receiver with the 23rd pick. Now, we are minus one of the most explosive, albeit, ill-tempered, players in the league. So, if…IF Tavon Austin is available at 25, should we take him.

He has drawn many comparisons to Harvin (the good kind, not the bad), though he is a little smaller. Is it wasteful to go with 2 receivers in the first round, assuming we do use #23 on a wideout? You could argue that with other needs, it is a perfect opportunity to grab a higher caliber player than we could have before at, say DT or LB. However, you could also argue that with Percy gone, our need at receiver is amplified and would warrant going double up in the first round. It would put us in exactly the same situation we were in prior to the Percy trade, assuming Austin pans out. We would have all the rest of our picks to address other needs after sealing up a couple star receivers.

The odds are decent that if Austin makes it #23, he will likely get to us at #25. Indianapolis picks in between us at #24, and they have plenty of needs besides receiver.

Thoughts?


                                                                                                                                                                                                               

This FanPost was created by a registered user of The Daily Norseman, and does not necessarily reflect the views of the staff of the site. However, since this is a community, that view is no less important.

Recent FanPosts

View All Fan Posts

The Next FanPosts

There are 12 Comments. Load Now. Loading

Shortcuts to mastering the comment thread. Use wisely.

C - Next Comment
X - Mark as Read

R - Reply
Z - Mark Read & Next

Shift + C - Previous
Shift + A - Mark All Read

Comment Settings

Live comment alert: Hide it!

Comments for this post are closed.

tracking_pixel_5341_tracker tracking_pixel_5351_tracker