Unit V — Organizational Systems
33. Organizational Structure
Organizational structure is the formal system of task allocation, reporting relationships, and coordination mechanisms that channels how work gets done. It is built from choices about specialization, centralization, formalization, and span of control, and it must fit the strategy, size, and environment of the firm. A structure that is right for a 200-person single-product company can strangle a 2000-person multi-product company.
- Work specialization: degree tasks are subdivided into separate jobs
- Departmentalization: grouping jobs by function, product, geography, or process
- Chain of command and span of control: who reports to whom and how many
- Centralization vs decentralization: where decision rights sit
- Formalization: extent of rules, SOPs, and job descriptions
- Coordination mechanisms: liaison roles, committees, integrators
- Average span of control (direct reports per manager) tracked in HRIS
- Number of approval layers for a capex request above a threshold
- Ratio of standardized SOPs to ad hoc decisions in audits
- Cross-functional project cycle time as proxy for coordination friction
- Employee survey item on role clarity and decision-authority clarity
Vasantha Auto Components, a Pune-based tier-1 auto parts maker with 850 employees and three product lines (brakes, suspension, electricals) sold to five OEMs, has grown 40 percent in two years through new OEM contracts. Currently organized purely functionally (one manufacturing head, one quality head, one sales head), the company is seeing OEM account managers complain they have no authority to prioritize plant capacity for their client, while functional heads say a product-based split would duplicate scarce quality engineers. The CEO must redesign the structure before a major EV OEM contract goes live next quarter, requiring dedicated program accountability without losing functional depth in quality and process engineering.
Revenue growth (2 years)
40 percent
On-time delivery to OEMs
82 percent (target 95)
Quality engineers (shared pool)
14 across 3 product lines
Average span of control, plant supervisors
1:22
New EV OEM contract value
Rs 180 crore annually
AStay functional, add OEM account coordinators
Retain the functional structure but insert dedicated OEM account coordinators with a dotted-line liaison role to speed cross-functional response.
BMove to product-line divisional structure
Split into three self-contained divisions (brakes, suspension, electricals), each with its own manufacturing, quality, and sales resources reporting to a division head.
CAdopt a matrix structure for the EV program
Keep functional departments but overlay a program manager for the EV OEM contract with real budget and prioritization authority, dual-reporting for assigned staff.
DFully decentralize with autonomous OEM-facing teams
Create independent OEM-facing business units with full P&L and hire-fire authority, functional roles absorbed into each unit.
AStay functional, add OEM account coordinators
Strengths
- Preserves technical depth and economies of scale in quality
- Low disruption and cost to implement
Risks
- Coordinators have no real authority, so the OEM-priority problem persists
- Accountability for OEM delivery remains diffuse
BMove to product-line divisional structure
Strengths
- Clear accountability per product line and faster OEM decisions
- Divisions can specialize to their OEM's specific quality standards
Risks
- Duplicates scarce quality engineering talent across divisions
- Loses functional economies of scale and cross-line best-practice sharing
CAdopt a matrix structure for the EV program
Strengths
- Balances functional depth with program-level accountability
- Scales to future OEM programs without a full reorganization
Risks
- Dual reporting can create authority conflict and role ambiguity
- Requires strong conflict-resolution norms and management maturity
DFully decentralize with autonomous OEM-facing teams
Strengths
- Maximum speed and accountability for each OEM relationship
- Strong ownership incentives for unit heads
Risks
- Very high cost of duplicated overhead for an 850-employee firm
- Risk of inconsistent quality standards across units
Which structural option should Vasantha Auto Components adopt for the new EV OEM program, and how should it manage the resulting coordination costs?
Retain the functional structure but insert dedicated OEM account coordinators with a dotted-line liaison role to speed cross-functional response.
Strengths: Preserves technical depth and economies of scale in quality; Low disruption and cost to implement. Risks: Coordinators have no real authority, so the OEM-priority problem persists; Accountability for OEM delivery remains diffuse.
Split into three self-contained divisions (brakes, suspension, electricals), each with its own manufacturing, quality, and sales resources reporting to a division head.
Strengths: Clear accountability per product line and faster OEM decisions; Divisions can specialize to their OEM's specific quality standards. Risks: Duplicates scarce quality engineering talent across divisions; Loses functional economies of scale and cross-line best-practice sharing.
Keep functional departments but overlay a program manager for the EV OEM contract with real budget and prioritization authority, dual-reporting for assigned staff.
Strengths: Balances functional depth with program-level accountability; Scales to future OEM programs without a full reorganization. Risks: Dual reporting can create authority conflict and role ambiguity; Requires strong conflict-resolution norms and management maturity.
Create independent OEM-facing business units with full P&L and hire-fire authority, functional roles absorbed into each unit.
Strengths: Maximum speed and accountability for each OEM relationship; Strong ownership incentives for unit heads. Risks: Very high cost of duplicated overhead for an 850-employee firm; Risk of inconsistent quality standards across units.
Set the weight of each criterion (1–5), then score every alternative (1–5). The matrix is a thinking aid, not a verdict.
| Criterion | Weight | A | B | C | D |
|---|---|---|---|---|---|
| Behavioural impact | |||||
| Employee acceptance | |||||
| Feasibility | |||||
| Cost (higher = more affordable) | |||||
| Risk containment | |||||
| Long-term sustainability |
With your current weights, alternative A scores highest. A matrix only reflects the weights you chose. Evidence, ethics, feasibility and the people affected still belong in your judgement — you decide.
Use contingency theory of structure (Lawrence and Lorsch) to argue that structure should fit task uncertainty and environmental complexity, and Galbraith's information-processing view to assess whether lateral mechanisms (liaisons, matrix, integrators) suffice versus needing structural differentiation. Weigh specialization versus coordination cost trade-offs explicitly.
- Short term: reassigning quality engineers to program or division roles disrupts ongoing OEM audits for 4-6 weeks
- Short term: role ambiguity in a matrix requires an explicit RACI to avoid manager conflict
- Long term: a durable OEM-program structure enables the firm to win further large contracts without repeated reorganizations
- Long term: divisional duplication, if chosen, raises fixed cost base and requires higher revenue growth to sustain margins
- Long term: unresolved authority ambiguity risks middle-manager attrition within a year
- How does span of control interact with formalization when a firm is scaling rapidly?
- What lateral coordination mechanisms could substitute for a full structural redesign?
- When does specialization stop producing efficiency and start producing coordination cost?
Formalization in organizational structure refers to:
Why do Vasantha's OEM account coordinators (Option A) fail to solve the prioritization problem?
For a single large, time-bound EV program layered on an ongoing multi-OEM functional business, which structure best balances accountability and technical depth?