DRAFT PREVIEW: Pick 29 – Green Bay Packers

The Packers have become used to building a team based around low Draft picks. How will they do in 2017?

Pick: 29

2016 Record: 10-6

What went right in 2016? Sheer willpower pretty much dragged the Packers into the 2016 playoffs after a poor start had threatened their ability to get there. There were some fine performances along the way. Aaron Rodgers was, as usual, ranked in the top four quarterbacks, whilst his old favourite Jordy Nelson returned from injury to snag 14 touchdowns.

And what went wrong? The Packers were curiously poor on defense, with no position group performing to their usual high standard. The rib injury which Nelson suffered in the playoffs and which rendered him ineffective for the divisional championship game against Atlanta was a major factor in them not reaching Superbowl LI.

What do they need? Running Back, Defensive End, Cornerback

Who will they pick? Whilst the Packers could do with a running back, the controversy surrounding Joe Mixon, who will be the best one available at this point (Mixon was filmed punching a woman in the face in a car park in 2014), is likely to mean that the fan-owned Packers won’t touch him. Instead, we think they’ll shore up that defensive with Alabama cornerback Marlon Humphrey.

Richard O’Hagan

Like what you’re seeing? Why not give Uncle Sam a follow on Facebook or Twitter? We promise that we’re gentler than a Sebastian Janikowski tackle.



Richard O'Hagan
Writer on such diverse topics as sport, music, theatre, law and politics. Author of 'Eddie the Sheep'. Supporter of underachieving teams, including the Chicago Bears from before that brief, heady, period in the mid-1980s when they were actually any good. All I want for Christmas is a Jim McMahon away shirt.
Richard O'Hagan on EmailRichard O'Hagan on FacebookRichard O'Hagan on TwitterRichard O'Hagan on Wordpress
You can leave a response, or trackback from your own site.

One Response to “DRAFT PREVIEW: Pick 29 – Green Bay Packers”


Leave a Reply

You must be logged in to post a comment.