| Course | EDO 810 Organizational Theory |
|---|---|
| Module | Module 4 |
| Paper type | Doctoral theory application |
| Length | About 1,069 words, 6 pages |
| Format | APA 7 student paper |
| School | Aspen University |
| Program | Doctor of Education |
| Updated | October 2026 |
Free sample paper for EDO 810 Module 4
Built for Tuesdays, Tested by Ice Storms: A Systems and Contingency Analysis of a Merged 911 Authority
Student Name
Doctor of Education Program, Aspen University
EDO 810: Organizational Theory
Instructor Name
Month Day, Year
Built for Tuesdays, Tested by Ice Storms: A Systems and Contingency Analysis of a Merged 911 Authority
On an ordinary Tuesday, the Tri-County Emergency Communications Authority answers about 1,100 calls, nearly all within fifteen seconds. On a January night when freezing rain brought down trees and power lines across the three counties, it answered 3,400 calls in eighteen hours. For four of those hours, the average caller waited more than two minutes, police and fire dispatchers worked from different pictures of which roads were blocked, and county road crews could not reach anyone at the authority. The authority's structure works on Tuesdays and fails in ice storms. This paper uses systems and contingency theory to explain why. The authority, its environment and its figures are fictional.
The Authority as an Open System
Systems theory treats an organization as an open system that draws inputs from its environment, transforms them and returns outputs, adjusting through feedback to survive. The authority's inputs are calls, radio traffic, data from responders and staff time; its transformation is the interpretation of each emergency and the dispatch of help; its outputs are responders sent to the right places with the right information. Its environment includes callers, three counties' police, fire and medical agencies, utilities, road departments, weather and the state's 911 funding. Unlike a factory, the authority cannot store inventory or schedule demand: every input must be processed as it arrives.
How Uncertain Is the Environment?
| Condition | Calls per hour, typical | Share of time | Predictability |
|---|---|---|---|
| Ordinary weekday | 35 to 60 | About 90% of hours | High |
| Holidays, major events | 70 to 110 | About 8% | Moderate, scheduled |
| Storms, major incidents | 150 to 250 | About 2% | Low, hours of warning at best |
Differentiation and Integration
Lawrence and Lorsch (1967) compared companies in plastics, food and containers, three businesses whose markets and technologies changed at very different speeds. In the fast-changing plastics business, the stronger companies let research, sales and production grow apart in their aims, their sense of time and their habits, since each unit dealt with a different slice of the market and technology. Those same firms also achieved stronger integration, the collaboration needed to unify the units' efforts, often through dedicated integrating roles and procedures for resolving conflict. Differentiation and integration pulled against each other, and high performers managed both.
On ordinary days, sitting in one room and using one computer-aided dispatch system integrates the units well enough. In surges, the same arrangements fail, because everyone is busy and no role exists whose job is to see the whole picture and set priorities across units.
| Unit | Goal | Time horizon | Integration on ordinary days | Integration in surges |
|---|---|---|---|---|
| Call-taking | Answer fast, gather facts | Seconds | Shared screen, proximity | Overwhelmed; no role coordinates with dispatch |
| Police dispatch | Track units, officer safety | Minutes to hours | Shared software | Works from its own picture of road closures |
| Fire and medical dispatch | Fastest appropriate response | Minutes | Shared software | Separate picture; no joint priority setting |
| Technical services | Keep systems up | Days to months | Ticket system | Busy restoring failed equipment |
Loose Coupling, a Strength and a Weakness
Weick (1976) described educational organizations as loosely coupled systems, in which parts are linked but respond to each other only weakly, slowly or occasionally. Loose coupling, he argued, has advantages: it lets parts adapt locally, prevents a breakdown in one part from spreading and allows the organization to absorb change without total redesign. It also has costs: it makes coordination and system-wide change difficult.
The authority is loosely coupled to its environment's responder agencies. Each county's fire chief, sheriff and road superintendent runs an independent organization with its own priorities, and the authority's links to them are mostly radio and phone. Day to day, this protects the authority from the agencies' internal disputes and lets each work in its own way. In an ice storm, loose coupling becomes paralysis: road crews, utilities and responders all need a shared picture and fast priority decisions, and the loose links cannot carry them.
Which Kind of Fit?
Contingency theory claims that performance depends on fit between an organization's design and its context, but fit can mean different things. One study of fit set out three approaches (Drazin & Van de Ven, 1985). Fit as selection asks whether design features match the context, as when uncertain environments select for flexible structures. Fit as interaction asks whether the combination of context and design affects performance. Fit as a systems approach asks whether the whole pattern of design features is internally consistent and matched to the full set of contingencies, recognizing that there may be several equally effective patterns. In their study of organizational units, the systems approach captured relationships the narrower approaches missed.
The authority's problem is a systems fit failure. No single feature is wrong: protocols, shared software and differentiated units all suit an ordinary day. But the pattern as a whole has no mode for the rare, extreme surge, and adding one feature, such as more call-takers on standby, would not fix integration with dispatch and outside agencies.
A Design for Surges
The design adds three linked features that switch on together. A surge coordinator, a senior supervisor freed from calls, sets priorities across call-taking and both dispatch units and keeps a shared map of closures and incidents. A joint operations channel connects the coordinator with liaisons from the three counties' fire, police and road departments and the electric utility. And pre-agreed triggers, such as more than 120 calls in an hour or a weather service warning, activate both automatically, so no one has to decide in the middle of the storm whether conditions are bad enough.
Limits of the Analysis
Contingency reasoning explains why the design fails in surges, but it treats design as a response to the environment, leaving little room for leaders' choices or for politics. The joint operations channel requires three counties' agencies to agree, and the next modules show that agreement among the founding agencies is the authority's hardest problem.
Conclusion
As an open system facing a mostly stable environment with rare, extreme surges, the authority is well differentiated but integrated only for calm conditions. Lawrence and Lorsch explain why integration must rise with uncertainty, Weick why loose coupling with outside agencies both protects and paralyzes, and Drazin and Van de Ven why the failure is one of overall system fit. A surge mode with a coordinator, a joint channel and automatic triggers supplies the missing integration.
References
Drazin, R., & Van de Ven, A. H. (1985). Alternative forms of fit in contingency theory. Administrative Science Quarterly, 30(4), 514-539. https://doi.org/10.2307/2392695
Lawrence, P. R., & Lorsch, J. W. (1967). Differentiation and integration in complex organizations. Administrative Science Quarterly, 12(1), 1-47. https://doi.org/10.2307/2391211
Weick, K. E. (1976). Educational organizations as loosely coupled systems. Administrative Science Quarterly, 21(1), 1-19. https://doi.org/10.2307/2391875
Reading the EDO 810 Module 4 assignment instructions
Systems and contingency theory is the topic of EDO 810's fourth module, and the paper commonly asks students to analyze an organization as an open system and assess whether its design fits its environment. Your own Module 4 page in the classroom decides the requirements; the authority is invented. Describe the organization's inputs, transformations, outputs and environment. Assess how stable or uncertain the environment is. Map how the organization divides work and how it coordinates. Apply a contingency argument, stating which form of fit you mean. Locate where the design breaks and suggest repairs, drawing on journal research referenced in APA 7 style.
How the EDO 810 Module 4 example is put together
On an ordinary day the authority handles about 1,100 calls; during an ice storm in January it handled 3,400 in eighteen hours, with answer times rising far above standard. The paper maps four differentiated units, call-taking, police dispatch, fire and medical dispatch and technical services, and their goals and time horizons, following Lawrence and Lorsch (Administrative Science Quarterly). Integration on ordinary days relies on proximity and shared software; in surges it fails because no role coordinates across units. Weick (Administrative Science Quarterly) explains why loose coupling with the three counties' responder agencies protects the authority day to day and paralyzes it in a storm. Drazin and Van de Ven (Administrative Science Quarterly) clarify that the problem is a failure of systems fit. The design adds a surge coordinator role, a joint operations channel with responders and pre-agreed triggers for activating both.
EDO 810 Module 4 rubric: what earns full marks
Systems and contingency papers are graded on whether the environment is actually measured and whether the fit argument is precise. This example quantifies the authority's environment with call volumes and shows how variable it is, then maps differentiation and integration unit by unit. Using Weick, it treats loose coupling as both strength and weakness rather than a flaw to eliminate. Drazin and Van de Ven sharpen the analysis by naming which kind of fit is in question, a step many papers skip. The proposed design follows from the specific failure identified: integration mechanisms that work in calm conditions but have no counterpart in surges. The paper notes the limits of contingency reasoning too.
EDO 810 Module 4 help: mistakes that cost marks
Contingency papers often assert that an organization should be flexible or organic without measuring its environment. Use data to show how stable or uncertain conditions are. Another common weakness is describing structure without describing coordination; differentiation without integration is half the analysis. Say which form of fit you mean, since a match between one feature and one contingency differs from a coherent overall design. Do not treat loose coupling as simply bad. Propose design changes that address the specific mismatch you found, and acknowledge that contingency theory can underplay leaders' choices and politics, which later modules address.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More EDO 810 and Doctor of Education sample papers
- EDO 810 Module 1: The Study of Organizations
- EDO 810 Module 2: Classical and Bureaucratic Theory
- EDO 810 Module 3: Human Relations and Behavioral Perspectives
- EDO 810 Module 5: Institutional Theory
- EDO 810 Module 6: Power, Politics and Networks
- EDO 810 Module 7: Organizational Effectiveness
- EDO 810 Module 8: Applying Theory to a Leadership Context
- EDN 810 Module 8: A Leadership Reflection
- EDO 820 Module 1: Leadership Ethics and Its Central Question
- EDO 816 Module 1: Change in Uncertain Environments
- EDN 820 Module 6: Quality Improvement Plan and Measures
EDO 810 Module 4 questions, answered
What does EDO 810 Module 4 usually ask for?
Aspen's EDO 810 covers systems and contingency theory in this module, so analyzing an organization as an open system and assessing the fit between its design and environment is typical. Read your classroom prompt.
What did Lawrence and Lorsch find?
Firms in uncertain environments performed best when their units were highly differentiated and also strongly integrated by coordinating mechanisms.
What is a loosely coupled system?
Weick's term for an organization whose parts are connected but respond to each other only weakly or slowly, which can buffer them or hinder coordination.
Where can I find a free EDO 810 Module 4 sample paper?
Scroll up and the whole paper is there, free: a systems and contingency analysis of an invented 911 authority, with a fit assessment and a design for surges.
What are the forms of fit in contingency theory?
Drazin and Van de Ven distinguished fit as selection, as interaction and as a systems approach that looks at many design features together.