The Doctrine Most Founders Have Never Heard Of
A platoon commander in the Indian Army does not radio headquarters before every tactical decision. He receives what the doctrine calls the "commander's intent", the outcome the senior officer wants and the reason behind it, and then acts on his own judgment to achieve it. The Army calls this Mission Command. It is not a motivational concept. It is a warfighting doctrine built on the recognition that no central authority can process information fast enough to direct every decision in a fast-moving environment. Startups are fast-moving environments. Most founders still run them like headquarters.
Chanakya Understood Delegation Before It Had a Name
The Arthashastra, Chanakya's treatise on statecraft and administration, is explicit on this point: a ruler who attempts to supervise every function of the state will exhaust himself and make the state fragile. The text argues for appointing capable ministers and giving them genuine authority within their domains, not nominal authority with the king still deciding every detail. Chanakya's word for this is not delegation in the modern HR sense. It is a structural argument: power distributed to competent people is more durable than power concentrated in one person who becomes the single point of failure. Founders who have read the Bhagavad Gita for leadership lessons and skipped the Arthashastra have missed the more operational text.
Why Founders Keep Becoming the Bottleneck
The pattern is consistent across early-stage companies. A founder hires for a function, product, growth, operations, and then continues to approve every significant output from that function. The hire learns to wait. The founder's calendar fills with reviews. Decisions that should take an afternoon take two weeks because they require the founder's attention, and the founder's attention is rationed across twelve other things. This is not a time-management failure. It is a command architecture failure. The founder has built a hub-and-spoke system where every spoke terminates in one person. Mission Command is the argument that the spoke should terminate in a clear outcome, not a person. The person who owns the function should be able to act toward that outcome without routing through the center.
Three Things the Indian Army Gets Right That Startups Get Wrong
First: the Army states intent, not method. A commanding officer tells a unit what must be achieved and why it matters to the larger operation. He does not specify the route, the timing of each movement, or which sub-unit takes which position, unless those details are genuinely critical. Founders tend to specify method. They describe what they want and then describe exactly how to do it, which means the team is executing instructions, not solving a problem. When the situation changes, and in a startup, the situation always changes, a team executing instructions stops and waits. A team that understands intent adapts.
Second: the Army builds trust before it distributes authority. Mission Command does not mean handing a junior officer a vague objective and walking away. It means years of training, shared doctrine, and demonstrated judgment before independent authority is granted. Founders skip this. They hire someone and immediately want them to operate autonomously, without having established shared language about what good decisions look like. The investment in alignment upfront, what the company is optimizing for, what trade-offs are acceptable, what the non-negotiables are, is what makes decentralized decision-making safe. Without it, autonomy is just chaos with a positive framing.
Third: the Army treats initiative as a duty, not a personality trait. In Mission Command doctrine, a soldier who sees an opportunity and does not act on it because he was not explicitly ordered to has failed. Initiative is expected, not rewarded as exceptional. Most startup cultures do the opposite: they celebrate the employee who went above and beyond, which implicitly signals that going above and beyond is optional. If a founder wants a team that acts without being told, the culture has to treat inaction in the face of a clear opportunity as the failure, not the safe default.
Where This Breaks, and What to Do About It
Mission Command has limits that the Army acknowledges openly. It requires teams with high baseline competence. It requires a commander's intent that is specific enough to actually guide decisions, vague intent produces random action, not aligned autonomy. And it requires a feedback loop: decentralized decisions still need to be visible to leadership so the overall operation stays coherent. Founders who adopt the principle without these conditions get something that looks like empowerment but functions like disorganization. The fix is not to abandon the principle. It is to do the prerequisite work: hire for judgment, not just skill; write down the intent with enough specificity that a new team member could use it to make a decision you weren't present for; and build the reporting rhythm that keeps distributed action visible without requiring approval.
The Indian Army has been refining this doctrine across terrain and conditions that would break most organizational systems. The insight it carries for founders is not that they should give up control. It is that control exercised through clear intent and capable people is more durable, and produces faster decisions, than control exercised through approval. A startup that can only move as fast as its founder can review is not a company. It is a founder with staff.
