Principles of Organization in Management (with Examples)

Table of Contents

• What is organization as a management function?
• The 6 principles of organization

  • Division of work
  • Hierarchy
  • Unity of command
  • Span of control
  • Delegation
  • Coordination
• Types of organizational structure

  • Line structure
  • Functional structure
  • Matrix structure
  • Divisional structure
  • Flat / network structure
  • How to choose?
• Application examples

  • Case 1 · A neighborhood bakery
  • Case 2 · A 25-person digital agency
  • Case 3 · A consumer multinational
  • Case 4 · A software startup
• Org chart: how to reflect the principles
• Frequently asked questions

  • What is organization as a management function?
  • What are the principles of organization?
  • Difference between line and matrix structure?
  • How many people can a manager supervise?
  • Why is it said that division of work creates silos?
• Conclusion

What is organization as a management function?

Within the four classic functions (planning, organizing, leading, controlling), organizing is the one that designs the structure the company will run on. It consists of:

1. Identifying all the tasks that need to be done to reach the objectives.
2. Grouping those tasks into positions and departments.
3. Assigning authority and responsibilities to each position.
4. Establishing the hierarchical and coordination relationships among them.

The result is the org chart: a visual representation of who does what, who reports to whom, and how information flows.

Organizing well is decisive because a poorly designed structure can sink a company with a good product and a good team. Wrong structures generate silos, slow decisions, duplicated effort, and conflict. Right structures enable speed, clarity, and focus.

The 6 principles of organization

Although different authors propose varied lists, there are six principles that capture the universal practice of business organization.

Division of work

It's the starting point: specialization. Instead of everyone doing everything (sales, production, accounting), each person focuses on one area. Result: more efficiency, more skill, less time lost to context switching.

Example: In a restaurant, there's a cook, a waiter, a cashier, and a manager. Each one specializes. If everyone did everything, chaos would be guaranteed.

Modern limit: Extreme specialization breeds boredom and fragility (if that person leaves, everything stops). That's why today we seek to combine specialization with versatility.

Hierarchy

Hierarchy is the chain of authority running top-down (and bottom-up) in the organization. Each level has a degree of authority over the level below, and answers to the one above.

Example: CEO → Marketing Director → Sales Manager → Sales Rep. Information flows both ways: objectives downward, reports and problems upward.

Modern risk: A hierarchy with too many layers creates the "telephone game": information gets distorted as it passes through layers. The current trend is to flatten the hierarchy to speed up decisions.

Unity of command

Each person should report to a single boss. If they get instructions from two, there's conflict over priorities and a dilution of responsibility.

Example: A designer who gets briefings from both the Marketing Director and the Product Director will be lost. They need a single point of reference.

Modern exception: Matrix structures deliberately break this principle (a developer reports to their tech lead and to their product manager). They work when there's clarity: each boss decides in their domain, and disputes are resolved with a protocol.

Span of control

The span of control is the number of people a manager can effectively supervise. Too wide → loss of control. Too narrow → too many managers, extra cost.

Practical rules:

• Routine, predictable work → wide span (15-30 people).
• Complex or creative work → narrow span (5-8 people).
• Mature, autonomous teams → span as wide as possible.

Common mistake: Promoting the best technician to manager and giving them a team of 12 people with no training. The span breaks and everyone suffers.

Delegation

Delegation is the mechanism by which a manager transfers authority and responsibility to a subordinate so they can make decisions on their behalf. Without delegation, everything escalates to the boss, who becomes a bottleneck.

Elements of good delegation:

1. Specific task: what needs to be done.
2. Sufficient authority: the power to decide what's needed.
3. Clear responsibility: answering for the results.
4. Limits: how far they can decide on their own, from where they must consult.

Typical mistake: Delegating the task but not the authority. "Do it, but check with me at every step." That's not delegating: it's micromanagement.

Coordination

Division of work creates specialists; coordination makes those specialists work as a team, not as isolated silos.

Coordination mechanisms (Mintzberg):

• Mutual adjustment: informal communication (typical of small teams and startups).
• Direct supervision: a manager coordinates (classic in hierarchical structures).
• Standardization: processes, norms, skills, outputs (typical of large companies).
• Rituals: dailies, weeklies, retrospectives (typical of agile teams).

Without coordination, division of work generates silos: marketing chases its KPI, sales its own, and product another. The customer notices the inconsistency.

Types of organizational structure

The principles aren't always applied the same way: they give rise to different types of structure, each useful depending on the context.

Line structure

Each person reports to a single boss, in a clear chain. Simple, easy to understand, slow for complex decisions. Typical of traditional SMEs and family businesses.

Functional structure

Departments are grouped by specialty (marketing, finance, production, HR). Efficient through specialization, but tends to create silos. Typical of mid-sized companies.

Matrix structure

Each person reports to two bosses: one functional (their specialty) and one project or product lead. Combines specialization and focus, but creates tension if not managed well. Typical of tech companies and consultancies.

Divisional structure

The company is split by products, markets, or geographies. Each division runs almost like an independent company. Typical of multinationals (Unilever, by product category).

Flat / network structure

Minimal hierarchical layers. Autonomous teams, direct communication. Fast but demands high maturity. Typical of startups and agile companies like Valve or Basecamp.

How to choose?

There's no perfect structure. It depends on:

• Size: more people, more structure.
• Industry: mass production favors functional; innovation favors matrix or flat.
• Culture: flat structures require trust-based cultures.
• Timing: what works during growth doesn't work in crisis.

Application examples

Case 1 · A neighborhood bakery

Pure line structure. The owner is baker, seller, and accountant. When growing to 3 people: split roles (baker, shop assistant, delivery). Span of control: 3 people, can be supervised directly. Unity of command: clear, everything goes through the owner.

Case 2 · A 25-person digital agency

Matrix structure. Each designer reports to the Creative Director (functional) and to the Project Manager of the client they're assigned to (project). It works if the two bosses agree on priorities; it blows up if each pulls their own way.

Case 3 · A consumer multinational

Divisional structure by categories (food, cleaning, personal care). Each division has its own marketing, sales, and production. Coordination across divisions through committees and standardized processes.

Case 4 · A software startup

Flat structure. 4 autonomous squads, each with a clear objective, with no middle manager between the team and the CEO. Coordination through dailies and weekly demos. Wide spans of control (8-12 people per squad).

Org chart: how to reflect the principles

The org chart is the visual representation of the structure. A good org chart should:

1. Show a clear hierarchy: top-down levels, with no ambiguity.
2. Reflect functional vs. hierarchical relationships: in a matrix, with different line styles.
3. Indicate the span of control: the number of people under each manager.
4. Include names and titles, not just abstract departments.
5. Be up to date: an old org chart creates more confusion than having none at all.

Frequent mistake: Making an org chart and forgetting about it. A company's real structure almost never matches the official org chart. It must be updated every time there's a reorganization.

Frequently asked questions

What is organization as a management function?

It's one of the four classic functions (planning, organizing, leading, controlling). It consists of grouping tasks into positions, assigning authority, and designing the relationships between areas. The result is the org chart.

What are the principles of organization?

The six main ones are: division of work, hierarchy, unity of command, span of control, delegation, and coordination. Fayol included some of these in his 14 general principles of management.

Difference between line and matrix structure?

In a line structure, each person reports to a single boss. In a matrix, they report to two: one functional and one project lead. The matrix is more flexible but requires better conflict management.

How many people can a manager supervise?

It depends on the work. Routine tasks allow wide spans (15-30). Complex or creative work requires narrow spans (5-8). The modern rule: small, autonomous teams outperform large, supervised ones.

Why is it said that division of work creates silos?

Because when each person specializes heavily and only interacts with their own department, they lose sight of the whole. Silos are fought with coordination: shared rituals, common objectives, role rotation.

Conclusion

Organizing a company isn't "make an org chart and done." It's designing the human system that will execute the strategy. The six principles —division of work, hierarchy, unity of command, span of control, delegation, and coordination— are the rules that make that system work.

If you want to keep going deeper:

• The complete guide to management principles (Post #3) to see how these integrate with the rest.
• The 14 principles of Fayol (Post #2) for the historical context.
• If you lead people, you'll also want our guide to HR management principles (Post #5).

And if you're building a company, don't miss how to build a business model step by step (Post #8): organization is one of the decisions you make on day one, even if you don't realize it.