re: Replay GIFs from the game last night....

quote:

---

It might be nit picking since it was still a 20 yd gain. But on the cross to Racey (if that’s the one I think you’re referring to) watch the replay. You’ll see Terrace break open deep across the middle at the same time he’s about to throw to Racey and it would have been a TD. You’ll see Terrace kind of throw his hands up because he knew it too and he seems a little tired of Myles not seeing it. When Myles starts making that throw, he will have arrived. It’s there often and he’s just not seeing it or not ready for it or whatever. Check it out though. He needs to start hitting those.

---

If WRs are doing there job, there will always be some of this.

I'd much rather our QB pull the trigger fast and choose the lesser of two open WRs than hold the ball waiting on one.

I know that above is exactly what happened, but I'm speaking to the QBs mindset. In his progressions, which vary play to play and if he sees a completion... pull the trigger. When you hesitate to try to decide the best of multiple options you get into trouble.

As long as we're getting 1st downs (AND WRs are doing their job) we can always come back to it and modify the progressions.

Our progressions in this offense are read based. Not fixed. For example, Cam Cameron's progressions started deep and worked down to the LoS. Which is fine, but often caused the QB to hold the ball too long and by the time the determination of deep was made, the shorter routes had already flashed open and were now covered.

Here, things such as leverage, safety, or pressure decide where you look first. And if the read says X, and X is open... you pull the trigger. If Y is open on that play, you adjust your reads (because the D will adjust to X), and you come back to Y.

You hate to see a QB miss an open WR deep, but if it is because of a completion it is NOT a problem. If a QB doesn't see a WR deep and there wasn't another option... you have a QB problem.