My Process: Letting Keaton Mitchell Go
Alright, so today I finally pulled the trigger on something I’d been thinking about for a bit – dropping Keaton Mitchell from my fantasy squad. It’s never fun cutting a guy you had high hopes for, but sometimes you just gotta do what’s best for the team overall.
It started a while back, really. I picked Mitchell up, like a lot of folks, because man, that speed was something else. Watched him break off a couple of nice runs and thought, “Okay, maybe this kid’s got something.” He felt like one of those lottery tickets that could pay off big down the stretch.
But here’s the thing, fantasy football waits for no one. First, it was the whole timeshare thing in Baltimore. You never really knew week-to-week how much work he’d actually get. Some weeks, flashes. Other weeks, kinda disappeared. That inconsistency starts gnawing at you when you’re trying to set a lineup.
Then came the big blow – the injury. That season-ending knee injury just sealed the deal, obviously. When I saw that news pop up, my first thought was, “Damn, that’s rough for the kid.” My second thought, almost immediately after, was about my roster spot.
I actually sat on it for a day or two. You know how it is. Part of me wanted to see if maybe, just maybe, there was a reason to stash him on IR. But my league’s IR spots are limited, and honestly, I already had a couple of guys parked there. I had to ask myself some real questions:
- Is he going to help me win this season? Clearly, no.
- Is the IR spot more valuable for someone who might come back later this year? Probably.
- Do I need the bench spot right now for bye week fill-ins or grabbing a handcuff? Yes, definitely.
So, this morning, I grabbed my coffee, logged into the league site on my computer. Went straight to my team roster page. Scrolled down, found Keaton Mitchell’s name there. Hesitated for like, half a second. It always feels a bit weird dropping an injured player, almost disrespectful, but it’s fantasy, right? Gotta be ruthless sometimes.
Clicked the little ‘drop’ icon next to his name. The confirmation box popped up, asking if I was sure. Took a breath, clicked ‘Yes’. And just like that, he was gone from my roster.
Felt a bit of relief, actually. Freed up that precious spot. Immediately went over to the waiver wire, started scouting for a potential replacement. Needed some depth at running back anyway with injuries piling up everywhere. It’s a tough part of the game, managing the roster churn, especially when potential gets cut short by injury. But yeah, that was the process. Had to make the call, executed it, and now I’m moving on, looking for the next guy up.
