3 Top Takeaways: Minnesota Vikings vs. Chicago Bears – Week 11

(Photo by Jonathan Daniel/Getty Images) Kirk Cousins
(Photo by Jonathan Daniel/Getty Images) Kirk Cousins /
facebooktwitterreddit
Prev
3 of 4
Next
CHICAGO, IL - NOVEMBER 18: Dalvin Cook #33 of the Minnesota Vikings is hit by Kyle Fuller #23 of the Chicago Bears in the first quarter at Soldier Field on November 18, 2018 in Chicago, Illinois. (Photo by Jonathan Daniel/Getty Images)
(Photo by Jonathan Daniel/Getty Images) Dalvin Cook /

DeFilippo has no idea how to use Cook

Prior to their game against the Bears on Sunday night, it was revealed that Vikings running back Dalvin Cook would not be on a pitch-count during the matchup. Minnesota had been easing Cook back into the offense as he recovered from a hamstring injury, but he was apparently good to go for Chicago.

It didn’t seem to really matter how healthy he was though on Sunday. The young Vikings running back finished with just 10 total yards on 12 touches against the Bears.

A lot has been said over time about how versatile of a player Cook is out on the field. He can not only gain tough yards up the middle, but he can line up on the outside as a receiver and get open downfield.

Despite this, Cook’s involvement in the offense on Sunday was pretty bland. The plays called by Minnesota offensive coordinator John DeFilippo didn’t really take full advantage of the running back’s abilities.

Cook has the skills to easily get past a defender in coverage and instead, DeFilippo had him running up the gut or trying to make something out of poorly timed screen passes.

Cook is a tremendous weapon to have in an offense. But his value to the Vikings will just continue to be wasted until the team’s offensive coordinator can figure out how to properly utilize him.