BUSI 610 Week 1 Group DB Forum 1: Part 1 Example

Group Discussion Board Forum 1: Part 1, Organizational Structure and Strategic Fit

BUSI 610 Organizational Design and Structure, Group Discussion Board Forum 1: Part 1 (thread)

Thread by [Student Name]

The forum prompt and the insurer are composites standing in for the course's own prompt; the research cited is real, and the requirements follow Liberty's public course guide for BUSI 610.

Thread

The organization I chose is a regional property and casualty insurer with about 1,200 employees, and my conclusion is that its structure no longer fits its strategy. For most of its history the company sold auto and homeowners insurance through independent agents in four states, competing on reliable service and careful underwriting. Its structure reflected that strategy: a classic functional design with separate departments for underwriting, claims, actuarial analysis, marketing, information technology and agent relations, each reporting to a vice president and coordinated at the top by the chief executive.

Three years ago the company adopted a new strategy. Facing competition from direct-to-consumer insurers and technology start-ups, it decided to launch digital products quickly, such as usage-based auto insurance priced from driving data and simplified renters' policies sold online, and to update them often. The new strategy requires speed, experimentation and close cooperation among actuaries, underwriters, software developers and marketers. Yet the first digital product took 22 months to launch, twice the plan, because every decision moved up and down separate functional hierarchies, and each department optimized its own goals.

Daft (2016) explains that an organization's structure should be designed to support its strategy and fit its environment. A functional structure suits a strategy of efficiency in a stable environment, because it groups specialists together, develops deep expertise and achieves economies of scale. Its weaknesses are slow response to environmental change, decisions piling up at the top and poor horizontal coordination across departments. Those weaknesses did not matter when the insurer's products changed slowly; they matter a great deal now. Daft's contrast between mechanistic and organic designs captures the shift. Mechanistic organizations, with centralized authority, rigid tasks and vertical communication, work well in stable conditions, while organic organizations, with decentralized decisions, flexible roles and lateral communication, work better when conditions are uncertain. The insurer's environment has moved toward uncertainty, but its design has remained mechanistic.

Research explains why this mismatch slows the company. In their comparison of plastics, food and container companies, Lawrence and Lorsch (1967) found that the high performers in the most uncertain industry did two things at once: they let departments develop distinct goals, time horizons and styles, and they invested heavily in roles and procedures that pulled those departments back together. Strong performers in stable industries needed far less of either. The insurer has the first without the second. Its actuaries think in years and statistical confidence, its developers in two-week sprints, and its marketers in quarterly campaigns. These differences are natural and useful, but without integrating mechanisms they produce conflict and delay. Galbraith (1974) offered a complementary explanation: as uncertainty increases, an organization must process more information to make decisions, and a hierarchy designed for routine work becomes overloaded. His remedies come in two families: cut down what must flow through the hierarchy, for instance by giving each product its own complete unit, or widen the channels that carry it, through liaison roles, task forces and managers whose job is integration.

The insurer's problem is not that its departments are specialized, but that nothing connects them at the speed the strategy requires. My recommendation is a hybrid structure. The company should keep its functional departments for core activities that benefit from specialization and scale, such as claims processing and regulatory compliance, while creating cross-functional product teams for each digital line. Each team would include an actuary, an underwriter, developers, a designer and a marketer, led by a product manager with authority over the product's roadmap and budget. Functional departments would remain the home for professional standards and career development, while product teams would be the home for day-to-day work. This creates a partial matrix, with the familiar risks of dual reporting, so the design should make clear which decisions belong to the product manager and which to the functional heads. For example, the product manager might decide feature priorities, launch timing and marketing spending, while the chief actuary retains authority over pricing models and the head of underwriting over risk acceptance rules, so that faster launches never override sound insurance practice.

An objection is that removing structure will cause chaos. Research suggests the opposite risk is real but manageable. Sine et al. (2006) found that new ventures in emerging, uncertain sectors performed better when they had more formal structure, defined roles, specialization and administrative intensity, not less, because formalization reduced ambiguity and freed founders to focus on strategy. Their finding cautions against equating an organic design with an absence of structure. The product teams I propose would have clearly defined roles, decision rights and metrics; what changes is that the structure is organized around products and customers rather than functions.

Implementation should be gradual, and it should begin, as most redesigns should, with the people who will feel the change most. Functional vice presidents will lose some control over their staff's daily work, and some will experience the change as a loss of status; involving them in designing the product teams and giving them clear roles in setting professional standards can reduce resistance. Employees assigned to product teams will need clarity about who evaluates their performance and how their careers will progress, since uncertainty about promotion ranks high among the frustrations people report in matrix designs. The company could pilot one product team for the usage-based auto product, measure its time to launch, error rates and employee satisfaction against the functional process, and expand the model if it works. Leaders will need to change performance measures, since functional heads currently earn bonuses for departmental efficiency, which discourages them from lending their best people to product teams. Training in collaboration and in managing conflict will also be needed, because the differences in goals and time horizons that Lawrence and Lorsch described do not disappear in a team; they simply become visible earlier, when they can be resolved.

The broader lesson from Daft's opening chapters is that structure is a strategic choice, not a permanent fact. Every structure trades off some advantages for others, and the right design depends on what the organization is trying to do and the conditions it faces. The insurer's functional design served it well for decades. Its new strategy calls for a design that keeps the strengths of specialization while adding the integration that speed requires, and the research suggests that a carefully defined hybrid is more likely to succeed than either the current structure or a sudden move to complete decentralization.

References

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

Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28-36. https://doi.org/10.1287/inte.4.3.28

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

Sine, W. D., Mitsuhashi, H., & Kirsch, D. A. (2006). Revisiting Burns and Stalker: Formal structure and new venture performance in emerging economic sectors. Academy of Management Journal, 49(1), 121-132. https://doi.org/10.5465/amj.2006.20785590