Cooperate Chanakya: Ancient Strategy for Modern Cooperatives

So a cooperative that gets trust wrong — what actually breaks? Because I assume it's the money.

It's not the money. The money leaks out later. What breaks is the members' willingness to keep showing up.

That's vague. Can you make it concrete?

Think of a shared kitchen. Each chef preps one part of the meal — someone else's mise en place, not their own. If one chef cuts corners, everybody's dish fails.

Okay, that I can picture. So the co-op is the kitchen.

Exactly. And the OECD — they're the ones making this argument — describes trust as a basic element in how markets, businesses, and institutions function. Not a soft virtue. Infrastructure.

Wait, the OECD said that? I'm not accepting it as, like, settled economics until I know who's making the claim.

Fair, and I won't move on past it. It's from the OECD Business and Finance Outlook. They frame business trust around expectations that companies contribute to sustainable, inclusive growth and don't impose losses on others.

So it's behavioral — what firms do, not what they say.

Right. And conduct that violates legal, professional, or community standards damages trust, they say, whether it's deliberate or just inadequate controls. Carelessness counts.

Carelessness counts? That's rough for a small co-op with sloppy bookkeeping.

It is. And there's a hard case on the other side of it. Volkswagen and Porsche — the FTC reported they repaid more than $9.5 billion to U.S. buyers over the clean‑diesel deception.

Nine and a half billion.

And more than 86% of eligible claimants chose a buyback or early lease termination rather than a fixed car. They didn't want the product anymore. They wanted out.

So the trust breach converts customers into, what, refugees?

That's the picture. Edelman's 2023 Trust Barometer found 88% of respondents said trusting a brand was an important or critical purchase criterion — right beside quality at 89%.

Hmm. But a co-op isn't selling diesel cars. Its members are owners — they can't just leave.

They can withdraw capital and commitment, though, which for a co‑op is the same wound. Now — the part that surprised me. There's research on what builds trust when contracts can't enforce anything.

Which research? Because that claim usually comes with no—

Simon Johnson, John McMillan, and Christopher Woodruff, studying business relationships in Vietnam. Firms relied on ongoing relationships rather than third parties to settle disputes.

So the kitchen analogy again — the chefs trust each other because they've cooked together, not because of a contract.

That's what the data showed. After roughly two months of trading with a supplier, customers paid twelve percentage points more of their bills on credit. Trust literally developed through experience.

Twelve points in two months, just from... showing up repeatedly?

Repeated dealings and reputation. Economists call these relational contracts — a 2022 NBER working paper by Rocco Macchiavello and Ameet Morjaria describes them as informal, self‑enforcing agreements sustained by repeated interactions.

So what would you wager on this? Say a co‑op adopts transparency — shared ledgers, open accounts. Does that pay?

I'd wager it pays, and I'd give it maybe three‑to‑one odds. Paul Zak's 2017 Harvard Business Review piece — people at high‑trust companies reported 50% higher productivity than low‑trust ones. Though that's employee reports, not a causal law.

Good caveat. And what builds it, concretely?

recognizing excellence, giving people discretion, sharing information, intentionally building relationships. And the OECD says transparency and disclosure let stakeholders hold management accountable and reduce risk.

So the shared ledger is the co‑op's version of the state inspecting its allies — anyone can check the prep work.

Yes. A ninety‑day protocol could be: open accounts from day one, a rotating audit among members, and small repeated deals before big ones — earn the twelve points early.

Because skipping that costs you the same thing VW paid — members who'd rather walk away than stay.

people who won't buy what you're cooking anymore.

I'll say it plainly, because I half believe it. A cooperative with one strong leader just moves faster. Everyone else is, well, quieter, but things get done.

That's the strongest version of the argument, and I want to grant it fully before we take it apart. Speed is real. One voice, no meetings, decision made by lunch.

Right. So where does it fail?

It fails on information. But let's chase it like a case. Suppose a co‑op's charismatic founder makes every call alone. Members go quiet, meetings get shorter — and that looks like proof it works.

Wait, that silence — isn't that the clue itself?

Exactly. That's the misleading lead. Silence looks like harmony, but it's often people protecting themselves.

Protecting themselves from what?

From being punished or humiliated for speaking up. There's a name for this — psychological safety. A shared belief the team can take interpersonal risks without getting crushed for it.

And that's measurable?

Amy Edmondson thought so. Early in her work she studied two nursing teams in the same hospital. One team reported medication errors openly. The other hid them, because nurses feared blame.

So the team reporting more errors — that was the better team?

That was the puzzle. More reported errors, better outcomes. The errors weren't higher; the reporting was. She then studied fifty‑one manufacturing work teams and found psychological safety linked to learning behavior, which linked to performance.

Okay, but hold on — that's a factory. My co‑op question is about, about who decides. Does shared decision‑making actually outperform?

Now we're at the pressure point. The honest answer: not automatically. A study of 278 Basque companies found participation practices related to employee well‑being — but did not find participation improved labor productivity.

So the leader crowd is right after all?

Not right — incomplete. The failure isn't sharing decisions. It's sharing them badly. McKinsey surveyed 1,259 respondents: people who said decisions were made at the right level were 6.8 times more likely to be in a winning company.

6.8.

Though that's an association, not proof of cause. And here's the sobering part — just over a quarter said their organizations made good delegated decisions. Most places botch it.

So what does botching look like? For example, in an actual co‑op?

Think of the founder who announces 'you all decide the pricing' — then reverses the group's choice in private. That's the classic confusion between inviting input and transferring authority.

So the fix is just being explicit? 'This one's yours' versus 'I want your opinion'?

That, plus the rest of it. McKinsey says employees need capability, authority, and confidence to decide well — and clear boundaries. What's outside the remit, when to escalate, who's accountable.

Which, weirdly, brings me back to Chanakya. Wasn't he the ultimate single adviser to a king?

You'd think. But the Arthashastra argues complex decisions should not rest on one minister's judgment alone. It recommends consulting a small group — though it allows the ruler to deliberate alone or with fewer advisers when circumstances warrant. It's not dogma.

Hold on — how small? Because I've sat in co‑op committees of twelve, and nothing—

Right. That's the piece I love. The text advises three or four ministers. One adviser goes unchecked; bigger groups make secrecy and decision‑making harder. It's a middle path between the myth of a single king and endless committees.

And the king actually listens — really listens?

That's the discipline. The ruler should hear advisers' reasoning and judge their ability by the reasons they give — not collect opinions as a formality. The council works if dissent is real.

Which loops back to the safety piece. A council where nobody dares disagree is just a slower way of being alone.

Google found that too. Project Aristotle looked at more than 180 teams. Psychological safety was the most important of five dynamics — ahead of dependability, structure and clarity, meaning, and impact.

Not talent? Not credentials?

Not sufficient. How teams worked together predicted effectiveness better than who was on them. Higher‑safety teams were rated effective twice as often by executives — associations again, not proof.

So a nurse in the silent hospital ward — her whole day is deciding what not to say.

That's the cost, in one person's ordinary day. The 2003 findings of the Columbia Accident Investigation Board noted that organizational barriers impeded safety communication and stifled professional differences of opinion. Silence scaled up becomes catastrophe.

So for the co‑op... the rotating chair, the advice process — those are the modern Sabha?

In spirit, yes. And Radhakrishnan Pillai's Corporate Chanakya puts decision‑making right inside its Leadership section — it's a core discipline, not an afterthought.

But I'm still stuck on speed. Three or four ministers still sounds slow next to one decisive founder.

Sometimes it is. And that's where we honestly part ways, maybe. Studies of nursing teams and data from Google indicate that shared deliberation surfaces what silence hides. Your speed argument says urgency overrides.

And the Arthashastra sits in between — counsel by default, solitude when the moment demands.

So the disagreement stays live. One could argue that a co‑op that rarely consults flies blind, while a co‑op that frequently consults may fly slowly. The text, at least, refuses to pick a side — and maybe that refusal is the lesson.

People stopped volunteering for the extra shifts. Within a year the co-op was, it was basically a name on paper.

And what happened after that? Because the entry is never the end of the story.

But to be fair — and I've made this argument — some say surplus should be hoarded. Keep every rupee, reinvest it, grow the pot. Isn't that just discipline?

That's the opening scene I wanted. One line in a ledger, and the whole organization drained out through it.

Right. So where does it fail?

That's the strongest version of the myth, yes. Every coin stays in, the machine gets bigger, and everyone benefits eventually.

Meaning what, exactly? Tax policy?

The tradition attributes to him a line about taking taxes the way a bee takes nectar. Enough to make honey — without breaking the flower.

Okay, but a co-op isn't taxing anyone. It's deciding what to do with its own surplus.

Calibrated to keep the payer productive. A dead flower gives no nectar next season. A crushed member gives no effort next season.

And the standard options are?

Exactly the same move, though. Think of it this week, practically. Your co-op's year ends, there's surplus on the table. The question isn't spend or save — it's how much leaves, to whom, and how visibly.

So retention isn't zero even under sharing. There's still a pot.

Broadly three. Patronage dividends — surplus returned in proportion to how much each member actually used the co-op. Proportional equity — returned on capital contributed. And reserve allocation — a slice held back before either of those is paid.

Fear wearing an accountant's hat. Okay. But why does distributed surplus outperform? Mechanically, why?

Keeping some. The disagreement is about proportion and purpose — not existence. A reserve with a stated job is a tool. A hoard with no job is, often, just fear wearing an accountant's hat.

And the second?

Information. Distribution is a feedback loop. Members who receive dividends track the co-op's health. They ask questions. Hoarded surplus hides performance inside a locked room.

So they succeed despite hoarding, not because of it.

There are, and I won't pretend otherwise. Some centralized-profit cooperatives have grown large. But look at what carried them — usually a protected market, or a founder's force of will. Remove those and the model wobbles, because the members were passengers, not owners.

equitable sharing fuels growth rather than draining it.

And the evidence leans that way — ownership perception converts dividends into effort, and effort into the next surplus. The cycle feeds itself.

That hoarding isn't strategy for a lot of boards. It's control. Whoever holds the pot holds the members.

Say it.

Which is exactly what the bee line was guarding against, wasn't it. A ruler who takes everything isn't collecting revenue — he's breaking the flower.

So I'll make the choice plainly. I'd distribute, with a named reserve. And I choose it knowing the strongest objection — that reinvestment compounds faster when nothing leaves.

Why does sharing survive that objection?

Because the objection counts coins and ignores people. The members are the compounding asset. Break the flower, and there's no nectar — next season, or ever.

Picture a market scale — the old kind, brass pans, one stone. Why is that your image for a co‑op's operations?

Because the stone sits on one side no matter what you pile on the other. Efficiency on one pan, member involvement on the other. The scale remains.

So you're saying the two sides are opposed? Because I hear people argue they're not.

I hold the opposition view, and I'll defend it. Lean operations want speed and clear accountability. Participatory design wants members' hands on each decision. Each optimizes for something the other sacrifices.

And what does the lean side optimize for, exactly?

Throughput. Think of it as a week's work — tasks divided so narrowly that nobody waits on anybody. The Arthashastra models this. Book II, the duties of government superintendents, describes specialized departments, each with its own defined work.

Departments — in an ancient text?

Highly organized ones. Officials assigned specific responsibilities, revenue collection, accounting, oversight — separated on purpose, so no single official held unchecked discretion.

Okay, and the participation side? What does it optimize for?

Ownership and welfare. And, honestly, resilience. Members who decide together stay committed. Chanakya himself, or the text under his name, contains that famous maxim — in the happiness of his subjects lies the ruler's happiness.

Wait — that's a welfare constraint inside a book about, what, power and administration?

Exactly. That's the tension. A text obsessed with state capacity also makes the ruler's well‑being contingent on the people's. It's a counterweight to a purely efficiency‑driven reading.

So which side wins? You said you'd defend the opposition —

Neither, and that's my concession. Because the evidence cuts both ways. Specialization clarifies responsibility, but coordination across departments remains essential. Lean without coordination is just organized chaos with job titles.

Give me a concrete case. Not a principle — a scene.

The best one is a librarian in Mysore. 1905. R. Shamasastry, going through a heap of manuscripts at the Mysore Oriental Library, identifies a work nobody had read in centuries. He published the Sanskrit edition in 1909, an English translation in 1915.

A heap. Not an excavation.

No dramatic digging. A pile, a patient man, and one of history's major treatises on governance back on the table. The Arthashastra covers administration, law, diplomacy, military organization, economic governance — it's not a narrow strategy manual.

But — sorry — how is that a case about balance? It sounds like luck.

Not luck. It's a division‑of‑labor story. One librarian, one heap, one defined responsibility, sustained over years. Shamasastry's specialty let the discovery happen. But its value only landed because others coordinated — editing, translating, publishing.

So the stone — specialization — on one pan, and coordination on the other. The scale again.

That's the reuse I wanted. The text prescribes oversight of officials too — delegation needs monitoring as well as trust. And it describes verification of accounts and receipts, records and audits as safeguards for the treasury.

Which answers the burnout question, doesn't it? Lean run without oversight burns people out.

And maximal participation without structure stagnates — slower choices, and often not better ones, because decisions climb the same ladder regardless of size.

So what's the fix? A co‑op can't run two systems.

It can run tiers. Routine operations lean — a named owner, a deadline, a checked ledger. Strategic choices to the full membership. The text treats selecting people for defined roles as central statecraft, not bureaucracy for its own sake.

But is that just my scale with extra steps? What would actually prove the balance is right?

Name your evidence before you look. Turnaround time on routine matters, member attendance at the big votes, turnover. If attendance holds and turnaround shrinks, the pans are level.

And if attendance falls while everything runs fast?

Then you've optimized the machine and broken the membership — the maxim about the subjects' happiness is your alarm, not decoration.

One honest worry, though. People treat Chanakya like a corporate manual. Should a co‑op copy a monarchy's admin?

No — and scholars at the Manohar Parrikar Institute for Defence Studies and Analyses make the same caution. The text arose in a monarchical setting. Treat it as historical statecraft. Borrow the lesson — clear ownership, real accountability — not the throne.

Clear ownership, real accountability, and the scale watching. The stone stays in the pans.

And the discovery in the heap is your proof that patience plus structure beats both extremes. Go check the attendance numbers.

Three to one. There's a claim that the text says one opinion should count three times another's. That can't be right.

It isn't. And I'm going to sit with that number for a moment, because the truth underneath it is stranger.

So it's fake?

Not fake. Misread. The three-to-one idea is really a prompt to look at what the text actually prefers — a small council of three.

Three ministers. Why exactly three? That feels arbitrary.

Kautilya works it through like an engineer. One adviser may offer unchecked, partial counsel. A pair can reinforce each other too strongly — or split into division.

So two is worse than one?

In a way, yes. Two can deadlock or gang up. Three gives you a tie-breaker built into the structure itself.

Okay, then why not five? More eyes, more wisdom.

Because the text warns a council larger than three makes decisions harder — and secrecy more difficult. Secrecy, as a practical constraint on committee size.

Huh. It's uncommon to size a committee by whether it can keep a secret.

Which is why I keep saying hold the number loosely. The chapter says three or four, but the text explicitly allows the number to vary with the task and context.

Wait — so the rule has an escape hatch built in?

It does. Kautilya permits the ruler to consult fewer advisers, or deliberate alone, when place, time, and the nature of the task make that appropriate. It's counsel by default, not dogma.

Now, suppose I run a co‑op and I love this. I make my three senior members the council. Done, right?

Not done. That's just a smaller throne room. The text says administrative measures should be preceded by deliberation in a properly constituted council — properly constituted is the hard part.

Meaning what? Who sits there?

Think of a family dinner deciding the household budget. The one who cooks knows the grocery prices — that expertise earns weight. But Kautilya says weight by reasons given, not status.

So assess ministers by the arguments they make, not their title.

Exactly. And he goes further — listen to differing opinions, don't dismiss a contributor out of hand.

Even if the contributor is nobody?

The text says a sensible remark from a child can be useful. A child.

In a co‑op, that's the newest member. The one who asks the awkward question at their meeting.

That's the person the room needs. A recent scholarly analysis of Kautilya's intelligence framework stresses exactly this — advice should be scrutinized, including examining analysts' reasoning and divergent views.

Okay, but how does a council actually deliberate? Give me the, the machinery of it.

The text names five elements. Means to carry out the work, available people and wealth, timing and location, remedies for dangers, and the prospect of success.

So it's not opinions in a circle. It's resources, timing, risk, odds —

Right. Implementation is part of deliberation. You don't decide and then discover you can't do it.

And where does the ruler's information come from? He can't have seen everything.

Three kinds, the text says. What is directly seen, what is learned from others, and what is inferred — reasoning about what you haven't observed from what you have.

Inference as a formal source. That's, that's basically saying judgment counts as evidence.

Alongside observation and reports, yes. No single source treated as sufficient in every case.

Now let me push back. Equal votes are the soul of a co‑op. Weighting anyone's voice is capture waiting to happen.

I'll grant your strongest version fully. Weighted voting has captured real co‑ops — capital weight becomes control, and members become passengers. That failure is real.

But?

But it still fails against the text, because the Arthashastra does not weight opinions by rank. It weights them by reasoning — and it distinguishes intellectual power, based on deliberation, from material power, treasury and army.

So the balance is — authority exists, but counsel disciplines it.

That's the design. A ruler with full authority, obligated to test it against three argued perspectives.

What would you wager on this translating to a modern board?

I'd bet even odds the small‑council design beats a twelve‑person committee on routine decisions — and I'd caveat it immediately. This is ancient statecraft, not a controlled study proving groups of three or four make better corporate decisions.

Honest odds. So the question a co‑op board should actually take away is —

Who needs to contribute, what evidence is missing, and how will we evaluate disagreement? Three questions before any consequential decision.

Three questions. Three ministers. Not a coincidence I'll forget.

And from now on, you'll notice it everywhere — the meeting where nobody's reasoning is ever tested, just their titles counted.

Or the quiet new member who says something sensible and everyone just... talks over them.

That's the child in the council. The whole system was built to catch that voice — if the room lets it through.