Ok, caveat I know chatGPT is kinda ass, but still. I like to have fun running scenarios.
Here's what it thought of that post Marv bobble INT series:
You’re not crazy—that was a trust-and-sequencing failure more than a “protect field position” choice.
Here’s why an OC doesn’t go right back to WR1 after a bobble-INT—and why that logic fell apart Thursday:
Recency bias after the pick. Because the ball went off MHJ’s hands, some OCs default to “cool him off, settle the QB.” But the right way to settle is with easy confidence touches, not silence. Even Kyler acknowledged the offense has been “too all over the place,” which is exactly when you simplify reads to your alpha.
Field-position fear + sack anxiety. Arizona had already eaten six sacks; that nudges coordinators toward low-aDOT calls to RB/TE or a safe run-run-throw sequence. The problem is you can be “safe” and still feature MHJ (screens, RPO glance, keeper flood). Playing scared simply produced a dead series.
Coverage paranoia. If staff feared bracket/double, that’s when you manufacture MHJ: stacks/short motion, quicks and glance RPOs. Instead, they treated the bracket as a reason to go away rather than a reason to scheme him open. Kyler’s postgame made clear he wanted to keep coming back to Marv—and did in Q4, where he went 5-for-5 to MHJ.
Process over player. Petzing’s offense has been criticized locally for predictable sequencing and an allergy to mid-game adjustments (horizontal quicks → inside run → 3rd-and-medium). That tendency showed up in the exact moment the game begged for a targeted, psychology-aware script.
Why I agree it was a defining coaching moment:
Your WR1 had a confidence fracture, your QB was pressing, and you’re coming out backed up. That’s textbook two-touch rule territory—script a quick screen/now to MHJ, then a keeper flood or duo-glance RPO with him first in the progression. Arizona didn’t. They got “safe” without giving their star a low-stress win, lost the series, and bled leverage in a one-score game they ultimately lost on a thin margin (and a special-teams gaffe).
-------
Here’s the clean takeaway:
Player psychology > playbook. After a high-leverage mistake, WR1 needs two fast, low-stress wins. Arizona chose “safe” without the confidence touch—that’s bad coaching, not bad luck.
Sequencing lost the room. Backed up? Fine—be safe. But “safe and intentional” means screen/flat/glance to MHJ, not hide him. That series screamed “we don’t trust our star”.
Kyler felt it. When the QB doesn’t believe in the sequence, execution drops. You saw it.
If you want a simple litmus test for next week (what you and I would grade on):
Two-Touch Rule: MHJ gets 2 touches in the first 10 snaps and 2 within 4 snaps after any negative play.
Under-center PA as a feature: at least 4 true PA shots in the first 25 plays (with one to MHJ).
Tempo pockets: go no-huddle right after any explosive (≥18 yds).
Constraint answers: after two runs from heavy, hit TE pop or glance—no “run-run-obvious pass.”
Coming-out script: inside your own 20, zero long-developing drops—move the launch point, get MHJ an easy ball.
If they don’t hit those five, that’s not personnel—that’s play-caller.
-------
This is why I was so pissed. I coach freaking girls varsity basketball and I'd never let my star player get iced like that after a mistake. Petzing is just a TERRIBLE coach. At all elements of coaching.