Use Discount Code TCTWINS for a Free ONE YEAR Premium Membership!

This is part two of a series of articles, to read part one, click here

After getting clear on their vision for the offense and anointing a quarterback for the next three to five years, Vikings General Manager Rick Spielman and Executive Vice President of Football Operations Rob Brzezinski must figure out the backfield. 

Dalvin Cook has been absolutely electric in the opportunities he has been given, but his injury concerns coupled with a league wide movement to shy away from paying big money to running backs pose a question as to what his future on the Minnesota Vikings looks like. 

At first it seems unfathomable to let Cook walk in the offseason or attempt a trade, but what if that’s what is best for the team? Do they want to tie up $15+ million a year to a recently injury prone running back given their current lack of cap space? 

What is their vision for Dalvin Cook and the rest of the backfield after this season? 

Dalvin Cook

When healthy, Dalvin Cook is without a doubt one of the best running backs in the NFL. His 2019 season was the best of his career as in 14 games he amassed 1654 total yards and 13 touchdowns. His touchdown total was good for 4th in the league among running backs and his 118.14 total yards a game was second among running backs only behind Christian McCaffrey.

But that is the key phrase when discussing Dalvin Cook: “when healthy”. He has played only 29 games in his three-year career, tearing his ACL in week 4 of his rookie year and fighting through the majority of his second year with lingering hamstring issues. 

The Vikings may not want to commit big money to a running back with injury concerns, and that is justified when looking at Todd Gurley’s utilization, or lack thereof, after signing a $15 million a year contract with the Rams. Cook is on the last year of his rookie contract and will be looking for big money next year. Le’Veon Bell is making on average $13 million a year with the Jets and Ezekiel Elliot is making $15 million a year with the Cowboys. A contract around $15 million a year is realistic given Cook’s performance and the contracts his peers have received.

On one hand, the league as a whole seems to be figuring out that spending money on an offensive line rather than a star running back seems to be a key to success. More and more teams are forgoing tying up money to talented yet injury prone players and spending that money elsewhere. This year, the 49ers proved that blocking is the most important aspect of the running game, as three different running backs succeeded in their system. 

On the other hand, Kirk Cousins plays his best when the play action is working, and if the Vikings commit to Cousins, they must maximize his strengths. In games last year when Dalvin Cook had over 100 total yards from scrimmage, Cousins averaged a 111-passer rating. When Cook failed to get 100 total yards, Cousins averaged a 102-passer rating. Not a massive difference in performance, but clearly Cousins plays the best when the run game is working, and what better player to have in the backfield than an elite running back? 

Not to mention, Cook’s injury concerns may very well be overblown. During his three-year career at Florida State, he played in 38 of 40 possible games. After tearing his ACL his rookie year with the Vikings, he suffered from lingering hamstring issues during his sophomore campaign, which is an extremely common issue for players recovering from an ACL injury. If not for tearing his ACL that fateful day against the Lions, “Dalvin Cook” and “injury prone” may have never been included in the same sentence.

Rick Spielman and Rob Brzezinski have a tough decision on their hands in deciding on the identity of the backfield and the running game as a whole. Do they extend Dalvin Cook and maximize the strengths of Kirk Cousins? 

Or do they let Cook walk next offseason, spend money elsewhere on the roster, and roll with the cheaper but slightly less talented option in Alexander Mattison? 

Viewing 2 reply threads
  • Author
    • #55253
      Ben_LysoBen Lyso
      • Offline
      • 17 Points
        Rank: Newbie

      This is part two of a series of articles, to read part one, click here After getting clear on their vision for the offense and anointing a quarterback
      [See the full post at: The Vikings are on the verge of an identity crisis II: What about Dalvin Cook?]

    • #55272
      puck1384Joe Johnson
      • Offline
      • 1456 Points
        Rank: Newbie

      Great piece!

      Dalvin Cook even more so than Kirk is what would keep me up at night if I worked in the Vikings front office.

      You have to pay him, you have to. But, if he’s getting consistently injured at this age, it’s not something that’ll get better as he gets older and accrues more touches.

      Thank god for Mattison, I guess. But, you’re going to have to handcuff yourself to a guy who has shown flashes of pure brilliance, while also showing that he can’t make it a full season if used the way this offense wants to use running backs.

      I’m sure that Kubiak and company will find a way, but it still scares me that he might go down at any moment and the Vikings will be stuck with a guy whose going to get paid.

      From a human perspective, I feel for the guy. He works hard, he doesn’t want to get injured. I”m sure he hates missing games, and he should have the economic benefits of what he’s putting his body through. So, I hate to talk about this at all, but then again, he’d get paid anywhere if he left.

    • #55273
      shoeless6Joe Oberle
      • Offline
      • 731 Points
        Rank: Newbie

      We used to say the injury thing about Kyle Rudolph and he has played all 16-plus games in the past five seasons and only 18 games in a nine year career. That is pretty good. We can go too far with injury prone, in my opinion, some of it is luck and some of it conditioning. And Dalvin came back after his second season of injury with a lot better conditioning. His luck has got to get better and I think you have to pay him. (I hope they do.)

Viewing 2 reply threads
  • You must be logged in to reply to this topic.