So the planning ends up being one of the more useful things to do because it prepares you for both your intentions but also to handle things when they fail (in some fashion). The plans, themselves, are useless because they will very rarely be carried through as written. You can't just read a plan and memorize it and expect to carry it out in an adversarial situation. If you're lucky, or your adversary is severely outmatched, then this can work. However, you can't count on luck and you can't count on your adversary being unprepared or incapable or incompetent.
Planning, contrasted to plans, prepares you (or should) for when the plans fail and you have to adapt and overcome in the field.
The enemy gets a vote
This generalizes beyond what's strictly though of as a "plan" (but if you squint enough may have some plan-like elements to it).
There are many forms of documents that we engineers produce and they serve different purposes at different times. And some of their uses may not be very effective in most cases, leading to wasting too much time in over-specifying a system that has not yet been built.
Yet, writing design documents / specs may be still useful despite the output not being useful. It's the act of writing it that yields most value.
I thought I added a nuance to what Eisenhower's said (or at least to how I noticed people interpret it) but apparently I did a poor job and adding more words would just make it worse.
An aphorism by definition doesn't contain all the nuances. If we looked through Eisenhower's whole life, which is pretty well documented, I'm sure we could find lengthy explanations of his approach to war.
What I try to add here is the fact that other forms of technical writing can be seen as forms of planning and thus there is a connection between the two aphorisms
In this world, there is no way to have a tyrannical plan.
So I've been studying a lot about WW1 recently and one of the things that struck me was the incredible similarity between how many of these generals operated in the early years of the war. With detailed down to the minute plans that would account for everything, trying to be more and more precise, and how the bigwigs on a software project operate, with a belief that if they can just nail things down more tight and make sure they've got every dependency mapped out they'll finally make it work and it will avoid other problems.
The results are the same as the WW1 battles the first part goes well, things seem to flow along as predicted everything is great in the first day, but as things go on reality diverges more and more from the plan and the more people insist on the plan the worst things get because they haven't been able to adapt to the real world.
My point is the tighter and tighter your plans are and the more comprehensive they are and the more autonomy they take from individuals on the ground doing the actual work, the more likely it is to go poorly and the more catastrophic it will get the longer you push on.