The Niche Cache

View Original

Here’s a bit of Perspective on Paul Lasike Getting Waived

Sometimes a thing we write lingers in relevancy for months, other times it goes out of fashion so quickly you’ve barely had time to hit publish. Paul Lasike deserved a proper analysis after his efforts in week two of the NFL, taking a carry for a couple of yards to become the first NZer ever to register an NFL rush – as well as a crushing block on the goal-line which probably had zero impact on Jeremy Langford getting into the endzone but at least it looked cool on telly.

So we wrote this:

See this content in the original post

Problem was, within 18 hours he’d been waived.

See this content in the original post

That’s the life of a fringe player in the NFL, where things can change so quickly. Lasike was never indispensable and the Bears showed that their commitment to having a fullback was never all that concrete. So when roster moves needed to be made he was always gonna be vulnerable.

See this content in the original post

Argh but why did it happen to him!? What did he do wrong? Well, blocking was one thing. It’s kind of his one job and although he won a few fans with his bulldozing in the red zone but there were also a few where his initial contact might have rocked the bugger but he couldn’t hold the block. There’s an example of that in the article above. And keep in mind that the iceberg effect is definitely on the active roster of theories in this case – for every instance on the field that the coaches might have been disappointed in, there were probably ten similar once on the training turf. Seeing his offensive snaps drop from 14 to 5 from week one to two (with no special teams opportunities in the second game either) suggest that trust levels weren’t all there and it wasn’t getting better.

The Bears have lost both games so far and their running game has been pathetic – 27th in rush yards and 21st in yards per rush. Considering that they also aren’t going many places through the air, that is a serious issue and Lasike’s work wasn’t helping it. Windy City Gridiron suggested as much with their ideas on the move:

“In the season opener against the Houston Texans, Lasike saw the field 14 times, primarily as an extra blocker (that the Bears badly needed). However, his snaps were reduced to 5 total in the Bears home opener Monday Night versus the Philadelphia Eagles, indicating they didn't think he was contributing in his current role. Considering the shape the offensive line is in and how badly they need help, the Bears aren't likely making this move for any reason other than Lasike's own performance.”

Some of those running difficulties fall back on Lasike, though most are down to the offensive line (which has been a multi-year issue for them) and an under-skilled running back group. Before the season, Pro Football Focus had their RBs ranked as the 28th best unit, highlighting Jeremy Langford’s struggles – though also pointing out that in Jordan Howard they have a very promising backup. In the loss against the Eagles, Langford ran for 28 yards on 11 rushes. Howard had three runs for 22 yards.

Pro Football Focus: “I think it’s fair to say that, of all the sophomore running backs coming into this season as starters, Jeremy Langford’s job is in the most danger. Out of 52 qualifying backs, Langford finished dead last in elusive rating (10.3) and second-to-last in yards after contact per attempt (1.76). Jordan Howard (Indiana), on the other hand, was one of our top-rated running backs in the draft, and has impeccable vision. The rookie could easily be starting by the season’s end.”

There was a point in the game when Howard came in to relieve Langford in the third quarter with the score at 9-7 to Philly. Howard had back to back runs of 10 yards and then 8 yards, setting up a Second & 2 at the halfway line. But with Howard gunning, they brought back in Langford who was promptly dumped for a four yard loss. Cutler threw an incompletion to follow and the Eagles scored a TD on the next drive (followed by a Cutler interception and another PHI TD).

See this content in the original post

So yeah, dramas ensue. But the main reason Lasike was waived is because somebody had to be. Jay Cutler is out for a few weeks with a thumb injury and it’d be reckless to go into a game with only Brad Hoyer on the roster. Matt Barkley has been sitting quietly on the practice squad, and dutifully he was the fella recalled to take up the place evacuated by Lasike. It’s a little bit stink that he was chosen given that along with Langford and Howard the Bears are also carrying two other running backs in Ka’Deem Carey and Raheem Mostert. Carey has had three carries all season and is currently hurt, while Mostert was called up from the practice squad a day after Lasike was waived. But bear in mind that Lasike was an undrafted free agent and is still coming to grips with a lot about this sport, plus is still practice squad eligible himself.

Under the waiver process, other teams have 24 hours to make a claim on those players. Despite a few unlikely dreams in Nichey Towers that maybe Lasike would find his way onto the Dallas Cowboys, he didn’t. Instead he predictably went unclaimed (if you want a fullback two weeks into the season, you already have one) and was promptly reinstated to the practice squad that he spent last season on. That’s a promising thing. They gave him a shot on the active roster and it didn’t quite work out but when they cut him they still kept him around among the non-playing dudes. That means they still see promise in him, that they’re still invested in him. No big worries for the lad himself, either.

See this content in the original post

For all we know, Lasike could be back on the roster in a couple weeks’ time once Cutler is healthy again. Or maybe he doesn’t play again this season, who knows? Again, things change bloody quickly in this sport.