Veda Verse
Menu

Organisation Structure

The framework that defines roles, responsibilities, authority and communication, so resources align with goals and accountability is clear.

Uses ideas from Management and Its Principles. Which ideas

7 conceptsAbout 26 min
5 cited passagesHow they are marked

Documented 3 of them. The passage exists in a named text, and the modern concept is a fair reading of what it says.

My view 2 of them. An interpretive parallel. The text does not discuss the modern concept; the link is a reading offered for reflection, not a claim about what the authors meant.

Start with the first concept
Part one

The concepts

Concept 1 of 7.

Types of structure

How a firm groups its people, and what each way of grouping costs.

Before you read

Can a person report to two managers and the structure still work?

Core idea

A structure sets who does what, who reports to whom and who decides; each type buys one strength at the price of one challenge.

An auto-parts maker in Pune starts with one plant and one product. Ten years later it makes brakes, clutches and wiring harnesses for buyers across India. Who should now report to whom? The answer is its organisation structure.

In plain wordsOrganisation structure is the agreed pattern of who does what, who reports to whom, and who decides.

Exam definitionAn organisational structure defines how job tasks are formally divided, grouped and coordinated (Robbins and Judge).

A structure sets roles, responsibilities, authority and lines of communication. It lines up people and resources with goals, and it makes clear who answers for what. The main choice is how to group people: by the work they do, by what they make or serve, or both at once.

The colours stand for functions. In the divisional chart the same three colours appear under every division: that repetition is the duplication the table below lists as its cost.

The Pune firm, as an illustration. In a functional structure it has one head of production, one of sales and one of finance, each serving all three products. In a divisional structure it has a brakes division, a clutches division and a harness division, each with its own production and sales. In a matrix, an engineer working on a new part answers to the head of engineering for technical work and to the project manager for deadlines.

StructureGrouped byStrengthChallenge
FunctionalSpecialised functionsEfficiency, specialisationFunctional silos
DivisionalProduct, geography or customerFlexibility, focusDuplication
MatrixDual reporting: function and project managerCollaborationDual authority
HierarchicalTop-down authorityClear authority, accountabilitySlow adaptation
VirtualDispersed teams linked by technologyFlexibility, cost efficiencyTechnology dependence
LeanFlat, waste eliminatedEfficiency, autonomyManagerial overload
HybridA combination of the aboveAdaptabilityComplexity

Informal and flexible forms loosen the fixed chart:

  • Network: fluid relationships, often with outside partners; agile.
  • Flat: few management levels, so communication is fast.
  • Holacracy: self-managed teams and circles that make decisions collectively.
  • Team-based: cross-functional teams organised around goals.
  • Boundaryless: fewer barriers inside the firm and with outside partners.

Don't confuse the functional structure with Taylor's functional organisation. In a functional structure, departments are grouped by function and each worker still has one boss. In Taylor's functional organisation (next block), several specialist foremen give orders to the same worker.

Where it breaks. Each structure solves one problem and creates another, as the last column of the table shows. Silos, duplication and dual authority are the prices of specialisation, focus and collaboration. Self-managed forms such as holacracy need clear rules on who decides what, and they get harder to run as a firm grows.

For exams. Match each structure to its basis, its strength and its challenge. The matrix is the one with dual reporting, so it breaks unity of command. The divisional structure is the one that duplicates functions.

Go deeper for practitioners

Structure follows strategy. Alfred Chandler's study Strategy and Structure (1962) traced how large American firms that spread into new products and regions later moved from functional to divisional structures. The lesson: change the strategy first, then expect the structure to strain.

A decision. The Pune firm still runs functionally. Its sales head argues every week with production about which product gets machine time, and nobody answers for the profit of clutches alone. Those are the usual signs that a functional structure has been outgrown. A divisional move gives each product a head who answers for its profit, at the cost of separate sales and production teams. A common middle path is a hybrid: finance, HR and purchasing stay shared at head office, while production and sales move into divisions.

Links. Centralisation and decentralisation (this chapter): divisional structures usually go with more decisions taken in the divisions. Strategy implementation (Unit 6) returns to the fit between strategy and structure.

Check yourself

1. Which structure gives an employee two bosses, a function head and a project head?

Not quite. The answer is “Matrix”. Dual reporting is the mark of the matrix, and it is why the matrix breaks unity of command. In a divisional structure each person still has one boss, inside the division.

2. A Pune auto-parts firm sets up separate brakes, clutches and harness units, each with its own production and sales team. This is a…

Not quite. The answer is “Divisional structure, which risks duplicating functions”. Grouping by product, with each unit repeating the same functions, is divisional, and its cost is duplication. A functional structure would have one production head for all three products.

3. A firm's functional heads argue every week over which of its three products gets machine time, and nobody answers for each product's profit. What do these signs suggest?

Not quite. The answer is “It has outgrown its functional structure; a divisional or hybrid one may fit better”. Fights over shared resources and no one owning a product's profit are the usual signs a functional structure has been outgrown. Adding functional heads only adds more silos to argue between.

Ancient lens
  1. Documented

    Functional structure and departmental superintendents

    Book 2 of the Arthaśāstra assigns each domain (treasury, mines, trade, agriculture, accounts) to its own head, with defined duties and audit. This is a functional structure.

    Arthaśāstra, Book 2

    About this text: ArthaśāstraDiscuss

    What it adds

    Each domain (treasury, mines, trade, agriculture, accounts) under its own head, with defined duties and audit.

    Where they differ

    The Arthaśāstra describes the departments of a state. The chapter's functional structure is a way to group a firm's specialised functions.

  2. My view

    Holacracy and team-based forms and the sabhā and samiti

    The Atharvaveda speaks of the sabhā and samiti as two deliberative assemblies, daughters of Prajāpati. They are group bodies where decisions were made by discussion, which a modern reader may compare to self-managed circles. The comparison is loose: these were assemblies of a polity.

    A reading offered for reflection, not a claim about what the authors meant.

    सभा च मा समितिश्चावताम् । sabhā ca mā samitiś cāvatām. Atharvaveda 7.12.1

    About this text: AtharvavedaDiscuss

    What it adds

    Group assemblies in which decisions were made by discussion.

    Where they differ

    The text describes assemblies of a polity, so the comparison with self-managed circles is loose, and the chapter offers it only as a reading.

Side by sideModern ideaClassical idea
Documented

Modern: Functional structure

Classical: departmental superintendents

My view

Modern: Holacracy and team-based forms

Classical: the sabhā and samiti

Reflect & discuss

“Which structure does your workplace use, and which of its challenges do you see?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Types of structure
  • Structure: how job tasks are formally divided, grouped and coordinated (Robbins and Judge).
  • Functional: efficiency, but silos. Divisional: flexibility, but duplication. Matrix: collaboration, but dual authority.
  • Hierarchical: clear authority, but slow adaptation. Virtual: flexibility, but technology dependence. Lean: autonomy, but overload. Hybrid: adaptability, but complexity.
  • Flexible forms: network, flat, holacracy, team-based and boundaryless.
  • Structure follows strategy (Chandler, 1962): diversified firms tend to move to divisional structures.
Remember

Every structure trades a strength for a challenge.

Concept 2 of 7.

Line, line-and-staff and other forms

The classical forms, and two ways of describing a structure.

Before you read

A manager gets expert advice from a legal adviser who cannot give orders to the manager's team. Which form is that?

Core idea

Line is one chain of command; line-and-staff adds advisers who do not command; Taylor's functional form lets several specialists command the same worker.

A transport company grows from five lorries to fifty. The owner hires a lawyer and a cost accountant. Should they give orders to the drivers, or only advise the owner? Each answer gives a different form of organisation.

In plain wordsIn a line organisation, orders pass down one chain, and each person takes orders from one boss.

Exam definitionA standard textbook definition: line organisation is the simplest form of organisation, in which authority flows vertically from the top to the lowest level through a single chain of command.

In the transport company, as an illustration, the line runs owner, depot managers, supervisors, drivers. The lawyer who checks contracts and the accountant who works out the cost per kilometre are staff: they advise the line. If the accountant could order drivers to change routes, the firm would be moving toward Taylor's functional form.

Line and staffGeneral managerWorks managerForemanWorkersAdviseradvises onlyOrders flow down one lineTaylor's shop-floor bossesGang bossSpeed bossRepair bossInspectorWorkerFour bosses, one worker
Line-and-staff keeps one chain of command and adds advisers beside it. Taylor's functional foremanship gives the worker several bosses, each for one part of the job.
FormHow it worksStrengthWeakness
Line (scalar, military)Authority runs straight down a single chain from top to bottomSimple, clear, quick decisions, strict disciplineNo specialists; key managers overloaded
Line-and-staffLine managers command; staff specialists advise and serve them (general staff assist an executive, specialist staff give expert advice, service or control)Expert advice while unity of command is kept; used by most large firmsConflict between line and staff; staff advise without answering for results
Functional (F. W. Taylor)Grew from Taylor's functional foremanship: specialist foremen each direct the same worker on their own functionExpertise at every pointBreaks unity of command; confusing for workers
CommitteeA group of managers decides jointly on matters referred to itPooled judgement; decisions accepted more readilySlow and costly; responsibility diluted
ProjectA temporary team drawn from several departments for one time-bound goal, disbanded at the endFocus and speed on complex one-off workUncertain careers; conflict over shared people

Taylor's eight foremen. Taylor proposed eight functional foremen in place of one. Four worked in the planning room: the route clerk, the instruction card clerk, the time and cost clerk, and the shop disciplinarian. Four worked on the shop floor: the gang boss, the speed boss, the repair boss and the inspector.

Mechanistic and organic structures (Tom Burns and G. M. Stalker, 1961) describe how rigid a structure is.

FeatureMechanisticOrganic
RulesRigid rulesFew rules
DecisionsCentralisedDecentralised
Spans of controlNarrowWide
CommunicationVerticalLateral
SuitsStable conditionsA changing environment

Formal and informal organisation. The formal organisation is deliberately designed: official positions, rules and the chart. The informal organisation grows on its own from friendships and social groups. It communicates through the grapevine, the unofficial channel by which news spreads. It can support or undermine the formal one, so wise managers work with it.

Don't confuse line-and-staff with the functional form. Staff specialists advise the line manager, who still gives the orders. In Taylor's functional form, the specialists give the orders themselves.

Where it breaks. Line-and-staff often brings friction: line managers may resent advice, and staff may feel ignored. Taylor's scheme confused workers who had several bosses, and few firms used it in full; its idea survives as functional authority (next block). Burns and Stalker's two types are ends of a range, and one firm can be mechanistic in accounts and organic in research.

For exams. Line, scalar and military organisation are the same thing. Taylor's form comes from functional foremanship and breaks unity of command. Mechanistic and organic structures are Burns and Stalker's (1961).

Line commands, staff advise, Taylor's foremen each command one part.

Check yourself

1. Which form breaks unity of command?

Not quite. The answer is “Taylor's functional organisation”. Under Taylor's scheme several specialist foremen each give orders to the same worker. Line-and-staff keeps unity of command, because the staff only advise.

2. A transport company's cost accountant works out the cost per kilometre and advises the owner, but cannot give orders to drivers. The accountant holds…

Not quite. The answer is “A staff position”. Advising the line without commanding it is staff. If the accountant could order drivers to change routes, the firm would be moving toward Taylor's functional form.

3. A software firm faces customer needs that change every few months. Which structure do Burns and Stalker's findings point to?

Not quite. The answer is “Organic: few rules, decentralised decisions, lateral communication”. Organic structures suit a changing environment; mechanistic ones suit stable conditions. A rigid, centralised structure would be slowest to respond to the changes.

Reflect & discuss

“In an organisation you know, where does the informal organisation help the formal one, and where does it work against it?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Line, line-and-staff and other forms
  • Line (scalar, military): one chain of command; simple and quick, but short of specialists.
  • Line-and-staff: staff advise, line commands; risk of line-staff conflict.
  • Functional (Taylor): eight specialist foremen; breaks unity of command. Committee and project forms.
  • Mechanistic suits stable conditions, organic suits change (Burns and Stalker, 1961).
  • The informal organisation grows from friendships and speaks through the grapevine.
Remember

Line commands, staff advise, Taylor's foremen each command one part.

Concept 3 of 7.

Authority, responsibility and accountability

Who may decide, who must do it, and who answers for it.

Before you read

Can a manager hand over responsibility for a task entirely, along with the authority?

Core idea

Authority is the right to decide, responsibility the duty to perform, accountability answering for results. Authority flows down, the other two flow up, and authority should match responsibility.

A bank branch manager is told to cut bad loans, but she cannot refuse loans her regional office pushes through. She is responsible for a result she has no authority to control, and that seldom ends well.

In plain wordsAuthority is the right to decide. Responsibility is the duty to do the job. Accountability is having to answer for the result.

Exam definitionAuthority is the power to make decisions which guide the actions of another (Herbert Simon).

Authority is the right to give orders, make decisions and use resources. Responsibility is the obligation to perform the duties assigned. Accountability is answering to a superior for the results. Authority flows downward; responsibility and accountability flow upward.

A Diwali sale, as an illustration. An electronics store manager lets the floor supervisor approve discounts of up to ₹2,000 on a bill. That limit is her authority. Running the sales floor through the sale is her responsibility. She answers to the store manager for sales and for the discounts she gave: her accountability. The store manager still answers to the regional manager for the whole store.

Regional managerStore managerFloor supervisorAuthorityflows downResponsibility andaccountabilityflow up
The right to decide is passed down the chain. The duty to perform, and the answer for results, come back up it.
TheorySource of authority
Formal (classical)Position and ownership: it flows down from the top through the hierarchy
Acceptance (Chester Barnard, 1938)The subordinates who accept it: an order has authority only if it is accepted. Orders within a person's zone of indifference are accepted without question
CompetencePersonal knowledge and skill that others defer to, whatever the position

Kinds of authority: line authority to command; staff authority to advise; and functional authority, a specialist's right to direct a particular activity in other departments. A finance head who sets how every department must file expense claims is using functional authority.

Parity of authority and responsibility. Authority should match responsibility (Fayol's second principle; Urwick's principle of correspondence). Authority without responsibility invites misuse. Responsibility without authority leaves a person unable to act. Authority is used within the limits set by the organisation's policies, not by personal preference.

Absoluteness of responsibility. A manager can delegate authority, and the subordinate becomes responsible for the task. But the manager's own ultimate responsibility and accountability to the superior cannot be passed on.

Don't confuse authority with power. Authority comes with a position and is accepted as legitimate. Power is the wider ability to influence others. An experienced clerk whom everyone consults has power without the authority of a post.

Where it breaks. Acceptance theory shows the limit of formal authority: orders outside the zone of indifference may be quietly ignored. Parity is an ideal rather than a fact. A sales manager is held responsible for targets that also depend on prices and markets she does not control.

For exams. Know the three sources of authority, with Barnard (1938) and the zone of indifference. Remember the directions: authority down, responsibility and accountability up. Parity is Fayol's second principle and Urwick's principle of correspondence; ultimate responsibility cannot be delegated.

Check yourself

1. Barnard's acceptance theory says authority comes from…

Not quite. The answer is “The subordinates who accept it”. Barnard (1938) held that an order has authority only if it is accepted; orders inside the zone of indifference are accepted without question. Position as the source is the formal, classical theory.

2. During a Diwali sale a store manager lets the floor supervisor approve discounts up to ₹2,000 a bill. The discounts are later found to be misused. Who answers to the regional manager?

Not quite. The answer is “The store manager, who keeps ultimate responsibility”. The supervisor answers to the store manager, but delegating does not remove the store manager's own accountability upward. Ultimate responsibility cannot be passed on.

3. A branch manager must cut bad loans but cannot refuse loans pushed by her regional office. What is the problem, in this chapter's terms?

Not quite. The answer is “Responsibility without matching authority, so she cannot act”. Parity requires authority to match responsibility. Authority without responsibility is the reverse case, and it leads to misuse rather than to a manager who cannot act.

Reflect & discuss

“Have you ever been responsible for something without the authority to do it? What happened?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Authority, responsibility and accountability
  • Authority: the right to decide. Responsibility: the duty to perform. Accountability: answering for results.
  • Sources: formal (position), acceptance (Barnard, 1938; zone of indifference), competence.
  • Line authority commands, staff authority advises, functional authority directs one activity in other departments.
  • Parity: authority should match responsibility (Fayol; Urwick's correspondence). Ultimate responsibility cannot be delegated.
  • Authority comes with a post; power is the wider ability to influence.
Remember

Authority down, accountability up, and the two should match.

Concept 4 of 7.

Span of control and charts

How many people one manager supervises, and how to draw the result.

Before you read

Does a wider span of control mean closer supervision?

Core idea

Span of control is the number of people reporting to one manager; it sets the hierarchy's shape, wide and flat or narrow and tall.

Two firms each employ 64 sales staff. One gives each manager 4 people to supervise; the other gives each manager 8. The first needs more than twice as many managers.

In plain wordsSpan of control is the number of people who report directly to one manager.

Exam definitionA standard textbook definition: span of control, or span of management, is the number of subordinates a manager can effectively supervise.

Working it out, as an illustration.

  • Span of 4: 64 ÷ 4 = 16 first-line managers; 16 ÷ 4 = 4 middle managers; 4 ÷ 4 = 1 head. That is 21 managers in three levels above the sales staff.
  • Span of 8: 64 ÷ 8 = 8 first-line managers; 8 ÷ 8 = 1 head. That is 9 managers in two levels.
  • If each manager costs ₹12 lakh a year, the narrow span needs 12 more managers: 12 × ₹12 lakh = ₹1.44 crore a year.
Narrow span of 2: tallWide span of 8: flat7 managers, 3 levels1 manager, 1 level
The same eight workers under a narrow span and a wide one. The narrow span gives a tall hierarchy with many managers; the wide span gives a flat one.
FeatureWide spanNarrow span
ShapeMany subordinates per manager, fewer levelsFew subordinates per manager, more levels
GainsFaster decisions, lower managerial cost, greater autonomyClose supervision, better coordination
CostsManager overload, limited supervisionSlower decisions, higher cost, bureaucracy

An organisational chart shows who reports to whom. Four common charts are hierarchical (top to bottom), flat (few levels, broad span), matrix (dual reporting) and divisional (separate business units). A team-based chart maps cross-functional teams.

The organising process turns a purpose into work and learns from the result:

Purpose and goals → Inputs → Activities and tasks → Outputs → Monitoring and feedback, back to the start

Inputs are materials, information and resources. Outputs are products, reports and services. Monitoring and the feedback loop drive improvement.

Don't confuse span with levels. The span is how wide each manager's group is. The number of levels is how tall the hierarchy is. For the same number of people, wider spans mean fewer levels.

Where it breaks. No span is right everywhere. A wide span works for skilled people doing routine, similar work; it fails when work is complex and changing. Cutting levels saves cost, but it can leave managers with no time to coach.

For exams. Wide span means a flat structure; narrow span means a tall one. Expect a question pairing each with its gains and costs, and one on the four chart types.

Wide and flat, or narrow and tall.

Check yourself

1. Span of control is…

Not quite. The answer is “The number of people who report directly to one manager”. The span is width; the number of levels is height. For the same number of people, wider spans mean fewer levels.

2. A firm widens its spans of control from 4 to 8 without changing its staff. What should it expect?

Not quite. The answer is “Fewer levels and faster decisions, but less close supervision”. Wider spans flatten the hierarchy and cut managers, so decisions speed up. Closer supervision and more levels come with narrow spans, not wide ones.

3. A firm has 64 sales staff and a span of 4 at every level. How many managers does it need?

Not quite. The answer is “21”. 64 ÷ 4 = 16, then 16 ÷ 4 = 4, then 4 ÷ 4 = 1: 16 + 4 + 1 = 21. 16 counts only the first-line managers, and 9 is the answer for a span of 8.

Ancient lens
  1. Documented

    Span of control and tiers of ten

    Manu prescribes a layered administration: an officer over one village, one over ten, one over twenty, one over a hundred and one over a thousand. Each tier reports to the one above it, a description of scalar chain and span.

    Manusmṛti 7.115–117

    About this text: ManusmṛtiDiscuss

    What it adds

    A layered administration: officers over one village, ten, twenty, a hundred and a thousand, each reporting upward.

    Where they differ

    Manu prescribes tiers of local administration for a polity. The chapter's span of control is about how many people one manager supervises.

  2. My view

    The organising process and a cycle of exchange

    The Gītā's wheel of sacrifice has inputs, transformation, outputs and a return, and says whoever refuses to turn it lives in vain. As a picture of purpose, input, activity, output and feedback, it parallels the organising process. The verse is about exchange between beings and nature, not about organising work, so the parallel is a reading.

    A reading offered for reflection, not a claim about what the authors meant.

    “Whoever here does not keep turning the wheel thus set in motion…” एवं प्रवर्तितं चक्रं नानुवर्तयतीह यः । evaṃ pravartitaṃ cakraṃ nānuvartayatīha yaḥ. Bhagavad Gītā 3.14–16

    About this text: Bhagavad GītāDiscuss

    What it adds

    A cycle with inputs, transformation, outputs and a return, which whoever refuses to turn lives in vain.

    Where they differ

    The Gītā's wheel of sacrifice is a picture of exchange between beings and nature. The chapter's process is a way to organise work.

Side by sideModern ideaClassical idea
Documented

Modern: Span of control

Classical: tiers of ten

My view

Modern: The organising process

Classical: a cycle of exchange

Reflect & discuss

“How many people report to your manager, and what does that do to how decisions are made?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Span of control and charts
  • Span of control: the number of subordinates one manager supervises.
  • Wide span: flat, faster decisions, lower cost, more autonomy; but overload and limited supervision.
  • Narrow span: tall, close supervision, better coordination; but slower decisions, higher cost, bureaucracy.
  • Charts show who reports to whom: hierarchical, flat, matrix, divisional, team-based.
  • Organising process: purpose and goals, inputs, activities and tasks, outputs, monitoring and feedback.
Remember

Wide and flat, or narrow and tall.

Concept 5 of 7.

How wide a span: Graicunas and Urwick

Why relationships multiply faster than subordinates.

Before you read

A manager with 6 subordinates takes on a 7th. Roughly how much do the possible relationships grow?

Core idea

Graicunas counted direct single, direct group and cross relationships, which grow exponentially as subordinates are added; Urwick drew a limit of five or six where work interlocks.

A team leader manages four people comfortably. Her team grows to eight, and her days fill with meetings, disputes and messages. The team doubled, but the relationships she has to handle grew far more than twice.

In plain wordsA manager deals with each person, with groups of them, and with the way they deal with each other. Graicunas counted all of these.

Exam definitionV. A. Graicunas, in "Relationship in Organization" (1933): a manager with n subordinates has R = n[2n−1 + n − 1] possible relationships.

R = n [2n−1 + n − 1]

The formula adds three kinds of relationship:

  • Direct single: the manager with each subordinate alone. There are n of them.
  • Direct group: the manager with a subordinate while others are present. Each combination counts once for every person who could lead it: n(2n−1 − 1).
  • Cross: subordinates dealing with each other, each direction counted: n(n − 1).

Worked example, n = 5. 24 = 16. Then 16 + 5 − 1 = 20. Then 5 × 20 = 100. Check by kinds: 5 direct single + 75 direct group + 20 cross = 100.

Subordinates (n)Direct singleDirect groupCrossPossible relationships (R)
11001
22226
339618
44281244
557520100
6618630222
7744142490
881,016561,080
11621834441005222649071,0808Subordinates (n)
Subordinates grow one at a time, while relationships grow exponentially. Going from six subordinates to seven more than doubles them, from 222 to 490.

Urwick's rule. Lyndall Urwick drew the practical conclusion: no superior can directly supervise the work of more than five, or at most six, subordinates whose work interlocks.

What sets the right span:

  • the subordinates' competence and training;
  • how simple, similar and standardised the work is;
  • how clear the plans and the delegation are;
  • how fast conditions change;
  • communication technology, and how spread out the people are;
  • the manager's other duties, and the degree of decentralisation.

Spans are usually narrower at the top and wider at the operating level. Removing levels to widen spans is called delayering.

Don't read R as a workload. R counts possible relationships, not the ones that actually take time. Many combinations rarely occur. And Urwick's limit of five or six applies only where the subordinates' work interlocks.

Where it breaks. The formula weighs every possible relationship equally, so it overstates the burden. Where people do independent, routine work, such as tellers or field sales staff, one supervisor can handle many more than six. Clear plans and good communication tools widen the workable span further.

For exams. Expect to calculate R for a given n; work it inside the brackets first. Remember 4 → 44, 5 → 100, 6 → 222 and 7 → 490, and Urwick's five or six for interlocking work.

Add one person, and the relationships more than double.

Check yourself

1. Urwick held that no superior can directly supervise more than about…

Not quite. The answer is “Five or six subordinates whose work interlocks”. Urwick's rule is five or, at most, six, and only where the subordinates' work interlocks. Where work is independent, wider spans are workable.

2. Which team could one supervisor run with a span well above Urwick's five or six?

Not quite. The answer is “Bank tellers doing independent, routine work with clear procedures”. Simple, standardised, independent work with clear plans allows a wide span. Interlocking work, fast change and scattered staff all call for a narrower one.

3. Using R = n[2^(n−1) + n − 1], how many relationships does a manager with 4 subordinates have?

Not quite. The answer is “44”. 4 × (2³ + 4 − 1) = 4 × 11 = 44: 4 direct single, 28 direct group and 12 cross. 100 is the answer for five subordinates.

Reflect & discuss

“How many people could you supervise well at once, and what would let you handle more?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
How wide a span: Graicunas and Urwick
  • Graicunas (1933): R = n[2^(n−1) + n − 1].
  • Three kinds: direct single (n), direct group n(2^(n−1) − 1), cross n(n − 1).
  • 4 → 44, 5 → 100, 6 → 222, 7 → 490, 8 → 1,080 relationships.
  • Urwick: five, or at most six, where work interlocks.
  • Span depends on competence, the work, plans, change, technology, dispersion and decentralisation; delayering widens spans.
Remember

Add one person, and the relationships more than double.

Concept 6 of 7.

Delegation and decentralisation

Passing on a task, and spreading decisions across the organisation.

Before you read

If a manager delegates a task, who answers for the result?

Core idea

Delegation hands one person a task and the authority for it, while the manager still answers for the result; decentralisation spreads decisions across the whole organisation.

A bank branch manager cannot read every loan file herself. She can hand some decisions to one officer, or the bank can decide which decisions every branch makes on its own. The first is delegation; the second is decentralisation.

In plain wordsDelegation is handing a task, and the power to do it, to someone below you, while you still answer for the result.

Exam definitionA standard textbook definition: delegation is the process by which a manager assigns tasks to subordinates, gives them the authority to carry those tasks out, and holds them accountable for results.

Delegation passes responsibility and authority for a task from superior to subordinate. Responsibility is the duty to do the work; authority is the power to decide; accountability is answering for results. The superior keeps ultimate accountability.

Responsibility → Authority → Action → Accountability

At the branch, as an illustration. The manager asks a loan officer to process gold loans and lets him approve any loan up to ₹2 lakh. The officer now has the responsibility and the authority. He acts on each file, and he is accountable to her for bad loans. She stays accountable to the regional office for every loan the branch makes.

A sound delegation provides training, guidance, trust and feedback. It sets clear limits, such as the ₹2 lakh ceiling, and agrees when the manager will check progress.

Decentralisation spreads decision-making power systematically across the organisation. It can be functional, geographic, product- or service-based, or market-based.

FeatureDelegationDecentralisation
MeaningSpecific authority transferredAuthority systematically distributed
ScopeNarrowBroad
LevelA task, an individualThe organisation, a unit
FocusResponsibility and supervisionAutonomy and distribution

Don't confuse delegation with abdication. Delegating means handing over a task with limits, support and checks. Handing it over and never following up is abdication, and the manager still answers for whatever goes wrong.

Where it breaks. Many managers delegate too little. They fear losing control, distrust their staff, or believe they can do it faster themselves. Subordinates may also avoid taking it on, for fear of criticism or because they lack information. Then the manager stays overloaded and nobody below learns to decide.

In practice. Delegate the decision together with the information needed to make it. Set a limit in rupees or in scope, and agree check-in points in advance.

For exams. Know the three elements, responsibility, authority and accountability, and that ultimate accountability cannot be delegated. Delegation is narrow and personal; decentralisation is broad and organisation-wide.

Memory hook: delegation is about the person; decentralisation is about the system.

Check yourself

1. When a manager delegates a task, what stays with the manager?

Not quite. The answer is “Ultimate accountability for the result”. Responsibility and authority for the task pass to the subordinate. The manager's own accountability upward cannot be passed on.

2. A branch manager lets a loan officer approve gold loans up to ₹2 lakh. A ₹1.5 lakh loan goes bad. Who answers to the regional office for it?

Not quite. The answer is “The branch manager, though the officer answers to her”. The officer is accountable to the branch manager for his decision, but she stays accountable to the regional office for every loan the branch makes.

3. A manager hands a junior a project with no limits and no information, and never checks on it. In this chapter's terms, that is…

Not quite. The answer is “Abdication, not delegation”. Delegation needs clear limits, support and checks. Handing a task over and walking away is abdication, and the manager still answers for what goes wrong.

Ancient lens
  1. Documented

    Delegation and the one-wheeled cart

    Kauṭilya argues that no ruler can govern alone. Sovereignty needs helpers, so appoint counsellors and listen to them. This is the case for delegation, with the listening that makes it work.

    “Kingship is possible only with assistance; one wheel alone does not move.” सहायसाध्यं राजत्वं चक्रमेकं न वर्तते । sahāyasādhyaṃ rājatvaṃ cakram ekaṃ na vartate. Arthaśāstra 1.7.9

    About this text: ArthaśāstraDiscuss

    What it adds

    The case for helpers: appoint counsellors and listen to them.

    Where they differ

    Kauṭilya argues about a ruler governing a state. The chapter's delegation also stresses training, guidance, trust and feedback.

Reflect & discuss

“What is one task you could delegate, and what would you still answer for?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Delegation and decentralisation
  • Delegation passes responsibility and authority for a task from superior to subordinate.
  • Responsibility → authority → action → accountability; the superior keeps ultimate accountability.
  • Sound delegation: training, guidance, trust, feedback, clear limits and check-ins.
  • Decentralisation spreads decisions across the organisation: functional, geographic, product- or service-based, or market-based.
  • Delegation: narrow, a task, an individual. Decentralisation: broad, the organisation, a unit.
Remember

Delegation is about the person; decentralisation is about the system.

Concept 7 of 7.

Centralisation and decentralisation

Where decisions are kept, and how far down they go.

Before you read

Is any real organisation completely centralised or completely decentralised?

Core idea

Centralisation keeps authority at central points; decentralisation pushes it to the lowest level able to use it. Every firm mixes the two, decision by decision.

A chain of 40 restaurants has to decide who sets menu prices, who hires waiters, and who chooses the Diwali specials. Every decision kept at head office slows the branches; every one pushed out loosens control.

In plain wordsCentralisation keeps decisions at the top. Decentralisation pushes them down to the people closest to the work.

Exam definitionCentralisation is the systematic and consistent reservation of authority at central points in the organisation. Decentralisation is the systematic effort to delegate to the lowest levels all authority except what can only be exercised at central points (Louis A. Allen).

No organisation is wholly one or the other; it is a matter of degree.

The restaurant chain, as an illustration. Head office fixes the brand, the core menu, hygiene standards and supplier contracts. Branch managers set staff rosters, choose festival specials and approve refunds up to ₹2,000. The chain is centralised on what must be the same everywhere and decentralised on what depends on the place.

Ernest Dale's tests of the degree of decentralisation. The more of each, the more decentralised the firm:

  1. how many decisions are made lower down;
  2. how important those decisions are;
  3. how many functions they cover;
  4. how little they need to be checked above.
FeatureCentralisationDecentralisation
MeritsUniform policies and action; tight control; no duplication of specialists across branches; suits small firms and emergenciesLighter load on top management; faster, local decisions; develops future managers; suits large, diversified firms; better morale
DemeritsOverloads the top; slow decisions; stifles initiative and morale lower downCostlier, with duplicated functions; harder coordination and control; conflict between units

Factors that decide the degree:

  • the size and spread of the organisation;
  • the cost and importance of decisions;
  • the need for uniform policy;
  • top management's philosophy;
  • the availability of capable managers lower down;
  • control techniques and information systems;
  • how quickly the environment changes.

Decentralisation is delegation extended systematically through every level.

Don't confuse decentralisation with having many branches. Decentralisation is about where decisions are made, not where offices are. A firm with branches across India is still centralised if every decision goes to head office.

Where it breaks. Decentralisation works only when managers lower down are capable and have good information. Without them, units drift apart and head office loses control. Firms often swing between the two as problems on one side become visible.

For exams. Allen's two definitions, Dale's four tests, and the merits on each side are the usual questions. Remember that it is a matter of degree.

Go deeper for practitioners

A decision. One branch of the restaurant chain fails a food-safety inspection. The board wants every purchase approved at head office. A narrower answer recentralises only what failed: supplier approval and hygiene audits. Rosters and specials stay with the branches, so they keep their speed and their managers keep learning.

A useful test. Keep a decision at the centre when a mistake is costly and hard to undo, or when it must be the same everywhere. Push it down when it depends on local knowledge and a mistake is cheap to correct.

Links. Types of structure (this chapter): divisional structures usually decentralise more than functional ones. Principles of management (this unit): Fayol treated centralisation as a matter of proportion, to be set for each case.

Check yourself

1. Whose definitions call centralisation the systematic reservation of authority at central points?

Not quite. The answer is “Louis A. Allen”. Allen defined both terms. Ernest Dale is the tempting answer, but he gave the tests for measuring the degree of decentralisation, not these definitions.

2. A restaurant chain fixes its menu and hygiene standards at head office, but lets branch managers set rosters and festival specials. The chain is…

Not quite. The answer is “Centralised on some decisions and decentralised on others”. It is a matter of degree, decided decision by decision. Having many branches says where offices are, not where decisions are made.

3. By Dale's tests, which change makes a firm more decentralised?

Not quite. The answer is “Branch decisions need less checking by head office”. Dale's tests look at how many and how important the decisions made lower down are, how many functions they cover, and how little they are checked above. Opening branches alone changes none of these.

Reflect & discuss

“Which decisions in an organisation you know should move closer to the people who carry them out?”

Kept on this device. Nobody sees it unless you share it.

Still unsure, or see it differently? Ask the community about thisYou’ll sign in first if you haven’t. Your note above stays private.

One-page summary
Centralisation and decentralisation
  • Allen: centralisation reserves authority at central points; decentralisation delegates all but that to the lowest levels.
  • A matter of degree; Dale's four tests measure it.
  • Centralisation: uniformity and control. Decentralisation: speed, initiative and management development.
  • Factors: size, cost of decisions, need for uniformity, philosophy, managers available, controls, change.
  • Decentralisation is about where decisions are made, not how many branches there are.
Remember

Keep the few at the centre; push the rest down.

Translations are paraphrases. Arthaśāstra references follow Kangle's critical edition; Bhagavad Gītā references are chapter.verse; Tirukkuṟaḷ references are couplet numbers. Check each reference against your own edition before quoting it in submitted work.

Test yourself

All 21 questions from this chapter, in a new order.

The ones you miss join your review, and come back until they stick.

Start the chapter test

How this chapter connects

Worked out from the glossary terms each chapter uses. A chapter is listed when two or more terms are shared.

Uses ideas from

Texts quoted in this chapter: Arthaśāstra, Manusmṛti, Atharvaveda, Bhagavad Gītā. All the classical texts.

Cite this page
  • APA

    Veda Verse. (2026, October 18). Organisation Structure. https://myvedaverse.in/learn/organisation-structure

  • MLA

    “Organisation Structure.” Veda Verse, 18 Oct. 2026, myvedaverse.in/learn/organisation-structure.

  • Chicago

    Veda Verse. “Organisation Structure.” Last modified October 18, 2026. https://myvedaverse.in/learn/organisation-structure.

Check the form your course asks for. The date is when this page's content last changed.