Jayden Daniels Returns, But Commanders Continue to Spiral in Loss to Vikings
Jayden Daniels was back under center in Week 14, and for a moment, there was hope that his return might jolt the Washington Commanders out of their downward spiral. But by the end of the afternoon at U.S. Bank Stadium, that hope had faded into yet another frustrating loss - the team’s eighth in a row - and Daniels didn’t even make it to the final whistle.
Let’s get this out of the way: the idea that Washington would sideline their franchise quarterback for the rest of the season was never really on the table. Daniels is too competitive, and the Commanders are too invested in his development.
After weeks of carefully managed rehab from the elbow injury he suffered against Seattle, Daniels was a full participant in practice leading into the game. That was enough for the green light.
But returning to the field against a defense like Minnesota’s was always going to be a trial by fire. Brian Flores’ unit is relentless - one of the most blitz-heavy groups in the league, and among the leaders in total pressures.
This isn’t the kind of defense that eases a quarterback back into rhythm. And right from the jump, it was clear Daniels was in for a long day.
Daniels Looked Rusty - and the Vikings Took Full Advantage
From the opening snap, Daniels looked like a quarterback still trying to find his footing. The timing was off.
The rhythm wasn’t there. And the protection?
Nonexistent. Flores dialed up pressure early and often, and the Commanders' offense never found an answer.
This wasn’t the same Daniels who dazzled earlier in the season with poise and precision. There was hesitation where there used to be decisiveness.
That trademark confidence - the kind that made him one of the most electric rookies in the league before the injury - just wasn’t there. And Minnesota smelled blood.
The Vikings’ defense didn’t just rattle Daniels - they overwhelmed the entire offensive operation. Kliff Kingsbury’s play-calling struggled to adjust, and the Commanders looked completely out of sync. The result was an offense that couldn’t build any momentum, couldn’t sustain drives, and couldn’t protect its quarterback.
The Bigger Picture: A Team That’s Lost Its Way
Let’s be clear: nobody was expecting Daniels to return and immediately light up the scoreboard after missing significant time. But the Commanders needed more than what they got - especially against a Vikings team that’s had its own struggles this season.
Instead, what unfolded was another demoralizing performance in a season that’s spiraling fast. And with Daniels unable to finish the game, the concerns only deepen.
This wasn’t just about rust or recovery. It was about a team that’s lost its identity on both sides of the ball.
The offensive line couldn’t hold up. The play-calling couldn’t adapt.
And the quarterback - their franchise cornerstone - looked like he was thrown back into the fire without the tools to survive.
What Comes Next?
Daniels’ return was supposed to be a turning point - a chance to stop the bleeding and maybe, just maybe, build some momentum heading into the final stretch of the season. Instead, it raised more questions than answers.
The Commanders have five games left, and while the playoffs are a distant memory, the focus now shifts to development and evaluation. Daniels' health and growth remain the top priorities. But if Washington can’t protect him - physically or schematically - they risk stunting the progress of the player they’re banking their future on.
This latest loss didn’t just extend a losing streak - it underscored just how far this team has to go. And if Daniels is going to be the face of this franchise, he’s going to need a whole lot more help than he got on Sunday.