Chanakya's Upaya — the methods of achieving an objective — includes a four-part framework that the Arthashastra applies repeatedly: to statecraft, to conflict resolution, to managing ministers, and to dealing with rivals. The four methods are Sama (conciliation and persuasion), Dana (incentive and reward), Danda (force and consequence), and Bheda (division and separation). What makes this framework durable is not the individual methods — all four are obvious in isolation — but the prescribed order and the diagnostic logic for knowing which one fits which situation.
The Four Methods and Why the Sequence Matters
In Book 2 of the Arthashastra, and again in Book 9, Chanakya specifies that the methods should be applied in sequence — Sama first, then Dana, then Bheda, and Danda last. This is not a soft preference. He argues that applying Danda before exhausting the others is wasteful of resources, creates unnecessary enemies, and signals poor judgment from the leader.
Sama is persuasion and conciliation — appealing to reason, shared interest, and aligned values. It costs nothing and, when it works, produces the strongest commitment because the other party has chosen the outcome rather than been coerced into it.
Dana is giving — reward, incentive, material or non-material exchange. It costs something, but it produces action without destroying relationship. The person who acts for Dana feels they have made a reasonable deal.
Bheda is division — identifying and addressing the structural or relational cause of resistance, separating conflicting parties, or using information to shift alliances. It is more complex to apply and requires better intelligence about the situation than Sama or Dana.
Danda is force, penalty, or formal consequence. It works, but it is expensive: it consumes authority, creates resentment, and often triggers the very resistance it was meant to suppress if applied without the other three having been genuinely attempted first.
Chanakya's insight is that most leaders, when frustrated, skip straight to Danda — the email with a deadline ultimatum, the formal warning, the termination — without asking whether Sama was genuinely attempted or whether a well-designed Dana would have worked just as well at a fraction of the cost to the relationship.
Sama in Practice: Persuasion With Logic and Shared Vision
Effective Sama is not soft. It is not vague encouragement or appeals to team spirit divorced from rational argument. Chanakya describes Sama as addressing the other party's actual interests — explaining why the proposed action serves them specifically, not just the king. Sama that ignores what the other person actually cares about is not really Sama — it is a speech.
In a business context, Sama with an employee who is resistant to a process change means explaining the change in terms of what makes their job easier or better, not just why the business needs it. Sama with a client who is pushing back on a timeline means addressing their underlying concern — which is usually risk, not the timeline itself — before explaining why the timeline is what it is. Sama with a vendor who is missing deliverables means understanding why the miss is happening before presenting your expectation.
Three techniques that Chanakya's Sama implies: first, establish the shared goal before stating your position ("we both want this project to succeed, and here is the problem I am seeing…"). Second, use the other party's own statements as the basis for your argument — when you argue from their words rather than your position, resistance drops. Third, make the logic visible — do not ask people to trust you, show them the reasoning. Chanakya was writing for a political world where trust was contingent and earned, not assumed.
Where Sama does not work is when the other party has already made a private decision and is presenting surface-level resistance while waiting for the conversation to end. This is where most managers waste the most time — applying increasingly sophisticated Sama to someone who has already decided. Chanakya's prescription is to distinguish genuine openness to persuasion from performed resistance, and to move to Dana if Sama is getting nowhere after a genuine attempt.
Dana in Practice: Matching Incentives to Motivational Profiles
Dana is not just money. Chanakya identifies multiple forms of giving that motivate different types of people: material reward (salary, bonus, gifts), honour and recognition (titles, public acknowledgement, status elevation), security (guaranteed position, reduced uncertainty), and protection (shielding someone from consequences they fear). Knowing which form of Dana is valued by each person is what makes the method effective.
A senior developer in a Kochi software firm who is underperforming because they feel overlooked for a team lead role will not respond to a salary increment — they will respond to a title change and visible responsibility. A junior marketing executive who is pulling back effort because they are financially stressed will not respond to public recognition — they need a raise. A long-term vendor who is deprioritising your projects will not respond to a performance review — they will respond to faster payment terms or a longer contract.
The mistake most managers make with Dana is applying the same reward structure to everyone and then being confused when some people respond enthusiastically while others barely register it. Chanakya's system assumes that different people have different primary motivations, and that the leader's job is to learn those motivations through observation, not to assume them.
One important limit Chanakya places on Dana: it should not permanently substitute for Sama. If you consistently use Dana to get compliance from someone who should be persuaded by reason, you create a transactional relationship that will eventually price you out — every subsequent request will carry a higher Dana expectation. Use Dana to move past a specific impasse, then return to building the Sama-based relationship of shared understanding.
Danda in Practice: When to Enforce, and Why Leaders Wait Too Long
Danda in a business context is the formal consequence: the performance improvement plan, the contract penalty clause invoked, the termination, the client relationship ended, the vendor relationship replaced. Chanakya is clear that Danda must be available and credible — a king who never exercises Danda loses authority because everyone learns there are no real consequences. But Danda should be the last resort, applied after the other methods have been genuinely exhausted.
The most common failure mode in business leadership is not applying Danda too quickly — it is applying it too late. A manager who tolerates chronic underperformance because the conversation is uncomfortable, continues a client relationship that is destroying team morale because the revenue feels necessary, or keeps a vendor on despite repeated misses because replacing them feels complicated — all of these are failures to apply Danda at the appropriate moment after Sama and Dana have been genuinely attempted and failed.
Chanakya's test for when Danda is appropriate: Has Sama been genuinely attempted? Has the relevant Dana been offered? Is the continued non-compliance damaging the organisation and signalling to others that there are no real standards? If all three answers are yes, Danda is not cruelty — it is maintenance of the standards that make the organisation function. Delay past this point is not kindness; it is abdication.
When applying Danda, Chanakya specifies that it must be proportional. Disproportionate punishment — firing someone for a first minor offence, ending a five-year client relationship over a single dispute without prior communication — damages the leader's authority by appearing arbitrary or emotional. Proportional Danda, applied calmly and clearly after the other methods have been tried, is understood by everyone in the organisation as the natural consequence of a clear sequence of events.
Bheda in Practice: Separating Conflict Sources and Ethical Limits
Bheda is the most complex of the four methods and the most easily misused. At its legitimate core, Bheda involves identifying and addressing the structural source of resistance rather than fighting the surface behaviour. Two team members who are in constant friction are a Bheda problem — separating them structurally (different projects, different reporting lines, different working hours) may resolve what Sama and Dana cannot, because the problem is not individual motivation but interpersonal chemistry.
A client relationship where the primary contact is blocking progress because of a personal agenda within their own organisation is a Bheda problem — expanding the relationship to include other stakeholders may solve what no amount of persuasion aimed at the blocker will. A vendor who is underperforming because a key person at their end has been poached is a Bheda problem — addressing the structural gap by expanding the vendor's team or creating a backup arrangement solves it where escalation conversations will not.
The ethical line is this: Bheda is legitimate when it addresses genuine structural causes of dysfunction. It crosses the line when it is used to manufacture divisions that do not exist — creating distrust between people who are currently aligned, using private information about one party to undermine their standing with another, or engineering situations to make people dependent on you. Chanakya himself describes these darker applications of Bheda in Book 9, and the Arthashastra applies them in the context of weakening enemy kingdoms — not managing your own team. The distinction matters. Within your own organisation, Bheda should always be a structural intervention, not a psychological manipulation.
Frequently Asked Questions
I manage a team of 15 people and everyone responds differently. How do I know which method to use?
Chanakya's answer is observation before action. Before choosing a method, know which primary motivation drives each person — is it recognition, money, security, belonging, or challenge? Watch what they talk about when work is going well, and what upsets them when it is not. A team member who lights up when publicly praised responds to recognition — Sama that acknowledges their contribution will work. A team member who always brings conversations back to salary or fairness is motivated by material equity — Dana will land better. A team member who becomes anxious when expectations shift is motivated by security — Sama in the form of clear, stable expectations is most effective. With 15 people you cannot apply one method uniformly and expect uniform results. Map each person to their primary motivator over two to three months of observation, then tailor your approach. It is more work upfront and significantly less management overhead over time.
Is Bheda (division) ever ethical to use in a business context?
Bheda has both legitimate and illegitimate applications. The legitimate use is separating parties whose continued proximity is damaging the organisation — two co-founders with irreconcilable disagreements, a senior employee whose influence over a subgroup is pulling it away from organisational goals, or a client relationship so dysfunctional that it is affecting your team's ability to serve other clients well. In these cases, structurally separating the parties is not manipulation — it is prudent management. The illegitimate use is deliberately sowing distrust between people to make them dependent on you as the only trusted party, or using private information to divide alliances that are legitimate. That version of Bheda is manipulative, typically backfires when discovered, and creates exactly the toxic environment Chanakya warned against in his descriptions of a poorly governed state.
What if Sama doesn't work and I jump straight to Danda — what's the cost?
The cost is credibility and relationship capital — usually with the wider team, not just the individual involved. Chanakya is explicit that Danda applied prematurely weakens the authority of the person who applies it. When a manager moves from a request directly to a formal consequence without attempting Dana, they signal to everyone watching that they either cannot persuade or are unwilling to invest in persuasion. Both signals are damaging. The person who receives disproportionate Danda often leaves — but not before letting others know what happened. In Kerala's tight professional networks, where reputations travel quickly within industries, this kind of reputation damage is a real cost. The four-method sequence exists for a reason: exhaust Sama genuinely, attempt Dana, diagnose whether Bheda is the actual issue — then apply Danda as a last resort, with full awareness that it is largely irreversible.