Matchup rankings earn their keep on the two or three lineup spots you actually agonize over. Week 5's list hands you one clear action and one trap: upgrade D'Andre Swift, fade James Cook III.
The names matter less than why they're paired. Swift and Cook sit on opposite sides of the same problem, and treating the two labels as equals is how people lose a week.
Start with Swift. A matchup upgrade means the defense moved, not the player. Swift didn't get better this week; the opponent did him a favor. That makes him a lever, and this is the week to pull it. Put him in the flex, take the upgrade, move on. The managers who get burned by backs like Swift are the ones who treat a matchup-dependent asset as set-and-forget and eat the bad Sundays right alongside the good ones. This is a good Sunday. Use it.
Cook is where I split from the sheet. Fade is a projections word, not a lineup word. It means the ceiling you were counting on got shorter, not that the man belongs on your bench. If you roster a similarly-tiered back with the friendlier draw, this is a defensible week to make the swap. If you don't, Cook stays in and you accept a lower ceiling. Benching him for a waiver body who happens to draw green is the mistake this column invites, and it's a bad one. Matchup upgrades are tiebreakers. They are not talent overrides.
The detail I'd want before fully buying the fade: is it the opponent's run defense, or a projected game script that takes the ball out of Cook's hands? Those are different bets. Fronts are sticky. Scripts flip, often by the second quarter, and a back who gets scripted out on paper frequently isn't. If the fade rests on the front, I take it seriously. If it rests on script, I'm downgrading Cook from locked-in starter to solid starter and nothing more.
My call: Swift in, Cook in, and the only managers who should act on the fade are the ones who already own a real alternative. I expect Swift to finish the week as a top-end flex play and Cook to land lower than his managers are used to without costing them the matchup. If Cook's usage comes in light enough that the script read was right, I'll have been wrong, and I'll say so next week.
Swift is the actionable name on this list. Cook is the name people will overreact to.
