7.1 Organisational structure

Syllabus
9609–2026–2027
Topic
7.1
Level
A2

Learning objectives

7.1.1Objectives and structure• The relationship between business objectives and organisational structure- the purpose and attributes of an organisational structure such as flexibility, meeting the needs of the business, allowing for growth and development and encouraging intrapreneurship7.1.2Types of structure• Types of structure: functional, hierarchical (flat and narrow), matrix- the advantages and disadvantages of the different types of structure- why some organisations are structured by product and others by function or geographical area- the reasons and ways structures change e.g. due to growth or delayering- the features of a formal structure: levels of hierarchy, chain of command, span of control, responsibility, authority, delegation, accountability, centralised, decentralised7.1.3Delegation and accountability• Delegation and accountability- the relationship between delegation and accountability- the processes of accountability in a business- the impact of delegation on a business7.1.4Control, authority and trust• Control, authority and trust- the relationship between span of control and levels of hierarchy- the difference between authority and responsibility- the conflicts between control and trust that might arise when delegating7.1.5Centralisation vs decentralisation• Centralisation and decentralisation- the impact of centralisation and decentralisation on a business7.1.6Line and staff• Line and staff- examples of and distinctions between line and staff functions and the conflicts between them

Structure turns business objectives into coordinated decisions and action

Organisational structure is the formal framework that groups work and shows roles, reporting relationships, authority, responsibility, accountability and communication. Its purpose is to help people coordinate decisions and resources to achieve business objectives.

Evaluate the causal path: objective/strategy → work and decisions required → grouping, hierarchy and decision rights → communication, coordination and behaviour → cost, speed, quality, innovation, customer response and growth → objective achieved or obstructed.

Objective or need Useful structural attribute Why it may help Risk to test
Rapid customer/market response Fewer layers or authority near customers Shorter communication and locally informed decisions Inconsistent decisions or weak control
Efficiency/quality consistency Specialist roles, clear accountability and standard authority Expertise, scale and repeatable control Silos, slow cross-functional action
Innovation/intrapreneurship Delegation, flexible teams or matrix links Combines expertise and gives ideas ownership Dual authority/conflict and resource competition
Growth/product/geographic expansion Scalable divisions, roles and coordination systems Focuses distinct markets/products and develops managers Duplication, cost and fragmented objectives

A suitable structure should be flexible enough to adapt, meet current business needs, allow growth and employee development, and encourage intrapreneurship where relevant. Fit also depends on size, products, geography, technology, workforce capability, culture, risk and environmental change.

A flat or matrix structure may motivate through delegation and combine specialist knowledge, improving innovation and development speed; that can raise sales or profit. But the benefit occurs only if authority, priorities and accountability are clear—otherwise conflict and delay can reverse the chain.

An organisation chart is only a representation. A structure is not effective because it has a fashionable label; judge whether its actual decision, information and accountability mechanisms support the stated objectives.

Structural forms trade specialisation, focus, control and flexibility

Structure/grouping How it works Advantages Disadvantages
Functional Groups specialists such as marketing, operations, finance and HR Expertise, scale, clear professional leadership and efficiency Functional silos, slower cross-functional response and weak product/customer ownership
Hierarchical: tall/narrow span Many levels; each manager supervises fewer people Close supervision, clearer promotion path and manageable direct reports Long chain, slow/distorted communication, cost and less delegation
Hierarchical: flat/wide span Few levels; managers supervise more people Short communication, lower management cost, delegation and faster response Manager overload, less supervision and unclear support if capability is weak
Product division Self-contained focus around product/product line Product expertise, clearer revenue/cost accountability, coordinated functions and fast market response Duplicated functions/cost and rivalry for resources
Geographic division Self-contained focus around country/region Local knowledge, customer response, faster local decisions and divisional performance visibility Duplication, inconsistent policy/brand and weaker central scale/control
Matrix People report across function and project/product teams Combines expertise, flexible teams, innovation and project focus Dual authority, conflict, meetings, unclear accountability and resource competition
Formal feature Meaning
Levels of hierarchy Number of authority layers from top to bottom
Chain of command Route through which authority/instructions pass
Span of control Number of direct subordinates reporting to a manager
Responsibility Duty to perform a task/achieve an outcome
Authority Legitimate power to decide and direct resources
Delegation Passing authority down to carry out responsibility
Accountability Obligation to explain and answer for results
Centralised/decentralised Important decisions retained at the centre/distributed lower or to divisions

Choose grouping by the dominant coordination need: product when offerings, production or customers differ; geography when local tastes, regulation or distance matter; function when shared specialist capability and economies are more valuable. Hybrids are common.

Structure may change because of growth, new products/countries, technology, competition, merger, cost pressure or strategy. Delayering removes hierarchy levels to reduce cost and shorten communication, but may widen spans, overload managers, remove promotion steps and create insecurity unless roles/systems are redesigned.

For a multi-country firm, geographical units can adapt products and promotion to local needs, increasing customer satisfaction and sales; however duplicated specialists may raise cost. For multiple distinct products, product divisions can coordinate R&D, operations and marketing faster and identify product profitability, but may lose shared-function scale.

Flat does not mean structureless, matrix does not remove hierarchy, and delayering is not simply deleting managers. Compare the mechanism and context, then trace both benefit and cost to business performance.

Delegation passes authority, while accountability remains traceable

Delegation is passing authority down the hierarchy so another employee can decide or act for an assigned responsibility. The delegate is accountable upward for use of that authority; the delegating manager retains ultimate accountability for the function and cannot simply transfer blame.

Effective accountability process: define required outcome/standard and responsibility → choose a capable person → grant enough decision/resource authority and clear limits → agree time, evidence, reporting and escalation → provide training/support → monitor milestones without taking the task back → give feedback, correct and recognise → manager answers for the overall result.

Potential benefit Causal mechanism Potential disadvantage/condition
Faster, better local decisions Decision sits nearer relevant information; senior approval delay falls Poor/inconsistent decisions if skill, limits or information are weak
Motivation and job enrichment Trust, autonomy and achievement can raise engagement/productivity Extra responsibility may overload or demotivate unwilling staff
Employee development/succession Practice builds judgement and prepares promotion Training/support increases cost and mistakes may occur while learning
Senior focus on strategy Operational decisions no longer consume all senior time Micromanagement or vague reporting prevents the time saving

A trained junior analyst may receive authority to research packaging options and recommend within a defined budget. Better evidence may improve the decision and develop the analyst; but senior management must set strategic constraints, review evidence and remain answerable for the final policy.

Impact depends on employee capability/willingness, task risk, clarity of authority, quality/timeliness of information, culture of trust, training and monitoring. High-risk or irreversible decisions usually need tighter limits and escalation, not necessarily zero delegation.

Giving a task without decision authority is allocation, not full delegation. Accountability requires evidence and answerability; it should enable learning and correction, not become blame after vague instructions.

Span and hierarchy shape the balance between authority, control and trust

Term Precise meaning
Span of control Number of people directly reporting to a manager
Authority Legitimate power/right to decide, instruct and commit resources
Responsibility Duty to perform work or achieve an outcome
Control Processes used to set standards, monitor evidence and correct performance
Trust Willingness to allow discretion based on expected competence and integrity

Other things equal, a narrow span needs more managers and tends to create more hierarchy levels; a wide span needs fewer managers and tends to create a flatter structure. Technology, task similarity, staff capability, location and required supervision can alter this relationship.

Design Possible gain Possible cost
Narrow span/more layers Close support/control and manageable direct reports Cost, long chain, slow/distorted communication and less autonomy
Wide span/fewer layers Lower cost, short communication, delegation and ownership Manager overload, weak coaching/monitoring and coordination risk
High prescribed control Consistency, compliance and lower immediate variance Slow response, low initiative, gaming metrics and weak trust
High discretion with outcome controls Local response, motivation and innovation Inconsistent/risky action if capability, information or accountability is weak

Responsibility without enough authority makes the employee answer for an outcome they cannot control. Authority without defined responsibility/accountability permits decisions without ownership. Effective delegation matches authority to responsibility, sets limits and preserves escalation.

Control-trust conflict arises when a manager delegates but then approves every detail, withholds information or punishes reasonable learning: authority is nominal and speed/motivation fall. The opposite—no standards, data or intervention—can expose quality, safety and reputation. Use agreed outcomes, risk-based limits, timely indicators, review points and proportionate exception escalation.

Trust is not absence of evidence, and control is not constant surveillance. Wider span does not automatically mean loss of control if work is standardised, staff are capable and information systems expose exceptions.

Decision rights can be centralised, decentralised or deliberately split

Centralisation retains important decision-making authority at head office/senior level. Decentralisation distributes authority to lower levels, branches or divisions. These describe degrees: a business can centralise some decisions and decentralise others.

Centralisation may provide Decentralisation may provide
Consistent policy, brand, ethics, safety and quality Faster decisions close to customers/operations
Whole-business priorities and coordinated resource allocation Better use of local product/geographic knowledge
Senior expertise and tighter control of high-risk choices Manager motivation, development and succession
Central purchasing and other economies of scale Flexibility, experimentation and adaptation
Centralisation risk Decentralisation risk
Senior bottleneck, slow response, remote/poor local information and lower initiative Inconsistent decisions/brand, duplication/cost, sub-unit goals and variable manager quality
One poor central decision affects the whole business Centre may lose visibility/control and scale benefits

Design a decision-rights map. A growing premium chain might centralise brand/safety standards, major capital, finance limits, supplier contracts and data definitions, while branches decentralise staffing schedules, local promotion and service recovery within limits. Specify who recommends, decides, supplies evidence, implements and reviews.

Central purchasing may increase buying scale, lowering unit cost and supporting competitive prices/profit. Central brand decisions may protect consistency during franchising. Yet if head office becomes a bottleneck or misunderstands local demand, delayed/poor choices can reduce sales. Judge by decision urgency, local-information value, risk/irreversibility, scale, capability, technology and need for consistency.

Centralisation is not guaranteed to be rapid—too many decisions can queue at the centre. Decentralisation is not absence of central strategy: objectives, limits, information and accountability can remain common.

Line and staff functions need distinct authority and shared outcomes

Role Main contribution Examples Typical authority
Line function Directly carries out the organisation's core operating/revenue/customer purpose and is accountable for operating results Production/operations, sales, store/branch management; exact examples depend on the business Command authority through the line over people/resources in its operation
Staff function Supplies specialist advice, systems and support that enable line performance HR, finance, legal, IT, data, health and safety Usually advisory/support authority; may hold formal functional authority for law, policy, standards or specialist controls

Line managers contribute customer and operational knowledge, speed and ownership of delivery. Staff specialists improve legal/technical quality, consistency, evidence and economies from shared expertise. Neither contribution is automatically superior.

Conflict source Why it occurs Resolution
Advice versus operating priority Specialist ideal may seem costly/slow; line pressure may underweight risk Shared objective and evidence; quantify cost, benefit and risk
Ambiguous authority Staff recommendation is mistaken for command—or ignored despite mandatory authority Written decision rights, escalation and policy boundaries
Accountability gap Staff designs policy while line implements; each blames the other Named owners, consulted roles, measures and joint review
Central standard versus local reality One policy may not fit operating conditions Common non-negotiables plus justified local adaptation/feedback
Status/language conflict Specialists and operators use different assumptions and incentives Cross-functional teams, mutual consultation and plain decision criteria

Finance staff may advise that a machine investment has unacceptable cash risk, while operations knows the capacity/quality consequences of delay. Define who owns capital approval, require shared demand/cash/capacity evidence, document assumptions and escalate disagreement. Advice informs the accountable decision; mandatory finance limits still bind it.

The best arrangement depends on regulation/risk, specialist scarcity, scale, speed, local variation and management capability. More staff expertise may improve decisions but add overhead/bureaucracy; too little may expose the line to avoidable legal, financial or technical failure.

Staff does not mean junior, optional or unimportant, and line does not mean free from specialist standards. Distinguish contribution, formal authority and accountability in the actual organisation.