Henri Fayol’s 14 Principles of Management

A Practitioner’s Guide — Beyond the Textbook

Why Fayol Still Matters — and Why Most Articles Get Him Wrong

Henri Fayol published his 14 Principles of Management in 1916 as part of his broader theory of administrative management. He was writing as a practitioner — a mining engineer who had spent decades running large organizations — not as an academic theorist. That matters, because his principles were designed to solve real operational problems, not to fill textbook chapters.

Most summaries of Fayol’s work stop at definitions. This guide goes further: for each principle, you’ll find the core idea, a practitioner interpretation drawn from real operations and project management experience, and an honest assessment of where the principle still holds and where it breaks down in modern organisations.

Who Was Henri Fayol?

Henri Fayol (1841–1925) was a French mining engineer and executive who spent most of his career at Compagnie de Commentry-Fourchambault et Decazeville, eventually serving as its director general for 30 years. He turned around a failing company and documented the management principles that underpinned his approach in his 1916 work Administration Industrielle et Générale.

Fayol identified five core functions of management — planning, organising, commanding, coordinating, and controlling — and 14 principles that supported effective administration. Unlike Frederick Winslow Taylor, who focused on optimising individual task efficiency, Fayol was concerned with how to structure and lead entire organisations. His work is the foundation of what we now call classical management theory.

The 14 Principles: A Practitioner’s Deep Dive

Each principle below includes the core concept, a practitioner commentary based on real operations and project management environments, and a plain-English view of its modern relevance.

1. Division of Work

Specialisation increases efficiency. When people focus on a defined area, they develop deeper skill and make fewer errors.

Practitioner View: In business operations, this plays out daily. A team split between inbound calls and back-office processing will almost always outperform a generalist team handling everything. The risk is over-specialization — narrow roles can create bottlenecks when key people are absent. The practical fix is cross-training at least one backup per critical function.

2. Authority and Responsibility

Authority (the right to give orders) must be balanced with responsibility (accountability for outcomes). You cannot hold someone accountable for results if they lack the authority to act.

Practitioner View: This is one of the most commonly violated principles in project management. I have seen operations managers held accountable for vendor SLAs they had no authority to enforce or renegotiate. If you’re assigning ownership of a deliverable, ensure the person has the access, budget, and decision rights to go with it.

3. Discipline

Employees must follow agreed rules and norms. Leaders are responsible for fair, consistent enforcement — not punishment for its own sake.

Practitioner View: Discipline in operations isn’t about enforcement — it’s about consistency. Inconsistent application of policies (e.g., attendance rules applied strictly to some and loosely to others) destroys team morale faster than almost anything else. The standard you walk past is the standard you accept.

4. Unity of Command

Each employee should receive orders from only one supervisor. Conflicting instructions from multiple managers create confusion, stress, and accountability gaps.

Practitioner View: Matrix organisations violate this constantly — and pay the price. When a project team member reports to both a functional manager and a project manager, they’ll often get conflicting priorities. The workaround is a documented RACI that clarifies who has decision authority vs. who provides input.

5. Unity of Direction

All activities aimed at the same objective should be grouped under one plan and one manager.

Practitioner View: This is where poor OKR alignment shows up. Teams working toward different interpretations of the same goal will drift. The diagnostic question is simple: can every team member articulate the same top priority? If answers vary, you have a unity of direction problem.

6. Subordination of Individual Interest to General Interest

The goals of the organisation take precedence over individual or departmental interests.

Practitioner View: Departmental silos are the enemy of this principle. When a finance team delays a project approval to protect their own quarterly numbers, or a department head hoards resources to look good in reviews, the general interest suffers. Building cross-functional accountability into performance reviews is one practical counter-measure.

7. Remuneration

Compensation should be fair, equitable, and motivating — for both employees and the organisation.

Practitioner View: Fayol understood that underpaying creates attrition, and overpaying without structure creates entitlement. In high-turnover environments like IT and contact centres, compensation benchmarking matters enormously. But so does non-financial remuneration — recognition, flexibility, and development opportunities often move the needle more than incremental pay increases for frontline staff.

8. Centralisation

Decision-making authority should be concentrated or distributed based on what best serves the organisation — there is no one-size-fits-all answer.

Practitioner View: Fayol was ahead of his time here. He didn’t advocate for centralisation — he advocated for calibration. Fast-moving operational decisions (routing, scheduling adjustments, escalation handling) need to be decentralised. Strategic and financial decisions often need to stay central. The trap is centralising everything for control, which slows execution.

9. Scalar Chain

A clear line of authority should exist from the top of the organisation to the bottom. Communication should follow this chain — but Fayol also allowed for a ‘gangplank’ (direct cross-communication) when speed demands it.

Practitioner View: The gangplank concept is often overlooked. Fayol didn’t say people must always go through the chain — he said the chain should exist and be respected, but that peers can communicate directly when time is critical, provided they inform their respective managers. That’s essentially what we call stakeholder escalation protocols today.

10. Order

Resources — both material and human — should be in the right place at the right time.

Practitioner View: In workforce management, this is the entire discipline. WFM tools exist precisely to solve the order problem: ensuring the right number of people with the right skills are scheduled at the right intervals. When order breaks down — wrong shift patterns, misaligned skills — service levels follow immediately.

11. Equity

Leaders should treat employees with fairness and kindness. Equity is not identical treatment — it is just treatment.

Practitioner View: Equity vs. equality is a live debate in modern people management. Equity means adjusting support based on individual need — a newer team member may need more coaching time; a high performer may need more autonomy. The risk is that inequitable treatment, however well-intentioned, is perceived as favouritism if it isn’t communicated transparently.

12. Stability of Tenure of Personnel

High employee turnover is costly and disruptive. Organisations should prioritise stability and retention.

Practitioner View: This is one of the most undercosted problems in operations. Attrition doesn’t just show up in recruitment costs — it shows up in quality scores, customer satisfaction, and the hidden cost of experienced colleagues spending time training replacements instead of doing their primary role. A 30% annual attrition rate means you’re rebuilding a third of your capability every year.

13. Initiative

Employees should be encouraged to take initiative within the boundaries of their role. Leaders who suppress initiative lose the creative energy of their team.

Practitioner View: The best process improvements I’ve seen in operations have come from frontline staff who spotted inefficiencies no manager would have noticed. Creating structured channels for initiative — even simple suggestion mechanisms with rapid feedback — unlocks significant value. The failure mode is organisations that invite ideas but never act on them.

14. Esprit de Corps

Team unity and morale are organisational assets. Leaders should actively cultivate a culture of camaraderie and shared purpose.

Practitioner View: This isn’t about pizza Fridays. Esprit de corps in a high-pressure operations environment comes from shared wins, clear purpose, and feeling seen by leadership. Teams that celebrate milestones together — even small ones — perform better under pressure. The signal that esprit de corps is failing is quiet: people stop offering to help, collaboration becomes transactional.

At a Glance: All 14 Principles Summary Table

Use this as a quick reference when applying Fayol’s framework to your own organisation or projects.

Principle	Core Idea	Modern Relevance	When It Fails
Division of Work	Specialisation increases efficiency.	Still highly relevant	When over-applied in flat or agile teams where flexibility is essential
Authority and Responsibility	Authority (the right to give orders) must be balanced with responsibility (accountability for outcomes).	Critically relevant	When authority is centralised at the top but accountability is pushed to the front line
Discipline	Employees must follow agreed rules and norms.	Relevant, but tone has evolved	When applied rigidly in high-autonomy or creative environments
Unity of Command	Each employee should receive orders from only one supervisor.	Partially relevant	Matrix and agile structures where multiple reporting lines are intentional
Unity of Direction	All activities aimed at the same objective should be grouped under one plan and one manager.	Highly relevant	When organisations set too many strategic priorities simultaneously
Subordination of Individual Interest to General Interest	The goals of the organisation take precedence over individual or departmental interests.	Relevant, but requires careful framing	When used to suppress legitimate employee concerns or override individual wellbeing
Remuneration	Compensation should be fair, equitable, and motivating — for both employees and the organisation.	Very relevant	When organisations treat compensation as the only lever for motivation
Centralisation	Decision-making authority should be concentrated or distributed based on what best serves the organisation — there is no one-size-fits-all answer.	Highly relevant	When organisations default to centralisation as a control mechanism rather than a deliberate design choice
Scalar Chain	A clear line of authority should exist from the top of the organisation to the bottom.	Relevant in structured organisations	In flat or agile teams where hierarchy is minimal by design
Order	Resources — both material and human — should be in the right place at the right time.	Very relevant	When used to justify rigid processes over adaptive planning
Equity	Leaders should treat employees with fairness and kindness.	Critically relevant	When equity is interpreted as treating everyone identically regardless of context
Stability of Tenure of Personnel	High employee turnover is costly and disruptive.	Very relevant	When used to justify retaining underperformers out of a preference for stability
Initiative	Employees should be encouraged to take initiative within the boundaries of their role.	Highly relevant	When initiative is permitted in theory but penalised in practice through bureaucratic friction
Esprit de Corps	Team unity and morale are organisational assets.	Critically relevant	When it becomes performative culture-washing rather than genuine team investment

Where Fayol’s Framework Falls Short

Fayol’s principles were developed for hierarchical, stable, industrial-era organisations. They work best when roles are clearly defined, environments are relatively predictable, and authority flows through a single chain of command. Modern organisations increasingly look different:

• Agile and flat teams deliberately break unity of command and scalar chain.
• Remote and distributed work challenges discipline, order, and esprit de corps in new ways.
• Matrix structures create intentional dual reporting, which Fayol’s framework treats as a problem.
• Psychological safety — now recognised as a primary driver of team performance — is underweighted in Fayol’s framework relative to authority and discipline.

None of this makes the 14 principles obsolete. It means they are best used as a diagnostic lens — a way of asking ‘what is broken here and why?’ — rather than a prescriptive operating model.

Frequently Asked Questions

Q: Are Fayol’s 14 Principles of Management still relevant today?

A: Yes — most of them, with context. Principles like equity, initiative, esprit de corps, and the balance between authority and responsibility are as applicable in a modern agile team as they were in a 1910 mining operation. Others, like unity of command, need adaptation for matrix and flat structures. The key is treating them as frameworks for thinking, not rigid rules.

Q: What is the most important of Fayol’s 14 principles?

A: There is no single most important principle — they are interdependent. That said, authority and responsibility are foundational: if accountability is not matched with decision-making power, every other principle is harder to apply. Unity of direction is similarly critical because without shared goals, even well-run teams pull in different directions.

Q: How do Fayol’s principles apply to project management?

A: Directly. Division of work maps to role clarity and WBS design. Scalar chain maps to escalation paths and stakeholder hierarchies. Unity of direction maps to project vision and OKR alignment. Stability of tenure matters for managing team continuity through a project lifecycle. Fayol’s framework provides a useful diagnostic lens for common project failure patterns.

Q: What are the limitations of Fayol’s 14 principles?

A: The main limitations are that they were developed for hierarchical, industrial-era organisations and assume relatively stable environments. They fit less naturally with agile, self-organising, or flat team structures. Principles like unity of command and scalar chain can actively conflict with cross-functional collaboration models. They also underweight psychological safety, which research has since identified as a key driver of team performance.

Q: How does Fayol’s management theory compare to Taylor’s scientific management?

A: Taylor focused on optimising individual task efficiency from the bottom up — time-and-motion studies, standardised methods, piece-rate pay. Fayol focused on organisational structure and managerial functions from the top down. They are complementary: Taylor tells you how to design work; Fayol tells you how to structure the organisation doing it. Most modern management frameworks draw on both.

Final Thoughts

Over 20 years working in project management and operations — including global client delivery, and process improvement — I have seen Fayol’s principles play out in ways that no textbook fully captures. The organizations that struggle most are rarely those that have never heard of Fayol. They are the ones that violate two or three of his principles consistently: misaligned authority and responsibility, no unity of direction, suppressed initiative, or chronically high attrition.

You do not need to treat Fayol’s 14 principles as a checklist. But running a periodic diagnostic against them — asking which principles are strong in your organisation and which are quietly failing — is a genuinely useful exercise. The answers are often uncomfortable, and usually actionable.

Related Reading on ProjInsights

• Decision Log: How to Build Organisational Memory That Actually Works
• Emotion vs. Fact in Operations and Project Management
• Mastering Follow-Up Strategies: How to Stay Ahead Under Pressure
• Why Honesty Is Your Best Policy in Business