BUSI 610 Week 6 Group DB Forum 3: Part 2 Example

Group Discussion Board Forum 3: Part 2, Replies and Group Response

BUSI 610 Organizational Design and Structure, Group Discussion Board Forum 3: Part 2 (2 replies and the group response)

Thread by [Student Name]

The group, its members' threads and the organizations discussed are composites; the research cited is real, and the requirements follow Liberty's public course guide for BUSI 610.

Reply to Monique

Monique, your thread on the hospital laboratory adopting automated analyzers was a strong example of how technology shapes structure. You argued that automation would let the lab reduce staff and supervision. I agree that much of the work will change, but Perrow's framework suggests that the lab's structure should become more differentiated rather than simply smaller.

Perrow (1967) classified work along two dimensions: task variety, how often unexpected situations arise, and analyzability, whether those situations can be resolved through standard procedures or require judgment and experience. Routine work, with low variety and high analyzability, suits formal rules, centralized control and narrow spans of supervision based on procedures. Nonroutine work, with high variety and low analyzability, suits decentralized decisions, expert staff and flexible coordination. Daft (2016) uses this framework to explain why departments within the same organization often need different structures.

Automation will move most of the lab's testing toward the routine category: samples are loaded, analyzed and reported with little human judgment. But automation also creates new nonroutine work: troubleshooting instrument errors, investigating unusual results, validating new tests and integrating the system with the hospital's records. Those tasks are high in variety and low in analyzability, and they require experienced technologists with the authority to make decisions quickly.

Automation does not make an entire department routine; it often splits the work into a routine core and a more demanding set of exceptions. That suggests a two-part structure: a production unit run with standardized procedures and performance monitoring, and a small technical team of senior technologists who handle exceptions, quality control and system changes, reporting directly to the lab director. Reducing supervision may be right for the first group, but the second will need more expertise and autonomy than the lab has now.

I would also watch the effect on employees. Technologists who spent years doing manual tests may see their skills devalued, and some may welcome moving into the technical team while others prefer the predictability of routine work. Giving people a choice where possible, and training for the new troubleshooting roles, would help the transition. The lab should also expect a period of lower productivity as staff learn the new instruments; budgeting for that dip, rather than counting on immediate savings, will make the change less stressful and more likely to succeed. Clear performance measures for each unit will show whether the split structure is working. How is the hospital planning to retrain the technologists whose manual testing work is being automated?

Reply to Darnell

Darnell, your thread on the regional department store chain that closed half its stores over five years made a vivid case, and I agree that online competition was a major cause. I would push back on the conclusion that the internet alone explains the decline, because research on organizational decline suggests that how leaders respond to external pressure often determines whether decline becomes failure.

Weitzel and Jonsson (1989) described decline as a sequence of stages. In the blinded stage, the organization fails to notice internal or external signs of trouble; in the inaction stage, it notices but does not act; in the faulty action stage, it acts, but in ways that do not address the real problem; in the crisis stage, it faces a critical turning point; and in dissolution, it can no longer recover. They argued that intervention is easiest and most effective in the early stages. Your description of the chain's leaders dismissing online sales as a fad for several years sounds like the blinded and inaction stages, and the later decision to cut store staff to reduce costs, which damaged service, sounds like faulty action.

Cameron et al. (1987) studied colleges and universities facing decline and turbulence and found that decline was associated with a set of internal effects, including centralization of decisions, reduced innovation, more conflict, loss of morale and the departure of capable people. Staw et al. (1981) argued that threats lead organizations to restrict information and concentrate control, relying on familiar routines just when new approaches are needed, a pattern they called threat rigidity. Both studies help explain why the retailer's leaders tightened control and cut costs rather than experimenting with new formats or online sales.

The practical lesson is that decline is partly an organizational problem, not only an environmental one. Many retailers faced the same online competition; the ones that recovered tended to act early, protect the parts of the business customers valued and give a separate team room to build new channels. That comparison suggests the chain's leaders had real choices, which is a more useful conclusion for managers than blaming technology alone, since it points to decisions they could have made differently. Had the chain recognized the threat earlier and created a separate team with authority to build an online business, it might have adapted. What evidence did you find about whether any managers inside the company raised concerns during the early years, and how leadership responded to them?

Group Response: How Technology, Size and Decline Reshape Organizations

Our group's threads examined four organizations shaped by the forces in Daft's chapters on technology, information and control, and size and life cycle: a hospital laboratory adopting automation, a regional retailer in decline, a fast-growing software company adding layers of management, and a logistics firm using data systems to monitor drivers. Despite their differences, our replies led us to four shared principles.

First, technology shapes structure department by department, not organization by organization. Daft (2016) explains that the work of each department can be analyzed separately, and the framework of task variety and analyzability in Perrow (1967) shows why departments within one organization may need different designs. Our discussion of the laboratory showed that a single technology can split a department into a routine core and a nonroutine group handling exceptions. The logistics firm showed the same pattern: route planning became more routine through software, while handling customer problems and disruptions remained nonroutine. The design lesson is to match structure to each kind of work, with standardized procedures where work is routine and expert discretion where it is not.

Second, information technology changes control as much as it changes efficiency, and the choice of how to use it is a design decision. The logistics firm's data systems allowed managers to monitor drivers' locations, speed and stops in real time, which Daft would describe as a shift toward output and behavior control through information systems. Our member who studied the firm found that drivers accepted monitoring for safety but resisted it when used to discipline small delays. The broader point is that technology can make control tighter and more centralized, and leaders must decide deliberately how much of that capacity to use, since tighter control can reduce the discretion that nonroutine situations require. Our group agreed that the firm would do better to use its data mainly to support drivers, for example by rerouting them around delays and flagging safety risks, and to reserve individual discipline for clear patterns rather than single incidents. That approach keeps the benefits of information while preserving drivers' judgment when roads, weather or customers do not follow the plan.

Third, growth brings bureaucracy, and bureaucracy brings inertia. Daft describes how organizations move through life cycle stages, from entrepreneurial to collective, formalization and elaboration, each bringing more rules, specialization and hierarchy. Our software company illustrated this transition: as it grew from 80 to 400 employees, it added managers, formal processes and approval steps that improved coordination but slowed decisions. Hannan and Freeman (1984) argued that the reliability and accountability that formal structures provide are valued by customers and investors, but that the same structures create inertia that makes change difficult. Growth is therefore a trade-off: formalization makes an organization dependable, but it also makes adaptation harder later. Our member who studied the software company recommended formalizing selectively, adopting clear processes for security, billing and hiring, where reliability matters most, while keeping product teams small and free to experiment. The group agreed and added that leaders should review new rules after a year to see whether they still serve their purpose, so that formalization does not accumulate simply because no one removes it.

Fourth, decline is often an organizational failure as well as an environmental one. Our retailer case showed how decline unfolds in stages, from failing to notice warning signs through inaction and faulty action to crisis (Weitzel & Jonsson, 1989). Research found that decline tends to bring centralization, reduced innovation and conflict (Cameron et al., 1987), and that threats can make leaders rigid, restricting information and relying on familiar responses (Staw et al., 1981). Ironically, the responses that feel safest during decline are often those least likely to reverse it. Our discussion suggested that leaders facing decline should deliberately widen the circle of people involved in decisions, protect a small budget for experiments and communicate honestly with employees, precisely because the natural reaction is to do the opposite.

These principles connect. Technology and growth push organizations toward routine and formal structures, which provide efficiency and reliability but also inertia. When the environment changes, as it did for the retailer, that inertia can turn into decline, and decline then pushes leaders toward still more centralization and rigidity. Breaking this cycle requires leaders to create space for nonroutine work and experimentation even in efficient, formalized organizations, for example through separate units with their own structures, deliberate information sharing during threats and periodic review of rules that have outlived their purpose.

Our group also noticed how often the right structure depended on distinguishing between kinds of work. In each case, the mistake would have been to treat the whole organization as one type: to make the whole laboratory routine, to monitor every driver activity the same way, to formalize every process in the software company or to centralize every decision in the declining retailer. Daft's chapters give leaders the concepts to make finer distinctions, and the research we drew on shows the costs of ignoring them.

The work of the group itself illustrated this point. In Part 1, each of us analyzed one organization and tended to describe it as a single type: an automated lab, a declining retailer, a growing start-up, a monitored workforce. Only when we compared cases in Part 2 did the shared pattern appear, that the most important design choices concern the boundaries between routine and nonroutine work inside each organization. We expect to use that lens in our own workplaces, asking which parts of a unit's work have become routine, which still require judgment and whether the structure treats them differently.

In conclusion, technology, size and decline are not simply forces that happen to organizations; they create pressures that leaders can shape, and the earlier those pressures are recognized, the more options leaders have. A laboratory can design a structure for both its automated core and its exceptions, a logistics firm can choose how to use monitoring, a growing company can formalize selectively and a retailer can create room for experimentation before decline becomes crisis. Our group's shared conclusion is that good organizational design anticipates these pressures rather than reacting to them after the fact.

References

Cameron, K. S., Kim, M. U., & Whetten, D. A. (1987). Organizational effects of decline and turbulence. Administrative Science Quarterly, 32(2), 222-240. https://doi.org/10.2307/2393127

Daft, R. L. (2016). Organization theory and design (12th ed.). Cengage Learning.

Hannan, M. T., & Freeman, J. (1984). Structural inertia and organizational change. American Sociological Review, 49(2), 149-164. https://doi.org/10.2307/2095567

Perrow, C. (1967). A framework for the comparative analysis of organizations. American Sociological Review, 32(2), 194-208. https://doi.org/10.2307/2091811

Staw, B. M., Sandelands, L. E., & Dutton, J. E. (1981). Threat rigidity effects in organizational behavior: A multilevel analysis. Administrative Science Quarterly, 26(4), 501-524. https://doi.org/10.2307/2392337

Weitzel, W., & Jonsson, E. (1989). Decline in organizations: A literature integration and extension. Administrative Science Quarterly, 34(1), 91-109. https://doi.org/10.2307/2392987