LEAD 6533 Module 4 Team Conflict, Negotiation and Mediation Analysis Example

Release Testing Versus the Launch Date: Diagnosing and Mediating Conflict on a Cross-Functional Launch Team

Student Name

American College of Education

LEAD6533: Team and Group Dynamics

Module 4 Assignment

Instructor Name

May 19, 2031

Introduction

Three papers into this course, the launch team's development, conditions and decision habits have been examined; its disagreements come next. With five months to launch, two conflicts threatened the team. One concerned the work itself: the quality manager at the plant insisted on extended release testing for the first lots, while the marketing director insisted on holding the announced launch date. The other concerned people: after the forecast error described in the previous paper, the sales lead and the marketing director stopped speaking except in meetings. This paper classifies the conflicts, applies research on their effects and describes how each was handled.

Types of Conflict

Jehn (1995) distinguished relationship conflict, interpersonal friction and animosity, from task conflict, disagreements about the content of the work. Her study of work groups found that relationship conflict was consistently harmful to performance and satisfaction, while moderate task conflict could help on nonroutine tasks, where debate improves decisions. Later research added process conflict, disagreements about how work is organized and who does what. The distinction matters because the right response depends on the type: task conflict can be channeled into better decisions, while relationship conflict usually needs to be reduced.

What Later Research Found

Subsequent meta-analyses qualified the early optimism about task conflict. De Dreu and Weingart (2003) reported that disputes over the work, not only personal friction, were linked on average to poorer output and to members who liked their teams less, and that task conflict was especially harmful when it occurred alongside relationship conflict. De Wit et al. (2012), with a larger body of studies, found that task conflict was not consistently related to performance overall though it looked more favorable where personal friction was absent, among senior executive groups and where outcomes were judged by the quality of decisions. The lesson is that task conflict is useful only under conditions that keep it from becoming personal.

Conflict One: Release Testing and the Launch Date

The quality manager's position was that the first three production lots needed extended testing, adding about four weeks before release. The marketing director's position was that the launch date had been announced to distributors and veterinarians and could not move without damaging credibility. Each had legitimate reasons. This was a task conflict, focused on the work, and it was nonroutine, involving trade-offs between regulatory risk, product quality and market commitments. Handled well, it could produce a better plan; handled badly, it could harden into a relationship conflict between the plant and headquarters.

Negotiating on Interests

Fisher et al. (2011) advised negotiators to treat the relationship and the substance separately, look beneath stated demands to the needs behind them, generate several options that could benefit both sides and settle differences by fair standards rather than will. I asked each party to explain what they needed rather than what they demanded. The quality manager's interest was assurance that the first lots met specifications, given the plant's limited history with the new process. The marketing director's interest was keeping faith with customers and capturing the fall shipping season. Neither interest required the other party's exact position.

Options and Agreement

With interests on the table, the subgroup developed options. Testing could begin earlier by running the first lot ahead of schedule as a validation batch. The launch could proceed on the announced date with a limited first shipment to a set of veterinary clinics, while full distribution followed after the extended testing of later lots. Objective criteria, the specification limits and the regulatory requirements, were agreed as the basis for any release. The team adopted a combination: an early validation lot, a phased launch beginning on the announced date and full release when testing confirmed specifications. Both parties said the plan met their core needs.

Conflict Two: The Sales Lead and the Marketing Director

The second conflict was different. After the forecast error became clear, the marketing director implied in a leadership meeting that sales had failed to warn of weak demand, while the sales lead felt she had tried to raise concerns but been ignored. Both felt blamed. Their exchanges in meetings became terse, and other members began avoiding topics that involved both. This was relationship conflict, rooted in a disputed account of what happened, and research suggests it would harm the team's performance if left alone.

Mediating the Relationship Conflict

I acted as an informal mediator, with both parties' agreement. In separate conversations, I listened to each account without judging it. I then held a joint conversation with simple ground rules: each would describe what happened from their view without interruption, then say what they needed going forward. The joint conversation revealed that both believed the other had more information than they did, and that the decision process, not either person, had failed, which the analysis in the previous paper supported. They agreed to a regular one-on-one check-in before forecast updates and to correct the account given in the leadership meeting jointly.

Process Conflict

A third, quieter conflict concerned process. Plant-based members felt decisions were made at headquarters between meetings. Unaddressed, process conflict can feed relationship conflict, as people interpret procedural slights as personal. The team adopted a rule, already suggested by the effectiveness assessment, that decisions affecting more than one function would be made only in scheduled sessions, with plant members present, and recorded in the project log.

Outcomes

Three weeks later, the release testing plan is on schedule, and the validation lot met specifications. The sales lead and marketing director have held four check-ins, and members report that meetings feel less tense. A short pulse survey showed relationship conflict scores dropping from moderate to low, while members still reported vigorous disagreement on task questions, which the research suggests is the healthier combination. The team has not had a new conflict of comparable size, though five months remain before launch.

Lessons for Leading Conflict

Three lessons follow. First, diagnose the type of conflict before acting, because the same intervention can help task conflict and worsen relationship conflict. Second, move quickly to keep task disputes from becoming personal, using interest-based methods that give both sides a stake in the solution. Third, when relationship conflict arises, address it directly and privately before joint conversation, and look for process failures that both parties can blame instead of each other. A leader without formal authority over members must rely on these methods rather than on directives.

Conclusion

The launch team faced a task conflict over release testing and the launch date and a relationship conflict between two senior members after the forecast error, along with a process conflict about where decisions were made. Research distinguishing conflict types and showing that task conflict helps only when it stays impersonal guided the response. Interest-based negotiation produced a phased launch that met both sides' needs, informal mediation repaired the working relationship and a process rule addressed plant members' concerns. The final paper will set out a development plan for the team through launch.

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

de Wit, F. R. C., Greer, L. L., & Jehn, K. A. (2012). The paradox of intragroup conflict: A meta-analysis. Journal of Applied Psychology, 97(2), 360-390. https://doi.org/10.1037/a0024844

Fisher, R., Ury, W., & Patton, B. (2011). Getting to yes: Negotiating agreement without giving in (3rd ed.). Penguin Books.

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