ORG 726 Week 2 Sociotechnical Systems Theory Example

Optimizing the Software, Neglecting the Adjusters: A Sociotechnical Analysis of an Insurer's Claims Platform

[Student Name]

University of Phoenix

ORG/726: The Impact of Technology on Organizations

Week 2 Assignment

[Instructor Name]

[Date]

Prairie Shield Mutual, its systems, people and figures are composites written for a model paper.

Week 1 described how Prairie Shield Mutual, a composite Midwestern property and casualty insurer, introduced a cloud claims platform and how its Des Moines and Omaha offices organized around it differently. A year later, the technical results are strong in both: settlement times for simple claims fell from 11 days to 4 and cost per claim fell 14 percent. The social results differ. Omaha's adjuster turnover rose from 15 to 31 percent, and its engagement scores fell to the lowest in the company. Des Moines's turnover held at 14 percent. This paper uses sociotechnical systems theory to explain the difference and to recommend changes.

Origins of the Theory

Trist and Bamforth (1951) studied the introduction of the mechanized longwall method in British coal mines. Before mechanization, small, self-selected groups of miners each worked a section of the coal face, sharing all tasks and regulating their own work. The longwall method divided the work into specialized shifts, each performing one task across a long face, with each shift dependent on the previous one. Despite the better technology, productivity disappointed, and absenteeism, conflict and stress rose. The researchers argued that the method had broken the social structure that allowed miners to manage the hazards and uncertainties of the work. Later Tavistock studies found that composite methods, which kept the technology but restored multi-skilled, self-regulating groups, performed better.

The central idea that emerged is joint optimization: a work system has a technical subsystem and a social subsystem, and optimizing one at the other's expense produces worse results than designing both together.

Cherns's Principles

Cherns (1976) set out principles of sociotechnical design. Among them: compatibility, the design process should fit its objectives, so participative designs need participative processes; minimal critical specification, specify no more than is essential; variance control, handle unplanned events as close to their source as possible; boundary location, draw unit boundaries so that people who share knowledge and data work together; information flow, give information to those who need to act on it; and incompletion, recognize that design is never finished.

Applying the Principles

Minimal critical specification. Omaha's locked routing specified exactly which adjuster handles each claim, removing judgment the adjusters had used for years. Des Moines specified routing as a default that adjusters could override with a reason. Omaha over-specified.

Variance control. In claims, variances arise when a claim turns out to be more complex than its score suggests, such as a hail claim that reveals a structural defect. In Des Moines, the adjuster who notices the issue can reroute it. In Omaha, the adjuster must report it to the analyst, who reassigns it, adding about two days and moving control away from the source.

Omaha's platform knows a claim's score; only the adjuster knows what she found in the attic.

Boundary location. Omaha's routing scattered each policyholder's claims across many adjusters, so no one held the whole picture of a customer with several losses. Des Moines's review group formed a boundary around complex claims that kept knowledge together.

Information flow. Omaha's adjusters see their own benchmark scores but not the reasoning behind routing; the analyst sees everything. Des Moines's adjusters see the routing score and can question it.

Compatibility. The platform's configuration team included IT staff, a vendor consultant and two claims managers but no adjusters. The design process did not involve the people whose work it most changed.

Why the Technical Results Hid the Problem

Both offices met the project's targets because those targets measured only the technical subsystem: speed, cost and automation rate. The social costs appeared later, in turnover, engagement and reopened complex claims. Turnover alone cost Omaha about $1.1 million in recruiting and training, roughly offsetting its savings in cost per claim. The project's measures were themselves a product of a technical rather than sociotechnical view.

Later Developments and Critiques

Clegg (2000) restated sociotechnical principles for modern system design and argued that systems should be designed by and for their users, that design choices are organizational choices and that the theory had been underused in large information system projects partly because of its limited tools and its separation from mainstream systems engineering. Critics have also noted that early sociotechnical work focused on manual work groups and gave less attention to power and to how managers' interests shape design. At Prairie Shield, power matters: Omaha's regional manager chose locked routing partly to increase visibility and control, a choice sociotechnical principles question but cannot prevent.

What Des Moines Did Differently

Des Moines did not set out to apply sociotechnical theory, but its choices followed several of its principles. The claims vice president, a former adjuster, insisted before launch that adjusters keep the right to reroute claims. When overrides grew in the first months, senior adjusters began meeting weekly to compare notes, and the meeting became the review group. The group noticed that hail claims on older roofs were consistently under-scored and sent examples to the configuration team, which adjusted the scoring. Adjusters in Des Moines describe the platform as a tool they work with; in Omaha, adjusters describe it as a system that assigns them work. The difference lies less in the software than in the room the design left for people to manage variances and learn.

Risks of the Redesign

Restoring discretion carries risks. Overrides could reintroduce inconsistency that the platform was meant to reduce, and regulators expect similar claims to be treated similarly. Pods could develop their own norms that drift from company standards. These risks argue for review, not for removing discretion: recorded reasons, weekly pod reviews and quarterly comparisons of outcomes across pods would keep variation visible.

Recommendations

Adjuster pods: groups of five to seven adjusters responsible for a geographic book of claims, sharing complex cases and handling variances within the pod.

Override rights with review: adjusters may reroute claims with a recorded reason; a weekly pod review examines overrides and feeds patterns to the configuration team.

Adjusters on the configuration team: two adjusters from each office join the team, rotating yearly.

Information: adjusters see the factors behind each routing score and their pod's results, not only individual benchmarks.

Measures: add turnover, engagement, reopened claims and adjuster use of skills to the platform's scorecard.

Measuring Joint Optimization

To judge whether the redesign works, the company will compare pods with the current arrangement on both subsystems for a year: settlement time and cost per claim on the technical side; turnover, engagement and reopened claims on the social side. If pods hold the technical gains while restoring the social outcomes, the case for extending them to Omaha will be clear.

Conclusion

Prairie Shield's claims platform repeated, in modern form, the pattern Trist and Bamforth found in coal mines: better technology, poorer results where the social system was neglected. Cherns's principles explain why Omaha's design produced turnover and delays and why Des Moines's fared better. Joint optimization, with pods, override rights, adjuster participation and balanced measures, offers a way to keep the technical gains while restoring the social system that makes them last.

References

Cherns, A. (1976). The principles of sociotechnical design. Human Relations, 29(8), 783-792. https://doi.org/10.1177/001872677602900806

Clegg, C. W. (2000). Sociotechnical principles for system design. Applied Ergonomics, 31(5), 463-477. https://doi.org/10.1016/S0003-6870(00)00009-0

Trist, E. L., & Bamforth, K. W. (1951). Some social and psychological consequences of the longwall method of coal-getting. Human Relations, 4(1), 3-38. https://doi.org/10.1177/001872675100400101