Montgomery leaving Detroit changed three running back roles at once: Gibbs has less traffic for premium touches, Montgomery has to turn Houston drives into touchdowns, and Pacheco has to earn more than breather work.
Draft Jahmyr Gibbs when you want a first-round anchor. Wait on David Montgomery until the touchdown profile fits the rest of your build. Stash Isiah Pacheco only after your weekly starters are already settled. If you treat all three as the same reaction, you are letting the headline make the pick for you.
That fork is the article. Gibbs is a premium role getting less crowded. Montgomery is a proven power back moving into a different offensive ecosystem. Pacheco is a familiar name entering a backfield where the job still has to be earned.
Gibbs is the spend because the role already worked
The Gibbs case does not require pretending Montgomery never mattered. It starts with the part of the job Gibbs already owned. Down the stretch, he was on the field for roughly three-quarters of Detroit's offensive snaps in the closing sample and still carried real receiving work. That is the profile you actually want to buy early: not just carries, not just catches, but both paths inside an offense that can push teams into weekly point chasing.
The March trade matters because it removes the clearest veteran obstacle from that profile. Detroit still has Amon-Ra St. Brown, Sam LaPorta, and Jameson Williams pulling targets through the passing game, so this is not a promise that every drive becomes a Gibbs touch parade. It is a bet that the highest-value backfield touches no longer need as much negotiation.
For Gibbs, the board shows RB2 and No. 2 overall, and that price is not a discount. It is the cost of buying the player whose role has already shown the most ways to pay you back. If your first-round plan is to leave with a back who can win through carries, screens, two-minute snaps, and red-zone work, Gibbs is the one from this shuffle who belongs on the clock.
The failure case is price compression. When you draft him that early, a merely good season is not enough. You need Detroit to keep the passing-game work alive while adding enough rushing volume to separate him from the rest of the first round.
Draft Room Fork: Three RB Timers
| If This Is Your Draft Spot | Treat The Shuffle As | Reader Move | What Has To Be True |
|---|---|---|---|
| Early Round 1 | Detroit lead-work upgrade | Draft Gibbs as an anchor RB | The receiving work stays attached to the extra carries |
| Round 4 to Round 5 | Houston scoring-role bet | Take Montgomery only if you already have ceiling elsewhere | Houston gives him goal-line work without making him live on empty targets |
| Double-digit rounds | Detroit contingency stash | Draft Pacheco after starters are built | He earns the clear No. 2 job or gets a Gibbs missed-time path |
Montgomery is useful, but do not draft the old uniform
Montgomery's Detroit role was easy to understand. He was the hammer, the short-yardage answer, and the back you could picture getting the ball when the Lions were tired of being cute near the goal line. That profile can still matter in Houston. It just does not travel as a one-for-one copy.
The official transaction record has Montgomery moving from Detroit to Houston, and the team context changes the bet. Houston's 2025 profile leaned more pass-first in neutral situations and ran it at a lower rate in the red zone than Detroit. That does not erase Montgomery. It changes the draft question from "Who inherits Detroit's touchdowns?" to "How much of Houston's scoring work can he actually lock down?"
That is why the middle rounds need discipline. Montgomery sits in the RB22 range and around No. 51 overall. That can work if your first few picks already gave you explosive receivers, an elite quarterback edge, or enough weekly spike potential that Montgomery can be the drive finisher. It gets shakier if you need that pick to create the ceiling by itself.
Draft Montgomery as a roster fit, not as a name-value reflex. If you need steadier touchdown access, he is on the list. If your build is short on explosive weekly outs, let someone else pay for the Detroit version of the player.
Pacheco is a stash, not a shortcut
Pacheco is tempting because the story writes itself: Montgomery leaves Detroit, Pacheco shows up in the Lions' backfield, and drafters imagine the old job sliding to the new veteran. That is too easy.
His prior Kansas City role did not close like a bell-cow audition. In the broader closing window, he was closer to a part-time runner with uneven receiving involvement, and the late efficiency signal was not strong enough to pretend the role is already solved. The move to Detroit is interesting because the offense can turn ordinary rushing work into usable fantasy weeks. It is not interesting because Pacheco has already become Montgomery.
The price is what keeps him alive. Pacheco lands in the double-digit-round range, with roster data putting him in Detroit and ADP around 151. That is exactly where a bench can absorb uncertainty. You are not drafting him to start in September. You are drafting him because Detroit is a good place to hold a back who could become more valuable if one specific door opens.
That door is role clarity. Does he get the clear No. 2 work? Does he handle enough early-down and goal-line snaps to matter without a Gibbs injury? Does any passing-game work follow, or is he mostly a physical series back? Until those answers show up, he is a stash with a useful offense behind him, not a weekly lineup plan.
The board rule
The best way to play this shuffle is to slow it down. One backfield headline created three prices, and each price asks for a different roster tolerance.
Spend on Gibbs if you want the role that already worked and can afford first-round expectations. Wait on Montgomery until your build wants touchdown stability more than open-field juice. Draft Pacheco only when your bench can wait for a role to declare itself.
Carry this rule into the draft room: buy the role that is already real, price the veteran like his new offense matters, and make the Detroit insurance pick late enough that patience is part of the plan.
Go deeper on Amon-Ra St. Brown.
Compare plans with FFN rankings, projections, and player context in one workflow.