Dan Campbell said Jahmyr Gibbs would be the “bell cow”, and the numbers show exactly why that matters for the Detroit Lions. In 2026, Gibbs has accounted for 134 of the team’s 163 rush attempts, a workload of 82.2% that leaves Detroit with very little proven running back depth behind its lead back.
That is a fine place to be only if your main runner stays healthy and available. The concern in Detroit is that the Lions do not have much margin for error, with the rest of the backfield consisting of Sione Vaki, Jared Goff and Amon-Ra St. Brown in the rushing game, while Isiah Pacheco is unavailable after an MCL injury and back surgery.
Gibbs is carrying the load
Gibbs has become the clear centrepiece of the Lions’ rushing attack. He is not just the primary option; he is the option the entire structure appears to be built around right now. That is why any workload discussion matters so much.
The comparison with other high-volume NFL backs only underlines the point. In a league where elite runners are often asked to do everything, the Lions are leaning on Gibbs at a level that makes his health central to everything they want to do on offense.
Against the Green Bay Packers, Gibbs appeared to twist both his ankle and his knee on a game-sealing rush, which immediately sharpened the focus on Detroit’s depth. Going into Sunday's matchup against the Minnesota Vikings, he was expected to be fine, but the broader concern remains the same: one knock to Gibbs and the Lions would be asking much more of a thin supporting cast.
Why the depth chart matters now
This is where the situation becomes more than just a usage statistic. The Lions signed Isiah Pacheco to a one-year deal in March to replace traded running back David Montgomery, but he has been out since August with an MCL injury and back surgery. The projected return is no earlier than December 6, which means Detroit has had to manage without the player who was supposed to help absorb some of the rushing burden.
That leaves the Lions in a difficult spot. A running game can survive one player taking the lead, but it becomes vulnerable when there is no obvious second runner ready to step in and handle a major share of the work.
The danger is not just that Gibbs has been heavily used. It is that the Lions have so far shown very little evidence of a reliable alternative if they need one. That is why the call for another running back makes sense, even in a season where Gibbs has been outstanding and reliable.
What the numbers say about Detroit
The usage pattern is stark. Gibbs has 134 of the Lions’ 163 rush attempts. The next-most-used options are far behind him, which is why the backfield conversation has shifted from convenience to necessity.
Detroit is not worried about Gibbs’ quality. The question is whether the team can keep asking him to carry such a large share of the ground game without exposing itself later in the season. The answer will depend on health, but also on whether the Lions decide they need more insurance before the next stretch of games.
For now, Gibbs remains the centre of the rushing attack. The issue for Detroit is what happens if that changes.
