The Kansas City Chiefs have plenty of needs. Edge rusher. Wide receiver. Defensive interior. Cornerback. Every team has varying concerns at this point in the offseason, from last year's Super Bowl entrants to obviously rebuilding franchises.
The question when selecting any NFL Draft class, and 2026 is no different, is whether a team should aim for a need or take the proverbial "best player available." Fans obviously hope that the overlap is complete in those magical moments when the draft board serves up the best value at a problem position. But that's not always the case.
A rare top-10 opportunity
An interesting conundrum could emerge for the Chiefs when looking at their initial pick in the first round. At No. 9 overall, the Chiefs are in range to select one of the few blue-chip prospects available this year. But the Chiefs rarely get such a premium position in a draft order—this being their first top-10 pick since they traded up to draft Patrick Mahomes in 2017—so it's also an ideal time to ensure a home run pick at a decent area of need.
That seems to preclude taking a running back, which means Notre Dame's Jeremiyah Love is out. Right?
For some, it feels obvious. One month ago, the Chiefs had a bleeding wound at running back. Isiah Pacheco, Brashard Smith, Elijah Mitchell, and Kareem Hunt formed the least threatening backfield in the NFL last season. Much of that was on the coaching staff and their odd player usage rates and play calls. Then again, Pacheco's post-injury productivity as the lead back was a major concern going into the season, and there's a reason the Chiefs tried their best to trade for Breece Hall before the trade deadline.
Then Kenneth Walker changed everything
But instead of waiting until the draft, the Chiefs ponied up big bucks to be able to snare Seattle Seahawks halfback Kenneth Walker in free agency. He was the biggest prize at the position, and the reigning Super Bowl MVP, and the Chiefs came away with the win by offering a three-year, $43 million deal. Walker now anchors a remade backfield that's also added Emari Demercado from the Arizona Cardinals. At this point, the backfield is one of the least of the Chiefs' concerns.
That said, Love is one of the few truly elite players available this spring. In a class where most prospects, even those most highly-regarded, have a fatal flaw or pressing concern, Love is a standout talent who is the rare near-guarantee of making a major impact at the professional level. A premium player, it could be argued, is always a premium player, no matter what position he plays. If the Chiefs are never in this position to draft such a player, should they not take one if he falls to them?
That's the way it looks at the present time. Love could very well make it through the first eight teams to Kansas City at No. 9 due to the position he plays. Some teams that could go for a running back also need premium positions while picking near the top of the draft order. Sure, the Tennessee Titans or Arizona Cardinals could add Love, but it might make more sense to land a franchise left tackle or edge rusher.
But with Walker already in place, the Chiefs have already stretched the rules of "don't pay a running back" to, well, pay a running back. To use such a rare selection on a running back (and not, say, a WR or EDGE) feels irresponsible. Then consider the money involved:
Year | Kenneth Walker | Jeremiyah Love |
|---|---|---|
2026 | $5.68M | $5.95M |
2027 | $18.7M | $7.44M |
2028 | $18.7M | $8.93M |
2029 | n/a | $10.4M |
If the Chiefs accepted that combined cap hit in the backfield over each of the next two seasons, fans would rightfully call for Brett Veach's head.
Thus, it feels crazy to think that the Chiefs are in a position to pass on a rare "sure thing"—and yet here they are. Jeremiyah Love could fall to them. One month ago, it would have been a dream scenario. Now, it feels like a luxury they simply cannot afford.
