ORG 535 Week 5 Conflict and Group Decisions Example

Arguing About the Machine, Not the Person: Conflict and Group Decision Making Over a Plant's New Shift Schedule

[Student Name]

University of Phoenix

ORG/535: People and Organizations

Week 5 Assignment

[Instructor Name]

[Date]

The plant, its supervisors, the schedule options and all figures are composites written for a model paper.

Week 2 found that rotating schedules announced on short notice were a leading reason operators left my Ohio packaging plant, the composite used throughout this course. Moving to fixed shifts became the obvious candidate fix, but it divided the plant's eight-person management team: three shift supervisors, the maintenance manager, the quality manager, the human resources manager, the production planner and me. This paper analyzes the conflict that followed and how the team reached a decision.

How the Conflict Unfolded

At the first meeting, the night supervisor argued for fixed shifts, saying her crews were exhausted by rotating and that absence would fall. The day supervisor, with 26 years at the plant, argued that rotation was fair, since nobody was stuck on nights forever, and that fixed nights would attract only the least committed operators. The planner worried about covering lines if night positions went unfilled. By the second meeting the tone had changed: the day supervisor said the night supervisor was "new and naive," and she replied that he wanted to protect his favorite operators. Two other managers stopped speaking in meetings.

Three Kinds of Conflict

Jehn (1995) distinguished task conflict, disagreement about the content of work, from relationship conflict, interpersonal friction, and found in her study of work units that personal friction tended to go with unhappier members and often weaker results, while task conflict could help on non-routine tasks. A later meta-analysis by De Dreu and Weingart (2003) found that, on average, both kinds of conflict went with poorer team output and lower member satisfaction, with relationship conflict more strongly tied to dissatisfaction, which tempered earlier optimism about task conflict. The schedule dispute began as task conflict over facts and options, turned into relationship conflict within a week and also contained process conflict, since several members felt the decision had already been made by the two loudest voices.

What the Team Did Not Know It Knew

At the first meeting, the team spent most of its time on information everyone already had: plant-wide absence, overtime costs and general complaints. Stasser and Titus (1985) found that group discussion tends to favor information members share in common and neglect information held by only one member, so that groups miss the best option when key facts are distributed. Later it emerged that the human resources manager had exit interview data showing night-shift operators who left cited rotation far more than pay; the planner had overtime data showing that most unfilled positions occurred in rotation weeks; and the quality manager had defect data showing more errors in the first two nights after each rotation. None of it was discussed at the first two meetings.

The best evidence in the room belonged to the people who were not speaking.

The Risk of Groupthink and Polarization

The team was not cohesive enough for classic groupthink, but it showed a related danger: two camps hardening around their first positions. Janis (1982) used the term groupthink for close-knit teams whose wish for agreement overrides honest weighing of the options. Here, dissent was loud but alternatives were not appraised at all; the debate stayed fixed on two options, full rotation or full fixed shifts.

A Structured Process

I paused the debate and proposed a process for the next two weeks. First, each manager brought data relevant to the decision, shared in writing before the meeting. Second, the team agreed on criteria before discussing options: operator retention, coverage of all lines, fairness, quality and cost. Third, the planner developed three options, including a hybrid: fixed shifts with a voluntary rotation pool paid a premium. Fourth, the quality manager acted as devil's advocate, assigned to challenge whichever option led. Fifth, members voted on each option against the criteria and recorded their reasons. Relationship issues were handled separately: I met privately with the two supervisors and asked each to restate the other's best argument.

The Decision

The hybrid scored highest on retention, coverage and quality and acceptably on fairness. The day supervisor supported it because the rotation pool kept an option for operators who preferred variety; the night supervisor supported it because her crews would no longer rotate involuntarily. The team chose it, with a six-month review.

Evaluating the Outcome

Six months later, ninety-day retention rose from 46 to 71 percent, defects in the first nights after shift changes disappeared and the rotation pool filled with 22 volunteers. Relationships improved: the two supervisors now co-lead the new-hire orientation. The decision process took two weeks longer than an immediate vote, a cost worth paying.

Why the Conflict Turned Personal

Looking back, three things pushed the task dispute into personal territory. First, the day supervisor's identity was tied to the rotation system he had helped design twenty years earlier, so criticism of the schedule felt like criticism of him. Second, the night supervisor was new and felt she had to prove herself, so she pressed her case hard in public. Third, I let the first two meetings run as open debates without a process, which rewarded whoever spoke most forcefully. All three point back to the manager's role: conflict about a task stays useful only when people feel their standing is not at stake.

Conflict-Handling Styles

The two supervisors began with competing styles, each trying to win. Two quieter managers avoided the conflict entirely, which is why their data stayed hidden. In the private meetings, I asked each supervisor to restate the other's best argument, which moved them toward a collaborating style, looking for an option that met both sets of concerns. The hybrid schedule was the product of that shift: it kept variety for those who wanted it and ended forced rotation for those who did not.

What It Cost

The structured process took about 24 additional management hours over two weeks, roughly $2,400 in salary time. Delay meant two more weeks of rotating schedules, with perhaps three additional early departures at $4,500 each. Against a decision that has since kept about forty more operators past ninety days in six months, the cost was small.

What the Operators Saw

The conflict was not confined to the conference room. Operators heard within days that the supervisors were fighting over schedules, and rumors spread that fixed nights would be assigned by seniority. Two night-shift operators quit during the dispute, citing uncertainty. Once the decision was made, the team explained it at start-of-shift meetings on every shift, with both supervisors present, and the human resources manager posted the criteria and scores. Several operators later said that seeing the two supervisors present the decision together mattered more than the details.

Recommendations for Future Decisions

Gather data from every member before meeting; agree on criteria first; generate at least three options; assign a devil's advocate; handle personal friction privately; and record the reasons for the decision.

Conclusion

The shift schedule dispute shows how task conflict can turn into relationship conflict and how groups overlook information held by single members. A structured process, data first, criteria before options, a devil's advocate and private repair of relationships, produced a better decision than either original position and left the team working better together.

References

De Dreu, C. K. W., & Weingart, L. R. (2003). Task versus relationship conflict, team performance, and team member satisfaction: A meta-analysis. Journal of Applied Psychology, 88(4), 741-749. https://doi.org/10.1037/0021-9010.88.4.741

Janis, I. L. (1982). Groupthink: Psychological studies of policy decisions and fiascoes (2nd ed.). Houghton Mifflin.

Jehn, K. A. (1995). A multimethod examination of the benefits and detriments of intragroup conflict. Administrative Science Quarterly, 40(2), 256-282. https://doi.org/10.2307/2393638

Stasser, G., & Titus, W. (1985). Pooling of unshared information in group decision making: Biased information sampling during discussion. Journal of Personality and Social Psychology, 48(6), 1467-1478. https://doi.org/10.1037/0022-3514.48.6.1467