Core Principles of Administration: Guidelines for Effective Management

Every large organisation, from a government ministry to a multinational corporation, faces the same fundamental puzzle: how do you get hundreds or thousands of people to work together without chaos? The classical thinkers of public administration, particularly Henri Fayol, Luther Gulick, and Lyndall Urwick, tried to solve this puzzle by proposing a set of universal principles. These principles, developed between 1916 and 1937, still shape how ministries, municipalities, and corporations are structured today. Let us walk through the core principles of administration and understand why they continue to matter.

The intellectual foundation: Why principles of administration mattered 🔗

The early twentieth century was a turbulent time for organisations. Factories were expanding, governments were taking on new welfare functions, and managers were often operating on instinct rather than systematic knowledge. Into this gap stepped Henri Fayol, a French mining engineer who later became known as the “father of modern management.” In his 1916 book Administration Industrielle et Générale, Fayol argued that managerial skills could be taught as “administrative functions” and that effective organisations could be built on general principles derived from day-to-day experience.

A few decades later, Luther Gulick and Lyndall Urwick refined and expanded Fayol’s work. Their 1937 collection, Papers on the Science of Administration, attempted to establish administration as a genuine science with teachable principles. As one study of classical theory notes, Gulick explicitly adapted his analysis of the chief executive’s work from Fayol’s earlier framework, creating a bridge between European managerial thought and American public administration.

Division of work and departmentalization 🔗

No single person can do everything. This simple observation lies at the heart of the first major principle, known as division of work or specialisation. When tasks are broken down and assigned to people with specific skills, productivity rises. A tax officer becomes efficient at tax assessment precisely because that is all she does; a surgeon becomes skilled at operations because she is not also running the hospital’s accounts.

But once work is divided, it must also be grouped, and this is where departmentalization enters the picture. Gulick proposed that departments within any organisation can be formed on four distinct bases, famously called the “4 Ps.”

Purpose or function 🔗

Here, departments are built around the end goal they serve. A Ministry of Health exists to deliver healthcare; a Ministry of Education exists to provide schooling. This approach ensures that purpose-based departmentalization creates self-contained units focused on specific products, customers, or geographic areas, which makes accountability straightforward.

Process or skill 🔗

Sometimes it makes more sense to group people by the technique or skill they share. All the engineers sit in one department, all the accountants in another. This is the logic behind having a Public Works Department that handles construction across ministries, or a central Printing Department that serves the entire government.

Clientele or persons served 🔗

Departments can also be organised around the people they serve. Think of the Ministry of Tribal Affairs or a department dedicated to veterans’ welfare. The entire structure revolves around meeting the specialised needs of a particular group.

Place or geography 🔗

Finally, departments may be structured by location. District administration, regional railway zones, and North-Eastern Council offices follow this logic. When problems or populations differ by geography, spatial grouping makes coordination easier.

Gulick himself acknowledged that no single basis is superior. In practice, large organisations blend all four. As one analysis observes, no department is created on a single basis from top to bottom; different levels and sections may use different bases depending on administrative convenience and socio-economic conditions. The Ministry of Agriculture, for instance, is both functional (agriculture) and clientele-based (farmers).

Unity of command: One boss per employee 🔗

Fayol’s fourth principle and one of his most enduring contributions is unity of command. The rule is elegantly simple: every employee should receive orders from one superior only. When two bosses issue conflicting instructions, discipline collapses, authority becomes unclear, and subordinates are caught in the crossfire.

Gulick endorsed this view strongly. In his coordination principles, he emphasised that each worker should have only one direct superior to avoid confusion and inefficiency. Anyone who has worked in a dysfunctional workplace with multiple reporting lines understands the wisdom here. A junior officer reporting simultaneously to two deputy secretaries on the same file will either please neither or become a skilled diplomat at the cost of actual work.

Closely related is unity of direction, which says that activities with the same objective should be guided by one plan and one head. If three different wings of a ministry are pursuing overlapping agricultural policies under three different directors, the result is duplication, waste, and policy incoherence.

Span of control: How many is too many? 🔗

The concept of span of control addresses a deceptively practical question: how many subordinates can one manager effectively supervise? Urwick famously championed this principle, arguing that there is a natural limit to human attention and coordination capacity.

The idea has obvious intuitive appeal. A Collector who directly supervises forty officers cannot possibly give each one meaningful attention. Gulick and Urwick suggested that the most effective arrangement assigns roughly three to six employees to each manager, though the exact number depends on the nature of the work and the independence of the subordinates.

When the span is too wide, supervision suffers. When it is too narrow, organisations become top-heavy with layers of middle managers, decisions slow down, and costs balloon. This is why modern civil service reforms often try to flatten hierarchies while still respecting reasonable spans of control.

Authority, responsibility, and the scalar chain 🔗

Fayol believed that authority and responsibility must go hand in hand. You cannot hold someone accountable for a task without also giving them the power to get it done. As one summary of his principles puts it, the right to give orders should not be considered without reference to responsibility, and the two must remain in balance.

Flowing from this is the scalar chain, the unbroken line of authority that runs from the top of the organisation to the bottom. In a state government, this chain might run from the Chief Minister through the Chief Secretary, to departmental secretaries, down to joint secretaries, deputy secretaries, section officers, and finally to dealing assistants. Fayol did acknowledge the need for what he called the “gang plank,” a horizontal shortcut that allows peers at similar levels to communicate directly when formal channels would cause dangerous delays.

Coordination: The master principle 🔗

If division of work creates specialists, coordination is what prevents them from pulling the organisation apart. Mooney and Reiley, writing in the same tradition, went so far as to call coordination the first principle of organisation. Without it, specialisation produces silos, and silos produce failure.

Gulick identified two main mechanisms for achieving coordination. The first is coordination through hierarchy, where authority flowing down the chain of command aligns the efforts of subordinates. The second is coordination through ideas or deliberate coordination, where shared objectives, committees, and inter-departmental consultations bring people together voluntarily. In practice, both mechanisms are needed. The Cabinet Secretariat, empowered committees of secretaries, and inter-ministerial groups all reflect the continuing relevance of this principle.

POSDCORB: The executive’s functional blueprint 🔗

Perhaps the most famous acronym in public administration, POSDCORB, was Gulick’s attempt to answer a deceptively simple question: what does a chief executive actually do? The seven letters stand for Planning, Organising, Staffing, Directing, Coordinating, Reporting, and Budgeting.

As scholars note, POSDCORB was crafted by Gulick and Urwick to make public administration effective and was presented in the Papers on the Science of Administration in 1937. Each function captures a core responsibility. Planning sets the direction. Organising builds the structure. Staffing fills it with people. Directing provides day-to-day leadership. Coordinating harmonises efforts. Reporting keeps everyone informed. Budgeting allocates resources.

POSDCORB became enormously influential in shaping Indian administrative training, including at institutions like the Lal Bahadur Shastri National Academy of Administration. It gave civil servants a mental checklist for what leadership actually meant in practice.

Urwick’s eight principles and the search for coherence 🔗

Urwick went further than Gulick in codifying the principles explicitly. His eight principles include the principle of objectives (every organisation must have a clear purpose), correspondence (authority and responsibility must match), responsibility (superiors remain accountable for subordinates), the scalar principle, span of control, specialisation, coordination, and definition (roles must be clearly defined in writing).

Together with Gulick’s ten principles covering division of work, departmental bases, coordination, decentralisation, unity of command, line and staff, delegation, and span of control, these form the classical canon of administrative principles.

Criticisms and continuing relevance 🔗

No intellectual edifice survives without challenge, and the classical principles were seriously contested by later scholars. Herbert Simon’s 1946 essay “The Proverbs of Administration” was particularly devastating. Simon argued that for almost every principle, one could find an equally plausible and contradictory principle, calling the whole framework an oversimplification of administrative reality.

Simon pointed out that span of control and unity of command often conflict in practice. A matrix organisation, for example, deliberately violates unity of command because modern work sometimes requires inputs from multiple specialists. Similarly, the four bases of departmentalization overlap so much that choosing among them can feel arbitrary.

Despite these criticisms, the classical principles have not disappeared. They endure because they capture enduring truths about human organisations: people need clear roles, clear reporting, reasonable supervision, and mechanisms for cooperation. Modern reforms in governance, from the Second Administrative Reforms Commission’s recommendations to the restructuring of public sector undertakings, continue to grapple with these same issues, even if the answers have grown more nuanced.

Why these principles still shape governance today 🔗

When a new ministry is carved out of an existing one, the debate over whether to organise it by purpose or process is essentially a Gulickian debate. When administrative reforms propose flatter hierarchies, they are arguing about span of control. When officers complain about receiving orders from multiple superiors, they are invoking unity of command. The vocabulary may have changed, but the underlying grammar of organisational design still draws heavily from these early twentieth-century principles.

The genius of Fayol, Gulick, and Urwick was not that they gave us final answers but that they gave us a shared language for asking the right questions. In a world of expanding government functions, digital workflows, and increasingly complex public problems, that language remains indispensable.

What do you think? In an era of matrix teams, digital collaboration platforms, and agile governance, do principles like unity of command and rigid span of control still hold, or do they need fundamental rethinking? And when a department seems to serve multiple purposes at once, which of Gulick’s four bases should guide its design?

References

1. https://www.mindtools.com/asjiu77/henri-fayols-principles-of-management/
2. https://en.wikipedia.org/wiki/POSDCORB
3. https://en.wikipedia.org/wiki/Departmentalization
4. https://gkscientist.com/department/
5. https://www.toolshero.com/management/posdcorb-theory/
6. https://www.iedunote.com/14-management-principles-henri-fayol/
7. https://www.yourarticlelibrary.com/public-administration/posdcorb-its-administration-and-evaluation/63423