Overview
Introduction: Organising is the process of identifying and grouping the activities required to achieve organisational objectives and establishing relationships among jobs, authority, responsibility and people. It converts plans into action by creating a structure that defines roles, allocates resources and coordinates efforts. Importance: Organising provides clarity of roles and responsibilities, promotes specialization and efficiency, facilitates coordination and delegation, creates a framework for growth and change, and helps avoid duplication of work. It establishes authority-responsibility relationships that enable effective decision-making and control. Key themes: definition and characteristics of organising; elements and process of organising (identification and division of work, departmentalisation, assignment of duties, establishing authority-responsibility relationships, and coordination); principles of organising (e.g., span of management, unity of command, delegation, scalar chain, functional definition); types and forms of organisational structure (functional, divisional/product, matrix, line and staff, committee); delegation and decentralisation (meaning, elements,…
Learning Objectives
- Define organising and explain its features, objectives and importance
- List and explain the principles of organising (e.g., unity of command, scalar chain, span of management) with examples
- Describe different organisational structures (functional, divisional, matrix, project) and their suitability for business situations
- Differentiate between formal and informal organisation and give examples of their impact on business
- Illustrate and draw a simple organisational chart showing line, staff and functional relationships and interpret it
- Explain the process of delegation of authority, its elements (authority, responsibility, accountability) and common barriers
- Apply the concept of delegation to allocate authority and responsibility in a given case study
- Analyse factors determining span of management and recommend an appropriate span for different managerial levels
Topics in this chapter
16 topics · tap a topic title to jump straight to it.
Meaning and Concept of Organising
Meaning and Concept of Organising
Key Point: Span of control (average) = Total number of subordinates / Number of managers (in the layer considered). Example: if 120 employees are supervised by 6 middle managers, average span = 120 / 6 = 20.
Definition: Organising is a managerial function by which work is divided into tasks, grouped into departments, authority and responsibility are assigned, and relationships are established to enable people to cooperate effectively to achieve organisational objectives.
Two senses: (a) Organising (process) – the ongoing managerial activity of establishing structures, dividing work and assigning responsibilities. (b) Organisation (structure) – the formal arrangement or pattern of relationships among people and resources.
Key features: It is a continuous and dynamic managerial function; involves division of work, departmentalisation, delegation of authority, assignment of responsibility, and establishment of lines of reporting and coordination.
Elements / components: identification and division of work, departmentalisation (grouping similar activities), assignment of duties, delegation (granting authority), establishing reporting relationships (chain of command) and ensuring coordination between units.
Process/steps of organising: 1) Identify objectives and activities to be performed. 2) Group related activities into departments. 3) Assign duties and allocate resources. 4) Delegate authority and assign responsibility. 5) Establish reporting relationships and communication channels. 6) Fix controls and provide facilities. 7) Review and adapt structure as environment changes.
Principles to follow: unity of command, unity of direction, scalar chain (clear line of authority), span of control (appropriate number of subordinates per manager), parity of authority and responsibility, delegation, balance and flexibility.
Importance: clarifies roles and responsibilities, promotes specialisation and efficiency, avoids duplication of efforts, helps in growth and expansion, facilitates coordination and control, improves communication and decision-making.
Distinction (brief): Organising (process) creates the organisation (structure). The process is managerial and continuous; the structure is the outcome — a formal framework of relationships.
- School: Principal sets objectives, staff are grouped into departments (Math, Science, Languages), teachers assigned classes, authority delegated to heads of departments; clear reporting to principal ensures coordination.
- Hospital: Clinical departments (Medicine, Surgery, Pediatrics), non‑clinical units (Administration, Pharmacy, Lab); nurses and doctors have defined duties, ward in‑charge reports to department head, enabling timely patient care.
- IT company: Projects are divided into teams (frontend, backend, QA, DevOps); team leads have authority to assign tasks, product managers coordinate across teams; cross‑functional squads for agile delivery illustrate departmentalisation + coordination.
- Manufacturing plant: Work divided into procurement, production, quality control, maintenance, sales; foreman supervises shop floor workers (span of control), production schedule links departments to meet output targets.
- Family vacation planning (small example): Tasks split (budgeting, booking, packing), one person delegated responsibility for each task with clear accountability — a simple organising process.
- \[Span of control (average) = Total number of subordinates / Number of managers (in the layer considered)\]\[Example: if 120 employees are supervised by 6 middle managers\]\[average span = 120 / 6 = 20.\]
- \[Workload per employee = Total work units (or hours) / Number of employees\]\[Use to decide staffing for a function.\]
- \[Labour productivity (simple) = Output produced / Number of employees\]\[Helpful to evaluate effects of organising on efficiency.\]
- \[Authority–Responsibility balance (conceptual) : Authority ≥ Responsibility. (Responsibility should be matched by sufficient authority\]\[imbalance indicates poor organising.)\]
- \[Chain length (approx.) = Number of hierarchical levels\]\[Fewer levels often imply wider span of control and faster communication\]\[more levels imply narrow spans and taller structure.\]
Importance and Need of Organising
Importance and Need of Organising
Key Point: Span of Control = Number of direct subordinates reporting to a manager
Definition: Organising is the process of identifying and grouping the activities to be performed, assigning duties, delegating authority, and establishing relationships for the purpose of enabling people to work most effectively together in accomplishing objectives.
Core elements of organising:
- Division of work (specialisation)
- Departmentalisation (grouping similar activities)
- Assignment of duties and authority
- Establishing relationships and coordination
- Provision for adjustment and growth
Importance of organising:
- Clarity in working relations: Organising defines who reports to whom, reducing confusion and overlap. Example: a clear org chart at a school shows principal → head of departments → teachers.
- Efficient use of resources: Resources (human, physical, financial) are allocated according to needs, minimising waste. Example: inventory-control department prevents overstocking in retail chains.
- Specialisation and division of work: Breaking tasks into smaller jobs increases skill and speed. Example: assembly-line workers each perform a specific task, speeding up production.
- Defines authority and responsibility: Employees know their duties and who can give instructions, which improves accountability and decision-making.
- Improves co-ordination: Departments and individuals work together toward common objectives through clear channels and procedures. Example: marketing and production coordinate launch schedules to meet demand.
- Facilitates managerial control: With organised structures, managers can monitor performance and take corrective action easily.
- Encourages growth and diversification: A good organisational structure can be expanded or adjusted when the business grows or diversifies into new lines.
- Promotes initiative and leadership development: By delegating authority, employees get opportunities to take decisions and develop managerial skills.
- Adaptation to change: Proper organising with flexible departments and clear communication helps the firm respond to market or technological changes quickly.
Need for organising (why it is required):
- To achieve common objectives in an orderly manner.
- To ensure effective utilisation of resources and reduce costs.
- To minimise duplication of efforts and reduce conflicts.
- To establish clear job roles, responsibilities and accountability.
- To create an adequate chain of command for communication and decision-making.
- To facilitate delegation which improves managerial efficiency.
- To prepare the enterprise for expansion by creating a scalable structure.
Practical outcome: Organising turns plans into action by arranging the human and material resources needed. Well-organised firms are more efficient, flexible, and better able to meet customer needs.
- Manufacturing plant: Work is divided into production, quality control, maintenance, and procurement departments so each unit specialises and operates efficiently.
- Hospital: Departments such as emergency, surgery, pediatrics and radiology ensure patients get specialised care and clear responsibility for each service.
- IT company: Teams are formed by function (development, QA, operations) or product (App A team, App B team) to coordinate releases and support.
- Restaurant chain (McDonald's): Standardised roles (cashier, cook, manager) and processes ensure consistent service across outlets.
- School: Principal → Head of Departments → Teachers structure ensures curriculum delivery, discipline and administration are coordinated.
- \[Span of Control = Number of direct subordinates reporting to a manager\]
- \[Span of Management (approx.) = Total employees at a level / Number of managers at that level\]
- \[Length of Scalar Chain = Number of hierarchical levels (higher value = longer chain of command)\]
- \[Degree of Decentralisation (%) = (Number of decisions delegated to lower levels / Total decisions) × 100\]
- \[Department Size (%) = (No. of employees in department / Total employees) × 100\]
Principles of Organising
Principles of Organising
Key Point: Total number of communication channels (for n people): n(n − 1)/2. (Shows how communication complexity rises rapidly with size.)
Organising is a managerial function that establishes structure of roles, relationships and authority to achieve organisational objectives efficiently. The Principles of Organising are general guidelines to design an effective organisational structure and to ensure smooth coordination of activities.
Key principles (brief description and purpose):
- Specialisation (Division of Work): Break down tasks into smaller parts so people can develop expertise. Purpose: higher efficiency and better quality.
- Departmentation (Grouping of Activities): Group related jobs into units (functions, products, regions, customers). Purpose: clarity, coordination and scale.
- Authority and Responsibility: Authority is the right to give orders; responsibility is the obligation to perform. Principle: authority and responsibility should be balanced so people can be held accountable.
- Delegation of Authority: Assigning work along with the necessary authority and responsibility to subordinates. Purpose: faster decisions, manager focus on planning.
- Unity of Command: Each person should receive orders from only one superior to avoid confusion and conflict.
- Unity of Direction: Activities having the same objective should be placed under one manager and one plan. Purpose: coordinated action towards common goals.
- Scalar Chain (Chain of Command): A clear, formal line of authority from top to bottom. Purpose: clarity in reporting and decision flow; use of 'gang plank' for quicker lateral communication if needed.
- Span of Control (Span of Management): Number of subordinates a manager can effectively supervise. Wider spans suit simpler, standardized tasks; narrower spans suit complex, variable work.
- Order (Principle of Order): Right person and right material at right place and time. Purpose: systematic arrangement and fewer delays.
- Equity: Fairness in treatment of employees to inspire loyalty and commitment.
- Stability of Tenure: Reasonable employee security to reduce turnover and retain skills.
- Initiative: Encourage subordinates to take thoughtful initiatives. Purpose: innovation and commitment.
- Esprit de Corps (Team Spirit): Promote unity and harmony among employees to improve morale and performance.
- Centralisation vs Decentralisation: Extent to which decision-making authority is concentrated at top levels (centralisation) or dispersed among lower levels (decentralisation). Choose the mix depending on environment, size and managerial capability.
- Coordination: Harmonising activities and efforts across different units. It is both a principle and the outcome of good organising.
Why these principles matter: They help managers design structures that reduce confusion, avoid overlapping duties, speed up decision-making, ensure accountability, motivate employees and adapt to change.
Application tips: Match span of control to task complexity; use departmentation that fits strategy (product for diversified firms, functional for single-line firms); delegate but retain accountability; establish clear reporting lines and procedures for lateral communication; balance centralisation and decentralisation according to control needs and environmental uncertainty.
- Specialisation: McDonald's divides work (cashier, cook, packager) so each employee masters one task, speeding service and ensuring consistency.
- Departmentation by product: Apple has separate teams for iPhone, Mac and Services to focus expertise and strategy per product line.
- Unity of Command & Scalar Chain: The army uses a strict chain of command—each soldier reports to one superior—ensuring clarity and quick execution.
- Span of Control: A call centre manager supervises a wide span (20–40 agents) for standardized tasks, while a hospital head nurse has a narrow span (4–6 nurses) for complex patient care.
- Delegation: A marketing manager delegates campaign execution to a team lead with authority to approve creatives and timelines, while holding them accountable for results.
- Centralisation vs Decentralisation: A small bakery keeps decisions centralised with the owner, while a multinational like Unilever decentralises many decisions to country teams for local responsiveness.
- \[Total number of communication channels (for n people): n(n − 1)/2. (Shows how communication complexity rises rapidly with size.)\]
- \[Number of horizontal (peer-to-peer) channels among n subordinates: n(n − 1)/2.\]
- \[Number of direct vertical relationships between a manager and n subordinates: n.\]
- \[Total relationships involving a manager and n subordinates (vertical + horizontal among subordinates): n + n(n − 1)/2.\]
- \[Average span of control = Total number of employees / Number of managers. (A simple measure to compare spans across units.)\]
Process/Steps in Organising
Process/Steps in Organising
Key Point: Span of control (s) = Number of direct subordinates per manager (no. per manager).
Organising is the management function that establishes an intentional structure of roles, responsibilities and relationships so organisational objectives can be achieved efficiently. The process of organising converts plans into action by defining who does what, how work is grouped, and how authority and responsibility flow.
- Identify and divide work into tasks
Start by studying the plan and determining the activities needed to achieve objectives. Break the total work into manageable tasks (work analysis). This clarifies what must be done before grouping or assigning.
- Group activities into departments (Departmentalisation)
Cluster related tasks into departments or units based on function, product, region, process, customer or matrix combinations. Departmentalisation creates specialization and coordination within similar activities.
- Assign duties and delegate authority
Allocate specific tasks to individuals or posts. Provide the necessary authority to perform those duties (delegation). Delegation involves giving responsibility plus commensurate authority and ensuring accountability.
- Allocate resources and responsibilities
Provide people, budget, equipment and time required for each role. Clarify who is responsible and what resources they control so they can complete assigned tasks.
- Establish reporting relationships (Span of control & Chain of command)
Decide who reports to whom. Define a clear chain of command (scalar chain) and an appropriate span of control (how many subordinates a manager supervises) to ensure supervision and communication are effective.
- Coordinate activities
Create mechanisms (meetings, committees, reporting systems, liaison roles) to integrate and align the departments and individuals so that interdependent tasks are synchronized.
- Establish policies, procedures and structure
Document standard operating procedures, rules and an organisational chart that shows formal relationships and authority lines. This institutionalises behaviour and makes the structure transparent.
- Review and adjust
Continuously monitor performance and environment. Revise the structure, authority, or processes where needed to correct inefficiencies or respond to change.
Key considerations and common principles: unity of command (each person reports to one superior), unity of direction (activities with same objective under one manager), span of control (wider spans suit routine tasks; narrow spans suit complex tasks), delegation, and departmental balance between specialization and coordination.
- Software company: Tasks are divided (development, testing, UI/UX), grouped into product teams (departmentalisation by product), duties assigned to developers/testers, authority delegated to team leads, reporting relationships set (team lead -> product manager -> CTO).
- Hospital: Work divided into medical, nursing, diagnostics and administration. Departments (surgery, pediatrics, radiology) with heads; doctors and nurses assigned duties; clear reporting to department head and hospital director.
- School: Curriculum and administrative tasks separated; departments for subjects; teachers assigned classes; head of department and principal define reporting; coordination via staff meetings and timetables.
- Manufacturing plant: Production, quality control, purchase and maintenance are separate units; supervisors delegated authority over shop-floor workers; resources (machines, materials) allocated to production lines.
- Restaurant: Kitchen (food prep), front-of-house (service), procurement and accounts departments. Chef, manager and supervisors have delegated authority; coordination ensures timely serving and inventory control.
- \[Span of control (s) = Number of direct subordinates per manager (no. per manager).\]
- \[Total persons in a perfectly balanced hierarchy with uniform span s and L levels (including top) : T = 1 + s + s^2 + ... + s^(L-1) = (s^L - 1)/(s - 1) (for s ≠ 1).\]
- \[If T and s are known\]\[approximate number of levels L ≈ log_s [(T*(s-1)) + 1]. (Useful to estimate hierarchy depth.)\]
- \[Manager-to-subordinate ratio = 1 : s (e.g.\]\[if s = 5 then one manager per five subordinates).\]
Departmentation
Departmentation
Key Point: Span of management (S) = Number of subordinates (N) / Number of immediate supervisors (M). (S = N / M)
Definition
Departmentation (or departmentalisation) is the process of grouping activities and people into manageable units (departments) so that an organisation’s objectives can be achieved efficiently. It is a key step in organising that creates a formal structure, defines roles and responsibilities, and establishes channels of coordination and control.
Objectives
- Group similar activities for specialization and expertise.
- Clarify authority and responsibility relationships.
- Improve coordination and control within units.
- Facilitate use of resources and managerial supervision.
- Help define career paths and training needs.
Key features / principles
- Division of work: activities are divided into logical groups.
- Unity of command within each department (one immediate superior).
- Functional specialisation: each department focuses on related tasks.
- Span of control: number of subordinates a manager can effectively supervise.
- Coordination mechanisms are needed to integrate departments.
Common bases (types) of departmentation
- Functional – grouping by functions (e.g., Finance, Marketing, Production, HR). Best for small/medium firms with homogeneous products.
- Product – each major product or product line has its own department (e.g., Cars division, Trucks division). Useful for diversified product lines.
- Geographical / Territorial – departments by region or territory (e.g., North Zone, South Zone). Useful for firms operating across wide areas.
- Customer – grouped by customer categories (e.g., Retail customers, Corporate clients, Government). Focuses on customer needs.
- Process / Equipment – grouping by production processes or equipment used (e.g., Cutting, Welding, Assembly).
- Project – temporary departments formed for projects (e.g., construction projects, IT implementations).
- Matrix – dual-reporting structure combining functional and product (or project) lines. Encourages flexibility but requires strong coordination.
- Time-based – shifts or time slots as departments (e.g., Morning, Evening, Night operations).
Advantages
- Specialization improves efficiency and expertise.
- Clear responsibility and authority lines reduce confusion.
- Better supervision and control within manageable units.
- Easier performance measurement and accountability by department.
- Flexibility to grow by adding new departments (e.g., new product lines or regions).
Limitations / disadvantages
- Risk of departmental silos and poor inter-departmental coordination.
- Duplication of resources (e.g., multiple marketing units) can increase costs.
- Potential conflicts of interest between departments (e.g., sales vs. production).
- Matrix structures can create confusion due to dual authority.
Factors affecting choice of departmentation
- Size and scale of the organisation.
- Nature and diversity of products/services.
- Geographical spread and market characteristics.
- Managerial capability and span of control.
- Need for flexibility and speed of decision-making.
- Cost considerations and resource availability.
Steps in creating departments
- Analyse and group activities by logical similarity (function, product, process, etc.).
- Decide department boundaries and size considering span of control.
- Assign authority and responsibility for each department.
- Establish coordination mechanisms between departments (liaison, committees, integrators).
- Review and adjust structure periodically as needs change.
Coordination methods: cross-functional teams, liaison officers, committees, standard operating procedures, information systems, and matrix arrangements.
Practical tip for students: In exam answers, define departmentation, list main types (at least 4–5), give advantages and limitations, and illustrate using a short example relevant to the question.
- Hospital: Departments by medical speciality — Cardiology, Pediatrics, Orthopaedics, Radiology, Administration. Each department has specialised doctors, nurses and equipment catering to patient needs.
- Automobile company (e.g., Tata Motors): Product-based divisions — Passenger Vehicles, Commercial Vehicles, Electric Vehicles. Each product division has its own R&D, production, marketing and after-sales teams.
- Retail chain (e.g., a supermarket): Geographical departmentation — North-region stores, South-region stores. Each region has regional managers handling local purchasing, staffing and promotions.
- IT services firm (e.g., Infosys): Matrix structure — functional managers (HR, Finance, Technology) and project managers. Employees report to functional heads for career development and to project managers for day-to-day project work.
- Bank: Customer-based departments — Retail Banking, Corporate Banking, NRI Banking, Wealth Management. Each department designs products and services for its customer segment.
- \[Span of management (S) = Number of subordinates (N) / Number of immediate supervisors (M). (S = N / M)\]
- \[Required number of supervisors (M) = Ceiling( N / S )\]\[Example: If 120 subordinates and an acceptable span S = 8\]\[M = Ceiling(120/8) = 15 supervisors.\]
- \[Approximate levels in hierarchy ≈ Ceiling( Total employees / Average span per level ). (This is a practical approximation — actual levels depend on management design and job complexity.)\]
- \[Managerial load (conceptual) = Total managerial activities / Available managerial time. (Used qualitatively to decide appropriate span\]\[not a precise numeric rule.)\]
Delegation of Authority
Delegation of Authority
Key Point: Span of management (simple average) = Total number of subordinates / Number of managers
Definition: Delegation of authority is the process by which a manager assigns responsibility and grants authority to a subordinate to carry out specific activities, while retaining ultimate accountability.
Core elements:
- Authority – the right to take decisions, use resources and give orders.
- Responsibility – the obligation to perform assigned tasks.
- Accountability – the requirement to answer for the outcomes; it flows upward and cannot be delegated.
Process (Stepwise):
- Identify and define the task to be delegated.
- Assign responsibility for the task to an appropriate subordinate.
- Grant the necessary authority to carry out the task.
- Establish accountability and set performance standards.
- Provide guidance and resources; monitor and give feedback.
Principles of effective delegation:
- Principle of clarity: Duties, authority and expected results must be clearly defined.
- Parity of authority and responsibility: Authority granted should match the assigned responsibility.
- Scalar principle: Delegation should respect the chain of command.
- Unity of command: A subordinate should report to only one superior for a given task.
- Accountability: Delegation does not remove the delegator s overall accountability.
- Exception principle: Managers should intervene only when performance deviates materially from standards.
Advantages: Faster decision making, managerial time freed for planning, employee motivation and development, better use of expertise, flexibility and quicker response to issues.
Disadvantages / Risks: Poor delegation can cause confusion, loss of control, inconsistent decisions, lower morale if responsibility is dumped without authority, or mistakes if subordinates are not trained.
Barriers to delegation: fear of loss of control, lack of trust in subordinates, inadequate training, unclear job descriptions, poor communication, managers habitually doing routine work themselves.
Ways to overcome barriers: select and train right people, give clear instructions, provide resources, allow autonomy, ensure two-way communication and follow-up with feedback.
Delegation vs Decentralisation: Delegation is a unitary process where authority is passed downward; decentralisation is the systematic effort to disperse decision making across the organisation. Delegation is a building block of decentralisation. Decentralisation is measured organisation-wide; delegation is manager to subordinate.
Practical tips for managers: delegate whole tasks not fragments, match tasks to competence, state expected outcomes, set limits of authority, schedule review points, coach rather than re-do the job.
Quick reminder: Authority flows downward, responsibility flows downward, accountability flows upward.
- Restaurant manager delegates opening duties (cash handling, prep) to a shift supervisor, gives authority to order supplies within a set limit, but remains accountable for overall operations.
- School principal delegates class scheduling and discipline for a grade to the head teacher, grants authority to approve day-to-day adjustments and holds the head teacher accountable for results.
- Project manager assigns coding modules to a team lead, grants authority to make technical decisions and allocate developer time; the project manager remains accountable to the client for delivery.
- Retail store regional manager delegates inventory reordering authority to store managers up to a monetary limit; final quarterly sales performance accountability stays with the regional manager.
- Healthcare: Chief nurse delegates medication administration to registered nurses per protocol but remains accountable for nursing standards and patient safety.
- \[Span of management (simple average) = Total number of subordinates / Number of managers\]
- \[Degree of decentralisation (%) = (Number of decisions made at lower levels / Total number of organisational decisions) × 100\]
- \[Delegation relationship (conceptual) = Responsibility + Authority → Accountability (Accountability remains with delegator)\]
- \[Authority-responsibility parity (guideline) : Authority granted ≈ Responsibility assigned (if Authority < Responsibility\]\[subordinate cannot perform effectively\]\[if Authority > Responsibility\]\[it may cause misuse)\]
Decentralisation
Decentralisation
Key Point: Degree of decentralisation (%) = (Number of decisions delegated / Total number of decisions) × 100
Definition: Decentralisation is the systematic delegation of authority to lower levels of management so that decision-making is dispersed throughout the organisation rather than being concentrated at the top.
Key points / Characteristics:
- It is a process and a structural feature: authority is permanently spread across levels.
- Delegation is a tool; decentralisation is the broader outcome or policy.
- Authority and responsibility are distributed to managers at various levels.
- It is a continuum from centralisation (little decentralisation) to full decentralisation.
Decentralisation vs Delegation (brief):
- Delegation is a one-to-one process (superior to subordinate) of transferring authority. Decentralisation refers to widespread delegation across the organisation.
- Delegation can exist without full decentralisation; decentralisation implies systematic, long-term dispersal.
Advantages:
- Faster decision-making and better responsiveness to local conditions.
- Improved motivation and development of managers through autonomy.
- Relieves top management, allowing focus on strategic issues.
- Better use of local knowledge and customer orientation.
- Encourages innovation and entrepreneurship within units.
Disadvantages / Risks:
- Potential loss of control and inconsistent policies across units.
- Higher risk of poor decisions if subordinates lack competence.
- Difficulty in coordination and standardisation; duplication of efforts.
- May increase administrative costs for local units.
Factors affecting the extent of decentralisation:
- Size and complexity of the organisation.
- Competence, experience and loyalty of subordinates.
- Top management philosophy and trust in subordinates.
- Nature of business and need for uniformity or local responsiveness.
- Cost and time required for centralised vs decentralised decisions.
- Environmental uncertainty and speed of change.
Principles / Good practices for implementing decentralisation:
- Clearly define authority and responsibility limits.
- Ensure adequate training and selection of managers.
- Provide required resources and information systems.
- Set measurable performance standards and controls.
- Maintain coordination through policy guidelines and reporting.
When to decentralise: When local responsiveness, speed, managerial development and use of local information outweigh the need for strict central control or uniformity.
Summary: Decentralisation improves responsiveness and managerial initiative but must be balanced with control, coordination and adequate training to avoid inconsistency and loss of strategic direction.
- Multinational corporations: Many global companies (for example, Unilever or Tata Group companies) give product divisions or country units autonomy to make marketing and operational decisions tailored to local markets.
- Franchise models: McDonald's and Subway grant franchisees authority to manage local operations (hiring, local promotions) while following central standards.
- Banks: Commercial banks like SBI or ICICI allow branch managers to sanction loans and manage local customer services within specified limits.
- Retail chains: A supermarket chain lets store managers decide local inventory mix, promotions and staffing to suit local demand.
- Government decentralisation: Panchayati Raj institutions delegate decision-making and budgetary authority to local self-governments for community-level development.
- \[Degree of decentralisation (%) = (Number of decisions delegated / Total number of decisions) × 100\]
- \[Level-based degree (%) = (Number of management levels with delegated authority / Total number of levels in organisation) × 100\]
- \[Delegation ratio (%) = (Number of managers with delegated authority / Total number of managers) × 100\]
Authority, Responsibility and Accountability
Authority, Responsibility and Accountability
Key Point: Span of Management = Total number of subordinates ÷ Number of managers (used to measure managerial span)
Overview
Authority, responsibility and accountability are three interlinked concepts in the process of organising. They define who can make decisions (authority), who must do the work (responsibility), and who must answer for results (accountability).
Definitions
- Authority: The formal right given to a person to give orders, make decisions and allocate resources to achieve organisational objectives. It flows downward in the hierarchy and is backed by the organisation.
- Responsibility: The obligation of an individual to perform assigned tasks and duties to the expected standard. It flows upward — from the subordinate who performs the task to the manager who assigned it.
- Accountability: The obligation to report and justify the results of delegated work and to face consequences for performance or non-performance. It remains with the person who delegates work (often the superior) or the person ultimately responsible, depending on organisational rules.
Characteristics and principles
- Unity (Principle of Parity): Authority and responsibility should be coextensive — the person given responsibility should have corresponding authority.
- Delegation: Authority can be delegated but not accountability. The process of delegation involves assignment of duties, granting of authority and creating accountability.
- Scalar Chain: Authority follows the chain of command; clear lines reduce confusion.
- Responsibility can be shared: Multiple people can share responsibility but accountability for results normally rests with a single person (or clearly defined group).
Delegation: process and elements
- Assignment/Delegation of duty: The superior assigns specific tasks or objectives.
- Granting authority: The superior gives the subordinate the right to make decisions and use resources to accomplish the task.
- Creation of accountability: The subordinate is expected to report results and is answerable for performance.
Types of authority
- Line authority: Direct chain of command (e.g., manager to supervisor).
- Staff authority: Advisory authority (e.g., HR, legal) — recommends but does not command in other units.
- Functional authority: Limited authority over specific activities across departments (e.g., quality-control manager can instruct on quality matters).
Relationship & key points
- Authority enables responsibility — a person cannot be expected to perform tasks without the power to do so.
- Accountability ensures that delegated authority is used responsibly; it creates answerability for outcomes.
- Effective delegation balances authority and responsibility and specifies accountability clearly.
Importance
- Clarifies who does what (reduces conflict and duplication).
- Improves managerial efficiency through delegation.
- Facilitates coordination and faster decision-making.
- Strengthens control and performance measurement through accountability.
Common problems & remedies
- Mismatch of authority and responsibility: Remedy — follow parity principle; give adequate authority to meet responsibility.
- Reluctance to delegate: Remedy — train managers in delegation, set clear controls and feedback systems.
- Ambiguous accountability: Remedy — define roles and reporting relationships clearly.
How CBSE exams may ask
- Define each term and explain their interrelationship.
- Give examples of delegation and explain why authority and responsibility must be equal.
- State features and principles of delegation, and methods to make delegation effective.
- Factory: A production manager assigns the task of meeting monthly output targets to a shift supervisor (responsibility), gives authority to allocate machine time and assign workers (authority), and requires weekly performance reports — the supervisor must answer for the results (accountability).
- School: The principal appoints a teacher to conduct examinations (responsibility), provides authority to call invigilators and use classrooms (authority), and expects the teacher to submit the exam report — the teacher is accountable for smooth conduct.
- Hospital: Head nurse delegates medication administration to registered nurses (responsibility), grants authority to access drug records and patient charts (authority), and the nurse must report any errors to the head nurse/doctor (accountability).
- Retail chain: Regional manager delegates store-level pricing decisions within company policy to store managers (responsibility + limited authority), but regional manager remains accountable to corporate for overall sales targets and compliance.
- Army: Orders flow top-down (authority) and soldiers are responsible for execution; commanders remain accountable for mission results and discipline in their units.
- \[Span of Management = Total number of subordinates ÷ Number of managers (used to measure managerial span)\]
- \[Principle of Parity (expressed conceptually): Authority assigned ≥ Responsibility assigned (ideally Authority = Responsibility)\]
- \[Delegation relation (conceptual): Delegation = Assignment of Duty + Grant of Authority + Establishment of Accountability\]
- \[Chain of command (conceptual): Authority flows downward\]\[Responsibility flows upward\]\[Accountability flows upward to the person who will be answerable\]
Span of Control
Span of Control
Key Point: Span of Control = Total number of subordinates / Total number of managers
Span of Control — Meaning
Span of control (or span of management) is the number of subordinates that a manager can effectively supervise and control. It determines how many employees report directly to a single manager.
Types
- Wide span: One manager supervises many subordinates. Fewer hierarchical levels, greater delegation and autonomy.
- Narrow span: One manager supervises few subordinates. More hierarchical levels, closer supervision and tighter control.
Factors Affecting Span of Control
- Nature of work: Routine, simple tasks allow a wider span; complex or specialized work requires a narrower span.
- Manager’s competence: Skilled, experienced managers can handle a wider span.
- Subordinates’ ability: Well-trained, motivated employees reduce supervisory needs and permit a wider span.
- Availability of systems and technology: Good information systems, reporting tools and standard procedures increase the feasible span.
- Geographical dispersion: If subordinates are spread out, span tends to be narrower.
- Nature of organisation: Small/flexible organisations often have wide spans; large/formal organisations may have narrow spans.
- Degree of centralisation: High decentralisation supports wider spans; centralised decision-making supports narrower spans.
Advantages and Disadvantages
Wide span — Advantages
- Lower managerial costs (fewer managers).
- Faster decision-making and greater flexibility.
- Greater employee autonomy and responsibility.
Wide span — Disadvantages
- Manager may be overburdened.
- Less close supervision; potential for communication gaps.
Narrow span — Advantages
- Closer supervision and control; easier coordination.
- Better training and guidance for subordinates.
Narrow span — Disadvantages
- Higher managerial costs (more levels).
- Slower decision-making and possible over-control.
Practical implications
Span of control affects organisational structure: a wider span tends to produce flatter structures (fewer levels), while a narrower span produces taller structures (more hierarchical layers). The choice of span should balance cost, control needs, and effectiveness.
- Retail store manager: A small shop owner may directly supervise 10–15 sales staff (wide span) because tasks are routine and staff are nearby.
- School principal: A principal may directly manage only a few vice-principals and heads of department (narrow span) because roles are complex and need closer coordination.
- Factory supervisor: On a production line with routine work and standard procedures, one supervisor can oversee 20–30 operators (wide span).
- IT team lead: For a specialist software development team doing complex tasks, the lead may supervise 4–6 developers (narrow span) to ensure quality and coordination.
- Call centre: A team leader may oversee 15–25 agents (wide span) because work is standardized, monitored by software, and decisions are routine.
- \[Span of Control = Total number of subordinates / Total number of managers\]
- \[Manager : Subordinate ratio = 1 : n (where n is the average number of direct reports per manager)\]
- \[Number of communication channels among n people = n(n - 1) / 2 (used to show rising complexity as span increases)\]
Organisational Structure/Design
Organisational Structure/Design
Key Point: Span of Control = Total number of subordinates reporting / Number of managers
Definition: Organisational structure (or design) is the formal system of tasks, reporting relationships and communication channels that link people into a working unit to achieve organisational goals. It shows how jobs are grouped, who reports to whom and how decisions are made.
Purpose & Importance: A good structure clarifies roles and responsibilities, improves coordination, enables effective decision-making, avoids duplication, and supports strategy implementation and growth.
Key Elements:
- Division of Work (specialisation) — grouping tasks into jobs.
- Departmentalisation — grouping jobs into units (by function, product, region, customer, process).
- Chain of Command (scalar chain) — the line of authority from top to bottom.
- Span of Control — number of subordinates a manager supervises.
- Unity of Command — each employee should report to only one superior.
- Authority and Responsibility — right to give orders and expectation to perform tasks; these should be balanced.
- Centralisation vs Decentralisation — where decision-making authority resides.
- Formalisation — degree to which jobs are standardized and rules/procedures used.
Common Types of Organisational Structure (with brief pros & cons):
- Functional Structure: Departments by function (e.g., marketing, finance). Pros: efficiency, expertise development. Cons: poor inter-department coordination, slower decision-making for cross-functional tasks.
- Divisional Structure: Units by product, geography or customer. Pros: product focus, accountability, faster decisions. Cons: duplication of resources, higher cost.
- Matrix Structure: Dual reporting (functional + project/product managers). Pros: efficient use of specialists, flexible. Cons: complexity, potential conflict from dual authority.
- Line Structure: Simple, direct chain (suitable for small organisations). Pros: clear authority. Cons: overburdened managers as organisation grows.
- Line & Staff Structure: Line managers (authority) supported by staff specialists (advisory). Pros: expert advice without losing command. Cons: possible conflicts between line and staff.
- Committee/Team Structure: Decisions made by groups/committees. Pros: democratic, better decisions. Cons: slow, diffusion of responsibility.
- Flat vs Tall: Flat structures have few levels, wide span of control (suitable for startups). Tall structures have many levels, narrow spans (common in large bureaucracies).
Principles of Good Organisational Design:
- Fit with strategy — design should support the organisation’s strategic objectives.
- Clarity — roles, responsibilities and reporting lines must be clear.
- Balance of centralisation and decentralisation — depending on environment and strategy.
- Coordination mechanisms — use committees, liaison roles, integrators or cross-functional teams where needed.
- Flexibility — structure should adapt to change (technology, markets).
- Economy — avoid unnecessary layers and duplication.
Factors Influencing Choice of Structure: size of organisation, organisational goals/strategy, environment (stable vs turbulent), technology and routine of tasks, workforce skills and culture, geographical dispersion.
Design Process (basic steps): Identify missions and tasks → Group tasks into jobs → Group jobs into departments → Establish reporting relationships → Distribute authority → Create coordination and control mechanisms → Review and adjust.
Common Problems & Remedies: Poor coordination — introduce cross-functional teams or integrators. Excessive centralisation — delegate decision rights. Over-bureaucracy — reduce layers and empower employees. Ambiguous roles — clarify job descriptions and reporting lines.
Summary: Organisational structure is the backbone that aligns people and processes to strategy. The best design balances clarity and flexibility, supports coordination, and matches the organisation’s size, technology and environment.
- Tata Consultancy Services (TCS) — uses a mix of functional departments (HR, Finance, Sales) with project-based teams and client-focused account managers, resembling a hybrid/matrix approach to serve diverse global clients.
- A startup (tech app) — typically adopts a flat structure with few hierarchical levels and wide spans of control to encourage rapid decisions and innovation.
- Maruti Suzuki (manufacturing) — largely functional structure with clear departments for production, procurement, quality and sales; for different models/markets it creates product or regional teams.
- Amazon/Flipkart — large e-commerce firms use divisional structures (by product categories or region) plus functional teams (tech, operations), enabling local responsiveness with centralised platforms.
- Hospitals — often use line and staff: doctors and nursing (line) deliver core services while HR, legal and finance act as staff specialists providing support and advice.
- Government ministries — classic hierarchical (tall) structure with clear chain of command and formal rules to ensure accountability.
- \[Span of Control = Total number of subordinates reporting / Number of managers\]
- \[Degree of Decentralisation (%) = (Number of decisions delegated / Total managerial decisions) × 100\]
- \[Delegation Effectiveness (%) = (Tasks completed without escalation / Total tasks delegated) × 100\]
- \[Authority-Responsibility Balance (qualitative rule): Authority ≥ Responsibility (ideally equal)\]\[if Responsibility > Authority\]\[performance suffers\]
Types of Organisational Structure
Types of Organisational Structure
Key Point: Span of Control = Total number of subordinates ÷ Number of managers (gives average number of direct reports per manager).
Introduction: Organisational structure defines how tasks, authority and responsibility are formally arranged and coordinated in an organisation. Choice of structure depends on size, strategy, environment and technology.
Main types:
-
Functional Structure
- Definition: Employees are grouped by functions (e.g., production, marketing, finance, HR) under functional heads who report to top management.
- When used: Stable environment, relatively small to medium or large firms wanting specialization and efficiency.
- Advantages: Specialisation, economies of scale, clear career paths, centralised control.
- Disadvantages: Poor inter-department coordination, narrow outlook, slow decision-making for cross-functional issues.
-
Divisional Structure
- Definition: Organisation is divided into semi-autonomous units (divisions) by product, geography (territory), customer or process. Each division has its own functional departments.
- When used: Large, diversified companies operating in different markets or products.
- Advantages: Focus on product/market, faster decisions, accountability, easier performance measurement.
- Disadvantages: Duplication of resources, higher costs, potential for inter-division rivalry.
-
Line Organisation
- Definition: Simple, clear chain of command — direct vertical links from top to bottom; every subordinate has one boss.
- When used: Small organisations or military-type organisations requiring clear authority.
- Advantages: Simplicity, quick decision-making, clear responsibility.
- Disadvantages: Overloaded managers, limited specialization, unsuited for complex operations.
-
Line and Staff Organisation
- Definition: Combines line (direct authority) with staff (advisory specialists) who support line managers without direct authority over subordinates.
- When used: Medium to large organisations needing specialist advice (e.g., legal, HR, R&D).
- Advantages: Specialist support, better planning and control, retains clear command.
- Disadvantages: Possible conflicts between line and staff, costs of staff departments.
-
Matrix Organisation
- Definition: Dual command structure where employees report to both functional managers and project/product managers. Organised along two dimensions (e.g., function and project).
- When used: Knowledge-intensive, project-driven firms (R&D, IT, aerospace) requiring flexibility and resource sharing.
- Advantages: Efficient resource use across projects, better communication, flexible, encourages teamwork.
- Disadvantages: Confusion from dual authority, potential power struggles, complex reporting.
-
Committee Organisation
- Definition: Authority vested in a group of persons (committee) rather than a single manager; decisions are collective.
- When used: Policy-making bodies, cross-functional issues requiring consensus (e.g., board committees, academic senates).
- Advantages: Collective wisdom, better acceptance of decisions.
- Disadvantages: Slow decision-making, risk of compromise solutions, diffusion of responsibility.
-
Project Organisation
- Definition: Formed for a specific task or project; team is built with required specialists and disbanded when project ends.
- When used: Construction, engineering, film-making, IT projects.
- Advantages: Clear focus on objectives, flexibility, accountability for project outcomes.
- Disadvantages: Temporary nature can cause uncertainty for staff, resource duplication.
-
Network / Virtual Organisation (Modern variant)
- Definition: Core organisation outsources major functions to external partners; relies on networks and technology to coordinate.
- When used: Firms seeking agility and low fixed costs (platform companies, design firms outsourcing manufacturing).
- Advantages: Flexibility, access to specialist capabilities, lower capital requirement.
- Disadvantages: Dependency on partners, control & coordination challenges, confidentiality risks.
Choosing a structure: Consider size, strategy, environment, technology, degree of centralisation, need for specialization, and need for flexibility. No one structure is best; many organisations use hybrids (e.g., divisional units with functional departments, or matrix overlay on a functional base).
- Functional: A manufacturing company with separate departments for Production, Marketing, Finance and HR reporting to the CEO (typical of small to medium enterprises).
- Divisional: Hindustan Unilever (HUL) or Procter & Gamble — separate product divisions (soaps, foods, personal care) with their own marketing and production functions.
- Line Organisation: Small retail shops, family-run businesses and military organisations with strict vertical command.
- Line & Staff: A large hospital where doctors and nurses (line) are supported by staff departments like Medical Records, HR, Legal and Finance.
- Matrix: An IT firm where employees report to a Functional Head (e.g., Backend) and simultaneously to a Project Manager for a client project (example: software teams in TCS/Infosys).
- Committee: A university’s academic council or a corporate board committee (audit committee) that makes collective decisions.
- \[Span of Control = Total number of subordinates ÷ Number of managers (gives average number of direct reports per manager).\]
- \[Number of Hierarchical Levels = (can be counted directly) — equals levels from top management to lowest operational employee (scalar chain length).\]
- \[Approximate levels required (illustrative) = log_e[ N*(s-1) + 1 ] / log_e(s) where N = total employees and s = average span of control (used in organisational-design estimations).\]
- \[Degree of Centralisation (qualitative) ≈ Number of decisions made at top ÷ Total decisions (used conceptually\]\[usually measured by managerial audit rather than a single numeric formula).\]
Formal and Informal Organisation
Formal and Informal Organisation
Key Point: Span of Management (Span of Control) = Number of subordinates directly reporting to a manager. (Simple count, e.g., Span = 8 means one manager + 8 direct reports.)
Formal Organisation
Definition: A formal organisation is a deliberately planned structure of roles, responsibilities, authority and communication designed to achieve stated organisational goals. It is created by management and documented in charts, job descriptions, rules and procedures.
- Key features: Clearly defined roles and hierarchy; written rules and procedures; official communication channels; authority flows through chain of command; emphasis on organisational objectives.
- Advantages: Clarity of duties, predictability, easier coordination, accountability, efficient resource allocation, scalability.
- Limitations: Can be rigid, slow to adapt, may stifle creativity and informal cooperation.
Informal Organisation
Definition: An informal organisation is the network of personal and social relations that arise spontaneously among employees based on common interests, friendships, proximity and social needs. It is not officially prescribed but exists alongside the formal structure.
- Key features: Emerges naturally, flexible, based on interpersonal relationships, communicates through grapevine, serves social and psychological needs.
- Advantages: Faster communication, morale and cohesion, social support, transfer of unofficial information, can aid innovation and problem solving.
- Limitations: Information may be inaccurate (rumours), can resist formal policies, create cliques or factions, may undermine authority if misaligned with organisational goals.
Relationship and Interaction
Formal and informal organisations coexist and influence each other. The informal organisation fills gaps in the formal structure (e.g., faster problem solving, emotional support). Management should recognise and channel informal networks positively—using opinion leaders to implement change, reducing harmful rumours by improving formal communication, and aligning informal group goals with organisational objectives.
How to manage the balance
- Encourage positive informal networks (team-building, open communication).
- Use formal channels to clarify roles and reduce harmful rumours.
- Identify informal leaders (opinion makers) and involve them in change initiatives.
- Document essential procedures, but allow flexibility for creative solutions.
Summary
Formal organisation provides the official framework for achieving organisational objectives; informal organisation supplies the human, social fabric that can accelerate or obstruct those objectives. Effective management recognises, monitors and harmonises both.
- Formal organisation: A manufacturing company’s organisational chart showing CEO → Vice Presidents → Plant Managers → Supervisors → Workers; official job descriptions, SOPs and performance appraisal systems.
- Formal organisation (public sector): A government department with minister → secretary → directors → deputy directors with detailed rules and service regulations.
- Informal organisation: Employees in the marketing department who meet daily for coffee, share tips about clients, and informally coordinate campaign ideas outside official meetings.
- Informal organisation (grapevine): A circle of senior employees spreading news about an upcoming merger before the official announcement, accelerating rumours.
- Interaction example: During a system implementation, management uses respected informal leaders (opinion leaders) from different teams to pilot the change and persuade peers, improving adoption rates.
- \[Span of Management (Span of Control) = Number of subordinates directly reporting to a manager. (Simple count\]\[e.g.\]\[Span = 8 means one manager + 8 direct reports.)\]
- \[Approximate Number of Hierarchical Levels (L) ≈ ceil(log_{(S+1)}(N))\]\[where N = total people to be managed\]\[S = average span of management. (Used for estimating tall vs flat structure\]\[treat as an approximation.)\]
- \[Total Managers Needed ≈ ceil(N / (S + 1)) where S is average span and +1 accounts for the manager themselves if counting positions in a pyramid estimate.\]
- \[Note: These are heuristic formulas to plan structure\]\[Practical design also considers complexity of tasks\]\[geographical spread and skills.\]
Organisational Chart and Hierarchy
Organisational Chart and Hierarchy
Key Point: Span of control (for a manager) = Number of direct subordinates reporting to that manager. Example: If a manager directly supervises 8 employees, span = 8.
Definition — Organisational Hierarchy
Organisational hierarchy is the arrangement of positions and levels of authority in an organisation showing superior-subordinate relationships from top management down to operational staff. It defines who reports to whom, lines of command, levels of responsibility and authority.
Definition — Organisational Chart
An organisational chart (org chart) is a graphic representation of the organisational structure. It depicts positions (usually as boxes) and the formal reporting relationships (lines) among them. It makes the hierarchy visible and easy to understand.
Key elements & concepts
- Chain of command (Scalar chain): The continuous line of authority from top to bottom.
- Unity of command: Each subordinate should have only one direct superior to avoid confusion.
- Span of control: Number of subordinates who report directly to a manager.
- Levels of management: Layers such as top, middle and lower management; the number of levels defines the height of the hierarchy (tall vs flat).
- Formal vs. informal relationships: Org charts show formal reporting lines; informal relationships (networks) are not usually shown.
- Solid lines vs dotted lines: Solid line = direct authority; dotted line = advisory or secondary reporting.
Types of organisational charts
- Vertical (Hierarchical) chart: Top-down, common in traditional organisations.
- Horizontal (Flat) chart: Fewer levels, wider spans — used in small/start-up firms or teams.
- Functional chart: Departments by function (e.g., HR, Finance) reporting to top management.
- Divisional chart: Organisation split by product, geography or customer; each division has its own functional departments.
- Matrix chart: Dual reporting (functional manager + project manager); shows cross-functional teams.
How hierarchy and org chart relate
The hierarchy is the conceptual framework of authority and levels; the org chart is its visual map. The chart helps communicate the hierarchy clearly to employees, stakeholders and outsiders.
Advantages
- Clarifies roles, reporting lines and responsibility.
- Helps coordination and control by showing authority relationships.
- Assists in workforce planning, delegation and identifying gaps or overlaps.
- Useful for induction, performance appraisal and succession planning.
Limitations
- May hide informal communication and networks important for real work.
- Can be rigid — discourage initiative if overly hierarchical.
- Complex organisations may produce confusing, large charts.
Practical tips for drawing an org chart
- Start with the highest authority (CEO/Principal) at the top.
- Place direct reports below, connected with solid lines for authority.
- Use dotted lines to show advisory/secondary reporting.
- Group similar functions and use consistent box sizes and spacing.
- Use color coding to show departments, divisions or permanent vs temporary roles.
- Keep it readable — consider multiple charts (top-level + detailed unit charts) for large organisations.
- Large manufacturing company (e.g., Maruti Suzuki): Vertical org chart — Chairman/CEO at top, functional heads (Production, Marketing, Finance, HR) below, then managers, supervisors and workers. Clear chain of command aids mass production coordination.
- School: Principal at top, vice-principals/heads of department next, teachers under department heads and administrative/support staff (librarian, clerk) shown. Unity of command helps discipline and curriculum implementation.
- Hospital: Hospital Director → Heads of Departments (Surgery, Medicine, Pediatrics) → Consultants/Doctors → Nurses and support staff. Matrix features appear during specific projects (e.g., immunisation drive) with team leads from different functions.
- IT services firm using Matrix structure (e.g., project-based teams): Employee reports functionally to HR/Dept head and operationally to a Project Manager (dotted-line or dual reporting). Org chart shows both reporting lines to manage resources across projects.
- Start-up (Flat structure): Founders and a small team with few management levels — direct communication and wide spans of control. Org chart is shallow and broad, suited for rapid decision-making.
- \[Span of control (for a manager) = Number of direct subordinates reporting to that manager\]\[Example: If a manager directly supervises 8 employees\]\[span = 8.\]
- \[Average span of control = Total number of subordinates (except top) ÷ Number of managers/supervisors\]\[Example: 240 employees and 30 managers → Average span = 240 ÷ 30 = 8.\]
- \[Number of hierarchical levels = Count of management layers from top (level 1) to lowest operational level (level n)\]\[Chain (links) = Number of levels − 1\]\[Example: If there are 5 levels\]\[chain = 4.\]
Coordination
Coordination
Key Point: Coordination Index (%) = (Number of interdependent tasks completed on time / Total interdependent tasks) × 100
Definition: Coordination is the process of integrating the activities of different departments and individuals so that they work together harmoniously towards common organizational objectives.
Key points:
- Continuous process: Coordination is not one-time; it must be maintained while the organization functions.
- Pervasive and integrative: It applies to all levels and departments and brings diverse activities into a unified whole.
- Goal-oriented: Coordination directs efforts toward shared objectives and avoids counter-productive activity.
- Dynamic and reciprocal: It involves mutual adjustments among departments; feedback and follow-up are essential.
Importance: Effective coordination ensures unity of effort, reduces duplication of work, improves resource utilisation, speeds up decision-making, resolves conflicts, enhances flexibility, and raises overall efficiency and customer satisfaction.
Process/Steps to achieve coordination:
- Set common goals and clarify objectives.
- Define and assign responsibilities and authority to avoid overlaps.
- Establish effective communication channels for timely information flow.
- Compare and balance departmental plans and schedules.
- Take follow-up actions, provide feedback and make mutual adjustments.
Techniques/Devices used to secure coordination: committees and task forces, liaison officers, cross-functional teams, standing orders, coordination departments/units, regular inter-departmental meetings, information systems, standard procedures and policies, and mutual adjustment through informal contacts.
Barriers to coordination: departmental selfishness, unclear goals/authority, poor communication, resistance to change, rivalry, inadequate resources and conflicting priorities.
Coordination vs Cooperation (brief): Cooperation is willing assistance by individuals/departments; coordination is the managerial process that integrates that cooperation toward a common plan and timing. Cooperation may exist without planned coordination; effective coordination normally results in purposeful cooperation.
- Product launch: R&D, production, marketing, finance and logistics align schedules; production must finish units by X date, marketing prepares campaigns, finance releases budget and logistics sets distribution—coordinated planning avoids delays and stockouts.
- Hospital patient care: Doctors, nurses, lab, pharmacy and billing coordinate on patient charts, test orders and medication schedules so treatment is timely and safe.
- Construction project: Architects, engineers, suppliers, contractors and local authorities coordinate timelines, material deliveries and inspections to complete milestones on schedule.
- Airline operations: Ground crew, cabin crew, maintenance and air traffic control coordinate turn-around activities to minimise delays and ensure safety.
- Software development (Agile/Scrum): Developers, QA, product owner and operations hold daily standups and sprint planning to synchronise work and deliver increments every sprint.
- \[Coordination Index (%) = (Number of interdependent tasks completed on time / Total interdependent tasks) × 100\]
- \[Communication Effectiveness (%) = (Number of messages correctly understood / Total messages sent) × 100\]
- \[Net Benefit of Coordination = Benefits from reduced duplication and delays − Cost of coordination activities\]
- \[Number of communication channels (complexity) = n(n − 1) / 2 (where n = number of units/persons needing direct links)\]
- \[Coordination Effort (qualitative) ≈ Clarity of objectives + Strength of communication + Authority alignment + Mutual trust (used as a checklist rather than a strict numeric formula)\]
Problems in Organising and Remedies
Problems in Organising and Remedies
Key Point: Span of Control = Total Number of Subordinates / Number of Managers
Introduction: Organising involves arranging resources and activities to achieve objectives. While forming structure and assigning work, organisations commonly face practical problems that reduce efficiency, create conflicts or slow decision-making. Understanding these problems and their remedies helps managers design better structures and improve performance.
Common Problems in Organising
- Unclear lines of authority and responsibility: Employees don’t know who is accountable or who can make decisions, causing confusion and delays.
- Poor delegation: Managers either refuse to delegate (over-centralization) or delegate without adequate authority, resulting in bottlenecks or inability to perform.
- Excessive specialization: Too-narrow job roles lead to boredom, low motivation and inflexibility.
- Inadequate span of control: Too wide a span overwhelms managers; too narrow a span creates unnecessary managerial layers and high costs.
- Too many hierarchical levels (tall structure): Slows communication and decision-making; increases costs.
- Poor coordination between departments: Functional silos and lack of inter-departmental cooperation hinder goal achievement.
- Line and staff conflicts: Staff specialists give advice but line managers resist or misuse it, causing friction.
- Resistance to change: Rigid structures and vested interests block necessary reorganisation or innovation.
- Inadequate staffing and mismatched skills: Wrong people in wrong jobs reduce productivity and create turnover.
- Ambiguous job descriptions and authority overlaps: Lead to duplication of work and conflicts.
Remedies (How to Overcome These Problems)
- Clarify authority and responsibility: Issue clear job descriptions, organograms and written delegations so everyone knows reporting lines and expectations.
- Effective delegation: Follow the delegation chain—assign responsibility, grant sufficient authority, and ensure accountability. Use training and follow-up rather than micromanagement.
- Right span of control: Adjust the number of subordinates per manager depending on task complexity, geographical spread and required supervision.
- Sensible centralization vs decentralization: Decentralize routine and local decisions to lower levels while keeping strategic decisions centralized. Empower subordinate managers with authority & resources.
- Reduce unnecessary levels: Flatten structures where possible to speed decisions and cut costs; use team-based structures for flexibility.
- Improve coordination mechanisms: Use cross-functional teams, liaison roles, committees and integrated IT systems to share information and align goals.
- Resolve line–staff conflict: Define staff roles clearly, emphasize advisory nature, and promote mutual respect and joint accountability for outcomes.
- Job rotation and enrichment: Broaden job roles to reduce monotony and build multi-skilled employees for flexibility.
- Training and development: Build managerial and technical skills to reduce staffing mismatches and improve delegation capability.
- Use formal policies and performance systems: Standard operating procedures, KPIs and appraisal systems reduce ambiguity and align individual actions with organisational goals.
- Communicate change and involve people: Involve employees in design changes, explain reasons, and offer support to overcome resistance.
Summary: Problems in organising arise from unclear authority, poor delegation, wrong structure and weak coordination. The remedies focus on clarifying roles, redesigning structures (appropriate span and levels), empowering people, improving coordination and developing skills. Applying these remedies together creates an organisation that is responsive, efficient and aligned with its objectives.
- Too many levels — A national government office with 8–10 layers delays approvals; flattening to fewer levels reduced decision time and administrative cost.
- Poor delegation — A small manufacturing firm where the owner performs all approvals causes bottlenecks; delegating purchase authority to store managers sped up production.
- Line–staff conflict — An IT advisory team recommended a new ERP, but production managers resisted; forming a cross-functional implementation team resolved mistrust and ensured successful rollout.
- Excessive specialization — An assembly-line plant experienced high absenteeism; introducing job rotation and enrichment improved morale and reduced turnover.
- Lack of coordination — Sales and production at a consumer goods company worked in silos causing stockouts; instituting a weekly coordination meeting and shared dashboard aligned production with demand forecasts.
- \[Span of Control = Total Number of Subordinates / Number of Managers\]
- \[Average Managers per Level = Total Managers / Number of Hierarchical Levels\]
- \[Managerial Intensity (simple) = Number of Managers / Total Employees\]
- \[Degree of Decentralization (%) = (Decisions Made at Lower Levels / Total Decisions) × 100\]
- \[Approximate Levels (illustrative) ≈ log_{span}(Total Employees) — shows levels fall as span increases (used conceptually\]\[not as a strict rule)\]
Features and Qualities of a Good Organising System
Features and Qualities of a Good Organising System
Key Point: Span of management (S) = Number of direct subordinates reporting to a manager. (No single numeric ‘ideal’; depends on task complexity and manager capability.)
What is an organising system? An organising system is the set of principles, structures and processes that allocate tasks, group activities, distribute authority and establish relationships so that organisational goals are achieved efficiently and effectively. A good organising system provides clarity, coordination and control while being flexible enough to adapt to change.
Key features and qualities of a good organising system
- Clear objectives: Every unit and position must understand the organisation’s goals and how its work contributes. This prevents overlap and conflict.
- Defined division of work (specialisation): Tasks are divided into jobs that match skills and resources, increasing efficiency and expertise.
- Clear lines of authority and responsibility: Who gives orders, who executes them, and who is accountable must be unambiguous to ensure discipline and control.
- Unity of command: Each person should report to one direct superior to avoid conflicting instructions and confusion.
- Appropriate span of management: The number of subordinates reporting directly to a manager must be optimal — not so many that control is lost, not so few that hierarchy becomes too tall.
- Proper delegation of authority: Authority must match responsibility. Managers should delegate authority with accountability to speed up decision-making and empower subordinates.
- Coordination of efforts: Different departments and individuals must work together through communication, rules and procedures so that activities align with organisational objectives.
- Simplicity: The structure and procedures should be simple and easy to understand and operate; unnecessary complexity must be avoided.
- Flexibility: The system should be able to adapt to changing technology, markets and internal growth without major disruption.
- Balance: Workload, authority and responsibility should be balanced across positions and departments to prevent bottlenecks and overload.
- Efficiency and economy: Resources (human, financial, material) should be used optimally so the system achieves goals at minimum reasonable cost.
- Stability: The system must provide continuity and dependable routines, yet allow controlled change when needed.
- Effective communication channels: Open, timely and appropriate flows of information vertically and horizontally are essential for decision-making and coordination.
- Accountability and control: Mechanisms for monitoring performance and enforcing standards ensure objectives are met.
- Suitability to objectives and environment: The structure must fit the size, strategy, technology and environment of the organisation (no one-size-fits-all).
Why these qualities matter (brief): A system with these qualities reduces role conflict, speeds up decisions, maximises use of skills, enhances coordination and enables the organisation to respond to change — all of which improve performance and employee morale.
How to judge an organising system in practice: Look for clear job descriptions, visible reporting lines (organisational chart), balanced spans, documented authority limits, regular coordination meetings, efficient communication channels and documented performance controls.
- Hospital: Clear specialisation (surgeons, physicians, nurses, administrators), defined authority (department heads), unity of command (nurses report to a nurse manager), strong coordination (emergency protocols) and flexibility (on-call rotations).
- School: Principal → Heads of Departments → Teachers. Clear responsibilities (curriculum, assessment), appropriate span (HODs manage a few teachers), and communication systems (staff meetings, circulars).
- Manufacturing plant (assembly line): Division of work into specialised tasks, clear authority at supervisor level, short chains of command for quick decisions, and balance to avoid bottlenecks on the line.
- IT company using a matrix structure: Employees report to both project managers and functional managers. This allows flexibility and better resource utilisation but requires strong coordination and communication.
- Retail store (small): Store manager delegates cashier, floor staff and inventory duties; simplicity, clear authority, and close supervision keep operations efficient.
- \[Span of management (S) = Number of direct subordinates reporting to a manager. (No single numeric ‘ideal’\]\[depends on task complexity and manager capability.)\]
- \[Total positions in a balanced hierarchical tree: If each manager has b direct subordinates and there are L levels (level 0 to L)\]\[then Total employees N = (b^(L+1) - 1) / (b - 1)\]\[Example: b=3\]\[L=2 gives N=(3^3 -1)/(3-1)= (27-1)/2=13.\]
- \[Chain (length of command) = Number of hierarchical levels - 1. (Shorter chains imply faster decision flow.)\]
- \[Managerial ratio = Number of managers / Total number of employees. (Used to measure managerial intensity.)\]
- \[Approximate levels given total employees and span: L ≈ log_b((N*(b-1))+1) - 1 (inverse of the balanced-tree formula\]\[useful to estimate hierarchy depth for a chosen span).\]
Key Concepts
- Organising
- A managerial function of arranging and structuring work, resources and authority to achieve objectives efficiently.
- Organisation
- A structured group of people working together to achieve common goals; also the result of organising.
- Organisational structure
- The formal pattern of relationships and reporting lines that determines how tasks are divided and coordinated.
- Authority
- The right to give orders, make decisions and allocate resources to subordinates.
- Responsibility
- The obligation of an individual to perform assigned tasks and duties.
- Accountability
- The requirement to report and justify the outcomes of responsibilities; being answerable for results.
- Delegation
- The process of transferring authority and assigning responsibility for specific tasks to subordinates.
- Centralisation
- Concentration of decision-making authority at the top levels of management.
- Decentralisation
- Diffusion of decision-making authority to lower levels in the organisation.
- Span of management
- The number of subordinates a manager can effectively supervise.
- Chain of command
- The formal line of authority through which orders and decisions flow in an organisation.
- Unity of command
- The principle that each employee should receive orders from and be accountable to only one superior.
- Departmentation
- The process of grouping activities and people into departments based on function, product, territory or customers.
- Line organisation
- A simple organisational structure with direct, vertical relationships between superior and subordinate.
- Functional organisation
- Structure where specialists perform tasks according to their functions and employees report to multiple functional heads.
- Matrix organisation
- A hybrid structure combining functional and project lines of authority, where staff report to both functional and project managers.
- Formal organisation
- The official, deliberately planned structure of roles, responsibilities and relationships laid down by management.
- Informal organisation
- The network of social and personal relationships that arise spontaneously among employees.
- Job specialization
- The division of work into specific tasks so employees become proficient through repetition.
- Staff authority
- Advisory authority given to specialists to support line managers; it does not carry direct command over subordinates.
Practice Questions
-
Define organising and distinguish between organising as a process and as a structure. / संगठन को परिभाषित कीजिए और प्रक्रिया के रूप में तथा संरचना के रूप में संगठन में अंतर कीजिए।
Show answer
Organising is dividing work, grouping it into departments and assigning authority/responsibility to achieve goals; as a process it is the ongoing managerial activity, while as a structure it is the formal pattern of relationships that results. / संगठन कार्य का विभाजन, विभागों में समूहन और लक्ष्य प्राप्ति हेतु अधिकार/उत्तरदायित्व सौंपना है; प्रक्रिया के रूप में यह निरंतर प्रबंधकीय गतिविधि है, जबकि संरचना के रूप में यह परिणामस्वरूप बने संबंधों का औपचारिक स्वरूप है।
-
Explain the principle of 'unity of command' with an example. / 'आदेश की एकता' सिद्धांत को एक उदाहरण सहित समझाइए।
Show answer
Unity of command means each subordinate should receive orders from and report to only one superior to avoid confusion; e.g., in the army each soldier reports to one commanding officer. / आदेश की एकता का अर्थ है प्रत्येक अधीनस्थ को केवल एक वरिष्ठ से आदेश मिलें और उसी को रिपोर्ट करे ताकि भ्रम न हो; जैसे सेना में प्रत्येक सैनिक एक ही कमांडिंग अधिकारी को रिपोर्ट करता है।
-
Differentiate between functional and divisional organisational structures. / कार्यात्मक और प्रभागीय संगठनात्मक संरचनाओं में अंतर कीजिए।
Show answer
In a functional structure jobs are grouped by function (production, finance, marketing) suiting single-product firms, while in a divisional structure units are formed by product, region or customer suiting diversified firms with greater accountability but resource duplication. / कार्यात्मक संरचना में कार्य कार्यों (उत्पादन, वित्त, विपणन) के अनुसार समूहित होते हैं जो एकल-उत्पाद फर्मों के अनुकूल है, जबकि प्रभागीय संरचना में इकाइयाँ उत्पाद, क्षेत्र या ग्राहक के अनुसार बनती हैं जो विविधीकृत फर्मों हेतु अधिक जवाबदेही पर संसाधन दोहराव सहित उपयुक्त है।
-
What are the three elements of delegation, and which one cannot be delegated? / प्रत्यायोजन के तीन तत्व कौन से हैं, और किसका प्रत्यायोजन नहीं किया जा सकता?
Show answer
The three elements are authority, responsibility and accountability; accountability cannot be delegated as it flows upward and remains with the delegator. / तीन तत्व हैं अधिकार, उत्तरदायित्व और जवाबदेही; जवाबदेही का प्रत्यायोजन नहीं किया जा सकता क्योंकि यह ऊपर की ओर प्रवाहित होती है और प्रत्यायोजक के पास ही रहती है।
-
Distinguish between delegation and decentralisation. / प्रत्यायोजन और विकेंद्रीकरण में अंतर कीजिए।
Show answer
Delegation is a one-to-one transfer of authority from a superior to a subordinate, whereas decentralisation is the systematic, organisation-wide dispersal of decision-making authority to lower levels; delegation is a building block of decentralisation. / प्रत्यायोजन एक वरिष्ठ से अधीनस्थ को अधिकार का एक-से-एक हस्तांतरण है, जबकि विकेंद्रीकरण निर्णयन अधिकार का संपूर्ण संगठन में निचले स्तरों तक व्यवस्थित प्रसार है; प्रत्यायोजन विकेंद्रीकरण की आधारशिला है।
-
If 120 employees are supervised by 6 managers, find the average span of control. / यदि 120 कर्मचारियों का पर्यवेक्षण 6 प्रबंधक करते हैं, तो औसत नियंत्रण अवधि (span of control) ज्ञात कीजिए।
Show answer
Average span of control = Total subordinates / Number of managers = 120 / 6 = 20 subordinates per manager. / औसत नियंत्रण अवधि = कुल अधीनस्थ / प्रबंधकों की संख्या = 120 / 6 = 20 अधीनस्थ प्रति प्रबंधक।
-
Why does a narrow span of control lead to a tall organisational structure? / संकीर्ण नियंत्रण अवधि लंबी (tall) संगठनात्मक संरचना की ओर क्यों ले जाती है?
Show answer
A narrow span means each manager supervises few subordinates, so more managers and more hierarchical levels are needed to cover the workforce, producing a tall structure. / संकीर्ण अवधि का अर्थ है प्रत्येक प्रबंधक कम अधीनस्थों का पर्यवेक्षण करता है, अतः समस्त कार्यबल को संभालने हेतु अधिक प्रबंधक और अधिक पदानुक्रमिक स्तर आवश्यक होते हैं, जिससे लंबी संरचना बनती है।
-
State any two advantages and one limitation of a matrix organisational structure. / मैट्रिक्स संगठनात्मक संरचना के कोई दो लाभ और एक सीमा बताइए।
Show answer
Advantages: efficient use of specialists and flexibility for projects; limitation: dual authority/reporting can create confusion and conflict. / लाभ: विशेषज्ञों का कुशल उपयोग और परियोजनाओं हेतु लचीलापन; सीमा: दोहरा अधिकार/रिपोर्टिंग भ्रम और संघर्ष उत्पन्न कर सकता है।
Related Laws & Principles
Explore allFoundational laws & principles connected to this chapter — tap to open in the Laws Explorer.