The middle manager's position is structurally awkward in a way that most leadership books don't acknowledge: you have real accountability for outcomes but limited authority over the conditions that produce them. You answer to people who make decisions you sometimes disagree with. You lead people whose cooperation you need but cannot fully command. You translate strategy downward and surface reality upward — and you do both imperfectly, because the information loses something in each direction.
Chanakya understood this position. His Arthashastra describes a complex administrative hierarchy in which superintendents, department heads, and provincial governors occupied exactly this kind of middle space — accountable to the king's direction, responsible for the performance of people below them, and frequently caught between strategic intent and operational reality. His guidance for these officials is specific, practical, and largely unread by people who treat the Arthashastra as purely a text about kings and statesmen.
Why Chanakya Distinguished Authority from Influence
Chanakya made a consistent distinction throughout the Arthashastra between the formal authority that comes with a position and the actual influence that determines what a person can achieve in that position. A superintendent installed by royal decree had authority — the power to direct, assign, and evaluate. But whether that superintendent could actually get high-quality work out of their department depended on something else: whether they had earned the trust and professional respect of the people working under them.
He was direct about this in his description of what made an effective administrator: it was not the title but the prabhava — the personal standing and earned credibility — that determined whether instructions were followed with genuine commitment or mere surface compliance. An official who relied only on their formal position found that people did the minimum required to avoid consequences. An official who had earned their team's respect found that people went beyond the minimum because they trusted the direction they were being given.
For a middle manager, this distinction has immediate practical weight. Your formal authority is limited and clearly bounded by your role description. Your influence — built through consistency, demonstrated competence, fairness, and genuine interest in your team's development — can extend considerably beyond those formal boundaries. The manager who understands this invests in building influence rather than relying on authority, and finds that their effectiveness grows in proportion to the trust they accumulate.
The Translation Problem: Strategy Into Execution
One of the most underappreciated functions in any organisation is the translation of strategic direction into operational action. Chanakya described this function explicitly in Book 2, where he outlined what a superintendent was expected to do with the king's policies: not simply relay them unchanged, but interpret them into specific tasks, allocate them to appropriate people, and verify that the underlying intent was being served rather than just the literal instruction.
He recognised that strategies articulated at the top of an organisation are necessarily incomplete — they describe the destination and the general direction but cannot specify every operational decision required to get there. The middle official's job was to fill those gaps intelligently, using judgment to resolve ambiguities in ways that served the policy's intent. An official who waited for explicit instructions on every detail was considered incapable; one who resolved ambiguities badly through poor judgment was considered dangerous. The ideal was an official who understood strategic intent deeply enough to act correctly in situations the strategy had not anticipated.
This is a demanding standard, and it explains why Chanakya placed such emphasis on the intellectual quality of mid-level administrators. A manager who only knows what they are supposed to do when everything goes according to plan is not genuinely managing — they are executing a script. The real test of management capability is what happens when the script runs out, which is every day in a real organisation.
Earning Respect from Both Directions Simultaneously
The structural challenge of middle management is that you need the confidence of the people above you and the genuine respect of the people below you — and those two relationships can pull in different directions. Senior leaders want alignment and reliability. Team members want advocacy and fairness. A manager who optimises for one at the expense of the other tends to become either a management tool that the team does not trust, or a popular advocate that senior leadership cannot rely on.
Chanakya's guidance for administrators in this position was about demonstrating competence and integrity in both directions simultaneously rather than trying to manage the appearance of each relationship separately. With senior authority, this meant delivering clear, accurate reports — including bad news — and implementing decisions faithfully even when you had argued against them. With your team, it meant making decisions consistently and fairly, representing their interests accurately to senior leadership, and not using your team's performance to advance your personal standing.
The connecting thread is that both relationships are built on the same thing: demonstrated integrity. A manager who tells senior leadership what they want to hear rather than what is true undermines their own reliability. A manager who tells their team what they want to hear rather than what the organisation needs undermines their own credibility as a leader. Chanakya's recommendation was to resist both temptations and accept that integrity sometimes creates short-term friction in both directions — which is the cost of being genuinely trusted in both directions over time.
Handling Conflict Between Team Members
When conflict arises between people in your team, the instinct of many managers is either to avoid it (hoping it resolves itself) or to adjudicate it (declaring a winner and a loser). Chanakya's framework suggests a different sequence, applied at the team level.
Sama at the team level means facilitating a direct conversation between the conflicting parties. Not mediating a formal dispute, but creating conditions where the parties can actually hear each other's positions clearly. Many team conflicts exist because each party has constructed a story about the other's motives that the other person would not recognise. The manager's role in the Sama stage is to ensure that each party is genuinely heard before positions harden.
Dana at the team level means identifying and addressing the underlying need. Two people fighting over credit for a project outcome are often actually fighting over recognition and visibility within the team. Two people in conflict over how a task should be done are often fighting over whose professional judgment is valued. Addressing the surface conflict without touching the underlying need produces a temporary truce rather than a resolution.
Danda is appropriate when the manager has genuinely attempted the first two stages and needs to make a clear decision. At this point, the decision should be explained and final — not hedged or tentative. A Danda intervention that leaves ambiguity about the outcome invites continued contest.
Bheda — structural separation — is appropriate when the conflict is genuinely irresolvable given how roles and responsibilities are currently arranged. Sometimes two people with incompatible working styles or professional approaches simply cannot share a domain effectively. Reorganising their work so that the friction point is removed is a management decision, not an admission of failure.
The Foundational Role of Fairness and Consistency
Chanakya identified consistency as one of the most important qualities in a manager's daily decisions, and he was specific about why. When standards shift with a manager's mood or relationships, the team does not simply adapt — it starts managing the manager rather than doing the work. People spend energy predicting the manager's current state and calibrating their behaviour accordingly, which is energy not being spent on actual output.
He noted that a team which perceives its manager as fair — meaning decisions are based on consistent principles rather than personal favour — will tolerate difficult decisions and demanding standards with much less resistance than a team that suspects the rules apply differently to different people. Perceived unfairness is corrosive in a way that perceived difficulty is not. A team can accept that the work is hard. They struggle to accept that the work is hard for some of them but not others, or that the standards that apply to one person do not apply equally to another.
The practical implication is that a new manager's most important early investment is demonstrating that their standards are consistent. This means applying the same expectations to high performers and low performers, to people you like and people you find difficult, and across situations that are public and those that are private. Chanakya's administrative literature repeatedly shows rulers and superintendents applying this principle — the examples he gives of good administrators are almost always examples of consistent, legible behaviour rather than inspired individual decisions.
Giving Feedback That Actually Changes Behaviour
Chanakya's approach to correction in the Arthashastra has a specificity that most modern feedback frameworks lack. He was clear about the method: correction should be delivered privately, should be about the specific behaviour or output rather than the person's character, should include a clear description of what different behaviour looks like, and should be timed to be close enough to the event that the connection is clear but not so immediate that emotions prevent reception.
He was equally clear about what not to do: public correction of a capable person produces shame rather than improvement. A team member who is corrected in front of peers is managing their relationship with those peers after the conversation, not internalising the feedback. The correction has solved the manager's need to signal a standard but has not served the actual goal of changing behaviour.
He also noted that correction should be proportionate — a minor deviation from a standard deserves a brief private comment, not a formal conversation. Treating every imperfection as requiring significant intervention trains people to conceal small problems rather than surfacing them, because surfacing a small problem triggers a disproportionate response. Chanakya's administrative system was designed around early warning — managers need their team members to bring problems to them quickly, and that only happens when the consequences of surfacing a problem are clearly more manageable than the consequences of concealing it.
Building Credibility Through Demonstrated Competence
Chanakya was sceptical of leaders who relied primarily on positional authority or political relationships to establish their standing. In his assessment of what made administrators genuinely effective, demonstrated competence — actually knowing the work well enough to evaluate it, improve it, and make good decisions about it — consistently outranked formal credentials or social connections.
This has direct implications for how a middle manager should invest their time and attention. A manager who has risen into a role they no longer fully understand is in a fragile position — they can be managed by their team, who know the work better, and they cannot credibly evaluate the quality of what they are receiving. Chanakya's ideal superintendent was someone who understood the domain they were overseeing well enough to know when they were being misled or when the work was genuinely excellent versus adequately performed.
For modern managers, particularly those who have moved into management from technical or specialist roles, this argues for maintaining enough connection to the work — not doing it, but understanding it — that your judgment remains credible. The manager who becomes purely administrative loses the competence credibility that earns genuine respect rather than surface compliance.
For a broader perspective on how Chanakya's principles apply at the senior leadership level, the seven CEO leadership lessons cover the specific challenges that arise when you move from managing teams to leading an entire organisation.
Frequently Asked Questions
How does Chanakya distinguish between a manager's authority and their actual influence?
Chanakya treated authority and influence as related but distinct — and in the Arthashastra, he was clear that positional authority without earned influence produces compliance rather than genuine performance. Authority comes with a title or role; it gives you the power to direct, assign, and evaluate. Influence comes from demonstrated competence, consistent fairness, and a track record of judgment that others have learned to trust. In his framework, a superintendent who relied solely on their formal position to get work done was considered a weak administrator — one who would struggle when circumstances required people to go beyond their formal duties. An official who had earned the trust and respect of their team could achieve outcomes through persuasion and leadership that no amount of formal authority could compel. The practical distinction matters for middle managers because authority in most organisations is limited and clearly circumscribed, while influence can extend well beyond formal boundaries. A manager with high influence can shape decisions and outcomes that are technically above their authority level, while a manager who has not earned influence will struggle even within their formal mandate.
What does Chanakya say about how managers should handle conflict between their team members?
Chanakya's Sama-Dana-Danda-Bheda sequence applies directly to team-level conflict, though the application at a manager level looks different from how it works at a senior leadership level. When two team members are in conflict, Sama (gentle persuasion) means the manager facilitates a direct conversation between the parties, helping them articulate their respective positions and find shared ground without imposing a solution. Dana (addressing underlying needs) means looking past the surface conflict to identify what each party actually wants — which is frequently recognition, resource allocation, or clarity about their respective roles — and addressing that directly rather than adjudicating the surface disagreement. Danda (structural intervention) is appropriate when the first two approaches have not resolved the conflict and the manager needs to make a clear decision about how things will work. Bheda (separation of interests) means reorganising work, responsibilities, or team structure so the conflicting parties have minimal need to contest the same resources or decisions. Chanakya's emphasis was that managers should attempt the first stage genuinely before escalating — most team conflicts resolve at the Sama stage if the manager is willing to facilitate rather than judge.
How should a middle manager use Chanakya's principles when they disagree with a decision made above them?
Chanakya addressed the situation of disagreement with senior authority carefully in Book 1 of the Arthashastra. His counsel to ministers who disagreed with a king's decision was to raise the objection clearly and privately before the decision was finalised — making the case with specific reasoning rather than general objection. Once a decision was made, however, he expected officials to implement it faithfully even when they had argued against it. A minister who publicly undermined or half-heartedly implemented decisions they disagreed with was, in his view, violating the trust that made the relationship function. The appropriate channel for sustained disagreement was continued private counsel — making the case again with new evidence if circumstances changed — not passive resistance or visible dissent. For a modern middle manager, this translates to a clear two-stage approach: argue your position vigorously before the decision is made, through the appropriate channels and with your reasoning clearly stated; then implement the decision as well as you can if it goes the other way. If you cannot implement a decision in good conscience, that is a signal about whether the organisation is the right fit — not a reason to undermine the decision from within.