📝 Lecture Summary
Entering and Contracting
The planned change process generally starts when key managers or administrators sense that their organization could be improved or has problems that could be alleviated through OD. The organization might be successful yet have room for improvement, might be facing impending environmental conditions necessitating change, or could be experiencing specific problems like poor product quality, high absenteeism, or dysfunctional conflicts. Conversely, the problems might appear more diffuse, such as feelings that the organization should be "more innovative," "more competitive," or "more effective."
Entering and contracting are the initial steps in the OD process. They involve defining in a preliminary manner the organization's problems or opportunities for development and establishing a collaborative relationship between the OD practitioner and members of the client system about how to work on those issues. These steps set the initial parameters for carrying out the subsequent phases of OD: diagnosing the organization, planning and implementing changes, and evaluating and institutionalizing them. They help define what issues will be addressed, who will carry them out, and how they will be accomplished.
Entering and contracting can vary in complexity and formality depending on the situation. When a manager of a work group serves as their own OD practitioner, entering and contracting are relatively simple and informal, involving direct discussion with group members without many formal procedures. In situations where managers are considering the use of professional OD practitioners—either internal or external—entering and contracting tend to be more complex and formal. OD practitioners may need to collect preliminary information, meet with representatives rather than the total membership, and formalize their respective roles and how the change process will unfold.
💡 Why this matters: Unless there is clarity and agreement about what issues to work on, who will address them, and how that will be accomplished, subsequent stages of the OD process are likely to be confusing and ineffective.
Entering into an OD Relationship
An OD process generally starts when a member of an organization or unit contacts an OD practitioner about potential help in addressing an organizational issue. The organization member may be a manager, staff specialist, or some other key participant, and the practitioner may be an OD professional from inside or outside of the organization. Determining whether the two parties should enter into an OD relationship typically involves clarifying the nature of the organization's current functioning and the issue(s) to be addressed, the relevant client system for that issue, and the appropriateness of the particular OD practitioner. The OD practitioner may need to collect preliminary data about the organization, and the organization may need to gather information about the practitioner's competence and experience.
The activities involved in entering an OD relationship are: clarifying the organizational issue, determining the representatives of the client organization, and selecting the appropriate OD practitioner.
Clarifying the Organizational Issue
When seeking help from OD practitioners, organizations typically start with a presenting problem—the issue that has caused them to consider an OD process. It may be specific (decreased market share, increased absenteeism) or general ("we're growing too fast," "we need to prepare for rapid changes"). The presenting problem often has an implied or stated solution. For example, managers may believe that because members of their teams are in conflict, team building is the obvious answer. They may even state the presenting problem in the form of a solution: "We need some team building."
In many cases, however, the presenting problem is only a symptom of an underlying problem. For example, conflict among team members may result from several deeper causes, including ineffective reward systems, personality differences, inappropriate structure, and poor leadership. The issue facing the organization or department must be clarified early in the OD process so that subsequent diagnostic and intervention activities are focused correctly.
Gaining a clearer perspective on the organizational issue may require collecting preliminary data. OD practitioners often examine company records and interview a few key members to gain an introductory understanding of the organization, its context, and the nature of the presenting problem. These data are gathered in a relatively short period, typically over a few hours to one or two days. They are intended to provide enough rudimentary knowledge of the organizational issue to enable the two parties to make informed choices about proceeding with the contracting process.
📌 Example: A manager might say, "We need some team building." The OD practitioner must clarify whether the real issue is indeed team conflict or something deeper like an ineffective reward system or poor leadership. The practitioner might review company records and interview a few key members for a day or two to understand the situation better.
The diagnostic phase of OD involves a far more extensive assessment of the problematic or development issue that occurs during the entering and contracting stage. The diagnosis might also discover other issues that need to be addressed, or it might lead to redefining the initial issue identified during entering and contracting. This is a prime example of the emergent nature of the OD process, where things may change as new information is gathered and new events occur.
Determining the OD Team Members
A second activity in entering an OD relationship is to define who are the team members involved in addressing the organizational issue. Generally, organization members who can directly impact the change issue should be involved, whether it is solving a particular problem or improving an already successful organization or department. Unless these members are identified and included in the entering and contracting process, they may withhold their support for and commitment to the OD process. In trying to improve the productivity of a unionized manufacturing plant, for example, it will be necessary to include union officials as well as managers and staff personnel. It is not unusual for an OD project to fail because the team members were inappropriately defined.
Determining the team members can vary in complexity depending on the situation. When the organizational issue can be addressed in a specific organization unit, members of that unit must be included. For example, if a manager asked for help improving the decision-making process of his or her team, the manager and team members would be part of the OD process.
Determining the team members is more complex when the organizational issue cannot readily be addressed in a single unit. Here, it may be necessary to include members from multiple units, from different hierarchical levels, and even from outside of the organization. For example, resolving conflict between a production department and other departments would require including members from all departments involved as well as the executive to whom all departments report. If interdepartmental conflict also involved key suppliers and customers from outside the firm, those groups might need to be included as well.
In complex situations, OD practitioners need to gather additional information about the organization to determine the relevant team members, generally as part of the preliminary data collection. When examining company records or interviewing personnel, practitioners can seek to identify key members and organizational units that need to be involved. They can ask questions such as: Who can directly impact the organizational issue? Who has a vested interest in it? Who has the power to approve or reject the OD effort?
Selecting an OD Practitioner
The last activity involved in entering an OD relationship is selecting an OD practitioner who has the expertise and experience to work with members on the organizational issue. Perhaps the best criteria for selecting, evaluating, and developing OD practitioners are those suggested by Gordon Lippitt, a pioneering practitioner in the field. Lippitt listed areas that managers should consider before selecting a practitioner, including:
- The ability of the consultant to form sound interpersonal relationships
- The degree of focus on the problem
- The skills of the practitioner relative to the problem
- The extent that the consultant clearly informs the client as to his or her role and contribution
- Whether the practitioner belongs to a professional association
References from other clients are highly important. A client may not like the consultant's work, but it is critical to know the reasons for both pleasure and displeasure. One important consideration is whether the consultant approaches the organization with openness and an insistence on diagnosis or whether the practitioner appears to have a fixed program applicable to almost any organization.
OD consulting is as much a person specialization as it is a task specialization. The OD professional needs not only a repertoire of technical skills but also the personality and interpersonal competence to use himself or herself as an instrument of change. Regardless of technical training, the consultant must be able to maintain a boundary position, coordinating among various units and departments and mixing disciplines, theories, technology, and research findings in an organic rather than a mechanical way. The practitioner is potentially the most important OD technology available.
Thus, in selecting an OD practitioner, perhaps the most important issue is: How effective has the person been in the past, with what kinds of organizations, using what kinds of techniques? Interpersonal relationships are tremendously important, but even con artists have excellent interpersonal relationships and skills.
The burden of choosing an effective OD practitioner should not rest entirely with the client organization. Consultants also bear a heavy responsibility for seeking an appropriate match between their skills and knowledge and what the organization or department needs. Few managers are sophisticated enough to detect subtle differences in expertise among OD professionals. Thus, practitioners should help educate potential clients, being explicit about their strengths and weaknesses. If OD professionals realize that a good match does not exist, they should inform managers and help them find more suitable help.
🔑 Definition — Presenting Problem: The issue that has caused an organization to consider an OD process; it may be specific (e.g., decreased market share) or general (e.g., "we're growing too fast") and often has an implied or stated solution.
🔑 Definition — Boundary Position: The role of an OD consultant who coordinates among various units and departments, mixing disciplines, theories, technology, and research findings in an organic way.
🔑 Definition — Emergent Nature of OD: The characteristic that things may change as new information is gathered and new events occur, possibly leading to redefinition of issues identified during the entering and contracting stage.
Developing a Contract
The activities of entering an OD relationship are a necessary prelude to developing an OD contract. They define the major focus for contracting, including the relevant parties. Contracting is a natural extension of the entering process and clarifies how the OD process will proceed. It typically establishes the expectations of the parties, the time and resources that will be expended, and the ground rules under which the parties will operate.
The goal of contracting is to make a good decision about how to carry out the OD process. It can be relatively informal, involving only a verbal agreement between the client and OD practitioner. A team leader with OD skills, for example, may voice concerns to members about how the team is functioning. After some discussion, they might agree to devote one hour of future meeting time to diagnosing the team with the help of the leader. Here, entering and contracting are done together informally.
In other cases, contracting can be more protracted and result in a formal document. This typically occurs when organizations employ outside OD practitioners. Government agencies, for example, generally have procurement regulations that apply to contracting with outside consultants.
Regardless of the level of formality, all OD processes require some form of explicit contracting that results in either a verbal or a written agreement. Such contracting clarifies the client's and the practitioner's expectations about how the OD process will take place. Unless there is mutual understanding and agreement about the process, there is considerable risk that someone's expectations will be unfilled. That can lead to reduced commitment and support, misplaced action, or premature termination of the process.
The contracting step in OD generally addresses three key areas: what each party expects to gain from the OD process, the time and resources that will be devoted to it, and the ground rules for working together.
Mutual Expectations
This part of the contracting process focuses on the expectations of the client and the OD practitioner. The client states the services and outcomes to be provided by the OD practitioner and describes what the organization expects from the process and the consultant. Clients usually can describe the desired outcomes, such as decreased turnover or higher job satisfaction. Encouraging them to state their wants in the form of outcomes, working relationships, and personal accomplishments can facilitate the development of a good contract.
The OD practitioner also should state what he or she expects to gain from the OD process. This can include opportunities to try new interventions, report the results to other potential clients, and receive appropriate compensation or recognition.
Time and Resources
To accomplish change, the organization and the OD practitioner must commit time and resources to the effort. Each must be clear about how much energy and how many resources will be dedicated to the change process. Failure to make explicit the necessary requirements of a change process can quickly ruin an OD effort. For example, a client may clearly state that the assignment involves diagnosing the causes of poor productivity in a work group. However, the client may expect the practitioner to complete the assignment without talking to the workers.
Resources can be divided into two parts:
- Essential requirements are things that are absolutely necessary if the change process is to be successful. From the practitioner's perspective, they can include access to key people or information, enough time to do the job, and commitment from certain people. The organization's essential requirements might include a speedy diagnosis or assurances that the project will be conducted at the lowest price.
- Desirable requirements are those things that would be nice to have but are not absolutely necessary, such as access to special resources and written rather than verbal reports.
Being clear about the constraints on carrying out the assignment will facilitate the contracting process and improve the chances for success.
Ground Rules
The final part of the contracting process involves specifying how the client and the OD practitioner will work together. The parameters established may include such issues as confidentiality, if and how the OD practitioner will become involved in personal or interpersonal issues, how to terminate the relationship, and whether the practitioner is supposed to make expert recommendations or help the manager make decisions. For internal consultants, organizational politics make it especially important to clarify issues of how to handle sensitive information and how to deliver bad news. Such process issues are as important as the needed substantive changes. Failure to address these concerns may mean that the client or the practitioner has inappropriate assumptions about how the process will unfold.
Application 1: Contracting at Charity Medical Center
This extended example illustrates how entering and contracting unfolded at Charity Medical Center (CMC), a 500-bed acute-care hospital that was part of the Jefferson Hospital Corporation (JHC). CMC had a declining market share for six months, and senior management recognized that other hospitals were newer, had better facilities, were more "user friendly," and had captured the interest of referring physicians.
An external OD practitioner named John Murray was invited to make a presentation on implementing a total quality management (TQM) process. John conducted an initial interview with CMC's vice president of patient-care services, Joan Grace, who noted that the hospital's primary advantage was its designation as a level-one trauma center but that the hospital's reputation was: "once we save a patient's life, we tend to forget they are here."
John collected preliminary data by reviewing documents (corporate mission statement, strategic planning document, organization chart, performance analysis) and conducting interviews (hospital president, nursing unit observations, human resources vice president from corporate office). His investigation revealed several important issues:
- CMC was actually two hospitals—a 150-bed suburban hospital also reported to CMC's president
- A budget existed for initiating a patient-care quality improvement process
- JHC was in a state of flux with systems still being established
- Management and nursing staff were extremely busy with meetings
- Another consulting firm had been awarded a contract for "job redesign" in two departments
- Most nursing units operated under traditional and somewhat outdated nursing management principles
In his presentation to senior management, John noted that implementing a quality process was a major organizational change requiring thorough diagnosis, considerable resource commitment, and high-level involvement by senior management. He also suggested that TQM was capable of addressing certain problems but was not designed to directly address such broader performance issues as market share.
When Joan asked John to meet to discuss how to proceed, John identified several knotty issues:
- The relationship between market share problems and a quality program was unclear
- Managers and nursing heads were frustrated by their inability to influence change because of busy meeting schedules
- The job redesign effort being conducted by another consulting firm seemed disconnected from the TQM effort
John proposed that CMC should: thoroughly diagnose the reasons for market-share decline and managerial frustration; postpone the job redesign effort; and have CMC management meet for two days to examine the diagnostic information and make a joint decision about whether TQM made sense.
Joan found these requests difficult because of time constraints, a sense of urgency, and the political sensitivity of postponing the job redesign effort. John explained that his requests were necessary—collecting diagnostic information is the first step in any quality management process, and to proceed without that information could mean implementing the wrong change. He gave the example that the market share problem could result from how CMC was treating physicians, in which case a quality program would be inappropriate and costly.
John also offered to coordinate with the other consultants but strongly urged postponing the job redesign project until after the two-day management meeting. After a week of discussion, Joan agreed to John's requests and asked him to submit a written proposal.
📌 Example Key Points:
- Presenting problem: Declining market share
- Preliminary data collection: Company documents, interviews, observations
- Complex client system: CMC included two hospitals; stakeholders included the president, referring physicians, corporate office
- Multiple change efforts: TQM and job redesign were potentially conflicting
- Contracting negotiation: John insisted on diagnosis before committing to a solution, negotiated two-day meeting, access to key people, and postponement of the other consulting project
- Ground rules discussed: Confidentiality, access to information, coordination with other consultants
⭐ Key Takeaways
The entering and contracting phase is the critical foundation of any OD effort—without clarity and agreement at this stage, all subsequent phases risk failure. The presenting problem is often only a symptom of deeper issues, so OD practitioners must collect preliminary data to clarify the real organizational issue before proceeding. Determining the correct client system or team members is essential because excluding key stakeholders can cause them to withhold support and derail the entire project. Selecting an appropriate OD practitioner requires evaluating interpersonal skills, references, and fit with the organization's needs, not just technical expertise. Finally, a good contract must address mutual expectations, time and resource commitments, and ground rules for collaboration—and even when the client wants to move quickly, the practitioner must insist on proper diagnosis before action.
🧠 Quick Revision Questions
- What are the three main activities involved in entering an OD relationship, and why is each important?
- Why is the presenting problem often not the real problem that needs to be addressed in OD?
- What criteria did Gordon Lippitt suggest for selecting an OD practitioner, and why are references particularly important?
- What are the three key areas that must be addressed in the contracting step of OD, and what can happen if any of these areas are neglected?
- In the Charity Medical Center example, what were the "essential requirements" that John Murray insisted upon before proceeding, and why did Joan Grace initially find them difficult to accept?
📘 Lecture 15 — Diagnosing Organizations
📖 Overview: This lecture explores the concept of diagnosis in organization development, moving beyond the medical model to a collaborative process between OD practitioners and organization members. It explains the task/process relationship, the diagnostic cycle, performance gap analysis, and the importance of diagnostic models and open-systems theory for understanding organizational functioning.
🗂️ Topics Covered
The lecture covers the concept of diagnosis in OD, distinguishing it from the medical model and emphasizing collaboration. It details the diagnostic process as a cyclical activity involving data gathering, interpretation, and action planning. The concept of the performance gap and gap analysis is introduced as a key diagnostic method. The need for diagnostic models, including the open-systems model, is discussed to guide what information to collect and analyze. A case study, "The Old Family Bank," is presented to illustrate diagnostic application.
📝 Lecture Summary
Diagnosing Organizations
The lecture begins by comparing organizational diagnosis to medical diagnosis, noting that both involve identifying and closing gaps between the current and desired state. Kurt Lewin added a new dimension with the concept of the “task/process” relationship. Task refers to what is to be done—concrete, observable, and measurable. Process refers to how—reflecting perceptions, attitudes, and reasoning. The lecture emphasizes that task and process are inseparable, like the visual paradox of the Old Woman/Young Woman where you cannot see both images at once. Action reflects pure process, guided by right-brain creativity and insight. A key skill is diagnosing the linkages between task and process, such as what is not being talked about when work stops. The lecture warns that left-brain diagnostic thinking, which is objective and aloof, combined with a propensity to defer to authority, creates a setup for disappointment. The great contribution of group dynamics was its focus on process as inseparable from task, the diagnoser from the diagnosis, and a leader's effectiveness from follower contributions.
🔑 Definition — Task/Process Relationship: A concept highlighting the interplay between the what (task: concrete goals, targets) and the how (process: perceptions, attitudes, reasoning) in organizational dynamics.
What is Diagnosis?
Diagnosis is the process of understanding how the organization is currently functioning, providing the information necessary to design change interventions. It follows from successful entry and contracting. The lecture clarifies that the medical model of diagnosis is misleading for organizations. In OD, diagnosis is a collaborative process between organization members and the OD consultant, not a doctor-patient relationship. It does not assume something is inherently wrong. For example, a manager concerned about absenteeism might jointly decide with a consultant to diagnose the cause by examining records and interviewing employees, or they might focus on what encourages employee loyalty. Diagnosis can be problem-oriented (uncovering causes of problems) or development-oriented (assessing current functioning to discover areas for future enhancement). Organizational diagnosis examines two broad areas: the various interacting sub-elements (divisions, departments, products) and the organizational processes (communication, decision-making, leadership, conflict management).
🔑 Definition — Diagnosis (in OD): A collaborative process between organization members and the OD consultant to collect pertinent information, analyze it, and draw conclusions for action planning and intervention. It can be problem-oriented or development-oriented.
💡 Why this matters: This distinction moves OD from a reactive, problem-fixing model to a proactive, strengths-based approach to enhancing organizational effectiveness.
The Process:
Diagnosis is a cyclical process with nine steps:
- Preliminary identification of possible problem areas.
- Gathering data based on the preliminary problem.
- Categorizing and analyzing the data.
- Presenting data to the client in a feedback session.
- Determining if enough data is available.
- Jointly diagnosing and identifying likely problem areas.
- Determining the client's level of motivation to work on the problems.
- Identifying target systems and designing the change strategy.
- Monitoring the results to determine the degree of change achieved versus goals.
The Performance Gap:
A key method in diagnosis is determining the performance gap—the difference between what the organization could do and what it actually does. This leads to gap analysis. Data is collected on the actual state and the ideal or desired state. The gap forms the basis for diagnosis and intervention design. A performance gap may result from ineffective internal performance, competitive changes, or failure to adapt to the external environment. Recognizing a performance gap can unfreeze the organization and create conditions for change. One self-assessment version uses questionnaires to gather information on the organization's strengths, how to take advantage of them, its weaknesses, and how to alleviate them. In diagnosis, the practitioner looks for causality—a cause-effect relationship—identifying what factors are causing the problem (e.g., declining sales) versus the symptom.
The Need for Diagnostic Models:
To diagnose an organization, practitioners and members need a framework for what information to collect. These conceptual frameworks are diagnostic models, which describe relationships among different features of the organization, its context, and its effectiveness. Models point out what areas to examine and what questions to ask. However, all models are simplifications and may be biased if they focus on certain features to the exclusion of others. For example, a model focusing on interpersonal conflict would ignore skill composition and task complexity. Diagnostic models can be derived from academic research (e.g., on motivation, leadership, job design) or from practitioner experience in the field. The lecture introduces the open-systems model as a general framework for diagnosis.
🔑 Definition — Diagnostic Models: Conceptual frameworks that people use to understand organizations, describing relationships among different features of the organization, its context, and its effectiveness. They guide what to examine and what questions to ask.
Open-Systems Model:
This section introduces systems theory and the open-systems model. A system is a unitary whole composed of parts or subsystems that function together. Open systems, like organizations and people, exchange information and resources with their environments and are influenced by external forces (e.g., raw material availability, customer demands, government regulations). Open systems display hierarchical ordering: society > organizations > groups (departments) > individuals. Key properties of open systems include:
- Inputs, Transformations, and Outputs: Resources from the environment (inputs) are transformed (e.g., through work processes) into products/services (outputs).
- Boundaries: The demarcation between the system and its environment. In open systems, boundaries are permeable.
- Feedback: Information about outputs that is used to adjust the system's functioning.
- Equifinality: A system can reach the same final state from different starting points and by different paths.
- Alignment: For a system to be effective, its parts must be aligned with each other and with the environment.
🔑 Definition — Open Systems: Systems that exchange information and resources with their outside environments and are influenced by external forces.
🔑 Definition — Equifinality: The principle that a system can achieve the same final state from different initial conditions and by different pathways.
💡 Why this matters: The open-systems model provides a comprehensive framework for understanding that an organization's internal behavior (e.g., employee morale, departmental conflict) is often a response to, or in alignment with, external pressures and opportunities.
Case: The Old Family Bank
This case illustrates a diagnostic scenario. H. Day, the data-processing VP, examined turnover, absenteeism, and productivity figures across bank departments. He found the check-sorting department had low turnover/absenteeism and was the most productive, despite poor working conditions (hot, noisy). In contrast, the data-processing department also had low turnover/absenteeism and high cohesion, but ranked last in productivity, despite excellent working conditions (air-conditioned, quiet). Interviews revealed check-sorting workers were unskilled, loyal to the company, and committed to team performance. Data-processing workers were highly skilled, felt management valued production over staff units, believed their pay didn't reflect their skill, and thus felt little loyalty to the company.
📌 Example (Case Analysis): The case solution identifies the problems: a macro issue of lack of loyalty affecting bank effectiveness, and micro issues of data-processing personnel feeling unappreciated. Causes include their perception of pay inequity and their access to company-wide information without understanding managerial decision-making. Alternatives include: 1) gathering more data; 2) using a force-field analysis model; 3) checking regional pay data for competitiveness; and 4) explaining the bank's pay-setting procedures. The recommendation is to undertake all these alternatives.
⭐ Key Takeaways
The most critical concept from this lecture is that organizational diagnosis is a collaborative, cyclical process, not a top-down medical examination. Students must understand the distinction between task and process and how they are inseparable. The performance gap analysis is a key diagnostic tool for identifying the difference between actual and ideal states. Diagnostic models, especially the open-systems model, provide essential frameworks for deciding what information to collect and analyze, preventing a biased or incomplete diagnosis. Finally, the case study reinforces that apparent contradictions (e.g., good conditions but poor performance) often reveal underlying process issues like perceived fairness and organizational loyalty.
🧠 Quick Revision Questions
- What is the key difference between the medical model of diagnosis and the OD model of diagnosis?
- Explain the "task/process" relationship and give an example of each from a team meeting.
- What is a "performance gap" and how is it used in gap analysis?
- Why is it important to use a diagnostic model when beginning an organizational diagnosis, and what is a potential risk?
- According to the open-systems model, what are "inputs," "transformations," and "outputs" for a university, and what is an example of "feedback" it might receive?
📘 Lecture 16 — Organization as Open Systems
📖 Overview: This lecture explores the concept of organizations as open systems that constantly exchange information and resources with their external environments. Understanding these systemic properties—including inputs, transformations, outputs, boundaries, feedback, equifinality, and alignment—is essential for diagnosing organizational effectiveness and designing successful change initiatives.
🗂️ Topics Covered
The lecture introduces the key properties of open systems: inputs, transformations, and outputs; boundaries; feedback; equifinality; and alignment. It then presents the diagnostic model for analyzing organizations at three levels (organization, group/ department, and individual job), with detailed focus on organization-level diagnosis including inputs from the general environment and industry structure. The comprehensive diagnostic model showing inputs, design components, and outputs at each organizational level is also presented.
📝 Lecture Summary
Organization as Open Systems
Open systems, such as organizations and people, exchange information and resources with their environments and cannot completely control their own behavior, being influenced in part by external forces. Organizations are affected by environmental conditions including raw material availability, customer demands, and government regulations. Open systems display a hierarchical ordering: society comprises organizations; organizations comprise groups (departments); groups comprise individuals. Although systems at different levels vary in size and complexity, they share common properties by virtue of being open systems.
Inputs, Transformations, and Outputs
Any organizational system is composed of three related parts: inputs, transformations, and outputs. Inputs consist of human or other resources (information, energy, materials) coming into the system from the external environment. Transformations are the processes of converting inputs into outputs, typically carried out by a production or operations function composed of both social components (people and their work relationships) and technological components (tools, techniques, and methods of production or service delivery). Outputs are the results of what is transformed by the system and sent to the environment. For example, group health insurance companies receive premiums, individuals, and medical bills; transform them through physician visits and record keeping; and export treated patients and payments to hospitals.
Boundaries
The idea of boundaries helps distinguish between systems and environments. Closed systems have relatively rigid and impenetrable boundaries, whereas open systems have far more permeable borders. Defining boundaries of social systems is difficult because there is continuous inflow and outflow through them. The definition of a boundary is somewhat arbitrary because a social system has multiple subsystems and boundary lines for different subsystems may vary. The permeability of boundaries also varies from fixed to diffuse—for instance, a community's police force has far more rigid boundaries than its political parties. Conflict over boundaries is always a potential problem within organizations.
🔑 Definition — Boundaries: The borders or limits of a system that distinguish it from its environment. In open systems, these borders are permeable, allowing continuous inflow and outflow of resources and information.
Feedback
Feedback is information regarding the actual performance or results of the system, but only information used to control the future functioning of the system is considered feedback. Feedback can be used to maintain the system in a steady state (e.g., keeping an assembly line running at a certain speed) or to help the organization adapt to changing circumstances. McDonald's uses strict feedback processes to ensure consistency across outlets, while a salesperson's report of poor sales may trigger organizational change, and a market research study may recommend changing the advertising campaign.
🔑 Definition — Feedback: Information regarding actual system performance used to control the future functioning of the system, either to maintain a steady state or to help the organization adapt to changing circumstances.
Equifinality
The idea of equifinality suggests that similar results may be achieved with different initial conditions and in many different ways. In closed systems, a direct cause-and-effect relationship exists between initial condition and final state, but biological and social systems operate differently. This concept suggests that managers can use varying degrees of inputs and transform them in various ways to obtain satisfactory outputs. The function of management is not to seek a single rigid solution but to develop a variety of satisfactory options. Systems and contingency theories suggest that there is no universal best way to design an organization.
🔑 Definition — Equifinality: The principle that similar results may be achieved with different initial conditions and through many different pathways; there is no single best way to design an organization.
Alignment
A system's overall effectiveness is determined by the extent to which the different parts are aligned with each other. This alignment or fit concerns relationships between inputs and transformations, between transformations and outputs, and among subsystems of the transformation process. Alignment represents the extent to which features, operations, and characteristics of one system support the effectiveness of another system. The systemic perspective suggests that diagnosis is the search for misfits among various parts and subsystems of an organization. For example, General Electric's diversification strategy requires a divisional structure—a functional structure would not fit because it is more efficient for one division to focus on one product line.
💡 Why this matters: Alignment is the key diagnostic concept—organizational effectiveness depends on how well components fit together, not just on individual component excellence.
🔑 Definition — Alignment: The extent to which features, operations, and characteristics of one system support the effectiveness of another system; the search for misfits among various parts and subsystems.
Diagnosing Organizational Systems
When viewed as open systems, organizations can be diagnosed at three levels: (1) the overall organization (including strategy, structure, and processes), (2) the group or department (including norms and work schedules), and (3) the individual position or job (including job design for required task behaviors). Diagnosis can occur at all three levels or be limited to particular level issues. The key to effective diagnosis is knowing what to look for at each level and how levels affect each other. Figure 22 presents a comprehensive model showing for each level: inputs, key design components of the transformation subsystem, and outputs. Cross-level relationships emphasize that organizational levels must fit with each other.
Organization-Level Diagnosis
The organization level of analysis is the broadest systems perspective in diagnostic activities. The model in Figure 22(A) is similar to other popular models including Weisbord's six-box model, Nadler and Tushman's congruency model, Galbraith's star model, and Kotter's organization dynamics model. Figure 22(A) proposes that an organization's transformation processes or design components represent how the organization positions and organizes itself within an environment (inputs) to achieve specific outputs. The combination of design component elements is called a strategic orientation.
🔑 Definition — Strategic orientation: The combination of design component elements representing how an organization positions and organizes itself within its environment to achieve specific outputs.
Inputs (Organization Level)
Two key inputs affect how an organization designs its strategic orientation. The general environment represents external elements and forces affecting attainment of organization objectives, described in terms of uncertainty present in social, technological, economic, ecological, and political forces. The industry structure or task environment, as defined by Michael Porter, consists of five forces: supplier power, buyer power, threats of substitutes, threats of entry, and rivalry among competitors. Strategic orientations must be sensitive to powerful suppliers who can increase prices; powerful buyers who can force price reductions; threats of new entrants; threats of substitute products; and rivalry among existing competitors.
Inputs must be understood for their rate of change and complexity. The general environment or industry structure can be characterized along a dynamic-static continuum—dynamic environments change rapidly and unpredictably, suggesting flexible strategic orientations. Complexity refers to the number of important elements in the environment. For example, software development organizations face dynamic and complex environments with rapidly changing technologies, regulations, customers, and suppliers, while glass jar manufacturers face more stable and less complex environments.
🔑 Definition — Five Forces Model (Porter): A framework for analyzing industry structure consisting of supplier power, buyer power, threats of substitutes, threats of entry, and rivalry among competitors.
⭐ Key Takeaways
The most critical concept from this lecture is that organizations are open systems whose behavior can only be fully understood by examining their interactions with external environments. The core systemic properties—inputs, transformations, outputs, boundaries, feedback, equifinality, and alignment—apply at every organizational level and are essential diagnostic tools. For exam purposes, remember that there is no single best way to design organizations (equifinality) and that effectiveness depends on alignment between all system components (systemic perspective). The three-level diagnostic model (organization, group/ department, individual job) must be understood as interconnected, with higher levels serving as inputs to lower levels. Finally, Porter's five forces model provides the framework for analyzing industry structure inputs that shape strategic orientation.
🧠 Quick Revision Questions
- What are the three related parts of any organizational system, and how do they relate to each other?
- Why is defining boundaries more difficult in social systems than in biological or mechanical systems?
- How does the concept of equifinality challenge the notion of a "universal best way" to design organizations?
- What does the systemic perspective suggest about the primary purpose of organizational diagnosis?
- What are the five forces in Porter's industry structure model, and how does each affect an organization's strategic orientation?