Organizational Structure & Design Detailed & Easy-To-Understand Reviewer

1. Organizational Structure & Design

Core idea: Organizational structure and design explain how an organization divides work, coordinates people, and distributes authority.

Why it matters: Organizational design affects employee behavior, communication, and performance—not just administrative arrangements.

2. Learning Objectives

You should be able to: Define organization and organizational design; explain basic elements of organizational structure; differentiate horizontal and vertical differentiation; identify Mintzberg's five organizational components; compare line and staff functions and tall and flat structures; and apply structure concepts to a workplace case.

Central question: How does organizational design shape employee behavior, communication, and performance?

3. Thinking About Structural Problems

Example: A new employee receives instructions from three people, is unsure who approves work, experiences slow responses from other departments, and sees deadlines missed.

Possible structural issues: Role ambiguity, unclear authority, poor communication channels, weak coordination, and too many reporting lines.

Key lesson: A workplace problem that looks like a people problem may actually be a design problem. Structure can create confusion even when individual employees are capable.

4. Nature of an Organization

Organization: An organization is more than a group of people. It involves people working together toward a purpose, with structure and continuity.

People: Individuals working together.

Purpose: A shared mission or goal.

Structure: Defined roles, rules, and procedures

Continuity: Stability over time despite changes in members.

Examples: University, hospital, pharmacy, B.P.O company, government agency, and nonprofit organization.

5. Organizational Design

Definition: Organizational design is the process of arranging people, tasks, authority, and communication.

what?: What work must be done?

who?: Who is responsible?

who Decides?: Where is authority located?

how?: How do people coordinate?

Key principle: Good design reduces confusion and makes coordination easier.

6. Organizational Goals

Mission: The broad purpose of the organization. Example: provide accessible, quality healthcare.

Output: Specific product or service targets. Example: serve 500 patients daily.

Societal: Contribution to the community. Example: improve public health outcomes.

Operational: Internal efficiency and process goals. Example: reduce waiting time by 20%.

Important connection: Operational goals support larger goals. If day-to-day processes are poorly managed, achieving the organization's mission becomes harder.

7. Why Organizational Structure Matters

Role clarity: Who does what?

Coordination: How do units work together?

Communication: Where does information flow?

Authority: Who makes decisions?

Accountability: Who is responsible for outcomes?

Employee experience: Structure can affect autonomy, stress, support, motivation, and performance.

I/O perspective: Structure shapes behavior, motivation, stress, communication, and performance.

8. Elements of Organizational Structure

Division of labor: Who does what? Work is divided among jobs, roles, and specialized activities.

Authority: Who decides? Authority determines who has decision-making responsibility.

Communication: Who talks to whom? Communication connects people and units.

Overall result: Division of labor, authority, and communication work together to produce coordinated work.

9. The Organizational Pyramid

Senior leaders: Provide strategic direction and make major decisions.

Managers: Translate strategy into departmental plans.

Supervisors: Coordinate day-to-day work.

Frontline / operating core: Deliver products or services.

Why fewer people at the top?: Organizations typically have fewer positions with broad strategic responsibility and more positions involved in direct operations at the base.

10. How to Read an Organizational Chart

Purpose: Formal charts show reporting relationships, roles, and departments.

Boxes: Represent positions or departments.

Lines: Represent formal reporting relationships.

Levels: Represent hierarchy.

Important limitation: Charts do not show everything. They may not reveal friendships, informal influence, politics, or actual communication patterns.

11. Formal versus Informal Structure

Formal structure: Official roles, job titles, reporting lines, policies and procedures, and official communication channels.

Informal structure: Friendships, trust networks, informal leaders, workarounds, and actual information flow.

Key distinction: The formal structure shows how work is officially supposed to happen; the informal structure shows how work may actually happen.

12. Mintzberg's Five Organizational Components

Overview: Henry Mintzberg developed a model that maps important internal components of an organization.

1. Strategic Apex: Ensures the organization follows its mission and manages relationships with the environment. Examples: C.E.O, President, Board, University President.

2. Middle Line: Translates broad plans into operational activities workers can carry out. Examples: managers, deans, department heads, supervisors.

3. Operating Core: People who perform the basic work of producing products or delivering services. Examples: faculty, nurses, pharmacists, production workers.

4. Technostructure: People who design standards, systems, quality criteria, and training. Examples: Q.A, H.R training, planners, analysts.

5. Support Staff: Services that support the organization indirectly. Examples: legal, I.T, P.R, administrative services, cafeteria.

13. Mintzberg Applied to a University

Strategic Apex: University President / Board.

Middle Line: Deans / Department Chairs / Program Heads.

Operating Core: Faculty members / academic service providers.

Technostructure: Quality assurance / H.R development / institutional planning.

Support Staff: Legal / I.T / registrar / administrative services.

14. Division of Labor

Definition: Division of labor means tasks and responsibilities are divided among employees or teams.

Why divide work?: It builds expertise, improves efficiency, clarifies responsibility, and allows coordination of complex work.

Example: In a pharmacy, different people may handle dispensing, inventory, counseling, records, and quality checks.

15. Job Specialization

Definition: Job specialization refers to how narrowly or broadly a job is defined.

High specialization: An employee performs a small number of specific tasks repeatedly.

Benefits of high specialization: Efficiency, expertise, easier training, and standardization.

Low specialization: An employee performs broader, more varied responsibilities.

Benefits of low specialization: Variety, autonomy, flexibility, and meaningfulness.

Important trade-off: Specialization can improve performance and efficiency but may reduce motivation when work becomes too repetitive or narrow.

16. Span of Control

Definition: The number of employees directly supervised by one manager.

Narrow span: One manager supervises fewer employees. Often means more supervision, more managerial layers, and closer monitoring.

Wide span: One manager supervises more employees. Often means more autonomy, fewer layers, and greater need for competent employees.

Key trade-off: A wider span can reduce layers and increase autonomy, but managers may have less time for each employee.

17. Horizontal Differentiation

Definition: Grouping similar work together through departmentation.

Functional: People are grouped according to expertise or function. Examples: H.R, Finance, Registrar, Admissions, I.T.

Product/Service: People are grouped according to the service or program offered. Examples: College of Pharmacy, College of Nursing, College of Medicine.

Customer: People are grouped according to the people being served. Example: Students.

18. Functional Departmentation

Definition: People are grouped by area of expertise.

Example: President implies H.R, Finance, Operations, Marketing.

Strength: Deep expertise and efficiency.

Risk: Departmental silos and slow cross-functional coordination.

Silo: A department may focus heavily on its own work and communicate less effectively with other departments.

19. Product and Customer Departmentation

Product-based: Groups are organized around product or service lines. Examples: Customer Service, Technical Support, Sales, Collections, Healthcare Support.

Customer-based: Groups are organized around client/customer segments. Examples: Banking clients, Healthcare clients, Telecommunications clients, E-commerce clients, Government accounts.

Core distinction: Product-based asks what service/product is being handled; customer-based asks which client or customer group is being served.

20. Line and Staff Employees

Line: Directly contributes to core operations and often has operational authority. Examples: production, sales, service delivery.

Staff: Supports or advises core operations and provides specialized expertise. Examples: H.R, legal, finance, I.T.

Easy distinction: Line employees help deliver the core product/service; staff employees support those who deliver it.

21. Vertical Differentiation

Definition: The hierarchy of levels or ranks determines the height of the organization.

Tall organization: Many levels of hierarchy. Example: C.E.O leads to V.P leads to Director leads to Manager leads to Supervisor leads to Employee.

Tall strengths: Clear authority and close supervision.

Tall risks: Slower decisions and more bureaucracy.

Flat organization: Fewer levels of hierarchy. Example: Leader leads to Teams / Employees.

Flat strengths: Faster communication and more autonomy.

Flat risks: Role ambiguity and wider span of control.

22. Centralization versus Decentralization

Centralized: Decision-making authority is concentrated at higher levels.

Centralized strengths: Consistency, control, and standardization.

Centralized limits: Slower decisions and less autonomy.

Decentralized: Decision-making authority is distributed to lower levels.

Decentralized strengths: Faster local action, empowerment, and responsiveness

Decentralized limits: Less consistency and greater need for competent employees.

Emergency application: Centralization may be useful when consistency and tight control are critical; decentralization may be useful when local employees need to respond quickly and have sufficient competence.

23. Authority and Power

Authority: The formal right attached to a position to make decisions and direct others. Example: a department head approves schedules.

Power: The capacity to influence behavior, attitudes, or decisions. Example: a respected senior employee influences team norms.

Key distinction: Authority is formal and position-based; power is broader and can exist without a formal title.

Important: A person can have authority without strong influence, and another person can have influence without formal authority.

24. Communication Channels and Coordination

Vertical communication: Information moves up or down the hierarchy. Examples: instructions, reports, approvals, feedback.

Horizontal communication: Information moves across departments or teams. Examples: coordination, referrals, handoffs, collaboration.

Key problem: Many organizational problems come from poor handoffs between people or departments.

I/O implication: Structure influences how quickly and accurately information reaches the people who need it.

25. Workplace Case: Diagnose the Structure

Case: A growing company has 300 employees. Workers receive instructions from multiple supervisors; decisions take too long; departments rarely communicate; supervisors manage 25 to 30 employees each; and employees do not know who approves requests.

Issue 1: Multiple supervisors leads to authority ambiguity which leads to clarify reporting lines.

Issue 2: Decisions take too long to centralization / hierarchy to delegate selected decisions.

Issue 3: Departments do not communicate to poor coordination to establish cross-functional channels.

Issue 4: Supervisors manage 25 to 30 employees to wide span of control to add team leads or improve systems.

Issue 5: No one knows who approves requests leads to role ambiguity leads to define approval authority.

26. Key Takeaways

1. Structure divides work: Who does what?

2. Structure distributes authority: Who decides?

3. Structure establishes relationships: Who reports to whom?

4. Structure shapes communication: How does information flow?

5. Structure influences behavior: It affects autonomy, stress, motivation, cooperation, and performance.

Overall lesson: Good organizational design is not only about boxes and lines. It creates a system where people can work effectively together.

Master Memory Guide

Organization: People + Purpose + Structure + Continuity.

Organizational design: Arranging people + tasks + authority + communication.

Structure: Division of labor + authority + communication.

Horizontal differentiation: Grouping work across departments: functional, product/service, or customer.

Vertical differentiation: Number of hierarchical levels: tall versus flat.

Centralization: Higher levels make decisions.

Decentralization: Decision-making is distributed to lower levels.

Authority: Formal right to direct and decide.

Power: Ability to influence.

Formal structure: Official roles and reporting relationships.

Informal structure: Actual relationships, influence, and information flow.

Mintzberg: Strategic Apex + Middle Line + Operating Core + Technostructure + Support Staff.

Span of control: Number of employees directly supervised by one manager.

Line versus staff: Line = core operations; Staff = support/advice.

Communication: Vertical = up/down; Horizontal = across teams/departments.

Situational Review

1: Employee receives conflicting instructions from three supervisors to Authority ambiguity / unclear reporting lines.

2: Employees do not know who approves requests leads to Role ambiguity / unclear authority.

3: H.R, Finance, and Operations each work separately and rarely coordinate to Functional silos / poor horizontal coordination.

4: A manager directly supervises 30 employees, which indicates a wide span of control.

5: An organization has C.E.O arrow V.P arrow Director arrow Manager arrow Supervisor arrow Employee arrow Tall structure.

6: A company removes several management levels and gives employees more decision-making freedom to Flat/decentralized direction.

7: A respected employee influences team behavior despite having no management title to Power without formal authority.

8: A department head formally approves schedules implies Authority.

9: Information travels from supervisor to employee and employee to manager leads to Vertical communication.

10: Two departments coordinate a handoff leads to Horizontal communication.

11: An organization groups employees into H.R, Finance, Marketing, and Operations leads to Functional departmentation.

12: An organization groups teams around banking, healthcare, telecom, and government clients to Customer-based departmentation.

13: An organization groups employees by different products/services leads to Product-based departmentation.

14: A company needs people who create standards and quality criteria to Technostructure.

: Nurses, pharmacists, or production workers directly deliver the core service or product, which leads to the Operating Core.

16: Legal, I.T, P.R, and administrative services indirectly support operations leads to Support Staff.

17: Deans and department heads translate university strategy into operational plans leads to Middle Line.

18: The university president/board manages mission and external relationships leads to Strategic Apex.

Final Master Summary

Big picture: Organizational structure answers: Who does what? Who decides? Who reports to whom? How does information move?

Why I/O psychologists care: Structure influences employee autonomy, stress, motivation, cooperation, communication, and performance.

Best mental model: Think of an organization as a system: work must be divided, authority must be assigned, people must communicate, and units must coordinate.

Final principle: Good organizational design reduces confusion and helps people work effectively together.