A carpenter has a workshop with twenty apprentices. Some can handle one project at a time. Some can run ten projects simultaneously without dropping any. A rare few can hold a hundred projects in their head and keep all of them moving. The carpenter who treats all twenty apprentices as interchangeable — assigns work randomly, gives the same load to each — produces a workshop where the one-project apprentice is burning out under ten projects and the hundred-project apprentice is bored and quitting under one project. Same workshop. Same workload. Wrong assignment. The output collapses on both ends.
That is the diagnostic Kautilya gives for administrator selection at sutra 1.8.28–29. From the capacity for doing work is the ability of a person judged. And in accordance with their ability, by suitably distributing ranks among ministers and assigning place, time and work (to them), he should appoint these ministers. (1.8.28–29)1 Pillai walks the sutra in Ch 3 of Inside Chanakya's Mind as the first principle of administrative selection. The criterion for selecting an administrator is his capacity to do work — and the leader's job is to match each administrator's capacity to the rank, place, time, and work they get assigned. Four axes. One assignment. The match has to work on all four for the administrator to perform.
Pillai's reading parses the sutra into four assignment dimensions:1
Rank — the formal level the administrator occupies. CEO vs. Vice President. Senior Director vs. Junior Director. Chief Minister vs. Cabinet Minister. Rank is the authority the administrator can deploy. The high-capacity administrator at low rank cannot use what they have; the low-capacity administrator at high rank deploys authority they cannot back up.
Place — the geographic or organizational location. State capital vs. remote district. National headquarters vs. branch office. Pillai's anchor: High-performing government officials are underutilized if posted in some remote areas. It is almost like a punishment for them.1 When these high-performing officials are posted in state capitals or national capitals, directly reporting to a chief minister or the prime minister, they can work wonders.1 Place determines proximity to consequential work. Wrong place equals wasted capacity.
Time — the temporal window the administrator operates in. Pillai's compression: These administrators also have to be given time frames for projects. Goal-setting exercises are helpful. When leaders and administrators work in 'mission mode', they can achieve amazing possibilities.1 Time-boxing matters. The administrator with no deadline drifts; the administrator with a deadline they cannot reach burns out. Right timeframe to right capacity.
Work — the actual project or portfolio assigned. The variable that does most of the work in the assignment problem. Match the work to the capacity tier; match the capacity tier to the work.
The four axes are not independent. Rank without commensurate work creates idle authority. Work without commensurate rank creates an administrator unable to drive the work past organizational obstacles. Place without time creates strategic-position-without-execution-window. All four have to align for the assignment to perform.
Pillai gives a granular capacity taxonomy at lines 1037–1039.1 Some people can only handle one project at a time. Some can manage about ten projects at a time. There are some rare administrators (like rare gems) who can handle a hundred projects simultaneously. Three tiers — 1, 10, 100 — separated by an order of magnitude each. The administrator's tier is observable from past performance; the leader who has not measured it is guessing.
Tier 1 — single-project administrators. Most people. Reliable on one task at a time. Will deliver if the task is well-scoped and the load is single-stream. Multitasking degrades them rapidly. Pillai's diagnostic: if a person who is capable of doing one project at a time is given a hundred projects, that administrator will get burned out. Stressed, he will not even complete one project properly.1 The mismatch produces total failure, not partial failure — the over-loaded one-project person delivers nothing rather than completing one of the hundred.
Tier 2 — ten-project administrators. A smaller population. Can hold multiple projects in mind, switch contexts efficiently, manage parallel timelines. The functional senior managers in most organizations. Most operational leadership roles are sized for tier 2; assigning tier 1 people into them produces the burnout failure mode and assigning tier 3 people into them produces the boredom failure mode.
Tier 3 — hundred-project administrators ("rare gems"). Pillai's wording. A small fraction of the population. Can hold an entire department or business unit in their head, run dozens of parallel initiatives, integrate across domains the rest of the organization treats as separate. These are the rare integrators. Most organizations have one or two; the rest of the senior staff are tier 2. The diagnostic for tier 3: when given a tier 2 load, they get frustrated. Now what if the person who is capable of handling hundred projects is given only one project? He too will get frustrated in a different manner. The person thinks, "I am wasting my time here. The work assigned to me can be finished in no time. It is a no-brainer for me. The remaining time I am sitting idle. Give me more work."1
The mismatch produces two distinct failure modes — and they are not symmetric. Burnout (over-load on under-capacity) is total failure. Frustration (under-load on over-capacity) is exit-or-disengage failure. Both are bad. They are bad differently.
The over-loaded tier 1 administrator does not deliver one project well; they deliver zero projects well. The whole portfolio collapses because the cognitive load exceeds the capacity. Recovery from the burnout failure is hard — the administrator may need months to reconstruct their capacity even after the load is reduced.
The under-loaded tier 3 administrator delivers the one project trivially — and leaves the organization, or disengages and stops contributing the strategic value tier 3 capacity actually produces. The frustration failure looks fine on the immediate task and catastrophic on the longer arc. The organization that has lost a tier 3 administrator to under-load may not realize what they lost until the strategic-integration work nobody else can do starts going undone.
The doctrine therefore prescribes deliberate match: the right person should be given the right amount of work.1 Not "people work hard." Not "stretch assignments build people." Capacity-matched assignment, recognized capacity tiers, deliberate placement. The leader running this discipline knows each direct report's tier and matches the load accordingly.
Beyond the work-tier match, the doctrine prescribes three additional alignments.
Rank match. If a person is capable of running a full organization, do not make him or her a vice president. Make that person a CEO or a business unit head. They will feel empowered and work enthusiastically.1 Rank is recognition + authority. Tier 3 administrator at vice-president rank is being signaled "you are not the integrator we need" — even if the work assigned is tier-3 sized, the rank misalignment poisons the assignment.
Place match. Pillai's prime-minister-direct-reporting anchor. The high-performing administrator close to consequential decision-making produces strategic value. The same administrator in a remote district produces files that get filed and stop. Place determines the multiplier on capacity.
Time match. Mission-mode framing. Deadline-driven work where the deadline matches the administrator's capacity-to-deliver. The Patanjali quote Pillai cites: "When you are inspired by some great purpose, some extraordinary project, all your thoughts break their bonds: Your mind transcends limitations, your consciousness expands in every direction and you find yourself in a new, great and wonderful world. Dormant forces, faculties and talents become alive..."1 Time-bounded purpose-driven work activates capacity that drift-time work does not.
Pillai's framing places this sutra inside the king's responsibilities — Chanakya created about eighteen departments that were efficiently run during Chandragupta's rule.1 Eighteen departments. Each headed by an adhyaksha. Each adhyaksha matched to capacity, rank, place, time, work. The king's job at this scale is not running the work; it is running the people who run the work, and the four-axis assignment is what determines whether that delegation produces output or chaos.
Modern executives at the top of organizations face the same problem. The CEO of a multi-thousand-person company does not run the work of any single function; they run the people who run the functions. The four-axis assignment determines whether the company produces strategic execution or strategic drift. The CEO who has not done the capacity-tier mapping for their direct reports is guessing at every assignment.
1. Map your direct reports by capacity tier. For each person reporting to you, observe — not assume — what capacity tier they operate in. Past performance under varying loads is the data. The administrator who has thrived under multi-project portfolios is tier 2 or tier 3; the one who has struggled with that load and excelled under single-stream is tier 1. Write the tier assessments down rather than holding them as vague impressions.
2. Audit current assignments against capacity. For each person, ask: is the current load matched to their tier? The over-loaded tier 1 person needs load reduction. The under-loaded tier 3 person needs load expansion or risk losing them. Most leaders find at least one mismatch in their current org chart when they do this honestly.
3. Run the four-axis check on any new assignment. Before assigning a project or role: does the rank match the work? Does the place match the rank? Does the time match the place? Does the work match the capacity? The four-axis check takes ten minutes and prevents months of recovery from a bad assignment.
4. Watch for the mid-tier-pressure failure mode. The most common assignment error in modern organizations: assigning tier 2 administrators to tier 3 problems and hoping they grow into the role. Sometimes this works (capacity is somewhat malleable). More often, it produces a degraded version of tier 3 work plus burnout in the tier 2 administrator. The honest assessment is whether the person is stretching or breaking. If breaking, scale the assignment back; the org that consistently breaks tier 2 people on tier 3 work has a tier 3 hiring problem, not a tier 2 development problem.
5. Place the rare gems near the consequential decisions. Tier 3 administrators wasted in peripheral positions are the largest preventable strategic loss in most organizations. Identify the tier 3 people you have. Move them close to the work that needs integration. Give them rank and authority commensurate with what they can actually do. The cost of moving a tier 3 person is moderate; the cost of leaving them under-placed is enormous.
6. Use the Patanjali anchor for the time-mission match. Purpose-bounded mission mode produces capacity expansion that drift-time work does not. Frame assignments with the purpose attached, not just the deliverable. Why does this matter and what does it open up? — the capacity activated by the purpose framing is real and operationally useful.
Capacity tiers are presented as fixed. Pillai's framing implies people operate at a single tier reliably. Modern organizational research suggests capacity is partially malleable — administrators move between tiers based on context, training, motivation, and life circumstances. The page's reading of fixed tiers may oversimplify. The mitigation: treat the tier assessment as current rather than permanent, and re-assess regularly.
The "100 projects" tier may be partially mythical. Tier 3 administrators exist; whether any human reliably handles literally 100 simultaneous projects is questionable. The number is more useful as ordinal (way more than tier 2) than as cardinal (exactly 100). Pillai's framing is rhetorical here; the doctrinal claim survives even if the specific count does not.
The doctrine assumes the leader can accurately observe capacity. In practice, capacity assessment is contaminated by visibility — administrators who present well are read as higher-tier than administrators who deliver quietly. The page's discipline (observe past performance under varying loads) is the corrective, but it requires the leader to actually have the data. Many organizations do not.
Read this page next to the existing Adhyaksha Network — Bureaucratic Architecture (sourced from Trautmann/Kangle) and watch what the two pages reveal together. The adhyaksha page describes the structure of Kautilyan administration — eighteen named departments, specialization plus integration plus audit. This page describes the selection mechanism that places people into that structure. Two halves of the same governance design. The structural architecture without the selection discipline produces beautifully-organized incompetence. The selection discipline without the structural architecture produces high-capacity administrators with nowhere coherent to deploy. Kautilya's governance treats both as required.
Pillai's framing within his own corpus shows internal coherence: the Saptanga page gives the kingdom architecture; the Three Shaktis page gives the leader's powers (counsel, might, energy); this page gives the assignment mechanism that translates leader-powers into kingdom-functioning through capacity-matched administrators. The chain runs: leader → counsel/might/energy → assignments → administrators → kingdom limbs → outcomes. Removing any link breaks the chain.
Behavioral mechanics — modern executive succession and capacity-fit research. Contemporary leadership-development research has documented that executives operate at characteristic complexity levels — some thrive with multi-stream parallel decision-making, some break under it, and the matching of executive to role complexity predicts outcomes more reliably than any other single variable. Elliott Jaques's requisite organization framework (1980s–1990s) maps individual capacity-tiers (Stratum I through Stratum VII) onto organizational role-complexity. The Stratum levels are functionally identical to Pillai's three tiers expanded to seven. Modern HR research has independently rediscovered the capacity-tier assignment problem and produced more granular taxonomies than Pillai gives. The structural insight is the same. The cross-domain convergence: capacity-tier-to-role-complexity matching is one of the most-validated propositions in modern organizational psychology, and Kautilya prescribed it operationally 23 centuries before the validation. The leader applying the four-axis discipline is running what modern research calls level-of-work matching — and the research evidence supports the practice strongly.
Psychology — the Yerkes-Dodson curve and load-performance relationships. The Yerkes-Dodson law (1908) describes an inverted-U relationship between arousal/load and performance: too little load produces under-performance (boredom); too much load produces under-performance (overwhelm); the peak is at calibrated load matched to the individual's capacity. Pillai's burnout-vs-frustration failure modes are the two flat ends of the Yerkes-Dodson curve. The doctrine names what Yerkes-Dodson measures — both ends of the load-capacity mismatch curve produce performance collapse, and the calibrated middle is where capacity is fully expressed. The cross-domain convergence reveals: matching load to capacity is not a soft management nicety; it is a structural performance variable that has measurable effects across the population. The leader who runs the four-axis discipline is operating in the calibrated middle of the curve for each direct report; the leader who does not is running their organization at the flat ends.
Cross-domain — the modern hiring-misfit research and "Peter Principle" failure modes. Lawrence Peter's 1969 observation — people rise to the level of their incompetence — describes a structural failure mode of hierarchical organizations: each promotion eventually puts the administrator into a role that exceeds their capacity, and that is where they stop being promoted. The Peter Principle and the four-axis discipline are inverse statements of the same insight. The Peter Principle describes what happens when capacity-tier assignment is not done deliberately. The four-axis discipline is the prescription for doing it deliberately. Modern organizations that fall into Peter Principle patterns are usually organizations where the four-axis discipline is not running. The cross-domain convergence: organizational health requires deliberate capacity-tier matching; left to default mechanisms (promotion-based-on-current-role-success), organizations drift into structural incompetence at upper levels.
The Sharpest Implication. Most organizational dysfunction at scale is not a leadership-quality problem; it is an assignment problem. The same people who would perform well in correctly-matched roles produce failure in mis-matched ones, and the leader who blames the people rather than the assignment is treating a symptom of their own selection-discipline failure as if it were a personnel problem. The implication is uncomfortable: the failures of administrators in your organization are usually failures of your matching, not failures of their capacity. The fix is honest tier-assessment of every direct report, audit of current assignments against tier, and deliberate re-assignment where the audit reveals mismatch. This requires the leader to admit they have been mis-assigning people, which most leaders resist because the admission feels like a competence failure. The competence failure was the original mis-assignment; the re-assignment is the recovery. The leader who runs the audit honestly will find that several of their hardest organizational problems dissolve once the right people are in the right roles.
Generative Questions.