---
title: "Centralized Decision-Making: 13 Dead Russian Generals vs Mission Command — Delegation as Military Doctrine"
description: "Burnout doesn't come from the number of tasks, but from your having become the only person in the room allowed to think. A leader who keeps every decision in one hand cripples the team — and kills himself. But there's a dark payoff too: indispensability grants the status of a martyr without having to ask for power outright. Five mechanisms from Bowen to Whitehall, Russian generals as the price of centralization, Auftragstaktik, and a concrete repair protocol."
author: "Дністер"
published: 2026-09-07T03:01:40.000Z
language: en
url: https://neurodrift.org/en/blog/ya-vyrostyv-bezporadnykh/
tags: ["leadership", "team", "burnout", "systems"]
---
# Centralized Decision-Making: 13 Dead Russian Generals vs Mission Command — Delegation as Military Doctrine
## The Red Receiver
Picture a dim command bunker. Dozens of wires converge into a single field-telephone receiver, and that receiver is in one hand. Everyone waits for it to issue permission: permission to move, permission to decide, permission to think. **The red receiver on the desk isn't a symbol of communication. It's a monopoly on thinking.** In a healthy system the phone is a means of communication. In a sick one, it's a ventilator for the collective brain: unplug it, and no one can breathe on their own.
In "Downfall" (2004) the most frightening thing isn't the shouting. It's the map: divisions that no longer exist are still being moved around it, because at the top sits a man with a pencil, and at the bottom there's no one to say the front was breached long ago. This is the final form of centralization: reality has died, but the dashboard is still confident. In companies it's gentler — the founder drags cards around Notion even though the executive "army" is long gone: all that's left are column names, deadlines, and a few people waiting for him to do everything himself.
Now the numbers — carefully. As of late 2025, Russian sources confirmed at least **13 generals killed**; broader Ukrainian / OSINT lists by early 2026 already said "up to 19." The exact figure depends on methodology: who counts as a general, active-duty or retired, killed at the front or a targeted killing in Moscow. What matters for this text isn't the body-count bookkeeping, but the pattern: senior officers end up too often where, in a normal system, junior commanders with the right to decide should be acting.
Why — and it's not "because Russia has no sergeants" literally. It's that in the Soviet-Russian command culture the lower level lacks sufficient legitimacy for independent decisions; so the senior officer has to not just command but physically appear as a walking permission slip for action (add poor connectivity, dangerous inspections, insecure comms, and Ukrainian precision strikes). Centralization kills literally: the commander's body becomes the single point where the system is able to make a decision — and it drives to where it'll be killed.
Hold that image. Because this isn't only about someone else's army. It's the most precise metaphor for the founder, the team lead, the head of a family who's used to deciding everything alone. It's just that in business the general isn't killed — he burns out on his own, for free and unnoticed. In the army they at least give a posthumous medal. The founder gets a scheduled retrospective in a Slack thread called "lessons learned," where everyone leaves a sympathetic reaction and moves on to ask where the Stripe password is.
## This Isn't "Too Much Work"
The common diagnosis is "too much work." It's wrong. Back in 1979 Robert Karasek showed that mental strain comes not from a heavy load per se, but from high demands + **low control**. "Lots of work and lots of control" isn't burnout, it's drive. A truck stalls not from the weight, but from all the levers being wired to one pedal.
And here's the bitter turn the whole text rests on: most often what drowns you isn't *your* lack of control, but the lack of subjecthood in those *around* you. When your people can't decide — you have to. For everyone. Always. That's the weight you mistake for "the number of tasks."
## The Dark Reward of Being Indispensable
This is where most texts on delegation stop — at "the leader is afraid to let go." Not enough. Because micromanagement rests not only on fear — it rests on *pleasure*. A very unpleasant, ugly, but real pleasure: the pleasure of being the last adult in the room. You can sincerely hate this role — and at the same time jealously guard it.
Often the leader doesn't just fear that everything will fall apart without him. He quietly *needs* it to fall apart without him. Because then the exhaustion acquires meaning: every late-night rewrite isn't a symptom of a bad system but proof of sacrifice; every instance of someone else's helplessness isn't a parenting failure but one more proof that he really is indispensable. Indispensability is a very convenient form of power: you don't have to call it power. You can call it responsibility, standards, love for the craft, "well, who if not me." And it's almost true. That's exactly why it's so toxic: poison works better when it tastes of virtue.
Dark reward
How it sounds in your head
The real cost
Indispensability
"They can't manage without me"
You're the single point of failure
Moral superiority
"I'm the only adult here"
The team learns to be children
Control
"At least I know it's done right"
Every decision comes back to you
The right to resentment
"I carry it all myself"
You organized that "myself"
Martyr status
"I'm saving the system"
The system depends on the rescuer
Avoiding trust
"There's no one to trust"
So you never train anyone you could trust
Erich Fromm, in "Escape from Freedom" (1941), showed the other side of the coin: people often *give up* freedom themselves — because it's heavy — in exchange for security, clarity, and the right to say "I did what I was told." This applies to your team too: not everyone wants autonomy. Some want a clear order, the guaranteed rightness of the boss, and an alibi. That doesn't make them bad — it makes your job harder: you're not just handing over power, you're treating a dependency on its absence. Indispensability is a drug in the costume of responsibility, and your team is hooked on it along with you.
## I Grew Them (mechanism one: reciprocity)
The most unpleasant news: you didn't find your passive people. You *grew* them.
Family systems described this as the reciprocity of over- and under-functioning (Murray Bowen's school): exactly as much as one person takes on, the other unlearns. They don't exist separately — it's one pair of roles co-creating itself. Every "let me just do it, it's faster" of yours is a microdose. Three years on, the room is all executors, and you don't remember writing the prescription with your own hand. Like a muscle in a cast: you're "protecting" it — and it atrophies precisely from the care.
An officer who reviews every step of the platoon raises a platoon that won't take a step without him. Indispensability isn't a virtue or an achievement. It's a symptom of a system you built so it wouldn't work without you. You hired adults — and raised infants, and then you take offense that you've got a kindergarten. Congratulations: this isn't an HR problem. It's your pedagogical success.
## The Door Is Open — and He's Lying There (mechanism two: learned helplessness)
*The path is open. There's no order. So no one moves. Initiative isn't lost — it's drilled out.*
1967. Martin Seligman shocks dogs that *aren't allowed* to escape. Then he opens the door — and the dogs lie there. It turned out it's not the shock that does the damage. It's the *uncontrollability*.
This is your team in the third year of micromanagement. You open the door — "come on, take some initiative!" — and they lie there. Not out of laziness. Because you systematically taught them: any initiative will end in your "I said do it differently," or a silent sigh and a quiet late-night rewrite. They saw it. Initiative became a lottery whose prize is sometimes the boss's silent disappointment; after a few such wins, a person draws the rational conclusion: thinking is dangerous. Here you get punished for thinking — with edits.
In "Band of Brothers," the attack on Foy is almost a laboratory scene of managerial paralysis. Lieutenant Dike is no coward and no fool; under fire he simply stops giving clear decisions — and an entire company freezes in the middle of the field, because the intent died from above. Then Speirs runs across the field and does not magic but the basic thing: he gives the system back a direction. A team can have courage, weapons, and motivation — but without intent from above it becomes merely the brave users of a frozen operating system.
And "Chernobyl" (the HBO series) adds the strangest edge of powerlessness — a culture where the truth can't be sent up. The instruments scream, people see the graphite on the roof, skin is burning, but the official version is "the reactor is intact," because the senior man said so. In a micromanaged company the scale is smaller, the mechanics the same: everyone knows the client is unhappy, the process is dead, people are burning out — but until the boss admits it, "there is no problem." Radiation, though, doesn't read the org chart. When the truth can't be escalated, it starts to glow in the dark.
## You Hand Out the Control, You Keep the Heart Attack (mechanism three)
The Whitehall II study (Michael Marmot, 10,308 British civil servants) produced an uncomfortable number: those with little control over their own work had roughly **double the risk of ischemic heart disease** (OR ≈ 1.93) — *regardless* of workload. It's not overwork that kills. Powerlessness is carbon monoxide: odorless, painless, and you realize you've been poisoned when you're already on the floor.
Add this to the rest. By taking away your people's right to decide, you give them exactly this risk factor, and keep the opposite poisoning for yourself: you hold the whole wheel, and the surplus of decisions drowns you. One circuit slowly dies of boredom, the other quickly — of overload. You pay the salary of both. The system turned out elegant: subordinates have no power, you have no life. The symmetry is almost beautiful, like a well-composed obituary.
## Fourteen Pull Like Eight (mechanism four)
1913, the engineer Maximilien Ringelmann measures how people pull a rope. One pulls at 85 kg. In a group of 14, each delivers only **61 kg**. The more people formally "responsible" for a task, the less each one pulls. Darley and Latané added a second layer: in a crowd everyone is sure someone else will do it.
And there you are, the commander, instinctively making up the difference *yourself*: the 24 kilograms the fourteen failed to pull, you pull. Alone. At one in the morning. Social loafing has a very civilized look — no one's lying on a couch: everyone's on Zoom, everyone nods, everyone "+1"s, everyone "takes it on." And then, somehow, the work ends up again with the one least able to watch it go undone. In the company-retreat photo there are twelve of you. In production — three. At night — one. Guess who.
## "It'll All Fall Apart Without Me" — a Diagnosis, Not a Complaint (mechanism five)
*When no one below dares to decide, the decision has to drive up to the front in person — to where it'll be killed. An "indispensable" commander is the shortest path to a vacancy.*
Vietnam, November 1965, the Ia Drang valley. Lieutenant Colonel Hal Moore controlled nearly every aspect of the battle — down to when the helicopters could land. And here you have to be careful: Moore was neither a fool nor a cartoon boss with an Excel sheet. That's exactly what makes the example more dangerous. The problem isn't that he's a bad commander — it's that even a strong commander in an over-centralized model becomes so useful that others stop growing around him. On screen ("We Were Soldiers") this is heroism: "first to set foot on the field, last to leave it." But heroism is often not the opposite of bad design, but its last working patch: when the process doesn't work, character goes into battle. Character, unfortunately, doesn't scale and is poorly armored.
In "Moby-Dick," Captain Ahab isn't just a bad risk manager. He's a man who made a private obsession the strategy of the whole crew. The ship was meant to hunt whales; instead it became the instrument of one man's trauma. In the same way a founder quietly turns a company into a machine for compensating his own fear: that nothing will exist without him, that others will ruin it, that control is the only available form of love for the result. Then the ship sinks, but at least the standards were high. Ahab, too, probably said he just had high standards for the whaling industry.
This is "founder's trap" in its pure form: you become the single point of failure *and* the martyr at once. "It'll all fall apart without me" sounds like a complaint about others. In fact it's the acceptance criteria of a badly designed system. Indispensability is when HR hasn't yet worked up the courage to call your exhaustion a job title.
Mechanism
How it looks in the team
What it costs the commander
Reciprocity (Bowen)
"They can't do anything" — because you do it all
Indispensability as a trap
Learned helplessness (Seligman)
The door is open — no one moves
A team with no initiative
Powerlessness (Whitehall, OR 1.93)
Your people are poisoned by lack of control
You drown in a surplus of decisions
Social loafing (Ringelmann)
14 pull like 8
You make up the difference yourself
Single point of failure
"It'll all fall apart without me"
The general at the front / burnout
## The Cure Is Called Auftragstaktik (without the romance)
*Each with their own radio, each with the right to decide. The old single receiver lies in the mud — and a green sprout is already pushing through it. This is what delegated subjecthood looks like.*
In the 19th century the Prussian field marshal Moltke the Elder formulated a principle that still scares micromanagers: *Auftragstaktik* — command through *intent*. The senior says *what* must be achieved and deliberately stays silent about *how*; the junior is obliged to act on his own the moment the situation outruns the order. Modern doctrine (ADP 6-0) calls it mission command and stresses: it's not "do whatever you want," but **disciplined initiative within the commander's intent**. The senior sets the purpose, key tasks, end state, and constraints; the junior gets the right to act when reality has changed faster than the order.
This isn't an abstraction. RUSI, analyzing the first months of the full-scale war, noted that the Russian plan had a deficit of *reversionary courses of action* — the moment the bet on speed failed, the forces began to degrade, because the lower levels lacked flexible alternatives. A centralized system looks good while the plan works; its real test is where the plan has died. Western armies passed mission command to Ukraine from 2014, and analysts attribute the success of small Ukrainian units precisely to this idea. General Charles Krulak demanded back in 1999: "micromanagement must become a thing of the past." And the key thing worth tattooing on every founder: give people the **"freedom to fail."** The freedom to fail isn't humanism, it's a training budget: without it, the team doesn't learn — it only tries not to irritate the center.
What it looks like when it works is shown well by "Master and Commander": the ship lives not because the captain personally pulls every rope, but because everyone on board knows their slice of the world. The commander gives intent, discipline, and tempo — but doesn't make himself the single nerve node of the vessel. In a storm, that's the difference between a crew and a group of people very politely waiting to die.
And right away a caveat, so as not to fall into the opposite stupidity: autonomy isn't "everyone scattered, do as you please." "Lord of the Flies" convincingly showed that people without a mature structure don't automatically become free adults — sometimes they paint their faces and start hunting the weaker one. Auftragstaktik isn't the absence of command, but command through intent, limits, and trust. **Autonomy is designed, not announced.** Because you can, as in Orwell's "Animal Farm," hang ownership on the wall, autonomy in the manifesto, "take initiative" in Slack — while in reality returning every decision to one person who then quietly fixes it all. Then the language of freedom outlives freedom itself — and that's the worst kind of lie, because it sounds like a virtue.
## The Repair Protocol
To delegate isn't to give up the wheel. It's to install a second wheel so the car doesn't die together with the driver. Not "become colder" and not "cut the team back," but stop doing for people what they're capable of themselves. Three levels:
1. **Micro — one decision.** "You choose. I'll accept the result. We'll review it afterward — but I won't rewrite it overnight." And actually don't rewrite it overnight. This is the hardest and the most important.
2. **Meso — a zone of autonomy.** "Anything up to €200 / up to 2 hours / a standard client / no legal risk — you decide, without asking." A clear boundary lifts the paralysis better than any motivation.
3. **Macro — intent.** "The goal is this. This is forbidden. These are the risks. Everything else is your maneuver." And then — a review without punishment: we analyze how it went, we don't punish for its going differently than it would have in your head.
And honestly: this isn't an apologia for lack of control. Not every decision has to be pushed down. There are red zones — life, safety, law, big money, reputation, irreversible steps. But most everyday decisions aren't a nuclear button. It's just that a micromanager loves to paint every button red, so he can then heroically sit by the console.
Type of decision
Who decides
Reversible, low-risk
the executor — alone
Reversible, medium-risk
the executor + a review afterward
Irreversible, high-risk
the leader / senior
Reputationally sensitive
the leader sets the frame, the executor prepares
Repeatable
an SOP, not a person
New / chaotic
intent + limits
And beware pseudo-delegation — a disease "The Office" showed perfectly: Michael Scott seems to say "decide for yourself," but every decision still has to pass through his need to be important. "Decide for yourself" — but in such a way that I can later take offense, rewrite it, and prove that without me you're children. The team quickly learns: better not to decide, it's cheaper for the psyche. Pseudo-delegation is when you say "decide for yourself" while your face has already signed the appeal.
## Instead of a Conclusion
Look at your team, your family, your circle — and ask one honest question. Not "why is everyone around me so helpless," but — "what am I doing every day to keep them helpless?" This isn't about guilt. It's about ownership: if you grew it, then you can redesign it. What you grew can be let go. But first you'll have to survive the most frightening part: they'll do it differently than you. And the world won't end. Unpleasant, of course. Some cults dissolve after that.
A team doesn't become helpless in a day. It's trained to wait for permission to think. At first it looks like high standards. Then like care for quality. Then like indispensability. And one day you're sitting in a bunker, holding the red receiver into which all the wires converge, and you realize: this isn't a command post. It's the resuscitation of a system you spent years not letting grow its own heart. A leader burns out not from thinking a lot. He burns out from having forbidden others to think — and called it responsibility.