Chiefs Keep Elijah Mitchell and Fans Question What Comes Next
Elijah Mitchell’s surprising spot on the Chiefs roster highlights deeper concerns about Kansas City’s struggling backfield and puzzling personnel decisions.
The Kansas City Chiefs have a backfield problem — and it’s starting to drag down the offense in a very real way.
To be fair, this wasn’t exactly unpredictable. Throughout the offseason, there were warning signs that the running back room might be a soft spot.
The front office made only marginal moves to bolster the group, and now, just two games into the season, the cracks are showing. Injuries, miscues, and a lack of firepower in the run game are beginning to weigh heavily on an offense that’s used to setting the pace — not playing catch-up.
One of the more curious moves in the offseason came when general manager Brett Veach took a flyer on Elijah Mitchell, the former 49ers back who, once upon a time, broke rookie rushing records in San Francisco. That was back in 2021, and since then, Mitchell’s availability has been more of a rumor than a reality.
Over the past three seasons, he’s logged just 130 carries total — averaging a mere 43 per year — and missed the entire 2024 campaign with yet another hamstring injury. That followed a laundry list of ailments that would make even the most durable backs cringe: finger, shoulder, knee, groin, rib — you name it.
Mitchell’s addition was never supposed to be a game-changer. At best, he was a low-risk depth piece. But here we are in Week 3, and his role — or lack thereof — is raising eyebrows.
Despite a quiet preseason and minimal flash, Mitchell managed to survive roster cuts. Developmental backs came and went, but Mitchell stayed.
And yet, through the first two weeks, he’s been a healthy scratch on game day. That wouldn’t be particularly notable if the Chiefs’ backfield looked even remotely competent.
But right now, it doesn’t.
Isiah Pacheco, who was expected to take a step forward as the lead back, hasn’t found his rhythm. Kareem Hunt has been serviceable in short-yardage spots, but the duo lacks any real explosiveness. Together, they might be one of the least dynamic backfield pairings in the league — a harsh reality for a team that’s used to lighting up the scoreboard.
Then there’s Brashard Smith, a seventh-round rookie with some upside, but he’s barely seen the field. One touch in Week 2 isn’t exactly a sign of trust from the coaching staff. So the question becomes: Why keep Mitchell around if he’s not going to contribute?
It’s not just about touches — it’s about what those touches look like. On Sunday, both Pacheco and Hunt had passes in the flat with room to operate.
And both were stopped in their tracks by a single defender. Plays like that underscore the Chiefs’ current offensive problem: outside of Patrick Mahomes, there’s a lack of players who can create something out of nothing. And when that’s the case, even basic plays feel like uphill battles.
Mitchell was expected to be a Jerick McKinnon-type replacement — a third-down option with enough juice to make defenders miss and keep defenses honest. Instead, he’s watching from the sideline while the entire unit sputters.
Meanwhile, the Chiefs cut prospects like offensive tackle Esa Pole to keep Mitchell on the roster. That decision is starting to look less like a strategic maneuver and more like a head-scratcher.
To be clear, Mitchell isn’t the root of the problem. The issues in the backfield go deeper than one player.
But his situation is symbolic of the larger question facing Kansas City: What exactly is the plan at running back? And if the current rotation isn’t getting it done, why not give someone else — anyone else — a shot?
There’s still time for the Chiefs to sort this out. But for now, the offense is leaning heavily on Mahomes without giving him much help behind him.
Whether Mitchell ends up being part of the solution or just another missed opportunity remains to be seen. But if the Chiefs want to keep their offensive identity intact, they’ll need to figure out the backfield — and fast.
