How much of it is poor play design vs. not getting the ball out quickly vs. just bad OL play?16 of 33 drop backs had pressure. Even though the passing game feels likes it’s 2016-2019 they can’t do anything with this kind of shit show on drop backs. So frustrating. The OTs both sucked tonight in pass pro.
It helped keep Brissett upright. By the end, he looked pretty beat up though.If I see another fucking max pro 2 route high-low kind of play-action I’m going to snap. FFS
90%+ is piss poor pass pro.How much of it is poor play design vs. not getting the ball out quickly vs. just bad OL play?
Yup. In a non-monsoon, Pats WRs combined for 3 catches and 19 yards.The three key negative plays in the game to me were:
1) The miscommunication on the Metcalf long TD, that is the kind of killer mistake that just can't happen
2) Poor blocking on the Slye FG that was blocked
3) Wilson's DPI on third down in the end zone, which basically handed Seattle a TD when the receiver was never catching the ball anyway.
Those are the three things I look at when determining goats for the game. The biggest issue though, is the fact that the O-Line can't pass protect at all. Not sure what Brissett is really supposed to do on a lot of plays when he has no time to set his feet in the pocket. The complete lack of production from the WR group says it all, this team can't can't anything going downfield because 2-3 seconds seems about the max amount of time the line can hold a pocket for.
Agree with this. He's taking a beating, and my early prediction for the next game is he is physically unable to finish that one.Brissett was running for his life, made some plays early but faded later.
I'm not sure that is the goal at the momentwe need Maye if we want any chance to consistently win.
We all knew the offense was going to be shit but being ultra-conservative on top of it is just so disappointing from an entertainment standpoint.5.1 YPC and punting multiple times on 4th and 1ish In the year 2024. Fix this or get a new coach.
Also, you have no time to throw, what the hell are you having Pop Douglas do? Get him some touches on short/intermediate routes/screens. With 2 min left in the game, Polk’s TD was THE ONLY WR CATCH until the final 2 drives, where they added a whopping 14 more yards. 19 yards total on the day for Patriots WR!!
I found it strange they didn’t do much to get Douglas involved. Seems like with a porous OL, some quick hitters and screens to get him the ball would have made sense.5.1 YPC and punting multiple times on 4th and 1ish In the year 2024. Fix this or get a new coach.
Also, you have no time to throw, what the hell are you having Pop Douglas do? Get him some touches on short/intermediate routes/screens. With 2 min left in the game, Polk’s TD was THE ONLY WR CATCH until the final 2 drives, where they added a whopping 14 more yards. 19 yards total on the day for Patriots WR!!
Was there ever any explanation given for that endzone PI? The ball seemed clearly uncatchable no matter the contact.One or two plays break our way (e.g. that ridiculous pass interference in the end zone) and we'd be talking about what great in-game adjustments Mayo made. Ah, well
I think I saw Douglas had the 2nd most routes behind Henry, live sure seemed like he just was either never close to open or Brissett was flushed out away from him and wasn't going to throw back.A few things about Douglas: they were leaning into heavy all day with a lot of running. Douglas doesn’t fit into that. Douglas is a slot only but you really need the slot to be a good blocker in this offense given how run heavy it is. I don’t know how much 11 they were in today but it didn’t feel like a lot. Last minor note is Douglas is more effective beating man than zone per reception perception and the Seahawks should have been zone heavy today (I’ll know more of that later).
When he went down and held his knee I hoped they would not put in Maye since Brissett was running for his life out there.It helped keep Brissett upright. By the end, he looked pretty beat up though.
These are the kinds of games we should expect most of the year. The Pats can eek out 20 ppg, and hold most teams to below-average output. Anything beyond that is just luck.
I think you're the only one to mention the DPI on Wilson. That play was really bad and costly. Like you say, the Seattle WR wasn't coming down with that ball.The three key negative plays in the game to me were:
1) The miscommunication on the Metcalf long TD, that is the kind of killer mistake that just can't happen
2) Poor blocking on the Slye FG that was blocked
3) Wilson's DPI on third down in the end zone, which basically handed Seattle a TD when the receiver was never catching the ball anyway.
Those are the three things I look at when determining goats for the game. The biggest issue though, is the fact that the O-Line can't pass protect at all. Not sure what Brissett is really supposed to do on a lot of plays when he has no time to set his feet in the pocket. The complete lack of production from the WR group says it all, this team can't can't anything going downfield because 2-3 seconds seems about the max amount of time the line can hold a pocket for.
You've nailed it precisely. You've got to run the ball on second down to either force Seattle to call a time out, or to burn down some clock, both of which would adversely affect Seattle's chances to score at the end of the half should they get the ball back. The Pats choice of throwing twice did neither, and it cost them badly. That's a terribly amateurish approach to game strategy. Mayo has to get better at that.Can we discuss the end of the first half? I'm not sure I am in agreement that the Pats botched it (on offense; not talking about ST and D here), but I am open to changing my mind.
To reset:
- ball on the Pats 8
- 1:28 to play
- both teams had all timeouts
- the Pats ran for 2 yards on 1st down; Seattle did not call timeout
- the Pats threw incomplete on 2nd down (0:54 left) and 3rd down (0:47 left)
So for those arguing that the Pats botched it - what would you have done? Run on 2nd down? If the Pats ran on 2nd and 3rd down and Seattle stopped them and called their timeouts, they still would have gotten the ball back on their own 40 or better, with a timeout left, and 40 seconds. Plenty of time to pick up the yardage needed to get into FG range.
I am sympathetic to the argument that the Pats might have had a better chance to pick up the first down by running instead of throwing. But I think their mindset was that they needed a first down in order to kill the clock. That part was correct. Once they threw it on 2nd down, they had to throw it on 3rd down.
So, 2nd down was probably the problem play. Run it there, see what you pick up, see if Seattle is willing to call timeout. Otherwise, half is over.
I was wondering about that as well. The ball was 5 yards OOB and they still called PI.Was there ever any explanation given for that endzone PI? The ball seemed clearly uncatchable no matter the contact.
The secondary has a good amount of experience. There should never be any plays where a guy like Metcalf just runs straight right by you. Not sure a LB makes any difference.One other thing I haven't seen discussed is the loss of Bentley - I wonder how much that hurt in terms of setting the D, communication, etc. Obviously the D still did a great job against the run, and most of the issues they had were in the secondary.
What drove me nuts on that call was that they didn’t call pass interference in the end zone on the previous Patriots drive when Stevenson was attempting to catch a pass in the back corner. A little consistency is all I’m asking for.I was wondering about that as well. The ball was 5 yards OOB and they still called PI.
And the more I think about it, the more I think that Seattle not calling timeout after the 1st down run for only 2 yards was a tell. Given the field position, the Pats bad offense, Seattle's good defense, and the amount of time / timeouts left, Seattle should have been really aggressive there trying to get the ball back. If the Pats ran on 2nd down and gained several yards, I really do wonder if Seattle would have called timeout. A run for 0, 1, or 2 yards and they are likely calling timeout. But If the Pats ran for 4 or 5 yards and got it to 3rd and short, Seattle might have just let the clock burn.You've nailed it precisely. You've got to run the ball on second down to either force Seattle to call a time out, or to burn down some clock, both of which would adversely affect Seattle's chances to score at the end of the half should they get the ball back. The Pats choice of throwing twice did neither, and it cost them badly. That's a terribly amateurish approach to game strategy. Mayo has to get better at that.
My own two cents is that this is definitely effect and also partly causeI read Seattle was stacking the box. Is that cause or effect of the lack of a passing game?
This is one of these things where I'm not going to disagree with SJH and others about this drive. To neither get the first down nor burn clock is not what you want. And if you're Mayo you top priority should be to burn clock.Can we discuss the end of the first half?
So, 2nd down was probably the problem play. Run it there, see what you pick up, see if Seattle is willing to call timeout. Otherwise, half is over.
Agree on the Metcalf playThere should never be any plays where a guy like Metcalf just runs straight right by you.
No idea what went on with the secondary yesterday but it clearly wasn’t a very good performance for a unit that needs to be a consistent strength.
Yup, playcalling is like poker.This is one of these things where I'm not going to disagree with SJH and others about this drive. To neither get the first down nor burn clock is not what you want. And if you're Mayo you top priority should be to burn clock.
At the same time I'm not too worked up about it. In football you can get into this mental version of "the situation calls for X, so I'm going to do Y, but they're going to expect that, so I'll do X, except they're going to expect that I'm going to expect that, so..."
They tried something a little counter-intuitive and if it worked there would have been another little moment that contributed to the sense of "hey, this team is better than I thought". And it didn't work. It happens.
Yeah.This is what it looks like. The defense is good, the offense is garbage. They’ll play a bunch of one score game. Flip a coin any given week.
No pressure up front, inexcusable breakdown in the secondary on the Metcalf TD, and of course allowing Seattle to freely drive to both tie and win the game.According to NextGen, the #Patriots rank 31st in pressure rate on defense (24.1%) and dead last in pressure rate from a four-man rush (16.9%). On the other side of the ball, the Pats have allowed the second-highest pressure rate on offense (44.3%).
That's one stat. An important one, no doubt. But one stat.I would slow our roll on the "defense is good" talk:
Lazar on twitter:
No pressure up front, inexcusable breakdown in the secondary on the Metcalf TD, and of course allowing Seattle to freely drive to both tie and win the game.
We have overrated this defense because last year the offense was so historically bad we were not able to calculate the D's true level of play. The defense was better than the offense yesterday but that doesn't mean they were good. No Barmore is a crusher up front.
The offense is by far the bigger problem, but last year blinded us to the issue the defense has as well. No pressure yesterday, no forced TOs, and Geno completed 33 passes. Just not enough impact which played a huge part in the loss. Perhaps not as big as the offense, but a huge part nonetheless.That's one stat. An important one, no doubt. But one stat.
I agree that we overrate the D somewhat, but I also think the D has largely played well enough to win games (both last season and this season so far).
The real problem is the O, as it has been for a while now.
It was a weird mix of too aggressive and too conservative at the same time. They've stopped Seattle on 3rd down at 1:43. The clock is running, but Seattle is of course not calling timeout. The Pats used their first TO there. That seems like conventional usage, but they could have let it run down to 1:03. They're only down 1 point, Seattle's punter is a weapon, and the absolute best you can hope for is a touchback.Can we discuss the end of the first half? I'm not sure I am in agreement that the Pats botched it (on offense; not talking about ST and D here), but I am open to changing my mind.
To reset:
- ball on the Pats 8
- 1:28 to play
- both teams had all timeouts
- the Pats ran for 2 yards on 1st down; Seattle did not call timeout
- the Pats threw incomplete on 2nd down (0:54 left) and 3rd down (0:47 left)
So for those arguing that the Pats botched it - what would you have done? Run on 2nd down? If the Pats ran on 2nd and 3rd down and Seattle stopped them and called their timeouts, they still would have gotten the ball back on their own 40 or better, with a timeout left, and 40 seconds. Plenty of time to pick up the yardage needed to get into FG range.
I am sympathetic to the argument that the Pats might have had a better chance to pick up the first down by running instead of throwing. But I think their mindset was that they needed a first down in order to kill the clock. That part was correct. Once they threw it on 2nd down, they had to throw it on 3rd down.
So, 2nd down was probably the problem play. Run it there, see what you pick up, see if Seattle is willing to call timeout. Otherwise, half is over.
I think we just disagree on the "huge part" aspect.The offense is by far the bigger problem, but last year blinded us to the issue the defense has as well. No pressure yesterday, no forced TOs, and Geno completed 33 passes. Just not enough impact which played a huge part in the loss. Perhaps not as big as the offense, but a huge part nonetheless.
Good point about calling timeout after the 3rd down stop, I had forgotten about that. I get that it looks "wimpy" if they just let the clock run but maybe that was the more prudent play.It was a weird mix of too aggressive and too conservative at the same time. They've stopped Seattle on 3rd down at 1:43. The clock is running, but Seattle is of course not calling timeout. The Pats used their first TO there. That seems like conventional usage, but they could have let it run down to 1:03. They're only down 1 point, Seattle's punter is a weapon, and the absolute best you can hope for is a touchback.
If it's a touchback, Pats should still have had enough time at around :57 and three timeouts IF they can hit one good-sized play to get into FG range. If they can't (and it turns out they couldn't), then letting that 40 seconds go makes it virtually impossible for Seattle to tack on that last FG. So letting the clock run on Seattle's 4th down doesn't eliminate a FG opportunity for the Pats, but probably would have for Seattle, barring a turnover.
Defense had a good game against the Bengals, albeit helped by turnovers. And a bad game against the Seahawks. Not ready to say they are bottom quarter of the league bad, as the pressure stats can be misleading over a small sample. But they may be at best mediocre on defense.The offense is by far the bigger problem, but last year blinded us to the issue the defense has as well. No pressure yesterday, no forced TOs, and Geno completed 33 passes. Just not enough impact which played a huge part in the loss. Perhaps not as big as the offense, but a huge part nonetheless.
The defense has faced 20 drives this season, allowing 1.65 points per drive. The defense has forced 9 punts (8 3-and-outs), 2 turnover on downs and 1 turnover.The offense is by far the bigger problem, but last year blinded us to the issue the defense has as well. No pressure yesterday, no forced TOs, and Geno completed 33 passes. Just not enough impact which played a huge part in the loss. Perhaps not as big as the offense, but a huge part nonetheless.
Not Gonzalez, who looked like he didn't get the "we're not playing zone" message on the Metcalf TD.The secondary has a good amount of experience. There should never be any plays where a guy like Metcalf just runs straight right by you. Not sure a LB makes any difference.
No idea what went on with the secondary yesterday but it clearly wasn’t a very good performance for a unit that needs to be a consistent strength.
This is simply not true - Dugger took accountability for this mistake. Gonzo has been elite all season (and last)Not Gonzalez, who looked like he didn't get the "we're not playing zone" message on the Metcalf TD.
Duggar took responsibility for calling the max blitz. I can't imagine the result of that was supposed to be that *he* (and not Gonzalez) was supposed to cover Metcalf on the fly, while Gonzalez covers the RB lined up wide. It's the tweeter's opinion that it looked like Duggar jumping the route left Metcalfe open. It *looks* to me like Gonzalez let Metcalf go expecting help. I dont particularly care if I'm wrong about that play, but I dont think that tweet goes quite as far as suggested. (There were two wide guys and two DBs. Both wide guys were open). If, as suggested, Duggar was supposed to drop deep, Metcalf would have flown by him (because Duggar can't stay with him) while Gonzalez remains pasted to the guy lined up outside, which was a RB. That doesn't seem right to me.This is simply not true - Dugger took accountability for this mistake. Gonzo has been elite all season (and last)
There was talk yesterday after the game that the Pats may have been tipping their plays.We all knew the offense was going to be shit but being ultra-conservative on top of it is just so disappointing from an entertainment standpoint.
And this is why the All-22 is so valuable. Great play design that should have been an easy TD like you said. But JB was running for his life and we were lucky to get even anything out of it.There was talk yesterday after the game that the Pats may have been tipping their plays.
Also, the scheme has opened up some stuff, but the OL.... With any blocking at all, this is a walk-in TD. Henry chips, but Robinson doesn't get there in time to keep the rusher outside.