| Course | MT260 Group and Organization Dynamics |
|---|---|
| Unit | Unit 8 |
| Paper type | Conflict and cohesion case |
| Length | About 1,140 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT260 Unit 8
Sunday Rides and Job-Board Sniping: A Unit 8 Conflict and Cohesion Case at a Family Bike Shop
[Student Name]
Purdue University Global
MT260: Group and Organization Dynamics
Unit 8 Conflict and Cohesion Case
[Instructor Name]
[Date]
The bike shop, its owner, mechanics and every incident are composite and illustrative; the sources cited are real.
The Crew
Kestrel Cycle Works is a composite family-run bike shop in a mid-sized city. The service department has six mechanics. Four have worked together for eight years or more; two joined in the last three years, hired for their training in electric bike systems. The service manager, the owner's son, assigns repairs from a whiteboard job board. The writer has worked at the shop for six years as a mechanic.
The crew is close. They ride together on Sunday mornings, cover each other's shifts when someone's child is sick, and have a group chat that is mostly photos of bikes and jokes. Customers often comment on how well they seem to get along.
The Question Nobody Raises
The owner has been weighing a change for about a year: stop repairing inexpensive bikes bought from department stores. These repairs tie up a work stand for an hour or more, often because the parts are poor, and earn little, since customers will not pay more than the bike cost. At the same time, e-bike repairs, which pay much better, wait two or three days for a stand. The owner has mentioned the idea to the service manager but has not put it to the mechanics, and no mechanic has raised it with her.
The Incident Log
Over two months, the writer recorded six disputes over the job board, each about who took a complex e-bike repair.
Week 1: a veteran mechanic took an e-bike motor repair the newer specialist expected; service manager reassigned it; short replies in the group chat the next day
Week 3: the specialist took two e-bike jobs in one morning; a veteran said aloud that "some of us are stuck with the junk"
Week 4: argument over whether a battery diagnosis counted as one job or two on the board
Week 6: a veteran left a department-store bike half-finished on a stand to take an e-bike; service manager moved it back
Week 7: the two specialists traded e-bike jobs without telling the manager; a veteran complained
Week 8: dispute over a customer's e-bike that came back for a second repair; each side blamed the other's work
Each dispute was settled by the service manager within minutes and was followed by a day of short replies and fewer jokes in the chat. None reached the question of what work the shop should do.
The Cohesion Profile
Mullen and Copper (1994), in a meta-analysis of studies on cohesion and performance, distinguished three components: interpersonal attraction, commitment to the task and group pride. They found that commitment to the task was the component most strongly linked to performance.
At Kestrel, interpersonal attraction is strong: the crew likes each other and spends free time together. Group pride is strong: the mechanics take pride in the shop's reputation for careful work. Commitment to the task, though, is split. The four veterans see their work as fixing anything that rolls in, a value the shop was built on. The two specialists see the future in e-bikes, which they were hired to handle. The crew agrees on being a good shop but not on what a good shop works on.
Two Kinds of Conflict
Amason (1996), studying top management teams, separated cognitive conflict, disagreement about the substance of a decision, from affective conflict, disagreement that becomes personal. He found that cognitive conflict tended to improve decisions while affective conflict harmed them. Jehn (1995) found a similar distinction between task and relationship conflict in work groups.
The job-board disputes are affective conflict standing in for a cognitive conflict that never happens. The real disagreement is about the shop's direction: whether it should keep doing low-value repairs for loyalty and community, or focus on e-bikes. That is a legitimate cognitive question that the crew could debate with evidence, about revenue per stand hour, customer loyalty and what the veterans' skills are worth. Instead the disagreement leaks out as complaints about who took which job.
They fight about the whiteboard because they will not fight about the shop.
Why the Crew Avoids the Question
The crew's closeness is part of the reason. Raising the department-store question would put the veterans and the specialists on opposite sides of a decision that affects their status and their work, and nobody wants to risk the Sunday rides. Forsyth (2019) notes that highly cohesive groups sometimes avoid open disagreement to protect relationships, which can leave real problems unresolved. The service manager's quick settlements, meant to keep the peace, also keep the question off the table.
Is Cohesion the Problem?
One tempting reading is that the crew is too close for its own good. That would be the wrong lesson. The crew's interpersonal attraction is an asset: it is why shifts get covered, why newer mechanics learned the shop's standards quickly and why customers trust the service department. Mullen and Copper's findings suggest the problem is not too much cohesion but the split in its task component. A crew that liked each other and agreed on what work mattered would likely perform better than this one. The aim is not to make the mechanics less friendly but to let them settle together what kind of shop they are working in.
What the Disputes Cost
The six disputes cost little time directly; each was settled within minutes. Their indirect cost is larger. On the day after each dispute, the writer counted fewer offers of help between veterans and specialists, and twice an e-bike sat waiting while a specialist finished a department-store repair he had been handed in a settlement. Customers do not see the sniping, but they see the wait.
What the Owner Could Do
The owner holds the decision and the information. Putting the question to the whole crew, with figures on revenue per stand hour and wait times for e-bike repairs, would turn the affective conflict back into cognitive conflict about a real choice. The veterans may have strong arguments, such as the loyalty of customers who bring in cheap bikes and later buy good ones. The specialists may have figures on lost e-bike business. A decision made in the open, even one some mechanics dislike, is more likely to end the sniping than six more settlements by the manager.
The Writer's Position
The writer is one of the veterans and has complained about "the junk" on the board. Writing this case made clear that the complaint was really about the shop's future, a conversation the writer has also avoided.
References
Amason, A. C. (1996). Distinguishing the effects of functional and dysfunctional conflict on strategic decision making: Resolving a paradox for top management teams. Academy of Management Journal, 39(1), 123-148. https://doi.org/10.5465/256633
Forsyth, D. R. (2019). Group dynamics (7th ed.). Cengage.
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
Mullen, B., & Copper, C. (1994). The relation between group cohesiveness and performance: An integration. Psychological Bulletin, 115(2), 210-227. https://doi.org/10.1037/0033-2909.115.2.210
Reading the MT 260 Unit 8 instructions
The eighth unit asks students to analyze a group's cohesion and conflict together, using course frameworks. Describe the group and what holds it together, then record its conflicts with dates, causes and how each ended. The prompt usually expects cohesion broken into components, such as Mullen and Copper's attraction, task commitment and pride, and conflict sorted into types, such as cognitive and affective. The best cases show how the two interact: strong cohesion can keep a real disagreement from being raised. Recommendations should address the underlying issue, not just the disputes. About five pages in APA 7, with an incident log and a cohesion profile, is typical, and the writer's own part belongs in it.
How this MT260 Unit 8 example is built
The case introduces the shop, the six mechanics and how close they are. A section names the question nobody raises, whether to stop repairing department-store bikes. The incident log records six job-board disputes and how each ended, with a margin note on settlements that leave the issue untouched. The cohesion profile applies Mullen and Copper's three components and finds task commitment split. Amason and Jehn frame the disputes as affective conflict in place of a cognitive one, with the highlighted line about fighting over the whiteboard. Sections ask whether cohesion is the problem, count the disputes' indirect costs and explain the avoidance with Forsyth. The owner's options and the writer's position close it under a final note.
Where the points sit in the MT260 Unit 8 rubric
Conflict and cohesion cases earn credit for an accurate picture of the group, a dated record of conflicts, correct use of frameworks and insight into how cohesion and conflict interact. Breaking cohesion into components, and showing which are strong or weak, earns more than calling the group close. Instructors reward sorting conflicts by type with evidence, and especially recognizing when surface disputes mask a deeper disagreement. Avoiding the conclusion that cohesion is simply bad shows nuance. Recommendations that bring the real question into the open, with information to decide it, show practical judgment. The writer's own part, clear exhibits and accurate citations complete the marks. Counting the indirect costs of the disputes, such as delayed repairs, strengthens the case that they matter.
MT260 Unit 8 help from the desk
Students often describe a group as either harmonious or conflicted, missing that the two can coexist. Another frequent problem is listing disputes without asking what they are really about. Some papers recommend team-building for a group that already likes each other, which misses the split in task commitment. Others blame the manager who settles disputes without seeing that the settlements keep the real question hidden. Report incidents factually and without names, and log how each ended, since endings show whether the real issue was addressed. Describe your group and its recurring arguments, and a writer can build the incident log and cohesion profile and identify the question behind them.
Get an MT260 Unit 8 example written to your instructions
Is there a question your group has been avoiding, and some smaller argument that keeps recurring instead? Describe both, with a few incidents, and add the Unit 8 prompt and rubric. Built on exactly that material, the custom case is ready within 24-48h; there is no charge for a first one, and the unresolved parts stay unresolved. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More MT260 papers and BS in Business Administration samples
- MT260 Unit 1: Discussion Board Post
- MT260 Unit 2: Group Development Analysis
- MT260 Unit 3: Role and Structure Paper
- MT260 Unit 4: Norms Observation
- MT260 Unit 5: Communication Pattern Study
- MT260 Unit 6: Seminar Reflection
- MT260 Unit 7: Decision-Making Analysis
- MT260 Unit 9: Intervention Proposal
- MT260 Unit 10: Group Analysis Paper
- MT247 Unit 8: Impediment Analysis
- MT246 Unit 8: Resource Assignment Plan
- MT245 Unit 8: Feasibility Assessment
- MT243 Unit 8: Valuation and Pricing Memo
MT260 Unit 8 questions, answered
What if my group has no obvious conflict?
Look for what never gets discussed. Quiet groups often carry a disagreement they avoid because raising it would threaten something members value. Recurring small irritations, meetings where one topic never appears, or decisions always deferred to someone senior can all signal it. The absence of open conflict is sometimes the finding itself, if you can explain it.
Is cohesion always good for a group?
Not always. Research generally links cohesion to performance most strongly when it rests on commitment to the task, and less when it rests mainly on liking. Very cohesive groups can avoid necessary disagreement to protect relationships. A strong case explains which kind of cohesion the group has and what it makes easier and harder for members.
Should the case end with a solution?
Only if the prompt asks for one, and never by pretending the conflict ended when it did not. Many sections give credit for an unresolved disagreement described truthfully, with an explanation of what would be needed to address it. Recommendations, where required, should follow from the analysis rather than from general advice about communication.
Where can I find a free MT260 Unit 8 sample paper?
This page carries the complete MT260 Unit 8 conflict and cohesion case. It analyzes a close bike shop crew whose job-board disputes stand in for an unasked question about the work the shop should do.
Is the crew in the MT260 Unit 8 sample too cohesive?
Not exactly. Their liking for each other and their pride in the shop are strengths. The problem is a split in task commitment, veterans versus e-bike specialists, which their closeness keeps them from discussing openly.