📘 Lecture 32 — Team Building
📖 Overview: This lecture explores the formal process of team building within organizations, detailing a structured six-step approach from initiation to evaluation. It emphasizes the critical role of the manager in facilitating team development and provides frameworks for determining when team building is appropriate and whether an outside consultant is needed. The lecture also critically examines the actual results and limitations of team building interventions.
🗂️ Topics Covered
This lecture covers the complete team building cycle, beginning with the distinction between family group diagnostic meetings and team-building meetings. It details a six-step process: initiating the meeting, setting objectives, collecting data, planning the meeting, conducting the meeting, and evaluating the process. The manager's role in team building is analyzed, including a checklist for assessing the need for a consultant. The lecture then examines when team building is applicable and appropriate, differentiates between transactional and transformational team management styles, and concludes with a critical review of the research on the results of team building.
📝 Lecture Summary
The team building process recognizes two types of activities:
- Family Group Diagnostic Meetings – aimed at identifying group problems
- Family Group Team-Building Meetings – aimed at improving the team’s functioning.
Most team development training meetings follow a format involving the following steps:
Step 1: Initiating the Team Building Meeting
Step 2: Setting Objectives
Step 3: Collecting Data
Step 4: Planning the Meeting
Step 5: Conducting the Meeting
Step 6: Evaluating the Team Building Process
Step 1: Initiating the Team Building Meeting
The team building meeting may be initiated by a manager higher in the organization structure, who is not a member of the team. Whosoever decided, the decision to proceed is usually collaborative. During the formation stage the members of the team will probably discuss the degree to which they support team building. They will also discuss whether a team is necessary given the specific work situation.
Step 2: Setting Objectives
If a team building meeting is to be effective, there should be general agreement on the objectives before team building proceeds. The practitioner may address some pertinent questions to the work group. These might include: What is the purpose of this meeting? What do the participants and the consultant want to do? Why this group of people at this time? How does this meeting fit into the OD program? What is the priority of this project? Are the team members really interested and committed? What does the team want to accomplish? How will team building be measured or evaluated?
Step 3: Collecting Data
Some information is already gathered before the meeting, particularly during the diagnostic phase. The usefulness of this information depends on the extent to which it can be specifically identified with the team as opposed to the total organization. The members may be given additional questionnaires to fill out, or they may be interviewed. The practitioner may hold mini-group meetings with a few members at a time or with all the members to gather information.
Step 4: Planning the Meeting
The planning session will probably be attended by the practitioner, the manager, and a few of the team members. It is important at this point to restate the goals and objectives as precisely as possible, incorporating information obtained during the preceding steps. If the goals are specific behavioral objectives, the remaining work of planning the sequence of events of the meeting will flow more easily and logically. Going through this process will ensure a meeting that satisfies the needs of the participants. Planning for a team building meeting includes the logistics of the meeting, such as arranging for a time and a place. The planning stage will also ensure that all necessary personnel and resources are available.
Step 5: Conducting the Meeting
The meeting itself usually lasts two or three days. It is arranged at a place away from the work area. Reason being, it helps to put everyone – superior and subordinate – on a more equal level. It also lessens interruption.
On the morning of the 1st day, members are encouraged to share their expectations for the meeting and to develop specific norms that would guide their behaviors during the two-day meeting. This process is aided by an exercise in which the group members share their experiences about the best team they had ever worked on and in that way identified characteristics of effective teams. The norms and characteristics are placed on flipcharts and hung on the wall of the meeting room. All members agree to behave according to the norms and to assess periodically how well the norms were being followed. The consultant agrees to provide feedback on norm compliance during the session.
The meeting begins with a restatement of agreed upon objectives. The data are presented to the entire team, with attention given to problem areas or issues in which the team has expressed an interest, and then the team forms an agenda ranked in order of priority. The team critiques its own performance to prevent dysfunctional actions and improve functional activities. If the members feel that this is an opportunity for them to express open and honest feelings without fear of punishment, the leader of the team may come under attack. The success and failure of team building meeting may depend on how the manager reacts to the situation.
Once the team members have resolved their interpersonal issues, and developed a group understanding, they can move on to the task issues that need to be discussed. The purpose is to develop a specific action plan for improving the ways or processes it uses to reach its organizational goals. The first day ends with several unfinished lists of value statements, core purposes, and thoughts. An evaluation of the day was done. An overall rating and comments about the group were made.
The next day begins by feeding back the data from the evaluation and the important issues that remain to be addressed. The consultant then writes several important points on a flipchart and asks the group to identify the most important agenda items. Quickly they decide that they wanted to finish the core-values work and then discuss their core purpose. The consultant facilitates the conversation that is now under the control of the group members. Within a couple of hours, the group produces a list of core values, develops a process for involving the rest of the organization in creating a final list of values and crafts a core purpose that describes the essence of the organization. Before the meeting ends, the team should make a list of action items to be dealt with, who will be responsible for each item, and a time schedule.
Step 6: Evaluating the Team Building Process
At this meeting, the team examines the action items, exploring those that have been or are being carried out and those that are not working. It determines how well the implemented action items have aided the team’s operation and what else can be done. It reconsiders any action items that are not working and discards those that seem unnecessary. Items that appear to be helpful may now be given additional attention and support. The team will also explore how to resolve ongoing problems and what can be done to enhance continuous improvement.
The Manager’s Role in Team Building
Ultimately, the manager is responsible for group functioning, although this responsibility obviously must be shared by the group itself. Therefore, it is management’s task to develop a work group that can stop regularly to analyze and diagnose its own effectiveness and work process. With the group’s involvement, the manager must diagnose the group’s effectiveness and take appropriate actions if the work unit shows signs of operating difficulty or stress.
Many managers, however, have not been trained to perform the data gathering, diagnosis, planning, and action necessary to maintain and improve their teams continually. Thus, the issue of who should lead a team-building session is a function of managerial capability. The initial use of a consultant usually is advisable if a manager is aware of problems, feels that she or he may be part of the problem, and believes that some positive action is needed to improve the operation of the unit, but is not sure how to go about it.
Dyer has provided a checklist for assessing the need for a consultant (Table 11). Some of the questions ask the manager to examine problems and establish the degree to which she or he feels comfortable in trying out new and different things, the degree of knowledge about team building, whether the boss might be a major source of difficulty, and the openness of group members.
🔑 Definition — Consultant's Role: The consultant works closely with the manager (and members of the unit) to a point at which the manager is capable of engaging in team-development activities as a regular and ongoing part of overall managerial responsibilities. Two key principles guide this relationship: (1) the manager ultimately is responsible for all team-building activities, even though the consultant’s resources are available, and (2) the goal of the consultant’s presence is to help the manager learn to continue team-development processes with minimum consultant help or without the ongoing help of the consultant.
Thus, in the first stages the consultant might be much more active in data gathering, diagnosis, and action planning; particularly in a one- to three-day off-site workshop is considered. In later stages, the consultant takes a much less active role, with the manager becoming more active and serving as both manager and team developer.
Table 11. Assessing the Need for a Consultant — Scoring: if you have circled six or more “yes” responses, you probably do not need an outside consultant. If you have circled four or more “no” responses, you probably do need a consultant. If you have a mixture of “yes”, “no”, and “?” responses, invite a consultant to talk over the situation and make a joint decision.
When Is Team Building Applicable?
Team building is applicable in a large number of situations, from starting a new team, to resolving conflicts among members, to revitalizing a complacent team. Lewis has identified the following conditions as best suited to team building:
- Patterns of communication and interaction are inadequate for good group functioning.
- Group leaders desire an integrated team.
- The group’s task requires interaction among members.
- The team leader will behave differently as the result of team building, and members will respond to the new behavior.
- The benefits outweigh the costs of team building.
- Team building must be congruent with the leader’s personal style and philosophy.
When is Team Building Appropriate?
- To permit members to gain new expertise and experience and to develop and educate members.
- To build and enhance communication and interaction, because teams offer increased levels of participation in decisions.
- To build consensus and commitment on a controversial issue.
- Group leaders desire an integrated team.
- To allow more creative discussions by pulling together people of unusual and different backgrounds and interests.
- Team building must be congruent with the leader’s personal style and philosophy.
Team Management Styles
There are two main styles of team management.
-
A transactional, task oriented approach: Managers view the behavior of team members as an extension of team processes, and they attempt to modify that behavior through punishment and rewards.
-
A transformational, people oriented approach: Managers who apply a transformational approach, developing team members’ knowledge, skills, abilities, and careers, rather than focusing on the processes.
The Results of Team Building
The research on team building has a number of problems. First, it focuses mainly on the feelings and attitudes of group members. Little evidence supports that group performance improves as a result of team-building experiences. One study, for example, found that team building was a smashing success in the eyes of the participants. However, a rigorous field test of the results over time showed no appreciable effects on either the team’s functioning and efficiency or the larger organization’s functioning and efficiency. Second, the positive effects of team building typically are measured over relatively short time periods. Evidence suggests that the positive effects of off-site team building are short-lived, often fading after the group returns to the organization. Third, team building rarely occurs in isolation. Usually it is carried out in conjunction with other interventions leading to or resulting from team building itself. For this reason it is difficult to separate the effects of team building from those of the other interventions.
💡 Why this matters: This critical evaluation is crucial for OD practitioners. It cautions against assuming team building is a universal panacea and highlights the need for rigorous evaluation, follow-up activities, and integration with other organizational changes to ensure lasting impact.
⭐ Key Takeaways
The team building process is a structured, collaborative intervention consisting of six sequential steps: initiation, objective setting, data collection, planning, conducting (typically a 2-3 day off-site meeting), and evaluation. The manager retains ultimate responsibility for team functioning, though a consultant may be necessary, especially when the manager feels part of the problem or lacks expertise; Dyer's checklist helps assess this need. Team building is most applicable when communication is inadequate, the leader desires an integrated team, and the task requires member interaction, but it must be congruent with the leader's philosophy. Critically, while participants often perceive team building as highly successful, research shows that its positive effects on actual performance are often minimal and short-lived, and are difficult to isolate from other interventions.
🧠 Quick Revision Questions
- What is the primary difference between a Family Group Diagnostic Meeting and a Family Group Team-Building Meeting?
- According to Dyer's checklist, what scoring indicates that a manager likely does NOT need an outside consultant for team building?
- Describe the purpose of establishing group norms on the first morning of a team building meeting.
- What are the three main criticisms of team building research discussed in the lecture?
- How do transactional and transformational styles of team management differ in their focus?
📘 Lecture 33 — Organization Process Approaches
📖 Overview: This lecture examines system-wide process interventions—change programs directed at improving organizational problem-solving, leadership, and inter-group coordination across major subsystems or entire organizations. It covers four key approaches: the organization confrontation meeting, inter-group relations interventions, large-group interventions, and Grid Organization Development, providing practical frameworks for mobilizing organizational resources and driving large-scale change.
🗂️ Topics Covered
This lecture begins with the organization confrontation meeting, an early intervention designed to mobilize problem-solving resources by having members identify pressing issues. It then examines inter-group relations interventions, including microcosm groups and inter-group conflict resolution meetings. The third major approach is large-group interventions (such as search conferences and open-space meetings), which bring many stakeholders together simultaneously to address organizational problems. Finally, the lecture covers Grid Organization Development, a normative six-phase packaged program focused on achieving corporate excellence through changing managerial styles and organizational culture.
📝 Lecture Summary
Organization Confrontation Meeting
The confrontation meeting is an intervention designed to mobilize the resources of the entire organization to identify problems, set priorities and action targets, and begin working on identified problems. Originally developed by Beckhard, the intervention can be used at any time but is particularly useful when the organization is in stress and when there is a gap between the top and the rest of the organization (such as when a new top manager joins). General Electric’s “Work-Out” program is a recent example of how the confrontation meeting has been adapted to fit today’s organizations. Although the original model involved only managerial and professional people, it has since been used successfully with technicians, clerical personnel, and assembly workers.
The application stages involve ten steps: scheduling a group meeting of all involved; appointing groups representing all departments (with no subordinate in the same group as their boss, and top management forming its own group); stressing openness and honesty in identifying problems; allowing one to two hours for problem identification; reconvening in a central meeting place for reporting; categorizing problems to eliminate duplication; dividing participants into new problem-solving groups; having each group rank problems, develop tactical action plans, and set timetables; having groups periodically report priorities and plans; and establishing schedules for periodic follow-up meetings to ensure continuing action.
🔑 Definition — Confrontation Meeting: An intervention designed to mobilize the resources of the entire organization to identify problems, set priorities and action targets, and begin working on identified problems.
Inter-group Relations Interventions
The ability to diagnose and understand inter-group relations is important for OD practitioners because groups often must work with and through other groups to accomplish goals; groups within the organization often create problems and place demands on each other; and the quality of relationships between groups can affect the degree of organizational effectiveness. Two OD interventions—microcosm groups and inter-group conflict resolution—are described here. A microcosm group uses members from several groups to help solve organization-wide problems. Inter-group conflict resolution helps two groups work out dysfunctional relationships. Together, these approaches help improve inter-group processes and lead to organizational effectiveness.
💡 Why this matters: The quality of inter-group relationships directly impacts organizational effectiveness, making diagnostic skills in this area essential for OD practitioners.
Microcosm Groups
A microcosm group consists of a small number of individuals who reflect the issue being addressed. For example, a microcosm group composed of members representing a spectrum of ethnic backgrounds, cultures, and races can be created to address diversity issues. This group, assisted by OD practitioners, can create programs and processes targeted at specific problems. In addition to addressing diversity problems, microcosm groups have been used to carry out organization diagnoses, solve communications problems, integrate two cultures, smooth the transition to a new structure, and address dysfunctional political processes.
Microcosm groups work through parallel processes, which are the unconscious changes that take place in individuals when two or more groups interact. After groups interact, members often find that their characteristic patterns of roles and interactions change to reflect the roles and dynamics of the group with whom they were relating. Put simply, groups seem to "infect" and become "infected" by the other groups. The lecture provides an example where a diagnostic team role-played a department head meeting they had never observed—the simulated meeting closely approximated the actual session, demonstrating how parallel processes work.
🔑 Definition — Parallel Processes: The unconscious changes that take place in individuals when two or more groups interact, causing characteristic patterns of roles and interactions to reflect the dynamics of the other group.
The five application stages are: (1) Identify an issue—finding a system-wide problem from an organizational diagnosis or member idea; (2) Convene the group—forming the microcosm group with membership reflecting the appropriate mix of stakeholders, and giving the group status and credibility; (3) Provide group training—training in problem-solving and decision-making, with OD practitioners observing how the group reflects the larger organization's problem; (4) Address the issue—solving the problem and implementing solutions, using a communication plan, visible and accessible members, and appropriate participation levels; (5) Dissolve the group—disbanding after successful implementation.
Large Group Interventions
The third system-wide process intervention is called large-group intervention. Such change programs have been referred to variously as "search conferences," "open-space meetings," "open-systems planning," and "future searches." They focus on issues that affect the whole organization or large segments of it, such as developing new products, responding to environmental change, or introducing new technology. The defining feature of large-group intervention is bringing together large numbers of organization members and other stakeholders, often more than one hundred, for a two- to four-day meeting where attendees work together to identify and resolve organization-wide problems, design new approaches, or propose future directions.
Large-group interventions can vary on several dimensions, including purpose, size, length, structure, and number. The purpose can range from solving particular problems to envisioning future strategic directions. Groups have included less than fifty to more than two thousand participants, lasting between one and five days. Some processes are relatively planned and structured; others are more informal.
Preparing for the Large-Group Meeting: A design team comprising OD practitioners and several organization members addresses three key ingredients: (1) a compelling meeting theme—a powerful reason for change such as managing mergers or responding to threats; (2) appropriate participants—inviting as many stakeholders as possible to "get the whole system in the room"; (3) relevant tasks to address the conference theme—assigned to several subgroups responsible for examining the theme.
Open-Systems Methods: These approaches help organizations assess their environments systematically and develop strategic responses. The six steps are: (1) Map the current environment surrounding the organization, identifying and prioritizing external groups; (2) Assess the organization's responses to environmental expectations; (3) Identify the core mission of the organization as revealed in behavior, not official statements; (4) Create a realistic future scenario assuming no changes; (5) Create an ideal future scenario without worrying about constraints; (6) Compare the present with the ideal future and prepare an action plan with three timeframes: tomorrow, six months, and two years.
Open-Space Methods: This approach is distinguished by its lack of formal structure. It temporarily restructures or "self-organizes" participants around interests and topics. The three steps are: (1) Set the conditions for self-organizing—announcing the theme and norms, including the "Law of Two Feet" (taking responsibility for one's own behavior) and the "Four Principles" (whoever comes is the right people; whatever happens is the only thing that could have; whenever it starts is the right time; when it is over, it is over); (2) Create the agenda—participants describe topics they have passion for and sign up for sessions; (3) Coordinate activity through information—using community meetings and one-page summaries posted in a "newsroom."
Following Up on Meeting Outcomes: Follow-up efforts are vital to implementing action plans, involving communicating results, gaining wider commitment, and structuring the change process.
Grid Organization Development: A Normative Approach
Grid OD is one of the most widely used approaches to system-wide planned change. It is a systematic approach aimed at achieving corporate excellence, based on the belief that managers and organizations can only be made more effective if the basic culture of the system is changed. Grid OD starts with a focus on individual behavior, specifically on the Managerial Grid describing managerial styles, and moves through sequential phases involving the work team, inter-group relationships, and finally the overall organizational culture.
According to the Managerial Grid, an individual's style can be described according to his or her concern for production and concern for people. Concern for production covers behaviors like accomplishing tasks, developing creative ideas, and making quality decisions. Concern for people encompasses issues like personal worth, working conditions, commitment, security, and relationships. Managers with high concern for production and low concern for people minimize attitudes and feelings; those with high concern for people and low concern for production focus on comfort and security. The most effective style shows high concern for both, overcoming the communications barrier by allowing employees to think and influence the organization.
The six phases of Grid OD are: Phase 1: The Grid Seminar—a one-week program where participants analyze their personal styles and learn team methods of problem-solving, with learning objectives including analyzing thinking, increasing objectivity, achieving clear communication, working in teams, managing conflict, and analyzing corporate culture.
Phase 2: Teamwork Development—begins with the top manager and direct reports, then cascades down through the entire organization, with teams setting group and individual goals.
Phase 3: Inter-group Development—improves relations between units by having groups describe actual and ideal relationships, compare perceptions, and work on making relationships more productive.
Phase 4: Developing an Ideal Strategic Organization Model—top managers work toward a model incorporating six factors: clear financial objectives, character of activities, scope of markets, integrating structure, basic policies, and approaches to growth.
Phase 5: Implementing the Ideal Strategic Model—organizations are divided into segments with planning teams, a corporate headquarters team, and a coordinator ensuring clear understanding.
Phase 6: Systematic Critique—determines the degree of organization excellence using a 100-question survey investigating behavior, teamwork, inter-group relations, and corporate strategy, with measurements taken at each phase.
⭐ Key Takeaways
The four system-wide process interventions each serve distinct purposes: confrontation meetings mobilize resources by having all departments identify and prioritize problems, inter-group interventions use microcosm groups and conflict resolution to address relationships between units, large-group interventions bring many stakeholders together to address complex organizational issues through either structured open-systems methods or flexible open-space methods, and Grid OD provides a comprehensive six-phase program focused on changing organizational culture through the Managerial Grid's concern for production and people. The defining feature of large-group interventions is "getting the whole system in the room" to accelerate change. Microcosm groups work through parallel processes, where small representative groups unconsciously reflect and solve problems present in the larger organization. For the exam, remember: the ten steps of confrontation meetings, the five steps of microcosm groups, the six steps of open-systems methods, the three steps of open-space methods with their Law of Two Feet and Four Principles, and the six phases of Grid OD.
🧠 Quick Revision Questions
- What is the purpose of an organization confrontation meeting, and when is it particularly useful?
- How do parallel processes operate in microcosm groups, and why are they important for solving organization-wide problems?
- What are the six steps in open-systems methods for large-group interventions?
- Explain the "Law of Two Feet" and the "Four Principles" that govern open-space methods.
- What are the six phases of Grid Organization Development, and what is the central focus of the Managerial Grid?
📘 Lecture 34 — Restructuring Organizations
📖 Overview: This lecture examines techno-structural interventions that focus on changing an organization’s technology and structure. It explores how organizations are moving from traditional, rigid bureaucratic structures to leaner, more flexible forms in response to global competition and rapid change. The lecture covers structural design, downsizing, reengineering, and five distinct organizational structures including functional, self-contained-unit, matrix, process-based, and network-based forms.
🗂️ Topics Covered
The lecture begins by examining structural design and its contingency factors including environment, size, technology, strategy, and worldwide operations. It then explores five major organizational structures in detail: the functional organization, self-contained-unit organization, matrix organization, process-based structures, and network-based structures. For each structure, the lecture provides definitions, advantages, disadvantages, and specific contingency conditions. The lecture also briefly introduces downsizing and reengineering as restructuring interventions.
📝 Lecture Summary
Structural Design
Organization structure describes how the overall work of the organization is divided into subunits and how these subunits are coordinated for task completion. It is a key feature of an organization’s strategic orientation. Based on a contingency perspective shown in Figure 41, organization structures should be designed to fit with at least five factors: the environment, organization size, technology, organization strategy, and worldwide operations. Organization effectiveness depends on the extent to which its structures are responsive to these contingencies.
Organizations traditionally have structured themselves into one of three forms: functional departments that are task specialized; self-contained units that are oriented to specific products, customers, or regions; or matrix structures that combine both functional specialization and self-containment. Faced with accelerating changes in competitive environments and technologies, organizations increasingly have redesigned their structures into more integrative and flexible forms including process-based structures and network-based structures.
The Functional Organization
The functional structure is perhaps the most widely used organizational structure in the world today. The organization is usually subdivided into functional units such as engineering, research, operations, human resources, finance, and marketing. This structure is based on early management theories regarding specialization, line and staff relations, span of control, authority, and responsibility. The major functional subunits are staffed by specialists, and it is considered easier to manage specialists if they are grouped together under the same head who has training and experience in that particular discipline.
🔑 Definition — Functional Structure: An organizational structure that subdivides the organization into departments based on specialized functions such as engineering, finance, and marketing.
Table 12 lists the advantages and disadvantages of functional structures. On the positive side, functional structures promote specialization of skills and resources by grouping people who perform similar work and face similar problems. This grouping facilitates communication within departments and allows specialists to share their expertise. It also enhances career development within the specialty, whether it is accounting, finance, engineering, or sales. The functional structure reduces duplication of services because it makes the best use of people and resources.
On the negative side, functional structures tend to promote routine tasks with a limited orientation. Department members focus on their own tasks rather than on the organization’s total task, which can lead to conflict across functional departments. Coordination and scheduling among departments can be difficult when each emphasizes its own perspective.
📌 Contingencies: The functional structure works best in small-to-medium sized firms in environments that are relatively stable and certain. These organizations typically have a small number of products or services. This structure is best suited to routine technologies with interdependence within functions, and to organizational goals emphasizing efficiency and technical quality.
The Self-Contained-Unit Organization
The self-contained-unit structure, also known as a product or divisional structure, represents a fundamentally different way of organizing. It was developed at about the same time by General Motors, Sears, Standard Oil of New Jersey (Exxon), and DuPont. It groups organizational activities on the basis of products, services, customers, or geography. All or most of the resources necessary to accomplish a specific objective are set up as a self-contained unit headed by a product or division manager. In effect, a large organization may set up smaller (sometimes temporary) special-purpose organizations, each geared to a specific product, service, customer, or region.
🔑 Definition — Self-Contained-Unit Structure: An organizational structure that groups activities based on products, services, customers, or geography, with all necessary resources placed in a single unit.
Table 13 lists the advantages and disadvantages. These organizations recognize key interdependencies and coordinate resources toward an overall outcome. This strong outcome orientation ensures departmental accountability and promotes cohesion among those contributing to the product. These structures provide employees with opportunities for learning new skills and expanding knowledge because workers can move more easily among different specialties.
On the negative side, self-contained-unit organizations may not have enough specialized work to use people’s skills fully. Specialists may feel isolated from their professional colleagues. The structures may promote allegiance to department rather than organization objectives and place multiple demands on people, thereby creating stress.
📌 Contingencies: The self-contained-unit structure works best in conditions almost opposite to those favoring a functional organization. The organization needs to be relatively large to support duplication of resources. Because each unit is designed to fit a particular niche, the structure adapts well to uncertain conditions. It helps coordinate technical interdependencies falling across functions and is suited to goals promoting product or service specialization and innovation.
The Matrix Organization
The matrix organization maximizes the strengths and minimizes the weaknesses of both the functional and self-contained-unit structures. It superimposes the lateral structure of a product or project coordinator on the vertical functional structure. Matrix organizational designs originally evolved in the aerospace industry where changing customer demands and technological conditions caused managers to focus on lateral relationships between functions. Matrix organizations now are used widely in manufacturing, service, nonprofit, governmental, and professional organizations.
🔑 Definition — Matrix Organization: An organizational structure that superimposes a lateral product or project structure on a vertical functional structure, creating dual chains of command.
Every matrix organization contains three unique and critical roles: the top manager, who heads and balances the dual chains of command; the matrix bosses (functional, product, or area), who share subordinates; and the two-boss managers, who report to two different matrix bosses. For example, all engineers may be in one engineering department and report to an engineering manager, but these same engineers may be assigned to different projects and report to a project manager while working on that project.
📌 Example: In a matrix organization, each project manager reports directly to the vice president and the general manager. Since each project represents a potential profit center, the power and authority used by the project manager come directly from the general manager.
Table 14 lists the advantages and disadvantages. On the positive side, the matrix structure allows multiple orientations. Specialized functional knowledge can be applied to all projects. New products or projects can be implemented quickly by using people flexibly. Matrix organizations can maintain consistency among departments and projects by requiring communication among managers.
On the negative side, these organizations can be difficult to manage. Implementation requires heavy managerial costs and support. When people are assigned to more than one department, there may be role ambiguity and conflict, and overall performance may be sacrificed if there are power conflicts between functional departments and project structures.
📌 Three Conditions for Matrix: First, there must be outside pressures for a dual focus — many customers with unique demands and strong requirements for technical sophistication. Second, the matrix is appropriate when the organization must process a large amount of information — when external demands change unpredictably, when the organization produces a broad range of products, and when there is reciprocal interdependence among tasks. Third, there must be pressures for shared resources — when valuable human and physical resources are likely to be scarce. If any of these conditions is not met, a matrix organization is likely to fail.
Process-Based Structures
A radically new logic for structuring organizations is to form multidisciplinary teams around core processes such as product development, order fulfillment, sales generation, and customer support. Process-based structures emphasize lateral rather than vertical relationships. All functions necessary to produce a product or service are placed in a common unit usually managed by someone called a “process owner.” There are few hierarchical levels, and the senior executive team is relatively small.
🔑 Definition — Process-Based Structure: An organizational structure that forms multidisciplinary teams around core work processes, emphasizing lateral relationships and customer focus.
Process-based structures eliminate many hierarchical and departmental boundaries that can impede task coordination and slow decision making. They reduce the enormous costs of managing across departments up and down the hierarchy. These structures enable organizations to focus most of their resources on serving customers, both inside and outside the firm.
Six Key Features of Process-Based Structures:
- Processes drive structure — organized around three to five key processes, each governed by a process owner with clear performance goals.
- Work adds value — simplified by eliminating nonessential tasks and reducing layers of management; enriched by combining tasks so teams perform whole processes.
- Teams are fundamental — self-managing teams manage everything from task execution to strategic planning.
- Customers define performance — the primary goal is customer satisfaction.
- Teams are rewarded for performance — appraisal systems focus on team performance against customer satisfaction goals.
- Teams are tightly linked to suppliers and customers — through designated members with direct relationships.
Table 15 lists advantages and disadvantages. The most frequently mentioned advantage is intense focus on meeting customer needs, which can result in dramatic improvements in speed, efficiency, and customer satisfaction. Process-based structures remove layers of management, so information flows more quickly. Because process teams comprise different functional specialties, boundaries between departments are removed.
A major disadvantage is the difficulty of changing to this new organizational form. These structures typically require radical shifts in mindsets, skills, and managerial roles. Process-based structures may result in expensive duplication of scarce resources and, if teams are not skilled adequately, in slower decision making.
📌 Contingencies: Process-based structures are particularly appropriate for highly uncertain environments where customer demands and market conditions are changing rapidly. They enable organizations to manage non-routine technologies and coordinate highly interdependent work flows. They generally appear in medium- to large-sized organizations having several products or projects, with a heavy focus on customer-oriented goals.
⭐ Key Takeaways
A student must remember that organization structure describes how work is divided and coordinated, and that structures must fit five contingency factors: environment, size, technology, strategy, and worldwide operations. The four major structural forms each have distinct advantages, disadvantages, and contingency conditions — functional structures suit stable environments with routine technology, self-contained units suit uncertain environments with cross-functional interdependence, matrix structures require dual focus on product and technical demands with shared resources, and process-based structures require highly uncertain environments with customer-oriented goals. The matrix organization involves dual command with three critical roles (top manager, matrix bosses, and two-boss managers), while process-based structures emphasize lateral relationships, teams, and customer satisfaction. All structural forms should be evaluated based on their fit with organizational contingencies, not as universally superior designs.
🧠 Quick Revision Questions
-
What are the five contingency factors that influence which organizational structure is appropriate?
-
Under what conditions is a functional structure most appropriate, and what is its main disadvantage?
-
What three unique and critical roles exist in every matrix organization, and what happens if any of the three conditions for matrix is not met?
-
What are the six key features of process-based structures, and why is the difficulty of changing to this form considered a major disadvantage?
-
How do the contingency conditions for functional structures differ from those for self-contained-unit structures?