German has two words where English has one, and the gap between them is the whole idea.
A Befehl is an order to be obeyed to the letter. Do this, exactly this, in this way.
An Auftrag is much more general — a statement of overall mission, a directive to be followed in its spirit, not its letter.1
Auftragstaktik is the doctrine of commanding almost entirely in the second mode, and Robert Greene presents it as the mechanism that makes a decentralized organization coherent rather than merely scattered.1
The doctrine's most quoted moment is an anecdote Moltke liked to repeat, and generations of German officers repeated after him.
A major, receiving a tongue-lashing from Prince Frederick Charles for a tactical blunder, defended himself by saying he had been obeying orders — and reminded the prince that a Prussian officer was taught that an order from a superior was equivalent to an order from the King.
Frederick Charles's reply became doctrine:
"His Majesty made you a major because he believed you would know when not to obey his orders."1
Greene notes why this specific story got told and retold: it made unambiguous that acting contrary to orders was not considered disobedience or a failure of discipline. That had to be established explicitly, because every instinct in a military hierarchy says otherwise.
The doctrine was not folklore. Moltke personally inserted into a draft tactical manual for senior commanders the sentences that made it official:
"A favorable situation will never be exploited if commanders wait for orders. The highest commander and the youngest soldier must always be conscious of the fact that omission and inactivity are worse than resorting to the wrong expedient."1
That last clause is the load-bearing one, and it inverts the ordinary incentive structure of any hierarchy. In most organizations, doing nothing is safe and doing the wrong thing is punished — so under uncertainty, people wait. Moltke's formulation makes waiting the punishable failure.
The responsibility, as Greene describes it, was to do whatever the situation required as he saw it, without waiting for orders — and to act contrary to orders when those orders were inconsistent with the situation in front of him.1
That is an enormous amount of trust to extend downward, and it only functions because of what came before it. Officers were first thoroughly inculcated with the philosophy of German warfare — speed, the necessity of the offensive — and then put through exercises specifically designed to build independent judgment. They were given missions and turned loose, and judged by the results of their actions rather than by how those results were achieved.1
The mechanism is simple once stated. In a Befehl organization, a subordinate who encounters something the order didn't anticipate has to stop, report upward, and wait. Every such moment is a pause, and the pauses compound.
In an Auftrag organization, the same subordinate acts. Greene's demonstration case is the marshal at Ulm who, hearing that the northeastern escape route was weakly held, did not wait for Napoleon to send orders — he simply moved and covered it himself, closing the last door on sixty thousand Austrians.1
Nobody told him to. Nobody had to, because he understood what the campaign was for and could see what was in front of him.
You've given someone a project and they keep coming back with questions you consider obvious. You're irritated by the interruptions and they're anxious about the ambiguity, and both of you are correct about your own experience.
The diagnostic is whether you handed over an Auftrag or a Befehl with gaps in it. A detailed instruction that fails to cover an unanticipated case leaves the person with nothing — they can't extrapolate from a specification, only from a purpose. So they come back.
The change is to state the mission and the reasoning: what this is for, what a good outcome looks like, what constraints are real. Then say the uncomfortable part out loud, because it's the part that makes the doctrine work: if the situation turns out differently than we're assuming, use your judgment and tell me what you chose — I'd rather you moved and got it partly wrong than waited and got it exactly right two weeks late.
That sentence is Moltke's manual line in ordinary language, and until you actually say something like it, people will keep defaulting to the safe behavior, which is waiting. Then hold to it the first time someone acts independently and gets it partly wrong — because that's the moment the doctrine is either established or quietly revoked.
Auftragstaktik is a genuine and heavily documented military doctrine, not a popularizer's construct, and its influence on modern Western military command philosophy (including the US Marine Corps' adoption of "mission command") is well established. Greene quotes Colonel T. N. Dupuy's A Genius for War directly for the Frederick Charles anecdote. [POPULAR SOURCE] for the framing.
Open tension the chapter doesn't examine: Auftragstaktik requires an unusually homogeneous, deeply indoctrinated officer corps to function. The German version rested on decades of shared training, a common social background, and an institution that had been selecting and shaping the same kind of person for generations.
Greene presents the doctrine as portable — adopt mission command and gain speed. The precondition is not portable at all, and organizations that adopt the language of mission command without the shared model underneath it get something quite different: not fast independent action, but confident action in incompatible directions. The doctrine's own history suggests it takes a generation to install, which is not how it's usually sold.
And the tension inherited from its parent institution: this doctrine's institutional home is the Prussian and later German general staff, whose admired operational record runs directly through the Second World War. Greene's account of the doctrine praises its effectiveness at the 1940 invasion of France without addressing what the same institution and the same doctrine were used for afterward.
Set this against Strategy 5: The Command-and-Control Strategy and its central failure case, Gallipoli and the Broken Chain.
At Suvla Bay, Hamilton gave what was effectively an Auftrag — a general statement of intent, no specified timeframe, execution left to the commander on the ground. It produced catastrophe. Stopford and Hammersley, given latitude, used it to do nothing.
The pairing produces the constraint Greene never states directly: mission command and vague orders are behaviorally identical, and are distinguished only by whether the recipient shares your model of the objective. Given to a Prussian staff officer trained for years in a common doctrine, "take the hills" produces immediate independent action. Given to a risk-averse general who has never absorbed your thinking, the identical words produce a beach holiday. Hamilton wasn't practicing bad communication so much as practicing Auftragstaktik without any of its preconditions — which looks exactly like negligence, because functionally it is.
Business → Outcome Ownership vs. Task Assignment. The distinction between telling someone what to achieve and telling them what to do runs through most modern management writing, usually framed as an autonomy or motivation question.
The insight the pairing produces: the military version supplies the piece the business version usually omits — the explicit, doctrinally protected permission to disobey when the situation demands it. Most corporate "ownership" cultures grant latitude within the plan while leaving the plan itself unchallengeable, which is not mission command. Frederick Charles's line is specifically about a major who was punished for obeying, and no ordinary company is prepared to do that.
Psychology → Psychological Safety as the Enabling Condition. Research on team performance identifies psychological safety — the shared belief that taking interpersonal risks won't be punished — as a strong predictor of the willingness to act, speak up, and admit error.
The insight: Moltke's "omission and inactivity are worse than the wrong expedient" is a psychological-safety intervention written a century before the concept was named. It works by making the safe behavior explicit and inverting it, because in the absence of such a statement people accurately infer that inaction carries less career risk than a visible mistake. The doctrine had to be stated repeatedly, in manuals and in retold stories, precisely because the default inference runs the other way and reasserts itself constantly.
An organization gets the behavior its incentives actually reward, and in almost every hierarchy the honest reading of those incentives is that doing nothing is safer than doing something imperfect. Every genuine instance of mission command in history has had to attack that inference directly and repeatedly — which is why the Prussians needed a manual line, a repeated anecdote, and an officer publicly reprimanded for obedience.