The Arthashastra is not a motivational text. When Chanakya wrote about managing people, he was solving a logistical problem: how do you get a large group of individuals with different motivations, capabilities, and loyalties to consistently produce results in the same direction? His answers are operational in a way that most ancient texts are not — he specified spans of control, performance metrics, compensation structures, and accountability mechanisms with the precision of someone who had actually managed an empire's administrative apparatus.
That operational specificity is what makes Chanakya's management thinking useful for businesses today. You don't need to adapt it from abstract principles — you need to translate his administrative instructions into a modern organisational context, which is a much smaller leap than it might seem.
Classifying Team Members by What Actually Motivates Them
One of Chanakya's most practically useful contributions to management is his insistence that different people require fundamentally different management approaches — and that applying the wrong approach consistently produces underperformance regardless of the quality of the individual.
In the Arthashastra, he identified three primary motivational categories among workers and officials. The first are those driven by a sense of duty and personal standards — what he associated with Dharma as a motivator. These people perform well when they understand the purpose of their work, have clear standards to uphold, and receive recognition that is about the quality and significance of their contribution rather than purely material reward. Manage them with incentives alone and you undervalue them; they will feel their commitment is not being seen.
The second category are those motivated primarily by material reward — Artha as motivator. Chanakya designed detailed pay and performance-bonus structures in Book 2 precisely because he understood that a significant portion of any workforce responds to compensation clarity. If the link between output and reward is opaque, this group performs inconsistently. Make the link explicit and measurable, and their performance becomes reliable.
The third category are those who require consistent accountability structures — people whose performance tracks closely with how clearly and consistently rules are enforced. This group is often misread as lazy or indifferent, but Chanakya's view was more nuanced: they are not inherently poor performers, but they perform best in environments where the expectations and consequences are unambiguous. In ambiguous environments, they tend toward minimum effort because the signal about what is expected is unclear.
The management implication is direct: spend the first few months with a new team member identifying which category they primarily fall into before deciding how to manage them. Most managers apply one universal approach — usually the approach that motivates themselves — and wonder why some people respond well and others do not.
What Chanakya Said About Span of Control
Book 2 of the Arthashastra contains specific guidance on the structure of administrative departments, including how many subordinates a superintendent could effectively oversee. While Chanakya's exact numbers reflect a pre-industrial administrative context, the underlying principle is precise: there is a limit to how many direct reports a supervisor can manage without losing quality of oversight, and that limit varies with the complexity and interdependence of the work.
For complex, interdependent work requiring frequent coordination — what his senior ministers performed — he described smaller teams with close supervision. For more routine, measurable work — tax collection, grain warehousing, market oversight — larger groups under a single superintendent were workable because the output was quantifiable and the work was relatively independent.
Modern management research has converged on similar conclusions: spans of control around five to eight work well for knowledge-intensive roles requiring coaching and coordination, while spans of fifteen to twenty-five can work for roles with clear metrics and routine processes. What Chanakya adds to this is the insistence that the span of control must be set before you decide whether a manager is underperforming — a manager with twelve direct reports doing complex work is not failing; they are structurally set up to fail.
Output Metrics and the Arthashastra's Approach to Measurement
Chanakya was specific about performance measurement in a way that anticipates modern key performance indicator frameworks. In Book 2, he outlined how superintendents of different departments — trade, agriculture, manufacturing, public works — should have their performance evaluated against measurable outputs rather than effort or intentions.
He was explicit that accountability for outputs required those outputs to be defined in advance. An official who did not know what they were being measured against could not be fairly evaluated, and evaluations without pre-agreed standards were arbitrary — which he recognised as producing resentment rather than improvement. His administrative system required that each department head understand their targets at the beginning of the measurement period, not at the end when results were being reviewed.
He also distinguished between outputs that a person directly controlled and those that depended on external conditions. A trade superintendent could not be held fully accountable for revenue decline caused by an enemy blocking trade routes — that was a strategic failure at a different level. But he could be held accountable for how he responded to the disruption, how quickly he identified alternatives, and how effectively he maintained the department's operational capacity. This distinction — between what you control and what you influence — is one that many modern performance management systems still get wrong.
Building Accountability Without Building Fear
One of the more sophisticated aspects of Chanakya's management thinking is his recognition that accountability and fear are not the same thing — and that organisations that mistake the two consistently underperform. In Book 2, he described the characteristics of departments that functioned well: clear standards, consistent enforcement, visible recognition for good performance, and proportionate consequences for failures. He noted that departments governed primarily by punishment produced a predictable set of problems: officials hid errors rather than reporting them, effort was directed toward appearing compliant rather than achieving results, and the most capable people left for environments where their competence was recognised rather than simply used to avoid punishment.
His solution was to make the accountability system legible — meaning that everyone in the organisation understood what the standards were, how performance would be evaluated, what good performance looked like when it was achieved, and what the consequences of sustained underperformance would be. When those elements are in place, the emotional experience shifts from fear of arbitrary judgment to the more productive experience of working within clear expectations. Chanakya treated this shift not as a cultural aspiration but as a management design problem.
This connects directly to his broader thinking on systems and processes — a well-designed accountability system does not depend on the personality of the manager who happens to be running it at any given time.
Making Recognition Work: Chanakya's View on Visible Acknowledgment
Chanakya was specific about recognition in a way that distinguishes him from many ancient writers on governance: he insisted that recognition for good performance must be visible. A private acknowledgment delivered only to the individual performs a fraction of the function that public acknowledgment does. When an organisation sees that strong performance leads to visible reward — promotion, public commendation, increased responsibility, financial recognition — it sends a signal to every observer about what the organisation actually values, not just what it claims to value.
He designed recognition mechanisms into his administrative structure for exactly this reason. Merit-based advancement was documented and announced rather than handled quietly. Financial rewards for exceptional performance were given at formal occasions where others were present. This was not vanity — it was a deliberate system for communicating organisational standards through visible examples rather than through policy statements.
The failure mode he identified — private recognition of good work paired with private delivery of consequences for poor work — creates an organisation where nobody knows what is actually valued. In such an environment, people default to risk avoidance: they do what is safest rather than what is most impactful, because the link between performance and outcome is invisible.
The Role Definition Problem: Assigning Work to the Right People
A principle that runs through Book 2 of the Arthashastra is that role clarity is a precondition for performance accountability. Chanakya was emphatic that you cannot hold someone accountable for a result if their role and its boundaries have not been defined. This sounds obvious, but it addresses a persistent failure in growing organisations: roles that accumulate tasks over time without ever being formally defined, creating situations where multiple people believe they own something and nobody is actually accountable for it.
He also addressed the question of person-role fit from the direction that most modern organisations neglect: instead of asking "who can we fit into this role," he insisted the question should be "what does this role require, and who among our people genuinely has those qualities." The distinction matters because fitting people to existing role descriptions tends to preserve mediocre outcomes, while defining role requirements and then identifying who best matches them tends to produce better placement decisions.
For growing businesses, the practical application is a structured role design exercise: write down what each role is supposed to produce (outputs, not activities), what decisions it is authorised to make, what it depends on from other roles, and what it owes to other roles. Then evaluate whether the person in each role is genuinely positioned to deliver those outputs. Mismatches between role requirements and person capabilities that have been ignored for years become visible very quickly in this exercise.
If you're thinking about the hiring side of this — how to bring in people who fit roles well from the start — Chanakya's hiring and selection principles address that question directly.
Why Consistency Matters More Than Intensity in Management
One of Chanakya's less quoted but practically important management observations is that inconsistent management — alternating between neglect and intense intervention — is more damaging to team performance than consistently moderate management. In Book 1, he described the disorienting effect of a ruler who was alternately absent and overbearing: the organisation neither developed independent capability nor received the direction it needed to perform confidently.
Consistent management — regular check-ins, predictable standards, reliable response to both good and poor performance — creates what Chanakya described as a settled organisational environment. His word for this condition, roughly translated, refers to a state in which people know what to expect and can therefore commit their full energy to the work rather than managing uncertainty about their situation. The more unsettled that environment — through unpredictable leader behaviour, changing standards, or inconsistent consequence — the more cognitive and emotional energy is consumed by managing the environment itself, leaving less for productive work.
For business owners and managers who are naturally intense and variable in their engagement, this is a practical challenge. Building management routines — structured one-to-ones, regular team reviews, predictable decision timelines — is less about administrative formality and more about creating the conditions under which your team's actual capability can be expressed consistently. Chanakya would have seen this as basic organisational design, not optional management best practice.
Frequently Asked Questions
How did Chanakya classify different types of employees based on motivation?
Chanakya identified three primary motivational categories for workers and officials in the Arthashastra. The first category is those driven by duty and dharma — people who perform well because they take pride in their role and feel personal responsibility toward their work. These employees require clear standards and public recognition more than financial incentives. The second category is those motivated primarily by material reward — workers whose performance is directly tied to compensation structures, incentives, and the tangible consequences of their output. Chanakya designed elaborate pay and bonus systems for this group in Book 2, including performance-linked pay that varied with actual output. The third category is those managed primarily through accountability and consequence — workers who respond to clear rules and visible enforcement. He did not consider any of these motivational types superior to others; he considered it a manager's job to correctly identify which type each team member is and manage them accordingly rather than applying a single approach to everyone.
What did Chanakya prescribe for underperforming team members?
Chanakya's approach to underperformance in Book 2 of the Arthashastra was structured and graduated rather than reactive. His first step was diagnosis — distinguishing between underperformance caused by lack of capability, lack of understanding of the role, lack of motivation, or external interference. Each cause required a different response. Capability gaps called for training or role reassignment. Role ambiguity called for clearer instruction and metrics. Motivational failure called for adjusting the incentive or accountability structure. Only after this diagnostic process did he move to consequences. He specified that penalties for underperformance should be proportionate to the nature of the failure and should be documented rather than informal, so that both the employee and observers understood the standard being enforced. He was also explicit that repeated minor failures should be treated more seriously than a single significant one — consistent mediocrity was a larger management problem than an isolated mistake.
How does Chanakya's management system handle accountability without creating a fear-based culture?
Chanakya drew a deliberate distinction between accountability that produces performance and fear that produces paralysis. In Book 2 of the Arthashastra, he described the characteristics of a well-functioning administrative department: clear output metrics, consistent enforcement of those metrics, public recognition for good performance, and proportionate consequences for failure. He specifically noted that a workforce governed primarily by fear produces two predictable outcomes — people hide problems rather than surfacing them, and they do the minimum required to avoid punishment rather than the maximum they are capable of. His solution was to make the standard visible, make recognition equally visible as consequences, and ensure that the consequences for underperformance were about the work rather than the person. When accountability systems are consistent and fair, the emotional texture shifts from fear of arbitrary punishment to the more productive experience of working within clear expectations — which Chanakya explicitly identified as a condition for high-output organisations.