(11-25-2019, 09:00 PM)cardcrimson Wrote: My post wasn't about the one play, but the mentality that Shaw would take that match up all day long. Kinda like running the ball between the tackles four straight times against MSU, cause "that's what we do". Shanahan is unpredictable and finds very creative ways to get his best players involved. Jump balls and curl routes just don't cut it anymore.
I am willing to wager that Shanahan would take Kittle matched up with Blake Martinez all day long, if he could.
(11-25-2019, 09:18 PM)BostonCard Wrote: I wonder, what happens when/if the Niners start running this play more often. Does it keep working every time, or is there something that a savvy defensive coordinator, seeing the play on film, can counter-scheme. Would Kittle always be wide open because this is an indefensible play? I doubt that. The question is whether you still can get a decent match-up (and Kittle being an elite tight end, you probably can) even if the defense covers it. I don't think you can always count on your receiver wide open, so then it will require the offense to execute the play. If it truly is schematically indefensible, then shouldn't the Niners be running it every single time?
Same story with Mills' touchdown passes to a wide open Fehoko against both UW and Cal. You can make an argument that "scheme" was responsible, but more likely it was a combination of the play call being effective against what the defense was trying to do. In this case, we called the right play at the right time, but that doesn't mean that it was an indefensible play.
BC
Totally agree. If Cal doesn't blitz, Fehoko has to beat one-on-one coverage. It is still a "good" play call, just not a slam-dunk wide open one. Fehoko can probably run by the guy, but he has to do it. There is no immediate help over the top. If they do blitz, and the Safety reacts quicker, we get a big gain but not a TD, unless the Safety misses the tackle (which can happen). If Fehoko keeps running full speed, he runs right into the coverage by the Safety, so it is essential he recognize that and slow up a bit, which he did. Rector messed this exact play up several times back in the day by running right into coverage. Another example where execution can mess up a great call.
