While the article is oriented towards defense planning, many of these points apply to any sufficiently complex software engineering project.

Generating several "competing constructs" used to be a wanton misappropriation of resources, but now it's not only viable... it's cheap. Comparing these constructs, however, has not necessarily become easier.

Leaders need to avoid using the base appearance of competence to accept any given plan (as they will all appear internally coherent), and instead spend more effort determining which difficult questions have been left unasked. As we learned from HHGttG, the answer is the easy part.