Chiefs waive ShunDerrick Powell

The Chiefs made a small move on paper, but it tells you a lot about where the roster is heading. Kansas City waived running back ShunDerrick Powell on April 29, only a few days after spending a fifth-round pick on Nebraska runner Emmett Johnson. That is not a headline-grabbing cut. But it is the kind of post-draft move that shows how quickly depth-chart math starts once new rookies arrive. (chiefs.com) ### Who did the Chiefs waive? Powell was a back-end roster player — not someone with an established role in Kansas City’s offense. He signed a reserve/future contract with the Chiefs on January 6, which basically means the team wanted to keep him around for the offseason and take a longer look at him. Those deals matter, but they are fragile. The momen(chiefs.com)ets thin fast. (chiefs.com) ### What changed this week? The biggest change was Johnson. Kansas City drafted the former Nebraska running back with the No. 161 overall pick in the fifth round of the 2026 NFL Draft. A draft pick is different from a futures signing because the team has now spent real draft capital on that player. That does not guarantee a roster spot forever, but it (chiefs.com)is turned in. (nfl.com) ### Why does a fifth-round pick matter here? Because roster building is mostly about who gets developmental reps. Coaches only have so many offseason snaps, meeting-room spots, and preseason carries to hand out. Johnson comes in as a drafted back with upside, and Powell was competing for one of the last spots. (nfl.com)ike a reaction to one player and more like standard roster compression after the draft. (chiefs.com) ### Was Powell ever really in the plans? Probably only as a long-shot candidate. Powell did make it onto the Chiefs’ roster page, which shows he was in the offseason mix, but there is no sign he had carved out a real role yet. That is normal for reserve/future players. They are auditions more than commitments. If a team likes a rookie better, the audition can end quickly. (chiefs.com) ### What does this say about the running back room? It says Kansas City is sorting the room early instead of waiting for late summer. The Chiefs had already added veteran Kenneth Walker earlier in March, then drafted Johnson in April. Put those additions together, and the room got more crowded before rookie camp even opened. Powell was one of the easiest roster spots to reclaim. (chiefs.com) ### Is this about Johnson specifically? Yes — but only in the broad offseason sense. The Chiefs did not waive Powell because Johnson is already better in a proven NFL sense. Nobody knows that yet. They waived Powell because Johnson now gets the developmental runway. Draft status buys time, reps, and patience. Powell did not have much of any of those. (chiefs.com) ### What should fans take from it? Do not overread the name. Read the process. This is what teams do right after the draft — convert picks into actual roster consequences. Kansas City is already reshaping the bottom of the roster, and running back was one of the first places where the squeeze showed up. (chiefs.com)ise-changing move. It is a roster signal. The Chiefs drafted Emmett Johnson, and within days one fringe running back spot disappeared. That is how the post-draft churn starts. (chiefs.com)