You would likely love Malcolm Keyune's writings on this topic of the balance of power shifting due to drones and more inexpensive ballistic/anti-ship missiles obviating naval armadas and even traditional air power (to an extent).
Philip Pilkington also had a great piece in American Affairs about the economics of this shift.
Also a foundation of basic networking principles will to an extent help the Fish know he’s in water.
Help, not it’s a magic cure. Basic networking principles as foundation are , ah, er... 120 years of catching up. Call it Recognition of Military Affairs.
Right now the Fish is (to really mix the metaphors) still on Horseback, sending dispatch riders (the antiquated staff processes) and never adapting to the Telegraph, we got by on massive voice communications, we got farther on crypto and frequency hopping, the contemporary IEW (Electronic Warfare) we’re seeing may make a lot of chatter fatal indulgence, we can either start changing or wait upon an enemy as change agent.
I think for some time we need to align the staff process Forms with the 21st (or 20th really) century Functions; which means we acknowledge the radio changed things, the networks even more.
The Napoleonic Dispatch rider form, the Napoleonic staff, Napoleonic Staff, and the almost pre “wireless sets” Operations Order of the Sacred Five Paragraphs... is a full *Review* not in order?
It’s “Review”.
======
Now as that is much easier stated than done - what to do?
-------
From the Networker view and networking duty and tasks, start with the basics;
1. Logical Topology of the staff information flow you either *actually* use or NEED.
2. Apply basic network management principles- like say network segmentation on SIPR, for example.
3. I suggest the Topology for staff communication-coordination start with a grid - just as switching fabric for all time has - any logical overlay can then be applied on top as OverLay- this is basic networking since the first switchboards and also familiar to us as our maps grids.
----
If you start with the basics and a foundation it’s easier to understand and build.
-----
If as we now do we use Whatsapp to operate by exception around our French Staff rituals, well ... then we’ll just keep firing Lasers from Horseback I guess.
You would likely love Malcolm Keyune's writings on this topic of the balance of power shifting due to drones and more inexpensive ballistic/anti-ship missiles obviating naval armadas and even traditional air power (to an extent).
Philip Pilkington also had a great piece in American Affairs about the economics of this shift.
Thanks dude
Last note;
Glad we can whack all the moles although HAMAS may just have vitiated this concept, if the moles don’t use the cell phone...
What if they’re not moles?
What if they have air parity?
IEW parity?
Artillery parity (or overmatch)?
Ground game competence parity?
Then it becomes the better organization. Napoleon didn’t have better cannon, rifles, muskets or horses.
He had better systems (much of which he inherited) and an excellent teacher in Bourcet.
Bourcet had better skills than many, and he taught them to a young artillery officer named Bonaparte.
-----
Now you’re understandably looking at this from intelligence targeting, I’m looking at it from Infrastructure (Signals, Communications, the network).
Your points are valid.
So are mine, you’re trying to do Star Trek with staffs designed for Horseback...
That’s it ! Thanks for bringing up these vital topics.
Data myopia
What I am saying is we are wedded unto death to a staff model from Napoleon designed for horse dispatch riders and quill pens.
Not to mention unlike Napoleon we don't rise in rank by revolution and coup d'etat [at least not yet !]
Also a foundation of basic networking principles will to an extent help the Fish know he’s in water.
Help, not it’s a magic cure. Basic networking principles as foundation are , ah, er... 120 years of catching up. Call it Recognition of Military Affairs.
Right now the Fish is (to really mix the metaphors) still on Horseback, sending dispatch riders (the antiquated staff processes) and never adapting to the Telegraph, we got by on massive voice communications, we got farther on crypto and frequency hopping, the contemporary IEW (Electronic Warfare) we’re seeing may make a lot of chatter fatal indulgence, we can either start changing or wait upon an enemy as change agent.
They have the same tools.
They might get there faster.
I think for some time we need to align the staff process Forms with the 21st (or 20th really) century Functions; which means we acknowledge the radio changed things, the networks even more.
The Napoleonic Dispatch rider form, the Napoleonic staff, Napoleonic Staff, and the almost pre “wireless sets” Operations Order of the Sacred Five Paragraphs... is a full *Review* not in order?
It’s “Review”.
======
Now as that is much easier stated than done - what to do?
-------
From the Networker view and networking duty and tasks, start with the basics;
1. Logical Topology of the staff information flow you either *actually* use or NEED.
2. Apply basic network management principles- like say network segmentation on SIPR, for example.
3. I suggest the Topology for staff communication-coordination start with a grid - just as switching fabric for all time has - any logical overlay can then be applied on top as OverLay- this is basic networking since the first switchboards and also familiar to us as our maps grids.
----
If you start with the basics and a foundation it’s easier to understand and build.
-----
If as we now do we use Whatsapp to operate by exception around our French Staff rituals, well ... then we’ll just keep firing Lasers from Horseback I guess.