

Player mentions
...s undraftable or anything, but I’m hesitant. Jayden Reed is a name I’ve loved in the past, but there remain real con...
...nclusion both main backup RBs, Marshawn Lloyd and Chris Brooks , are probably decent very late bets right now. Lloyd </st...
...tm_source=publication-search">I wrote about last offseason in relating Jayden Daniels’ great rookie year to some of Anthony Richardson’s struggles,...
...behind him, and yet I came to the conclusion both main backup RBs, Marshawn Lloyd and Chris Brooks , are probably decent very late...
...ote> Carolina Panthers Key Stat: Jonathon Brooks — 0.365 MTF/touch, 4.13 YACo/Att, 9.2% breakaway run rate, 1.50 YPRR...
...li> I wrote about it in Field Tippers , but Tetairoa McMillan had a great rookie year given the circumstances, passing 1,000 ya...
...th actual size at 198 pounds. I have Brazzell pretty easily taking Xavier Legette’s role before we get too far into the season, because Leget...
...ock, but again, the major question is pass volume. Jalen Coker missed the first six games, then had just 7 catches in his first...
...before: In Sean Payton’s first year in Denver, Russell Wilson had decent per-dropback efficiency despite the Broncos running wa...
...althy, so the upside there doesn’t seem to be materializing. Mitchell Evans was most interesting of the group with a 1.30 YPRR on a tiny rout...
...ives from the rookie year. ” ( Field Tippers , on Matthew Golden ) <a href="https://bengretch.substack.com/i/188916898/green-...
...d. I wrote about it in Field Tippers , but Tetairoa McMillan had a great rookie year given the circumstances, passing 1,000 ya...
...early despite his rehab, let’s draw a comparison to 2026 top-10 pick Jeremiyah Love. Love had a lot more work in college, which is very important context, at...
...lan, but I do still really like the talent. Rookie Chris Brazzell is part of the issue for Coker, in that he’s a sub-4.4 guy...
...m the rookie year. ” ( Field Tippers , on Matthew Golden ) <a href="https://bengretch.substack.com/i/188916898/green-...
...n head into my bedroom and just pace around by the window that overlooks a street behind our house, for no real reason other than probably there’s mor...
...s like 22 tend to have more successful paths back from this kind of thing. Frank Gore had multiple ACL tears in college. That was a knock on Nick Chubb. These g...
...as dynamic as some of the guys who do keep producing into their 30s like a Derrick Henry or Christian McCaffrey or whoever. It should also be noted...
...on both main backup RBs, Marshawn Lloyd and Chris Brooks , are probably decent very late bets right now. Lloyd </st...
...ot, I argued the inverse of the Mahomes thing, which was that what Christian McCaffrey and Deebo Samuel were doing around the line of s...
...o win in spite of him. People compared his per-dropback numbers to Patrick Mahomes’ , in what was a down year for Mahomes, and I argued strongl...
...which was that what Christian McCaffrey and Deebo Samuel were doing around the line of scrimmage in terms of per-play effi...
...acks was actually hurt by that. I want to acknowledge how that may read as cherry-picking, but emphasize I don’t think it is; again, the key is when t...
..., but I do have concerns this is a profile that’s at too elevated of a price because of the efficiency smash last year. That doesn’t mean he̵...
Article text
I’m going to do things a little differently this year. In the past, I’ve broken up a lot of my team-by-team research into multiple projects. I used to work through all the projections, and take these extensive notes, and then those notes would help me with the projections podcasts I’d do at Establish The Run with Michael Leone, and then after I got through those two extensive projects, I’d basically start back over with the Offseason Stealing Signals writeups and get those detailed here. With any team-by-team project, there’s a real challenge where you want to go deep into each team, but you find that with 32 teams, that’s tough. The process of researching and projecting and writing about a given team is a multiple-hour process at the quickest, except there’s also an element of processing and analyzing and wanting to chew on the actual takes that are formulating that makes it frankly very difficult to just sit and pound out one projection after another. When I work through my projections process, I constantly find myself away from my computer. I have this habit of getting up to think. I often head into my bedroom and just pace around by the window that overlooks a street behind our house, for no real reason other than probably there’s more room and natural light than in my office. Years ago, I’d do the whole thing where I’d be really hard on myself, and think I was procrastinating and those things, but in more recent years I’ve come to embrace that as the good stuff. Cycling through the layers of information and really considering how it pieces together is how you get to the conclusions you want to get to, and that’s the whole point of the whole process. Relative to that, plugging in a bunch of assumptions into a projection so it’ll spit out some fake stats about one possible way a season could go for a team where a hundred assumptions underlying those numbers could be wrong — that part of it feels pretty unimportant. Anyway, I’ve always thought about my summer as having three major team-by-team projects, where I get pretty pumped when I finish the 32nd team for any of them. Those of you who have been around know the Offseason Stealing Signals posts inevitably wind up pushing into late July and early August, and I’m always trying to get them done while also handling a ton of the breaking news and strategy elements of content creation in peak draft season. That’s never been ideal, but it’s mostly been the product of me not writing those posts when I actually do the projections, because I feel like I’m not working through the projections quickly enough and need to push to the next team right when I finish one, as I try to speed up a process that ultimately just requires time. I’d love to be able to project all 32 teams in one week, but it’s my learned opinion that would require me to not do a worse job analyzing the teams. Last year, I wrote the first three installments of this series on July 8, 10, and 12, constituting three divisions and 12 teams. But then I was working on other things, including several other posts, and finished up and released the full set of projections, and then I didn’t get the fourth division out until July 26. Then July 31, but I was writing a bunch of other key stuff, and then eventually I wrote up the final three divisions in a flurry on August 7, 8, and 9, though I had a “mega rankings update with commentary” on August 5, a “camp risers and fallers” piece in the middle of that flurry on August 8, and the firs…