@texasag1969 said: He needs to get with his players and his O coaches and work this out far in advance of game day. He goes into brain freeze the closer they get to the goalline. Someone has to become the OC whisperer in his ear and remind him what they are doing on the plan the closer they get to scoring. AND no TOs early on dammit!! I have to agree.  Seems like he goes into "brain freeze" mode every time (almost every time) we're near the darn goal line.  I've brought it up a dozen times, but I'll bring it up again:  The last game of 2016 when we needed a TD to WIN THE GAME, and he calls the WR screen to Hawkins that loses 7 yards or more.  That did it for me.  The game didn't mean a thing for the Steelers, but it would've been nice for our team and our fans, and that might've been the worst play I've ever seen in my entire life.  With the game on the line.  Against a rival.  Jesus. And that's not an isolated incident by FAR.  Remember the 2016 Redskins game?  We had a lead (remember those?) and we were in the red zone, moving the ball up and down the field, and then Hue calls a running play with our young FB who I don't believe EVER carried the ball before in the NFL (I could be wrong, but don't think so).  Now, obviously Hue didn't fumble the ball.  Crow just ran several long plays and was winded.  Duke might've been injured.  Regardless, is that REALLY the best time to hand the ball off to that guy?  Again, fumbling the ball isn't Hue's fault, but COME ON.  Even a FG there puts so much pressure on the opposition (I forget how many we were up...maybe 10?).  Anyways, there are more and more situations I can bring up that call into question Hue's ability to finish off a drive.   Hue didn't throw the interception against the Jets, and he didn't throw the awful pitch to Crow.  He also wasn't the guy that failed to FALL ON THE DANG FUMBLE.  But an option?  UGH.