Again and again I am flabbergasted that staff officers (who are used to NATO staffs) consider staff procedure speeds fine that I consider to be pretty much suicidal.
I assume that this post will settle this issue once and for all at least for my private communications. From now on I will simply give the link to this when someone has suicidal ideas about proper staff speeds.
- - - - -
Back in 1940, on May 13, there was a battle that basically meant the destruction of the French army and the (temporary) loss of French sovereignty was ensured.
I have no doubt that emulating the French in this battle is unacceptable to EVERYONE, and thus should make the modern staff craziness obvious.
The action - crossing the Meuse river at Sedan after a few days of surprise advance through the Belgian Ardennes - was planned in detail as early as March, and rehearsed in a wargame on May 1st. The plan worked reasonably to spectacularly (reasonable in details, spectacular in effect) and was executed very close to original planning.
Yes, planning well in advance has at times benefits. That's what enticed NATO armies to create huge and ponderous staffs, after all. Hint: The French had planned much and wargamed themselves as well. The planning was done while there was no mobile warfare happening.
The surprise river crossing began with major air attacks.
1200: Major air attacks give away the site for the river crossing
1600: Infantry crosses the river.
2240: Dominating heights 8 km behind the crossing site taken by German infantry.
Now the French side:
1600: French General Grandsard (Corps commander) orders the corps reserves forward.
1730: Order arrives (apparently by motorcycle courier) at infantry regiment 213.
1800: Order arrives at Armour battalion 7.
1830: Infantry regiment 213 commander LtCol Labarthe orders to commence the march at 2000 (happens with delay).
2000: French division commander General Lafontaine orders counterattack after some confusion
2130: Armour battalion 7 begins its march.
0730: Begin of counter-attack
(The French side had a corps staff delay of 0-4 hrs depending on where to start the count, and a division staff delay of up to 4 hours. The total delay from revealing the location of the attack and counteratttack was 19.5 hrs.)
Now again the German side:
The German top officer on the scene of the counterattack, LtGen Kirchner, took ten (10 !) minutes to think up and issue orders for the German reaction to the counterattack.
Keep in mind: Most of the German Sedan attack was an infantry attack with foot mobility. The first German tanks crossed the Meuse on 0720 on the 14th. These tanks still won the speed competition against the French tanks which began their counterattack apparently at 0730 and had a shorter route to the critical point.
This is the battle that laid the foundation for the notion that the French lost the campaign of 1940 decisively within days because their command system was too slow to cope with the German command system's agility.
Yes, they were slow - in relation to the Germans of May 1940.
On the other hand, the French were extremely fast - in another relation.
Under some in-NATO national doctrines, staff procedures wouldn't have allowed for a counterattack order within four hours. Instead, staff procedures would have required a multi-layer process with info collection, processing, meetings, deliberations ...
Sure, a modern senior officer on the scene could (IF he was on the scene) issue reaction orders in ten minutes as well.
The problem is that this is not what doctrine and training emphasize.
Western forces train for slowness (a.k.a. thoroughness) more than for quickness.
- - - - -
Another problem for the '12 hrs staff procedures are quick enough' school of thought:
An attack of part of the 7th Panzerdivision (Rommel) began on 16th May at 1800.
1800 Attack begins.
2400 30 km advance already, French 5th motorised Division is being overrun in its resting area along a road and is being obliterated by parts of the 7. PD.
0600 7. PD forces cross the river Sambre.
0630 Regiment-equivalent advance guard reaches Le Cateau at 50 km depth.
That's about 12 hours. By now the '12 hrs staff procedures are quick enough' school would have prepared an order to react to the initial beginning of the attack.
Keep in mind that the tanks of this time reached only up to 40 km/h and were unable to shoot on the move accurately. Today's mounted combat and attacks can be much, much quicker.
- - - - -
Well, if ANYBODY does EVER again attempt to convince me for example that a 12 hrs planning cycle (or even something with up to 48 hrs !) is fine ... I'll simply tell him to read this.
Maybe I'll also tell him to forget everything he ever learned about staff procedures.
S O
P.S.:
Military history offers an incredible quantity of examples that smash slow staff proponents. I was lazy and took both examples and their details from Frieser's book.
Military history offers an incredible quantity of examples that smash slow staff proponents. I was lazy and took both examples and their details from Frieser's book.
edit: Another broad hint - the 2005 study "Trading the Saber for Stealth [...]" (I mentioned this nice study earlier) says:
For example, during the typical "high-intensity" rotation at the NTC, battalion and brigade commanders are required to solve a new tactical problem approximately every 48 hours. During the offensive maneuver portion of Operation Iraqi Freedom, commanders found themselves dealing with new and complex tactical problems on the order of every eight to 12 hours.