Subhas Chandra Bose's Organisational Discipline Has Real Lessons for Anyone Building a Team

Bose inherited soldiers from prisoner-of-war camps and volunteers from Indian diaspora communities across Malaya and Singapore. He had no institutional authority these men were obliged to respect. What he had was a stated standard of conduct that applied to him first. He wore the same uniform. He ate the same rations. He submitted to the same physical demands he placed on his officers.Chanakya wrote in the Arthashastra that a leader who does not live by the rules he enforces will find those rules enforced by no one. Bose understood this practically. Before he issued any order about discipline, he made his own conduct the reference point.For anyone building a team from the ground up, this is the first structural move. Write down what you expect, punctuality, preparation, direct communication, ownership of mistakes, and then audit your own behaviour against that list before you hold anyone else to it. The team will not follow the document. They will follow what they observe.

The INA's officer structure was unusual for its time. Bose created channels through which soldiers could raise grievances formally, without fear of reprisal. This was not sentimentality. It was a mechanism for catching operational failures before they became catastrophic ones.Teams that only run accountability downward, where the leader reviews the team but is never reviewed, develop a specific dysfunction. People stop surfacing problems. They learn that bad news travels up at personal cost, so they hold it. The organisation then operates on a version of reality that the person at the top constructed alone.Build a structure where your team can tell you when something you decided made their work harder. Make it formal enough that it doesn't depend on someone's courage on a given day. A monthly written feedback round, an anonymous channel, a standing agenda item, the mechanism matters less than the fact that it exists and that you visibly act on what comes through it.

One of the persistent mistakes in early-stage teams is treating structure as something you add later, once the team is bigger. Bose did the opposite. The INA had clear ranks, defined roles, and explicit chains of command from its earliest formation, not because it was large, but because clarity about who decides what is what allows small groups to move fast without constant negotiation.Structure becomes bureaucracy only when it serves itself, when the process exists to protect the process. Structure that serves the mission looks like: everyone knows their decision boundary, escalation paths are short and known, and no one is waiting for permission they should already have.For a team of five, this might mean a single written document that says who owns what. For a team of fifteen, it means defined domains with named owners. The document is not the point. The absence of daily ambiguity is.

Bose was present. He visited units at the front. He knew officers by name. He appeared at moments of difficulty rather than delegating the difficult appearances to subordinates. This is documented consistently across accounts of the INA's operation in Burma and across the Imphal campaign.Leaders who become invisible, who communicate through intermediaries, who are accessible only in formal settings, find that loyalty attaches to whoever is actually present. In a small team, that person is usually whoever has the most informal authority, which may or may not be the person with the most judgment.Visibility is not the same as micromanagement. You can be present without controlling. Show up to the work. Ask specific questions about what people are running into. Know the names of the problems your team is carrying, not just the names of the deliverables.

The INA's stated goal was the liberation of India. That was specific enough to be measurable and emotionally real enough to sustain sacrifice. But Bose also articulated what India after liberation would look like, the kind of nation, the kind of society. The vision gave the goal a direction that outlasted any single campaign.Most teams have goals. Quarterly targets, product launches, revenue numbers. These are necessary. They are not sufficient for the kind of discretionary effort that separates a team doing its job from a team doing something worth doing.The vision question is: what does winning actually look like, beyond this quarter? If you cannot answer that in two sentences that your team could repeat back to you unprompted, the team is executing tasks, not building anything. Bose spent considerable energy on this, speeches, writing, direct conversation, because he understood that people will work hard for a goal, but they will work hard and think creatively for a vision.The discipline Bose built into the INA was not a product of military convention, most of his soldiers had been stripped of their original military loyalties entirely. It was a product of clarity: about standards, about structure, about what the organisation was actually for. Teams that import discipline as a rule set, without first establishing that clarity, end up enforcing compliance rather than generating commitment. Those are not the same thing, and the difference shows up the first time the work gets genuinely hard.