Every business owner who has made a bad hire knows the specific exhaustion that follows — the months of managing the mistake, the conversations deferred, the performance reviews that go nowhere, the day you finally accept that this is not going to work. Chanakya was thinking about this problem with unusual precision 24 centuries ago. The Arthashastra contains a complete personnel management framework: how to recruit, how to place people in roles that suit them, how to pay them, how to manage poor performance, and when to dispense with the graduated process entirely. What makes it remarkable is how little of it is intuitive, and how much of modern business practice still misses the core insight.
Chanakya's Personnel Philosophy: Match the Person to the Role
In Book 2, Chapter 9 of the Arthashastra, Chanakya introduces the concept of svabhava — the natural disposition or essential character of a person — as the primary criterion for role assignment. His argument is direct: a person placed in a role that aligns with their svabhava will perform well even with modest instruction. A person placed in a role that contradicts their svabhava will perform poorly even with extensive training and supervision. The role should be shaped around what the person is, not what you need them to be.
This sounds obvious until you examine what actually drives most hiring decisions. Businesses typically hire for the vacancy: there is a role, it has requirements, and you find the person who most closely matches those requirements. Chanakya's approach inverts this. He would have you first understand the person — their inclinations, their strengths, what kind of work they find naturally engaging — and then determine what role they should hold. This is a more time-consuming approach to hiring, but it produces dramatically better long-term outcomes.
Applied practically, this means spending more time in the interview process understanding what candidates have genuinely been good at, not just what they have done. The question "What kind of work do you find yourself doing when no one is asking you to?" reveals svabhava more reliably than "Where do you see yourself in five years?" A person who naturally organises information and systems without being asked is a natural fit for operations roles. A person who naturally initiates new connections and conversations is suited for client-facing roles. A person who notices inconsistencies and asks uncomfortable questions is suited for quality and audit roles. Forcing these people into the wrong slots — because the vacancy says otherwise — wastes their ability and produces predictable friction.
This is particularly relevant in Kerala's business context, where the talent pool includes a high proportion of educated, English-fluent graduates from engineering, commerce, and arts programmes. The temptation is to hire an engineer for a technical role because they have an engineering degree — but what their svabhava actually suits them for may be project management, client education, or product design. The degree is a credential. The svabhava is the actual predictor of performance.
Chanakya also specified that the king who assigns work based on what he needs rather than what the person is suited for will produce poor results from even capable people. This remains one of the most persistent errors in growing businesses: the owner who promotes a brilliant individual contributor into a management role because management is the next logical step, then watches them fail at managing and lose their individual brilliance. The Arthashastra would say the error was in the assignment, not the person.
The Recruitment Process in the Arthashastra: Background, Testing, Probation
Chanakya's recruitment process for senior officers in the Arthashastra has four stages that map directly onto a structured modern hiring process. Understanding each stage helps you see what shortcuts in standard Indian business hiring actually cost you.
The first stage was background investigation — what Chanakya called anviksha. Before any serious consideration, the candidate's history was examined: their prior conduct, their reputation among those who knew them, their family circumstances, and any prior positions they had held. This was not a formality. It was a substantive inquiry designed to surface patterns of behaviour that the candidate would not volunteer. In modern terms: reference checks done properly, not perfunctorily. A reference check that consists of confirming employment dates is worthless. A reference check that asks "In what circumstances does this person perform best, and in what circumstances do they struggle?" yields genuinely useful information.
The second stage was character testing — placing the candidate in a controlled situation designed to reveal how they behave under pressure, temptation, or ambiguity. Chanakya described specific scenarios for testing different types of officers. For a candidate for a financial role, a test of their honesty when handling resources. For a candidate for an advisory role, a test of their willingness to give unwelcome counsel. Modern equivalents: a work sample test, a case study exercise, or a structured group discussion that reveals how the candidate actually thinks and behaves rather than how they present themselves in a prepared interview.
The third stage was probationary appointment — placing the successful candidate in a real but lower-stakes role before full appointment. This is the most-skipped stage in Indian SME hiring. The logic is straightforward: interviews are performance, and even bad hires can perform well in interviews. A 90-day probationary period in which the candidate handles real work with real consequences reveals capability and fit that no interview can. The cost of a 90-day probationary period that ends in a parting is orders of magnitude lower than the cost of a two-year mistake.
The fourth stage was formal induction — the explicit handover of role responsibilities, authority, accountability, and resources. This is what many businesses skip on the assumption that the new hire "will figure it out." Chanakya specified that a minister who did not have a clear understanding of their mandate could not be held accountable for failing it. The same logic applies: a team member who does not have a clear, documented understanding of what they are responsible for and what authority they have to act cannot be fairly evaluated against it.
Chanakya on Compensation: Paying Enough to Remove the Temptation to Steal
Chanakya's discussion of officer compensation in Book 5 of the Arthashastra contains one of the most practically useful insights in the entire text. He specified that officers must be paid enough that the temptation to steal from the treasury is outweighed by the cost of losing their position. His logic was economic, not moral: a poorly paid officer has a powerful incentive to make up the deficit through corruption. A well-paid officer has a powerful incentive to protect their income by maintaining their employer's trust. Set compensation at the level where the second incentive dominates.
This insight applies directly to business in Kerala and across India, where business owners routinely underpay employees relative to market rates and then wonder why they face petty theft, expense manipulation, undisclosed client kickbacks, and side work that competes with the business. The solution is not surveillance — though Chanakya had views on that too — but pricing the relationship correctly in the first instance.
What does "paying enough" mean in practice? It means paying at or slightly above the median for the role in your market, not below the median with the promise of future increases. It means reviewing compensation annually without waiting for the employee to ask. It means ensuring that the total package — salary, leave, flexibility, professional development — is competitive enough that the employee actively does not want to lose the job. This is the retention premium, and it is far cheaper than the hiring, onboarding, and productivity cost of replacing someone who left for a competitor offering 15% more.
Chanakya also specified differentiating pay based on the sensitivity of the role. Officers with access to treasury, intelligence, or strategic decisions were paid more — because the consequences of their dishonesty were greater. The same principle applies: a finance manager who handles client billing and your tax accounts represents more risk than a content writer. Pay the finance manager well enough that the risk-reward calculation of dishonesty simply doesn't arise.
Managing Poor Performance: Chanakya's Graduated Response
One of the most common mistakes in small business HR is binary thinking about underperforming team members: either tolerate the underperformance indefinitely because confrontation is uncomfortable, or fire them suddenly in a moment of frustration without prior documentation or process. Both options are bad. Chanakya prescribed a graduated response that is more humane, more legally sound, and more effective at either recovering the employee or ending the relationship cleanly.
Step one is private counsel — a direct, honest conversation about the specific performance gap, its impact, and the expectation going forward. Not a general expression of dissatisfaction but a specific: "The last three client deliverables were submitted after the deadline we agreed. This has caused client escalations. I need deliverables on time, and if there are obstacles to that, I need to know about them so we can solve them." This conversation is documented with a brief written note: date, what was discussed, what was agreed.
Step two is formal warning with an improvement plan. If the problem continues after the first conversation, a written Performance Improvement Plan sets out the specific metrics, the timeline, and the consequences of continued underperformance. In India, this documentation is also important for legal compliance — it demonstrates that the employer gave fair notice and opportunity before any termination.
Step three is reassignment. Before concluding that the person cannot perform, Chanakya's framework asks whether they are in the wrong role. A salesperson who is consistently poor at outbound prospecting but excellent at client retention may be misassigned. A project manager who struggles with ambiguous briefs but excels at structured execution may need a role with clearer inputs. This is not always possible, but for businesses where the cost of replacing the person is high, exploring reassignment first is worth the effort.
Step four is dismissal — the formal end of the relationship, executed correctly and without recrimination. Chanakya's point was that by the time you reach this step, if you have followed the prior stages, both parties know it is coming and neither should be surprised. A dismissal that is surprising is evidence that the prior steps were not done properly.
When to Skip the Process: Chanakya's Conditions for Immediate Dismissal
The graduated process is the right path for performance problems. But Chanakya specified conditions under which it was bypassed entirely — situations where the graduated approach makes things worse rather than better. Understanding these conditions protects both the business and the other team members.
Breach of trust is the first condition. If a team member has deliberately deceived you — falsified records, hidden information that affected a business decision, misrepresented work completed — the counselling process is not appropriate. Trust, once deliberately broken, is not recoverable through a Performance Improvement Plan. The question is not whether they can do the work going forward; it is whether they will. Chanakya understood that an officer who had once chosen to deceive the king retained the demonstrated willingness to do so again when sufficiently motivated. The business equivalent is real: an accounts person who has once manipulated invoices, a salesperson who has once taken a client kickback, a manager who has once falsified a timesheet, has shown you who they are under pressure.
The second condition was deliberate action that endangered the state — decisions made in bad faith that created serious risk. In a business, the equivalent is sharing client data with a competitor, sabotaging a project relationship, making commitments the business cannot honour to win personal benefit. These are not performance failures; they are acts of bad faith that require immediate and clean separation.
The third condition Chanakya specified was persistent defiance of lawful instruction — a team member who repeatedly and deliberately ignores clear direction despite having the information and capability to follow it. This is distinct from performance failure, which is often about ability or circumstance. Deliberate non-compliance is about will. The graduated process is designed for ability and circumstance problems. It does not address will problems.
For Kerala businesses, where labour relationships are sometimes complicated by personal networks, community ties, and family connections, these explicit conditions serve a clarifying purpose. They make the decision about what kind of problem this is — performance (process appropriate) or trust/intent (immediate action appropriate) — before emotions and relationships cloud the analysis.
Frequently Asked Questions
I have a team member who is good at their work but toxic to team culture. What do I do?
Chanakya's framework would first require you to document the specific behaviors causing the problem, not just the general feeling. Then have a direct private conversation: describe the behavior, explain its impact on the team, and give a clear expectation for change. Set a defined review period — 30 to 60 days — with specific observable outcomes. If the behavior continues, reassignment to a role with less team interaction may be workable if the work quality is genuinely irreplaceable. If it is not irreplaceable, Chanakya would say clearly: a person who damages the group costs more than their work contributes. The exit, handled respectfully and following correct process, is the better path for the business and, often, for the individual.
How do I let someone go in a way that is fair, legal, and doesn't destroy morale for the rest of the team?
Fairness requires documentation: have you given the person a clear understanding of the problem, a reasonable opportunity to fix it, and followed your own stated process? Legal compliance in India requires following the terms of the employment contract and applicable labour law — for businesses with fewer than 100 employees in most states, the requirements are less stringent but a final settlement must still be prepared correctly. For team morale: be brief, factual, and respectful when communicating the change. Say something like "We have made a change on the team — this role no longer fits our direction." Do not discuss the person's failings with remaining team members. The team will draw their own conclusions, and they will trust a process that was handled with visible dignity more than one handled with visible resentment.
Chanakya tested people before trusting them with responsibility. How do I do this without coming across as paranoid?
Frame probationary work as a structured onboarding, not as a test. Give every new hire a 90-day plan with specific deliverables and check-in milestones. Assign them a low-stakes but real project in the first month — something where mistakes are recoverable but the work is meaningful. Review performance explicitly at the 30, 60, and 90-day marks with documented feedback. This is standard professional practice in well-run organisations and signals that you take onboarding seriously. Most new hires actually prefer this structure because it gives them clear early wins to build confidence. The key is making the criteria transparent upfront, not springing them as a surprise evaluation midway through.