Indeed, there's a shitload of information in that black and yellow op-ed piece, much of which has a great deal to do with the successes of the players in the last two minutes of halves and games, and much less to do with actual clock management, but the author loses his credibility completely with the statement: "The first half of the season saw no errors in clock management." Is that so? That sounded a bit far-fetched to me, so I decided to do some research of my own.
With minimal effort, simply looking at the KC game, and the KC game only:
The Steelers did not score in the last two minutes of the first half; they got the ball with nearly nine minutes on the clock on their own one, drove 93 yards, and settled for a Boswell field goal at the 2:08 mark. Nothing at all to do with any clock management mastery here.
After a touchback, the Chiefs proceed to get one first down, then there's a six-yard sack. Then a false start. Then offsetting penalties. Then another sack for 9 yards. So it's 3rd-and-30 for KC on their own 17, with over 20 seconds left in the half, and Tomlin decides to keep his three timeouts in his pocket and allow the opposition to take it into halftime.
Why not at the very least force a punt from deep in their territory? Was he living in his fear of a 30-yard third down conversion? No, it was a clock management error in a tight road game.
And toward the end of the very same game, when Pittsburgh threw the ball on 3rd-and-8, it wasn't some brilliant aggressive strategy from Tomlin, it was a gift from Andy Reid, who foolishly called time out with 2:05 on the clock, essentially allowing the Steelers to pass (because in this case, the clock stops at the 2-minute warning whether they run the ball or not, so it is now a no-brainer to throw it), and taking away a tough decision from Tomlin.
Game-managing excellence? Hardly.