← NFL Drafts
NFLMay 8, 2014

2014 NFL Draft

Bortles, Manziel, and the Aaron Donald Masterclass

What Happened vs What Should've Happened

Compare the original draft order with career-based re-rankings

📋
Original Draft
🔄
Re-Draft by Career AV
Loading draft data...

The Scenario

Everyone wanted a QB. Jacksonville took Blake Bortles #3. Cleveland took Johnny Manziel #22. Meanwhile, the Rams quietly took Aaron Donald at #13 and the Seahawks got their next GOAT CB in Richard Sherman's backyard. The QBs failed. The defensive players became legends.

Analysis based on our NFL Methodology — weighing team environment, position development history, and situational factors.
QB

Blake Bortles

#3 • Jaguars

Out of NFL
DT

Aaron Donald

#13 • Rams

3x DPOY
WR

Odell Beckham Jr

#12 • Giants

3x Pro Bowl
QB

Johnny Manziel

#22 • Browns

2 seasons
THE GREATEST DT EVER

Aaron Donald → St. Louis/LA Rams (#13)

98/100
FactorRatingWeightContribution
Defensive System85/10018%15.3
Scheme Versatility95/10015%14.3
Wade Phillips Arrival (2017)98/10015%14.7
Surrounding D-Line Talent80/10012%9.6
GM Patience (Snead)90/10015%13.5
Franchise Commitment95/10015%14.3
Individual Dominance100/10010%10.0
TOTAL FIT SCORE91.5

What Happened

Donald transcended his situation. 3x DPOY, 8x All-Pro, probably the most dominant interior defender in NFL history. He made the Rams' defense elite regardless of who was coaching.When Wade Phillips arrived, Donald went from great to unstoppable. Context can amplify generational talent — but generational talent will shine anywhere.

THE REACH

Blake Bortles → Jacksonville Jaguars (#3)

32/100
FactorRatingWeightContribution
HC (Gus Bradley)35/10015%5.3
OC (Greg Olson → Hackett)40/10018%7.2
Offensive Line30/10015%4.5
Skill Weapons (early years)35/10015%5.3
GM (Dave Caldwell)35/10012%4.2
Ownership Patience40/10015%6.0
Market (small, forgiving)55/10010%5.5
TOTAL FIT SCORE37.2

What Happened

Bortles had one magical playoff run in 2017 (thanks to an elite defense), but his mechanics and decision-making never developed. Jacksonville's coaching carousel didn't help, but Bortles also never showed the processing speed of a franchise QB. Sometimes the tape is right. He was a reach at #3, and context couldn't save limited talent.

THE CIRCUS

Johnny Manziel → Cleveland Browns (#22)

15/100
FactorRatingWeightContribution
HC (Pettine → Manziel handling)25/10015%3.8
Franchise Stability15/10018%2.7
Off-Field Support Systems10/10020%2.0
Media Circus Management10/10015%1.5
Surrounding Talent30/10012%3.6
Ownership (Haslam)15/10010%1.5
City/Culture Fit20/10010%2.0
TOTAL FIT SCORE17.3

What Happened

Cleveland was the worst possible landing spot for a player who needed structure. The Browns' dysfunction enabled Johnny's worst tendencies. No accountability, no stability, no help.Could a better organization have saved him? Maybe. But Cleveland's chaos accelerated the spiral. Out of the NFL by 25.

WHAT IF

Johnny Manziel → New England Patriots

45/100

The Alternate Timeline

Belichick's structure, Brady's mentorship, the Patriot Way's intolerance for nonsense. Could it have worked? The organization would have demanded accountability. Johnny would've had to compete for every snap. It's the only environment that might have saved his career — or cut him immediately. Either way, a better outcome than Cleveland.

Context vs. Talent

🟢

Donald (LAR)

98

3x DPOY

🟡

Manziel (NE)

45

Hypothetical

🔴

Bortles (JAX)

32

1 playoff run

🔴

Manziel (CLE)

15

2 seasons

+30

Hypothetical point swing: Manziel in NE vs. Manziel in CLE

The Verdict

Traditional Re-Draft Says:

"Donald #1, Khalil Mack #2, OBJ #3, QBs all drop to day 2+"

Contextual Re-Draft Says:

"Donald was transcendent enough to overcome any context. But 2014's QB class shows that bad situations don't just hurt prospects — they can end careers. Cleveland killed Manziel's NFL future."

The 2014 draft taught us two things: generational talents like Donald will dominate anywhere, and fragile talents like Manziel need the right environment to survive. Cleveland provided the opposite. Context can't fix everything — but it can definitely break it.