Organizing
Domain 3 tests how organizations divide work, allocate authority, and coordinate activity. Expect questions on structural types, span of control, delegation, and job design.
Structure and authority
- Work specialization improves efficiency but can cause boredom and silo behavior.
- Departmentalization groups jobs by function, product, geography, customer, or process.
- Chain of command is the unbroken line of authority; unity of command (Fayol) says each employee should report to one boss.
- Span of control is the number of reports per manager. Narrow spans create tall structures with many levels; wide spans create flat structures. Wide spans work when work is routine and employees are capable.
- Centralization concentrates decision authority at the top; decentralization pushes it downward for speed and local responsiveness.
- Formalization is the degree of written rules and procedures.
Authority is the right to give orders; responsibility is the obligation to perform; accountability is answerability for results. Delegation transfers authority, not accountability - the manager remains answerable. Line authority directly commands operating units; staff authority advises and supports.
Structural designs
- Functional: efficient, deep expertise; slow cross-functional coordination.
- Divisional (product, geographic, customer): clear accountability for results; duplicated resources.
- Matrix: dual reporting to functional and project managers; flexible use of expertise, but creates role conflict and violates strict unity of command.
- Team and network structures: horizontal coordination, external partnerships.
Burns and Stalker: mechanistic structures suit stable environments; organic structures suit uncertain, innovative ones.
Job design
Job specialization narrows tasks. Job enlargement adds tasks at the same level; job rotation moves workers among tasks; job enrichment adds vertical responsibility (planning, control). Hackman and Oldham's job characteristics model links skill variety, task identity, task significance, autonomy, and feedback to meaningfulness, responsibility, and knowledge of results, which in turn affect motivation and performance.
Worked example
A software firm faces fast-changing products and heavy cross-functional interdependence. A tall functional structure with narrow spans slows decisions. The fit is a flatter, more organic design with wider spans, decentralized decisions, and project teams or a matrix. But the matrix should be introduced with clear priorities and a conflict-resolution process because dual reporting creates ambiguity.
Traps
Span of control is not the chain of command. A matrix deliberately creates two bosses, so "unity of command always improves performance" is false. Job enrichment is not job enlargement. Decentralization is not inherently better; it depends on environment and risk. Delegation does not transfer accountability.