Organizing and Organizational Design

Introduction

Organizing is the management process through which work is divided, coordinated, and integrated so that organizational goals can be achieved. Planning establishes what an organization intends to accomplish; organizing determines how people, resources, authority, and activities will be arranged to accomplish it. Organizing therefore converts strategy into an operating system.

For human resource managers, organizing is especially important because organizational design shapes jobs, reporting relationships, workforce requirements, career paths, communication, accountability, and employee experience. A poorly designed structure may create duplicated work, delayed decisions, conflict, excessive supervision, or unclear responsibility. A well-designed structure helps employees understand their roles while preserving the flexibility needed to respond to customers, technology, and changing markets.

Organizational design is not merely the production of an organization chart. It involves choices about division of work, departmentalization, authority, delegation, span of control, centralization, formalization, coordination, and adaptation. These choices should be consistent with organizational strategy, size, technology, environment, and culture.

Learning Objectives

By the end of this chapter, you should be able to:

1. Explain the meaning and purpose of organizing and organizational design.
2. Evaluate division of work and the main forms of departmentalization.
3. Distinguish authority, responsibility, accountability, delegation, and power.
4. Assess span of control, centralization, decentralization, and formalization.
5. Compare functional, divisional, matrix, team, network, project, and agile structures.
6. Apply organizational-design principles to practical human resource and management problems.
7. Identify ethical, technological, and contemporary issues in organizational design.

1. The Foundations of Organizing

Organizing as a management function

Organizing involves five connected activities:

• identifying the work required to achieve objectives;
• dividing work into jobs and tasks;
• grouping jobs into departments or units;
• allocating authority and resources; and
• establishing mechanisms for coordination and control.

A structure is the relatively stable pattern of roles, relationships, and reporting arrangements through which work is performed. Design is the process of creating or changing that structure. Structure is therefore an outcome; design is the managerial process that produces or modifies it.

Division of work

Division of work means breaking a large body of work into distinct tasks and assigning those tasks to individuals or groups. Specialization can improve efficiency because employees develop expertise, training can be focused, and repetition may reduce completion time. For example, a hospital may separate diagnosis, nursing, pharmacy, laboratory testing, billing, and patient scheduling.

However, excessive specialization can produce boredom, narrow skills, weak understanding of the whole process, and poor cooperation between units. Employees may optimize their own tasks while harming the overall customer experience. Modern organizations therefore balance specialization with job rotation, multiskilling, enrichment, cross-functional teams, and opportunities to understand the complete workflow.

A useful design question is not simply “Who performs this task?” but “What combination of tasks, skills, technology, and decision authority produces value for the customer?” This process perspective reduces the risk that departmental boundaries will dominate organizational purpose.

Coordination and integration

Division of work creates the need for coordination. Coordination aligns the activities of specialized individuals and units so that their combined efforts produce a coherent result. Common coordination mechanisms include:

• direct supervision;
• standardized procedures and rules;
• standardized skills through training and professional qualifications;
• standardized outputs such as service levels or performance targets;
• mutual adjustment through communication and collaboration; and
• integrator roles, committees, project managers, and liaison officers.

Coordination may be vertical, through authority and reporting relationships, or horizontal, through collaboration across departments. Stable, routine work often benefits from rules and standard procedures. Innovative and uncertain work generally requires more lateral communication and mutual adjustment.

2. Departmentalization

Departmentalization is the grouping of jobs into departments or organizational units. The basis selected affects expertise, communication, accountability, and responsiveness.

Functional departmentalization

In a functional structure, employees are grouped according to specialized activities such as marketing, finance, operations, information technology, and human resources. This arrangement promotes professional expertise, economies of scale, and consistent technical standards.

Its limitations include departmental silos, slower cross-functional decisions, and difficulty assigning responsibility for products or customer segments. Functional structures are often suitable for smaller or moderately diversified organizations with relatively stable operations.

Product or service departmentalization

Employees are grouped around products or services. Each product division may contain its own marketing, operations, finance, and support capabilities. This structure creates clear product accountability and supports responsiveness to different markets. It may, however, duplicate specialist resources and increase costs.

Geographic departmentalization

Activities are grouped by region, country, or territory. Geographic structures help organizations adapt to local regulations, cultures, labor markets, and customer preferences. Their risks include duplication, inconsistent practices, and difficulty maintaining organization-wide standards.

Customer departmentalization

Units are formed around customer groups, such as retail customers, corporate clients, government agencies, or students. This arrangement encourages customer knowledge and service customization. It can create competing priorities when the same products, systems, or specialists serve several customer groups.

Process departmentalization

Jobs are grouped according to stages in a workflow, such as purchasing, production, quality inspection, distribution, and after-sales service. Process structures can improve efficiency and clarify handoffs, but they require strong coordination to prevent delays at interfaces.

Hybrid departmentalization

Many organizations combine several bases. For example, a global company may use product divisions, regional offices, and centralized finance and human resources. Hybrid designs can reflect complex strategy, but they must clearly specify decision rights to avoid confusion.

3. Authority, Responsibility, Accountability, and Power

Authority

Authority is the formal right to make decisions, direct work, allocate resources, and require compliance within a defined area. Authority normally flows through the hierarchy. A manager’s authority should be sufficient to meet the responsibilities assigned to that manager.

Responsibility

Responsibility is the obligation to perform assigned duties. A supervisor may be responsible for staffing a unit, while a payroll specialist may be responsible for processing accurate salary payments.

Accountability

Accountability is the obligation to explain results and accept the consequences of performance. Responsibility can be assigned, but accountability must be clearly located. If several managers share a task, the organization should specify who is ultimately accountable for the result.

Power

Power is the capacity to influence behavior or decisions. Formal authority is one source of power, but others include expertise, control over information, reputation, access to resources, and relationships. A technically expert employee may have substantial informal influence even without a senior title.

Ethical management requires that power be used lawfully and fairly. Human resource professionals should be alert to coercion, favoritism, retaliation, discrimination, and abuse of confidential information.

Unity of command and scalar relationships

The traditional principle of unity of command states that an employee should normally receive instructions from one immediate supervisor. This can reduce conflicting orders. Matrix, project, and agile structures intentionally modify this principle by giving employees multiple forms of accountability. Where dual reporting exists, decision rights, priorities, evaluation processes, and conflict-resolution mechanisms must be explicit.

The scalar principle emphasizes a clear chain of authority from the highest level to the lowest. Contemporary organizations retain formal accountability but often supplement hierarchy with networks, communities of practice, and lateral coordination.

4. Delegation and Empowerment

Delegation is the assignment of authority and responsibility for a task to another person while the delegator retains ultimate accountability for the area. Effective delegation is not abandonment. It requires selecting an appropriate task, defining expected results, granting sufficient authority, agreeing on controls, and providing support.

A practical delegation process includes:

1. Define the outcome, scope, quality standards, and deadline.
2. Select a person with suitable competence or development potential.
3. Grant the authority and resources needed to act.
4. Agree on checkpoints and reporting arrangements.
5. Provide coaching without unnecessary interference.
6. Review results and recognize learning and achievement.

Delegation improves decision speed, develops employee capability, and allows managers to focus on higher-value work. Common failures include delegating tasks without authority, retaining every important decision, giving unclear instructions, or criticizing reasonable initiative after the fact.

Empowerment goes beyond one delegated task. It refers to enabling employees to exercise meaningful discretion, access information, develop competence, and influence work that affects them. Empowerment is credible only when employees have both discretion and the resources needed to use it.

5. Span of Control

Span of control is the number of individuals who report directly to a manager. A narrow span produces more hierarchical levels; a wide span produces fewer levels and greater managerial breadth.

There is no universally correct span. The appropriate range depends on task complexity, employee competence, geographic dispersion, similarity of work, technology, managerial capability, and the amount of coordination required.

A relatively wide span may be appropriate when employees are experienced, tasks are standardized, work is geographically concentrated, and information systems support visibility. A narrower span may be necessary when work is novel, employees require coaching, risks are high, or tasks are interdependent.

A wide span can reduce administrative cost and encourage employee autonomy, but managers may become overloaded. A narrow span can support close supervision and development, but may increase bureaucracy, delay decisions, and encourage micromanagement. The relevant question is whether the manager can provide adequate direction, support, feedback, and control—not whether a particular numerical ratio has been reached.

6. Centralization, Decentralization, and Formalization

Centralization and decentralization

Centralization is the concentration of decision authority at higher organizational levels. Decentralization distributes decision authority to lower levels, teams, or local units.

Centralization can promote consistency, control, economies of scale, and compliance with organization-wide standards. It can also slow decisions and reduce local responsiveness. Decentralization may increase speed, ownership, innovation, and adaptation, but it can create duplication, inconsistent decisions, and difficulty maintaining common standards.

Most organizations are neither completely centralized nor completely decentralized. Decision rights can be differentiated. For example, an organization may centralize cybersecurity standards and payroll systems while decentralizing customer-service decisions and local scheduling.

Formalization

Formalization is the extent to which roles, procedures, decisions, and behavior are governed by written rules and standardized expectations. Formalization supports consistency, training, legal compliance, quality assurance, and fairness. It can also restrict initiative, slow responses, and create a ritualistic “rule-following” culture.

Formalization should be proportionate to risk and variability. Safety-critical, regulated, and highly repeatable activities generally require stronger documentation and controls. Creative and rapidly changing work requires standards for outcomes and ethics but may need flexibility in methods.

7. Major Organizational Structures

Functional structure

The functional structure groups specialists under functional managers. It is efficient where activities are relatively predictable and the organization has a limited range of products or markets. HR implications include functional career ladders, specialized training, and the need for cross-functional development.

Divisional structure

A divisional structure groups activities by product, geography, customer, or strategic business unit. Divisions operate with substantial autonomy and are often evaluated on their own results. This arrangement improves market responsiveness and accountability but may duplicate HR, finance, technology, and procurement activities.

Matrix structure

A matrix combines two bases of grouping, commonly function and product or project. An employee may report to a functional manager for professional standards and to a project manager for deliverables. Matrix designs support resource sharing and cross-functional integration, but they can produce role conflict, competing priorities, and ambiguity about performance evaluation.

A sound matrix requires:

• explicit decision rights;
• agreed priority rules;
• transparent resource allocation;
• joint performance evaluation;
• conflict-resolution procedures; and
• managerial capability in collaboration.

Team-based structure

A team-based structure organizes much of the work around permanent or temporary teams. Teams may be cross-functional, self-managing, or both. Such structures support problem solving, knowledge sharing, and employee involvement. They require clear team purposes, role clarity, psychological safety, and methods for resolving free-riding or interpersonal conflict.

Project structure

A project structure organizes work around temporary initiatives with defined objectives, schedules, budgets, and deliverables. It is suitable for construction, consulting, software implementation, research, events, and organizational change. Project structures require disciplined scope management and decisions about what happens to employees when a project ends.

Network structure

A network organization retains a relatively small core while coordinating external suppliers, contractors, platforms, alliances, or specialist partners. It can provide flexibility and access to capabilities without owning every activity. Risks include dependence on partners, loss of internal knowledge, data-security exposure, weak employment protections, and difficulty enforcing quality or ethical standards throughout the network.

Agile structure

Agile structures organize work into short cycles of planning, delivery, review, and adaptation. Cross-functional teams prioritize customer value and respond to changing requirements. Agile is not simply a set of meetings or software tools; it involves delegated decision-making, rapid feedback, transparency, and continuous improvement.

Agile structures are useful when requirements are uncertain and experimentation is valuable. They are less appropriate when work is highly predictable, tightly regulated, or dependent on long-term sequential engineering. Even agile organizations need governance, role clarity, risk controls, and strategic alignment.

8. Contingency Perspectives on Organizational Design

Contingency theory argues that no single structure is best in all situations. Effective design depends on the fit between structure and context. Important contextual variables include:

• Strategy: A low-cost strategy may emphasize standardization and efficiency, whereas an innovation strategy may require flexibility and cross-functional collaboration.
• Size: Larger organizations generally need more specialization, formalization, and coordination mechanisms.
• Technology: Routine technologies may support standard procedures; complex technologies may require expert teams and mutual adjustment.
• Environment: Stable environments permit more formal planning. Uncertain environments require decentralization, information sharing, and adaptive structures.
• Culture: A culture emphasizing hierarchy may support centralized decisions; a culture emphasizing participation may support teams and empowerment.
• Workforce capability: Skilled employees can often operate with broader discretion and less direct supervision.

Burns and Stalker’s distinction between mechanistic and organic systems is useful here. Mechanistic systems rely on hierarchy, specialization, formal rules, and centralized control. Organic systems emphasize flexible roles, lateral communication, participation, and adaptation. Neither is universally superior. The design should fit the work and the environment.

9. Human Resource Implications

Organizational design directly affects human resource practice. Before recruiting, HR professionals should understand how work is structured and which capabilities are genuinely required. A redesign may change job descriptions, reporting relationships, grade structures, workforce numbers, performance measures, and learning needs.

Key HR implications include:

• Workforce planning: New structures may require different numbers and types of employees.
• Job analysis: Roles must reflect actual responsibilities and decision authority.
• Recruitment and selection: Agile and team-based structures may require collaboration, learning agility, and influence skills in addition to technical competence.
• Performance management: Measures should reflect shared outcomes where work is interdependent.
• Rewards: Individual incentives can undermine teamwork if they encourage competition for shared resources.
• Learning and development: Employees may need project management, cross-functional, digital, and conflict-management capabilities.
• Employee relations: Restructuring can affect consultation, job security, workload, and perceived fairness.
• Inclusion: Informal networks and discretionary assignments should not create hidden barriers to advancement.

HR should also examine whether a proposed structure creates excessive workloads, unclear accountability, unequal access to information, or discriminatory effects on particular groups.

10. Technology, Data, and Artificial Intelligence

Digital systems increasingly influence organizational design. Collaboration platforms enable geographically dispersed teams; enterprise systems provide shared information; analytics can reveal workflow delays and excessive managerial layers. Automation may remove routine tasks while increasing the importance of judgment, creativity, relationship management, and system oversight.

Artificial intelligence can support workforce planning, skill identification, scheduling, recruitment administration, and organizational-network analysis. However, AI-based recommendations should not be treated as neutral or infallible. Historical data may reproduce discrimination, algorithms may obscure reasoning, and monitoring systems may invade privacy or reduce trust.

Responsible use requires a clear purpose, data minimization, transparency, human review, security, auditability, and compliance with applicable employment and data-protection law. Technology should support sound design rather than become a substitute for consultation and managerial judgment.

11. Applied Case: Redesigning CareConnect Services

The following is an illustrative case.

Background

CareConnect is a medium-sized organization providing home-care services in three regions. It originally used a functional structure: scheduling, nursing supervision, finance, recruitment, and customer support each operated as separate departments. The organization grew rapidly, but service complaints increased.

Problem

Clients often had to repeat information to different departments. Schedulers optimized staff utilization, while regional supervisors prioritized continuity of care. Neither group had complete authority over client assignments. Recruitment was centralized and slow, even when regional labor markets differed. Employees reported conflicting instructions and limited opportunities to solve client problems.

Analysis

The structure had produced specialization but weak horizontal coordination. Centralized recruitment promoted consistency but reduced local responsiveness. Performance measures were functional rather than client-centered. The effective span of control for regional supervisors was also too wide because they managed staff, scheduling exceptions, quality issues, and client escalations simultaneously.

Approach and solution

CareConnect created regional, cross-functional service teams containing a care coordinator, scheduling specialist, and clinical supervisor. A central HR unit retained responsibility for employment standards, legal compliance, payroll, and common training. Regional teams received authority to resolve routine client issues within defined limits. A shared information system gave authorized staff a common view of schedules, client preferences, incidents, and service capacity.

The organization introduced a clear decision-rights matrix. Regional teams could adjust routine assignments; clinical decisions remained with qualified clinical staff; employment policies remained centralized. Performance measures combined service continuity, client satisfaction, safety, employee workload, and cost.

Outcome

After implementation, handoffs became clearer and regional decisions were faster. Some role conflicts initially emerged because managers were accustomed to functional control. CareConnect addressed this through team charters, manager coaching, joint performance reviews, and regular review of workload data.

Learning points

The case demonstrates that redesign should begin with the work and customer problem, not with an organizational chart. It also shows that decentralization does not require abandoning common standards. Centralized governance and local discretion can coexist when decision rights, information access, and accountability are explicit.

12. Designing and Evaluating a Structure

A practical design process can be organized into the following stages:

1. Clarify strategy and outcomes. Identify the customers, value proposition, risks, and results the organization must achieve.
2. Map core processes. Trace work from customer need to delivered outcome and identify delays, duplication, and handoffs.
3. Identify capabilities. Determine the knowledge, technology, roles, and resources required.
4. Choose grouping principles. Decide whether functions, products, regions, customers, processes, projects, or teams should be primary.
5. Allocate decision rights. Specify who recommends, decides, executes, reviews, and is accountable.
6. Set coordination mechanisms. Establish meetings, systems, standards, liaison roles, and escalation routes.
7. Align HR systems. Update jobs, skills, recruitment, rewards, learning, performance management, and employee consultation.
8. Pilot and evaluate. Test the design, gather evidence, and revise it rather than assuming the first arrangement is final.

Useful evaluation questions include:

• Are customers receiving value more reliably?
• Do employees understand their responsibilities and authority?
• Are decisions made at the right level?
• Are coordination costs acceptable?
• Does the structure support inclusion, safety, and ethical conduct?
• Are performance measures encouraging the desired behavior?
• Can the structure adapt as strategy or technology changes?

Challenges and Limitations

Organizational design involves trade-offs. More specialization may improve efficiency but reduce flexibility. More decentralization may improve responsiveness but weaken consistency. More formalization may support fairness and quality but inhibit initiative. Teams may increase collaboration but also create meeting overload and social conflict.

Structures can also become symbolic. An organization may adopt the language of agility while retaining centralized approvals, or establish teams without granting them authority. Redesign may fail when leaders ignore informal power, organizational culture, employee concerns, or the practical systems needed to support new roles.

Change also produces emotional and political effects. Employees may fear loss of status, role redundancy, relocation, or reduced career opportunities. Ethical redesign requires honest communication, meaningful consultation, nondiscriminatory selection processes, appropriate support, and respect for legal rights.

Best-Practice Principles

Effective organizational design generally follows these principles:

• Begin with strategy, customer value, and work processes.
• Keep accountability clear even when collaboration is broad.
• Match authority with responsibility.
• Decentralize decisions when local knowledge and speed matter.
• Centralize standards when consistency, safety, or legal compliance matters.
• Use formalization to manage risk, not to control every minor action.
• Design coordination deliberately; do not assume it will occur naturally.
• Align structure with jobs, skills, rewards, technology, and culture.
• Evaluate both performance outcomes and employee experience.
• Treat organizational design as a continuing process rather than a one-time charting exercise.

Chapter Summary

Organizing converts plans into coordinated action by dividing work, grouping activities, allocating authority, and establishing mechanisms for integration. Division of work can create expertise and efficiency, but excessive specialization may produce silos and narrow roles. Departmentalization may be functional, product-based, geographic, customer-based, process-based, or hybrid, and each basis involves benefits and risks.

Authority is the formal right to make decisions, responsibility is the obligation to perform duties, and accountability is the obligation to explain results. Delegation assigns authority and responsibility while retaining ultimate accountability. Span of control concerns the number of direct reports and should reflect task complexity, employee capability, technology, and coordination needs.

Centralization concentrates decisions, whereas decentralization distributes them. Formalization specifies the extent to which rules and procedures govern work. Functional, divisional, matrix, team, project, network, and agile structures differ in their approaches to specialization, coordination, authority, and adaptability. Contingency theory emphasizes that effective structure depends on strategy, size, technology, environment, culture, and workforce capability.

For HR professionals, organizational design affects workforce planning, job analysis, selection, development, performance management, rewards, employee relations, inclusion, and ethical governance. Good design aligns structure with work, decision rights, people systems, technology, and organizational purpose.

Key Terms

Organizing: Arranging work, people, authority, and resources to achieve organizational objectives.

Organizational design: The process of creating or changing an organizational structure.

Organizational structure: The pattern of roles, relationships, reporting lines, and coordination mechanisms.

Division of work: Breaking work into distinct tasks or responsibilities.

Departmentalization: Grouping jobs into organizational units.

Authority: The formal right to make decisions and direct work.

Responsibility: The obligation to perform assigned duties.

Accountability: The obligation to explain results and accept consequences.

Power: The capacity to influence behavior or decisions.

Delegation: Assigning authority and responsibility while retaining ultimate accountability.

Empowerment: Enabling employees to exercise discretion, access information, and influence work.

Span of control: The number of employees reporting directly to a manager.

Centralization: Concentration of decision authority at higher levels.

Decentralization: Distribution of decision authority to lower levels or local units.

Formalization: The extent to which work is governed by written rules and standardized procedures.

Functional structure: A structure grouping employees by specialized function.

Divisional structure: A structure grouping activities by product, region, customer, or business unit.

Matrix structure: A structure combining two bases of authority, often function and project.

Agile structure: A flexible arrangement using cross-functional teams, short work cycles, feedback, and adaptation.

Contingency theory: The view that effective organizational design depends on contextual conditions.

Review Questions

Short Answer Questions

1. What is organizational design, and how does it differ from organizational structure?
2. State two advantages and two disadvantages of division of work.
3. Distinguish authority, responsibility, and accountability.
4. What factors influence an appropriate span of control?
5. Define formalization and explain one possible benefit and one possible limitation.

Long Answer Questions

1. Compare functional, divisional, and matrix structures. In what circumstances might each be appropriate?
2. Explain the relationship between centralization, decentralization, and organizational responsiveness.
3. Discuss the delegation process and explain why delegation does not eliminate managerial accountability.
4. Evaluate the advantages and risks of team-based, project, network, and agile structures.
5. Explain how organizational design affects human resource planning and performance management.

Analytical / Application Questions

1. A rapidly growing technology company has functional departments, slow product decisions, and frequent conflict between engineering and marketing. Diagnose the structural problems and recommend a redesigned arrangement.
2. A hospital wants to decentralize scheduling decisions to local units while maintaining patient-safety standards. Which decisions should be decentralized, which should remain centralized, and what coordination mechanisms are needed?
3. An organization introduces a matrix structure but employees receive conflicting priorities from two managers. Analyze the causes and propose governance, accountability, and HR practices to address the problem.

Multiple Choice Questions with Answers

Question 1

Which statement best describes organizational design?

A. The process of creating or changing roles, relationships, authority, and coordination arrangements

B. The preparation of an annual financial budget

C. The measurement of individual employee satisfaction only

D. The process of selecting a brand name

Correct Answer: A. The process of creating or changing roles, relationships, authority, and coordination arrangements

Question 2

What is a major advantage of functional departmentalization?

A. It eliminates all coordination requirements

B. It promotes specialized expertise and economies of scale

C. It guarantees rapid local decision-making

D. It prevents departments from developing distinct priorities

Correct Answer: B. It promotes specialized expertise and economies of scale

Question 3

Which term refers to the obligation to explain results and accept consequences?

A. Authority

B. Responsibility

C. Accountability

D. Delegation

Correct Answer: C. Accountability

Question 4

A manager assigns an employee authority to complete a task but remains ultimately answerable for the area. This is an example of:

A. Departmentalization

B. Delegation

C. Formalization

D. Centralization

Correct Answer: B. Delegation

Question 5

Which condition generally supports a wider span of control?

A. Highly novel work requiring intensive coaching

B. Inexperienced employees performing complex tasks

C. Standardized work performed by capable employees

D. Severe geographic dispersion without communication systems

Correct Answer: C. Standardized work performed by capable employees

Question 6

What is a common risk of excessive centralization?

A. Inconsistent organization-wide standards

B. Slower decisions and reduced local responsiveness

C. Complete loss of formal accountability

D. Elimination of senior management

Correct Answer: B. Slower decisions and reduced local responsiveness

Question 7

Which structure commonly gives an employee both a functional manager and a project manager?

A. Functional structure

B. Divisional structure

C. Matrix structure

D. Network structure

Correct Answer: C. Matrix structure

Question 8

Which statement best characterizes formalization?

A. The distribution of work across geographic regions

B. The extent to which rules and procedures govern work

C. The number of employees reporting to a manager

D. The informal influence of technical experts

Correct Answer: B. The extent to which rules and procedures govern work

Question 9

An organization keeps cybersecurity standards centralized but allows regional teams to resolve routine customer issues. This illustrates:

A. Uniform total centralization

B. Differentiated decision rights combining centralization and decentralization

C. The elimination of accountability

D. Pure functional departmentalization

Correct Answer: B. Differentiated decision rights combining centralization and decentralization

Question 10

Agile structures are most useful when:

A. Requirements are uncertain and rapid feedback is valuable

B. Every task must follow an unchanging sequence

C. Employees must have no discretion

D. The environment is entirely stable and predictable

Correct Answer: A. Requirements are uncertain and rapid feedback is valuable