| Course | DIV 5003 Belonging and Inclusion in the Workplace |
|---|---|
| Module | Module 4 |
| Paper type | Constructive disagreement and tension plan |
| Length | 1,220 words, about 4 pages plus title and reference pages |
| Format | APA 7 student paper |
| School | American College of Education |
| Program | M.S. in Organizational Leadership |
| Updated | October 2026 |
Free sample paper for DIV 5003 Module 4
When the Junior Engineer Was Right and the Senior Engineer Was Annoyed: Handling Disagreement in an Engineering Team
Student Name
American College of Education
DIV5003: Belonging and Inclusion in the Workplace
Module 4 Assignment
Instructor Name
September 25, 2028
Introduction
The inclusive review practices introduced in Module 3 did what they were meant to do: in the first month of the pilot, junior and remote engineers spoke more, written comments doubled and two design changes came from engineers outside the senior group. They also produced friction. A senior engineer complained that the new speaking order made reviews feel like a classroom. A junior engineer's alternative design for a bridge approach led to a heated exchange. And a direct written critique by one engineer was read by another as a personal insult. This paper examines those tensions, uses research to separate productive from damaging conflict and sets out how the group will handle disagreement. None of these tensions is unusual, and each offers a lesson for teams opening up their routines.
Two Kinds of Conflict
Jehn (1995), drawing on groups and managers inside a large trucking company, separated task conflict, disagreement about the content of the work, from relationship conflict, personal friction and tension. In that study, personal friction lowered both satisfaction and results, whereas disputes about the work could help groups whose tasks were not routine. Later research complicates the picture. Pooling many later studies, a meta-analysis concluded that disagreement over the work itself does not reliably hurt teams and can help them, particularly when personal friction stays low (de Wit et al., 2012). Trust matters in both directions: following self-managing teams over time, Langfred (2007) found that conflict wore down trust among members, which then changed how the teams organized their work, so unresolved friction can undo the conditions that make disagreement useful.
Incident One: The Speaking Order
The senior engineer's complaint was partly about the practice and partly about status. Being asked to speak last after twenty years of leading reviews felt like a demotion, and the engineer worried that reviews would drag. This is not yet conflict between people, but it could become relationship conflict if junior engineers sense resentment. My response was a private conversation explaining the purpose of the order, asking what would make it work better, and agreeing to apply it only to major design elements, with the senior engineer opening the review by framing the key questions. The engineer's role changed from first speaker to framer and final synthesizer, which preserved standing while keeping the order.
Incident Two: The Bridge Approach
The bridge approach dispute was task conflict at first. A junior engineer, serving as alternatives lead, proposed a retaining wall design that would avoid acquiring a strip of private land. The senior project engineer considered it impractical and said so sharply in the review. The junior engineer pushed back, and voices rose. Afterward, both described the other as disrespectful, showing how quickly task conflict had become relationship conflict. Analysis later showed the junior engineer's design was feasible and saved about $180,000 in right-of-way costs, though it added some construction complexity. The design was adopted with modifications from the senior engineer.
Incident Three: A Critique Misread
The third incident involved two engineers of different backgrounds. One wrote, in a drawing comment, that a drainage calculation was wrong and should be redone. The engineer whose work was criticized, who was trained in a setting where criticism is usually softened and delivered privately, read the comment as a public rebuke. The writer, used to blunt technical feedback, had intended nothing personal. No one was wrong about the calculation's error; the conflict was about how the message was delivered. Such misunderstandings are a predictable cost of a team with varied norms, and they need a shared understanding of how critique will be given. When the two engineers talked it through, the writer offered to add a sentence of context to future comments, and the other agreed to ask directly when a comment seemed harsh rather than assuming intent.
Norms for Disagreement
The group agreed on four norms in a meeting I facilitated. Critique the design, not the designer: comments name the issue and the evidence, not the person. Disagreement is expected, especially in reviews, and is not a sign of disrespect. Written critiques on drawings include a reason and, where possible, a suggested fix. And anyone who feels a disagreement has become personal can ask for a pause and a conversation outside the review. These norms are posted in the review room and summarized in the pre-read template, so they are present when disagreements happen. The group will revisit them after three months to see whether they need adjusting.
A Protocol and Decision Rights
For substantial design disagreements, the group will use a short protocol: each side states its position, the evidence and the main risk of the other option; the group lists what additional analysis would settle the question; and the decision is deferred until that analysis is done, rather than settled by who speaks most forcefully. Decision rights are also made explicit. The licensed engineer of record makes final technical decisions, as professional practice requires, but must record the reasons in the review notes when rejecting an alternative. Clear decision rights reduce the sense that disagreements are contests of status.
Repairing Relationship Conflict
When task conflict turns personal, as in the bridge approach dispute, it needs repair, not just a decision. I met with the two engineers separately and then together, asked each to describe what the other did that felt disrespectful and what they had intended, and helped them agree on how they would raise disagreements in future. Because conflict left unattended erodes trust (Langfred, 2007), rebuilding it also means giving people experience of working through disagreement successfully. Pairing the two engineers on the bridge approach's final design, where they jointly refined the retaining wall, did more for their relationship than any conversation.
What Not to Do
Two tempting responses would make matters worse. The first is to retreat from the new practices because they caused friction, which would tell junior and remote engineers that their participation was welcome only as long as it was comfortable for others. The second is to suppress disagreement by asking everyone to be more positive, which would push task conflict underground, where it tends to resurface as relationship conflict or as quiet disengagement. The goal is not fewer disagreements but better ones: about the work, grounded in evidence, settled by a clear process and repaired when they become personal.
Measures
Progress will be judged three ways. Agreement that people feel comfortable disagreeing in reviews, 45 percent before the pilot, should climb. A short monthly pulse question will ask whether disagreements in reviews felt respectful, with a target of 80 percent agreement. And I will keep a simple log of disagreements that required my involvement, aiming for fewer over time as norms take hold. If relationship conflict rises while task disagreement increases, the norms and protocol will be revisited with the group.
Conclusion
Inclusive practices brought more voices into reviews and, with them, more disagreement. Research distinguishes task conflict, which can improve nonroutine work, from relationship conflict, which harms it, and shows that trust helps keep the first from becoming the second. The group's response, norms for critique, a disagreement protocol, explicit decision rights and active repair when conflict turns personal, aims to keep the benefits of disagreement while limiting its costs.
References
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
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
Langfred, C. W. (2007). The downside of self-management: A longitudinal study of the effects of conflict on trust, autonomy, and task interdependence in self-managing teams. Academy of Management Journal, 50(4), 885-900. https://doi.org/10.5465/amj.2007.26279196
DIV 5003 Module 4 instructions, in plain terms
In DIV 5003's fourth module, students are usually asked how a leader can handle disagreement and tension constructively. Expect to describe real or realistic tensions in a team, especially ones that arise as the team becomes more inclusive. Most prompts want research on kinds of conflict and what makes disagreement productive or damaging. Analyze each tension and propose responses suited to it, such as norms, structured processes, clarified decision rights or direct repair conversations. Many sections also ask how you will know whether the approach is working. Connect the plan to the practices from Module 3, and cite conflict research in APA. Note how status and culture shape each tension. Say what you would avoid doing.
Inside the DIV 5003 Module 4 example
Research comes first in the sample: a field study separating task from relationship conflict, a meta-analysis showing task conflict can help when relationships stay intact and a longitudinal study showing conflict wearing down trust. Three incidents are then analyzed: a status-related complaint answered with a revised role, a design dispute that turned personal before the junior engineer's idea proved sound and a critique read differently across cultures. Four norms, a disagreement protocol, explicit decision rights with recorded reasons and a repair process follow, ending with three measures, including a monthly pulse on whether disagreement felt respectful. Each incident gets its own response. A short section lists two responses to avoid.
Reading the DIV 5003 Module 4 rubric
Disagreement and tension papers earn credit for distinguishing kinds of conflict and responding to each appropriately. Graders look for research applied to specific incidents, not a general discussion of conflict styles. The strongest papers show how inclusion can increase disagreement and how to channel it, with concrete norms, processes and decision rights. Attention to status and cultural differences adds depth. Repair of relationship conflict, and measures to track progress, show follow-through. Plans that aim simply to reduce conflict, or that treat all disagreement as a problem, usually score lower. Conflict research should be cited in APA 7 throughout. Specific incidents matter more than abstract styles. Plans for repair after personal conflict also earn credit.
DIV 5003 Module 4 help from the desk
Conflict papers can turn into lists of conflict styles that never touch a real situation. If you are unsure how to analyze tensions in your team, which research applies or how to design norms and processes that keep disagreement productive, we can help. Describe the tensions you have seen and your module instructions, and our writer will draft a plan that sorts the conflicts by kind and answers each with research-based steps. Engineering, health care, education and corporate teams all fit. A disagreement plan for your team is usually ready within two days. Norms are written in plain words your team can post.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official American College of Education document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More DIV 5003 and M.S. in Organizational Leadership sample papers
- DIV 5003 Module 1: Measuring Workplace Belonging
- DIV 5003 Module 2: Perspectives and Innovation
- DIV 5003 Module 3: Inclusive Collaboration Practices
- DIV 5003 Module 5: Inclusive Communication Strategy
- DATA 5003 Module 5: Data-Driven Recommendation
- SUST 5013 Module 2: Vital Farms Crew Practices
- FIN 5013 Module 3: Working Capital and Cash Cycle
- DATA 5013 Module 4: Focus Groups and Coding
DIV 5003 Module 4 questions, answered
What does DIV5003 Module 4 usually ask for?
In many sections, the fourth DIV5003 module asks how a leader can handle disagreement and tension constructively, often in a team becoming more inclusive.
What is the difference between task and relationship conflict?
Task conflict is disagreement about the work itself; relationship conflict is personal friction. Research links relationship conflict to harm, while task conflict can help under the right conditions.
How does trust affect team conflict?
Research found that trust makes it less likely that disagreements about work will be taken personally and turn into relationship conflict.
Where can I find a free DIV 5003 Module 4 sample paper?
This page includes one: three tensions in an engineering team, from a speaking-order complaint to a bridge design dispute that saved $180,000, with norms, a protocol and repair steps.
Should leaders reduce disagreement in inclusive teams?
Not reduce it but channel it: encourage disagreement about the work, give it structure and step in quickly when it becomes personal.