If this is his point, he's a lousy writer.
Blank is talking about acknowledging and dealing with risks early.
True that. He also mentioned firing people for not complying with his new rules several times. And also that he did. Those seem like the more substantive acts of his reign, as communicated in this post.
However, we don't know the exact circumstances behind the firings. I'm giving Steve the benefit of the doubt that he didn't fire folks who slipped deadlines just once, but removed though who consistently didn't deliver or acknowledge risks early.
Effective policies need teeth. Particularly if your company is in a lean position (emerging from bankruptcy). It reminds me of the "War time CEO" chapter from Ben Horowitz's "The Hard Thing about Hard Things".
My interpretation is he's simply advocating that if someone is aware of an issue that will set a project deadline back, don't keep it a secret and surprise everyone when the deadline isn't met.
Instead of "management by fear", build a culture where missing meeting deadlines is OK as long as a valid reason was communicated to the stake holders BEFORE the due date (no surprises). If a someone who's a project dependency had a family member pass away which will likely lead to a project delay, Blank is suggesting that's something that can be communicated honestly + transparently to a superior (and very much understandably - should be no fear involved). The upside is the superior can potentially reallocate resources to keep the project on track while not be getting caught off guard with a project unexpectedly derailed.