Cade Cunningham: Why Managers Should Be Worried

The Cade Cunningham Problem: When Being Good Isn't Enough

Here's the thing nobody wants to admit about Cade Cunningham right now: he's playing some of the best basketball of his career on a team that's legitimately contending for a championship, and fantasy managers are treating him like he plays for the Wizards. His ownership is sitting at 80 percent, which sounds high until you realize that's mostly people holding him out of obligation rather than conviction. His ESPN rank is 69, which might as well say "I dunno, probably fine?" And that rank isn't lying to you exactly, but it's definitely not telling you the whole story either.

I'm going to level with you from the jump: I don't love Cade for fantasy right now, and I'm about to explain why in a way that'll probably piss off some of you. But first, I need to acknowledge something that's actually making this situation weirder than it needs to be.

The Rule That's Ruining Everything

The 65-game eligibility threshold is, and I say this with zero hyperbole, one of the dumbest things the NBA has done to fantasy basketball in years. I'm not here to litigate whether load management is good or bad for the sport itself. That's a whole different conversation that requires coffee and probably a therapist. What I'm saying is this: watching teams strategically manage games to keep star players under 65 contests is peak insanity. And Cade is stuck right in the middle of it.

Detroit's been quietly brilliant this season. They're 56-21 and they're the one seed in the East. That's not an accident. That's Brad's system, the development of guys like Isaiah Stewart and Jaden Ivey, and yes, Cade being a legitimate two-way point guard. So what does Detroit do? They protect their investment. They rest him strategically. They make sure they're not overextending him when they don't have to.

From a basketball standpoint, that's smart. From a fantasy standpoint, it's a nightmare. Because every time Cade misses a game, there's this nagging concern in the back of your head: are we going to hit that 65-game wall? Are my point guard is suddenly going to become ineligible at position for the stretch run? It's the kind of thing that shouldn't matter but absolutely does in fantasy, and it creates this weird discount on his value that isn't really justified by what he's actually doing on the floor.

What He's Actually Doing (And Why It Matters Less Than You'd Think)

Cade's averaging 12.4 points a night. Stop right there. I know what you're thinking, because I thought it too: that's not a lot. But here's where I tell you that I was raised by a single mother and can do math, so let me break this down.

He's playing next to Isaiah Stewart and Jaden Ivey. The Pistons aren't running an offense designed to get Cade 20 points a night. They're running an offense designed to win basketball games, which is a totally different thing. Cade is your point guard. His job is to facilitate, to run the offense, to make the right reads. When he's playing well, the whole team plays well. When he's not, they struggle.

The problem is, fantasy basketball doesn't reward "making the right reads" at the rate it rewards "putting the ball in the basket." If Cade is dishing out six assists and scoring twelve points, he's not killing it in the fantasy box score. He's doing fine. He's being useful. He's not carrying you to the championship.

And here's the kicker: sometimes he's not even doing that. His last ten games have been sketchy. We're talking inconsistent usage, some nights where he looks great and other nights where you're wondering if he's even on the floor. That's the reality of a guy who's third or fourth in the pecking order for shot attempts on his own team.

The Injury Elephant Nobody's Talking About

Look, I'm going to say something that might sound crazy: I think Cade has lingering stuff from his knee injury that nobody's being totally honest about, and I'm basing that on nothing except watching basketball and having common sense. The Pistons are being careful with him. Maybe too careful. Maybe exactly careful enough. Either way, it's affecting his availability, which is affecting his fantasy value, and we're all just supposed to pretend that's not happening.

This is the part where owning Cade gets frustrating. He's not hurt enough to be a red flag. He's not healthy enough to be completely trustworthy. He's just stuck in this murky middle ground where you're constantly second-guessing whether you should have him in your lineup.

What You Actually Need to Do

Here's my advice, and I'm saying this as someone who usually tries to find the bright side: if you own Cade, you're probably holding him for depth. Which is fine. Depth is important. But you need to stop waiting for him to explode and start using him as what he actually is: a solid point guard who gives you decent percentages, decent assists, and occasional scoring that makes you feel like maybe you made the right call drafting him.

If you don't own him, I wouldn't reach for him right now. There are too many question marks. There's the eligibility thing. There's the minutes management thing. There's the "is he actually healthy" thing. There's the "he's fourth on the depth chart for usage" thing.

What I would do is watch him. Keep him on your watchlist. See if he finds his rhythm. See if Detroit decides to give him more offensive touches down the stretch. See if the eligibility thing resolves itself one way or another. Then make a move when you actually have clarity instead of guessing.

Cade is a good basketball player on a great team. That just doesn't always translate to fantasy gold, and sometimes admitting that is more valuable than pretending you see something that isn't there.

He's probably fine for you. But he's also probably not the answer you're looking for.