Meditations on Moltke

I.

Every few years, a new book comes out telling executives that the secret to high-performing organisations is — surprise, surprise — giving your employees clear goals instead of detailed instructions and then trusting them to execute these. The book then sells a million copies. People put quotes from it on LinkedIn. Consulting firms sell six-figure transformations. Then everyone goes back to micromanaging and a new book comes out in three years saying the same thing in slightly different words.

I find this funny because the entire intellectual edifice — mission command, decentralized execution, commander’s intent, the whole “context not control” gospel — comes from a melancholic Prussian field marshal living in the 19th century.

II.

A quick sketch of the man, because he wasn’t quite what you would expect.

If casting sent you a Prussian field marshal, you would probably get a beefy shouter with a fancy mustache and an even fancier monocle. Moltke was the complete opposite of that. He was thin, ascetic, terrible at dinners, and so quiet that a contemporary joke held that he could be “silent in seven languages”. He translated Edward Gibbon’s Decline and Fall of the Roman Empire into German, partly for the money and partly, one strongly suspects, because he actually enjoyed it. In other words — he was a nerd.

He was born in 1800 into the kind of minor Mecklenburg nobility that had an impressive surname and almost no money. The family farm wasn’t really working out, so his father took a commission in the Danish army and moved the household north to Holstein (which was Danish territory back then). The timing turned out to be remarkably terrible, because shortly afterwards French troops invaded and the family estate was burned in 1806. By the time Moltke was a small boy his family was, as the diplomats used to put it, “embarrassed” — which is just a polite German aristocratic word for “broke”.

So at eleven he was packed off to the royal cadet school in Copenhagen, served briefly as a page in the Danish court and was commissioned into a Danish infantry regiment in 1818. Here Moltke faced the problem that Denmark was actually a relatively peaceful country and their army didn’t really promise a future. This is why in 1822 he transferred into Prussian service, sat for the officer exam a second time and was commissioned as a lieutenant again — this time in Prussian colors. He had effectively restarted his life.

This turned out to be a great decision. You see, the Prussian army had something the Danish army did not, which was the War Academy in Berlin — an elite three-year program for budding officers. The program had been recently overhauled by the reformers Scharnhorst and Gneisenau, and it left a major imprint on Moltke. He graduated in 1826 and spent the next decade doing the unglamorous staff work that nobody else wanted: surveying terrain, drawing maps, writing articles for military journals and picking up languages. This is also when he translated all six volumes of Gibbon. It’s just what you do in your spare hours as an underpaid Prussian lieutenant in your thirties.

Then, in 1835, he got restless, took some leave and traveled — meaning to spend a few weeks in Constantinople on a nice vacation. Instead, he had the good — or bad — luck (depending on your perspective) to arrive at exactly the moment when Sultan Mahmud II was trying to modernize the Ottoman army along European lines. When the Sultan heard that a young Prussian staff officer was hanging out in Constantinople, he asked if he would mind hanging around to help out with the modernization program. Moltke asked Berlin for permission. Berlin shrugged and said sure, it’s not like there is anything else going on.

Moltke spent the next four years travelling all over Anatolia, the Balkans and Mesopotamia. He made detailed maps of regions that had never been properly mapped. He learned passable Turkish, advised on fortifications, and eventually — in 1839 — he ended up as a staff officer in the Ottoman army during its campaign against the Egyptian forces of Muhammad Ali. While Moltke himself served with distinction, at the battle of Nezib his advice was politely ignored and the Ottomans faced a disastrous defeat. Moltke had to escape on horseback and made his way home via Syria and the Black Sea. By then he had spent four years in a foreign army watching, in extraordinary detail, what happens when senior commanders refuse to listen to their staff and decide everything themselves.

Back in Prussia he decided to write it all up. His Letters on Conditions and Events in Turkey from the Years 1835 to 1839 was a quiet hit and made him modestly famous in the sort of circles that read such things. He spent the next two decades climbing the career ladder. He served as a personal adjutant to Prince Frederick. He kept writing on basically everything that was going on at the time — the Russo-Turkish war, military geography and even on railways, which turned out to matter quite a lot going forward. He held no major command and fought in no major battle. In 1857, at the age of fifty-seven, he was appointed Chief of the Prussian General Staff — a job that nobody considered particularly important.

This was about to change.

III.

Moltke had ten years between his appointment and his first war, and he used them the way you would expect a nerd with a clean whiteboard and strong opinions to use them: he reshaped the General Staff from the inside out according to his ideas.

The best place to start talking about Moltke’s intellectual framework is the famous quote, because most people get it wrong.

You have probably heard it as: “No plan survives contact with the enemy.” Or in the words of the great intellectual Mike Tyson — “everyone has a plan until they get punched in the mouth” — same idea with better PR. But Moltke didn’t actually say this. What he wrote, in an 1871 essay on strategy, was longer and more measured:

No operation plan extends with any certainty beyond the first encounter with the enemy’s main force.

These qualifiers matter. Moltke emphatically did not say that plans were useless. He merely said that the operation plan — the detailed scheme of who goes where on which day — has a half-life that expires on contact. But the planning itself does not expire. The thinking, the preparation, the wargaming, the development — those persist even after the plan itself has gone to shit. The beautiful map with the colored arrows might turn out wrong — but the thinking behind it is still important. In fact, all of this means that your planning should be much more exhaustive that you would think — because you just don’t know which of your preparations will turn out to be relevant.

This sounds obvious when stated plainly. But it’s not obvious in practice. The natural impulse of any large organization — doesn’t matter if military, corporate or government — is to write the plan, laminate the plan, present the plan to senior leadership in a fancy PowerPoint with twelve bullet points per slide and then become emotionally committed to the plan even after reality has voted no. The plan essentially becomes a hostage situation. Moltke’s intellectual project was a campaign against exactly this.

His breakthrough idea was called Auftragstaktik, typically translated as “mission command”. Although Moltke himself never used that word, he wrote it into practice through his Instructions for Large Unit Commanders and dozens of internal papers across the 1860s. The core idea is deceptively simple: instead of writing up a detailed plan, the senior commander communicates to a subordinate the objective, the reason for the objective and allocates resources. He then stops talking. He does not prescribe the route of march. He does not pick the formation. He does not tell the subordinate which hill to attack or when to eat lunch. He leaves it to the subordinate to figure out the “how”. This has the massive advantage that if the situation changes — and it will — the subordinate adapts, because he understands the why. There is no need to send a courier fifty miles to the rear to ask for new instructions and then sit around in a field for six hours waiting for the reply.

Note that this is not the concept of delegation. Delegation says “you do this task instead of me”. Mission command says “here is what I need to be true about the world by Tuesday, here are two divisions and a cavalry brigade, figure it out”. The difference is that delegation transfers a task while mission command transfers ownership of a problem.

IV.

So far, so great and every organization that is at least a little bit competent pays at least lip service to doing this approach. But Moltke’s real achievement was the recognition of the fact that this required certain things to be in place.

First, the senior officer has to be able to express intent clearly. This is difficult, because expressing an intent is much harder than expressing a task. “Capture the bridge” is simple. “Prevent the enemy from concentrating forces against our left flank before their Second Army can close the gap” is much harder. Most people, when pressed, will struggle to express intent, which usually results in an attempt to delegate a task dressed up as intent. Writing real intent requires you to actually know what you want and why, and be willing to say it plainly, which means that you cannot hide behind vagueness. Moltke’s own directives were famous for being terrifyingly short. Two paragraphs was often all it took.

Second, the junior officers have to be really good at their jobs. Again, it’s pretty clear what to do with the order “capture the bridge”. Prevent the enemy from concentrating forces against our left flank before their Second Army can close the gap? Suddenly your job became much harder. This is especially true when you operate on the ground, under pressure and with incomplete information — which tends to be true when you are fighting a war. All of this means that you need to select excellent officers and then exhaustively train them. Not something most major organizations are naturally good at.

Third, the parties have to trust each other. The senior officer has to trust that the subordinate will do something sensible with the ownership he has been given and not charge off toward personal glory. The subordinate has to trust that if he uses his judgment and things go badly, he will not be court-martialed for initiative. This is a culture problem, not a process problem, and culture problems can’t be solved by a memo.

But when all three conditions hold — clear intent, competent subordinates, mutual trust — you get an organization that operates at the speed of the people closest to the problem, which is fast, instead of the speed of the reporting chain, which is not. The other European powers were about to find this out the hard way.

V.

By 1866, the German chancellor Otto von Bismarck had engineered the political conditions for a war against Austria — the details of how are a masterclass in diplomatic arson that we do not have space for here — and Moltke was faced with something that no Prussian general had done in living memory: fight a major European power. This was a problem, because Austria had a big, professional army commanded by experienced and competent generals. But they were operating under exactly the kind of centralized command doctrine that Moltke had spent a decade arguing against.

Moltke’s plan was audacious and, to his more traditional colleagues, alarming. He proposed to advance into Bohemia in three separate armies on widely separated routes. This was, by the account of most generals, an insane idea. Napoleonic doctrine said that you concentrated your forces before battle, not during it. Marching in dispersed columns meant that any one of them could be caught alone and destroyed before the others arrived. Classic defeat in detail.

But Moltke had two advantages that his enemies did not account for.

The first was the railway. Moltke had spent years studying rail networks — boring, logistical and deeply unglamorous work — and understood that railways had changed the calculus of war. You could not move 250,000 men down a single road without creating a traffic jam that stretched all the way to the horizon. But you could rapidly move smaller columns down three rail lines simultaneously and converge them on the battlefield faster than a single concentrated force could march there on foot.

The second advantage was of course Auftragstaktik. The widely separated armies can only converge on schedule if the commanders can make independent decisions and respond to local conditions. If every decision has to go back to HQ and wait for approval, things rapidly fall apart. Moltke’s system turned out to be perfect for the railway age. Each army commander received a directive — here is where you had to be by when and why — and off they went. For example, when the First Army ran into unexpected Austrian resistance at Münchengrätz, the commander did not freeze and send a courier. Instead he fought them off, adjusted the timetable and kept moving.

Everything came together on July 3rd, 1866, at Königgrätz — the decisive battle of the war and one of the largest in European history at that point: roughly 440,000 men on the field. The Austrian army was extremely strong. The First Prussian Army attacked frontally and got stuck, pinned down and taking heavy casualties through the morning. For several very unpleasant hours the Prussian situation looked bleak.

Then the Second Army arrived on the Austrian right flank.

Its commander, Crown Prince Frederick William, had been marching hard through difficult terrain. He was late. His artillery was behind him. Normally under such circumstances you should have waited to concentrate. But Frederick William knew the intent: arrive at Königgrätz and hit the Austrian flank. He was at Königgrätz. He could see the flank. He knew the overall strategy. So he attacked with what he had.

That attack broke the Austrian army. The war was effectively over after Königgrätz — it had lasted a grand total of seven weeks. The quick Austrian defeat came as a total shock to the rest of Europe.

VI.

The Franco-Prussian War is, if anything, an even more dramatic demonstration of the same principles, mostly because the French army was even better than the Austrian — brave, well-equipped and very experienced — and lost anyway, and did so catastrophically.

The contrast was almost as if lifted from one of those textbooks that introduce agile and then showcase it against an imagined waterfall model just to show how bad it is. The French system was centralized to the point of parody. Orders flowed from Napoleon III (who despite the surname was not a military genius) and his staff in Paris, down through a sclerotically slow chain of command. French commanders were not encouraged to exercise initiative. When Marshal Bazaine found himself in a position to counterattack and break through the Prussian line at Mars-la-Tour, he did not do so, preferring to wait for orders instead. The orders did not come in time and he had to retreat into Metz, where Moltke sealed him in with 180,000 men. That was the end of one of France’s two main field armies.

The other one did not fare any better. Marshal MacMahon’s army marched north to relieve Bazaine and was herded — there is really no other word — into the fortress town of Sedan, where Moltke’s converging columns surrounded it from three directions. MacMahon was wounded. His replacement attempted a breakout and failed. On September 2nd, 1870, Napoleon III personally surrendered along with 83,000 men. An emperor and an entire army, captured in a single afternoon. The war technically ground on for a few more months after that — Paris was besieged, a republic was declared, guerrilla fighters harassed the Prussians — but the strategic decision had been made in just a few weeks. Again.

And once again, the critical difference was not courage, equipment, numbers or some inherent Prussian military superiority (just remember what had happened only seventy years before at Jena-Auerstedt). The French military was perfectly adequate both technologically and courage-wise. The difference was the doctrine. Local Prussian commanders could exercise authority and knew how to do so. Local French commanders could not.

Moltke spent the next two decades as the most celebrated soldier in Europe, though “celebrated” might be the wrong word for a man who so visibly did not enjoy the attention. He continued to write and lecture at the War Academy. He kept refining the General Staff system which the other European powers spent the next forty years trying to copy. He even served in the new Reichstag. He retired in 1888, at the age of eighty-eight, and died three years later. His last evening was spent reading in his study, which feels exactly on brand.

VII.

I want to be careful now, because drawing straight arrows from 19th-century Prussia to modern organization-building is exactly the kind of thing that will make a serious historian wince a little bit. The Prussian General Staff was embedded in a specific political culture, serving a specific autocratic state, and it eventually helped produce the catastrophe of 1914. You can’t just copy-paste organizational ideas from this context and import them into your startup like downloading a plugin.

That said, the parallels between then and now are not subtle and they are important.

The United States Marine Corps formally adopted “commander’s intent” as a doctrinal concept in the 1980s. The Army and NATO followed suit. Stanley McChrystal’s Team of Teams, which describes how he reorganized Joint Special Operations Command in Iraq, reads like Moltke reincarnated as a special operations commander in the information age. And the corporate world has arrived at the same ideas as well.

Jeff Bezos’s two-pizza team is essentially the Prussian division: a self-contained unit with its own organic capabilities, capable of independent action. His six-page memo is Moltke’s directive: a forcing function for clear thinking that requires the author to actually know what they want and why, as opposed to a PowerPoint deck which allows you to hide behind fancy diagrams and bullet points. Reed Hastings’s “context, not control” at Netflix is literally Auftragstaktik with the Prussian filed off.

So why doesn’t everyone just do this?

Because it is brutally hard to actually do. Remember those three prerequisites? The thing about these is that they are all hard to maintain in practice, and each of them fails in its own distinctive way.

The first failure is at the top. Expressing clear intent requires you to actually have a clear intent and most leaders do not. They have vague feelings and a deadline. This is not that big of a problem when delegating tasks and an enormous problem when you are trying to do mission command. You can’t write a two-paragraph directive if you don’t know what you want — the brevity leaves you with no place to hide. So most leaders drift back toward detailed instructions, not because they really believe in micromanagement but because specifying the how is so much easier than specifying the why. It is the intellectual path of least resistance, and large organizations are very good at following the path of least resistance.

The second failure is at the bottom. Pushing decisions down only works if the people you are pushing them down to are genuinely excellent. This requires years of careful selection, training and investment — and it also requires saying no to a lot of people along the way, which is rarely pretty. Most organizations are not willing to do this. They hire fast, they onboard carelessly, they promote for loyalty or tenure instead of judgment and then they wonder why decentralization produces chaos instead of the promised speed. Whenever someone talks about empowering their teams, keep in mind that the Prussian War Academy washed out most of its candidates. Same goes for Amazon’s bar-raiser program. Decentralization without excellence is just disorder.

The third failure is between them. Remember that the third prerequisite for the system to work is trust. Trust between leaders at the top and the individual contributors at the bottom. And nothing falls apart easier than trust. Even if it doesn’t fall apart between the existing people, as the organization expands, trust becomes ever harder to sustain. Every new hire is someone who wasn’t there when the culture was built, every new leader brings their own instincts about how much control they need. Until one day a subordinate exercises initiative and it goes embarrassingly wrong — and instead of treating it as the expected cost of decentralization, the subordinate is punished and someone writes a fifty-page post-mortem document that becomes policy. Six more incidents, six more policies and now you are the French army at Sedan: brave, well-resourced, and getting the shit kicked out of you by your competitor.

In fact, this is exactly what happened to Moltke’s own system after he retired. The General Staff of 1914 had the same org chart as the General Staff of 1870 but a fundamentally different relationship to its own doctrine. The Schlieffen Plan, which Moltke’s nephew executed at the start of World War I, was precisely the kind of rigid, over-specified operational blueprint that the elder Moltke had spent his career arguing against. When the Belgians resisted harder than expected and the French didn’t collapse on schedule, there was no fallback and the German war machine ground to a halt.

Because that’s the thing about culture — it is the first thing to go and the last thing that anyone notices is missing. Moltke understood this. He spent thirty years building it. It outlasted him by about twenty, which as these things go is actually a pretty good run.

The upside of all of this is that the organizations that manage to build real Auftragstaktik and to actually sustain it are the ones that win. Long before Silicon Valley proved it in the 21st century, Moltke proved it on the battlefield in the 19th, twice, against the two strongest armies in Europe. And every fifteen years someone publishes a management book that says the same thing in different words, and everyone acts like it is new.

It is not new. It is just very, very hard.