[teejers1]

I assume you mean Stanford's second to last drive of the half, second and 14 from the Beav 34 with 1:30 left. 
At that point they were still playing to get the first down and to have time remaining for a TD.
Stanford took a time out after the sack on first down.
Second down was a short, high percentage completion to Fehoko. It was a hard out, with a high likelihood of ending up out of bounds (which it did). At that point, they were still trying to save clock. Maybe a little reckless, but not crazy if you are trying for a TD.
I'd take more issue with the third down call. There was a reasonable chance of popping a draw for a first down, which would have the extra benefit of allowing for a clock stop on making a first down if successful, but also allowing for running another 40 seconds off the clock if not.

Of course as things turned out leaving the Beavs some clock didn't harm anything, and but for a holding call that extra time would have ended up allowing a bonus TD on the last play of the half.

Maybe that was the down I was referring to, though I thought Stanford was more in midfield area.  Regardless, the play should NOT be one that likely ends up stopping the clock (as the Fehoko sideline pass did).  Maybe that's what chapped me most.

The problem with running a draw play on third down (or any play that comes up short of sticks) is that on fourth down OSU will definitely call a timeout to preserve clock for their final drive.  If you do it on second down - OSU may be burning a TO without any guarantee of getting the ball back.  Given that we stopped the clock ourselves, we failed to put OSU to that conundrum and permitted them to save a timeout.  Real time, this seems like very basic clock management to me, as we had plenty of time to score from where we were without worrying about clock stoppage.  People may say that reasonable minds can differ on this, but I disagree.  It struck me as basic clock mismanagement.

Now, Shaw isn't alone in this - but he has made so many of these kinds of mistakes over the years that I can only attribute it to fundamentally not getting it.  But if it's any comfort, Shaw isn't alone.  Shanahan, as great an offensive mind as he is, has demonstrated clock management blindness himself.  Think he is at 3 such situations already with the 'Niners, the most egregious being in game against Seattle in Super Bowl year regular season where there was no way on God's green earth that the Seahawks, who had no timeouts remaining, should have ever seen the ball in OT again.  But because Shanahan went pass, pass (inc), pass (inc.), they did.  And Seahawks won.  

Part of basic game clock management is removing worst-case downside at EOH and EOG.

[teejers1]

I assume you mean Stanford's second to last drive of the half, second and 14 from the Beav 34 with 1:30 left. 
At that point they were still playing to get the first down and to have time remaining for a TD.
Stanford took a time out after the sack on first down.
Second down was a short, high percentage completion to Fehoko. It was a hard out, with a high likelihood of ending up out of bounds (which it did). At that point, they were still trying to save clock. Maybe a little reckless, but not crazy if you are trying for a TD.
I'd take more issue with the third down call. There was a reasonable chance of popping a draw for a first down, which would have the extra benefit of allowing for a clock stop on making a first down if successful, but also allowing for running another 40 seconds off the clock if not.

Of course as things turned out leaving the Beavs some clock didn't harm anything, and but for a holding call that extra time would have ended up allowing a bonus TD on the last play of the half.

Maybe that was the down I was referring to, though I thought Stanford was more in midfield area.  Regardless, the play should NOT be one that likely ends up stopping the clock (as the Fehoko sideline pass did).  Maybe that's what chapped me most.

The problem with running a draw play on third down (or any play that comes up short of sticks) is that on fourth down OSU will definitely call a timeout to preserve clock for their final drive.  If you do it on second down - OSU may be burning a TO without any guarantee of getting the ball back.  Given that we stopped the clock ourselves, we failed to put OSU to that conundrum and permitted them to save a timeout.  Real time, this seems like very basic clock management to me, as we had plenty of time to score from where we were without worrying about clock stoppage.  People may say that reasonable minds can differ on this, but I disagree.  It struck me as basic clock mismanagement.

Now, Shaw isn't alone in this - but he has made so many of these kinds of mistakes over the years that I can only attribute it to fundamentally not getting it.  But if it's any comfort, Shaw isn't alone.  Shanahan, as great an offensive mind as he is, has demonstrated clock management blindness himself.  Think he is at 3 such situations already with the 'Niners, the most egregious being in game against Seattle in Super Bowl year regular season where there was no way on God's green earth that the Seahawks, who had no timeouts remaining, should have ever seen the ball in OT again.  But because Shanahan went pass, pass (inc), pass (inc.), they did.  And Seahawks won.  

Part of basic game clock management is removing worst-case downside at EOH and EOG.