| Course | MT340 Conflict Management and Team Dynamics |
|---|---|
| Unit | Unit 10 |
| Paper type | Conflict intervention proposal |
| Length | About 900 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT340 Unit 10
Change the Arrangements, Not the Engineer: An MT340 Unit 10 Intervention Proposal for a Game Studio's Late-Stage Disputes
[Student Name]
Purdue University Global
MT340: Conflict Management and Team Dynamics
Unit 10 Intervention Proposal
[Instructor Name]
[Date]
The studio, people and figures are composite; the frameworks and research cited are real.
Why Replacement Would Likely Fail
The disputes the director has in mind are real: arguments over bug severity, over who decides when a feature feels right and over objections that arrive after content lock, when changing course is most expensive. But the diagnosis in Unit 3 and the classification in Unit 2 found the same disputes on teams the lead engineer does not touch, including the narrative and art teams. A new lead engineer would inherit the same arrangements: no written decision rights, no rule for when objections are due and no shared definition of severity. Hackman (2002) argued that leaders often attribute team problems to individuals because people are visible and conditions are not. Replacing a person would change who argues, not why.
The Problem in Three Findings
From earlier units, three findings explain the late-stage disputes.
Process disputes over bug severity recur at every triage because QA and engineering use different definitions of "blocking" (Unit 2).
No one holds authority to decide when a feature feels right, so the creative director's weekly review overrides team decisions after work is done (Unit 3).
Objections from engineering and QA arrive after content lock, often because no one asked for them earlier (Units 2 and 6).
Jehn and Mannix (2001) found that teams performed better when process conflict was low near the end of a project. This studio's process conflict peaks exactly then.
Four Changes
The first change is a decision-rights table. Its purpose is to end arguments about who decides. Its mechanism is a table naming, for five kinds of decision, who decides and who must be consulted. Its owner is the producer.
For feature scope, the creative director decides after consulting the leads. For feel, meaning whether combat or controls feel right, the team lead decides within the measurable definition agreed in Unit 3, after consulting the creative director. For bug severity, QA decides using the shared rubric, after consulting engineering. For schedule changes, the producer decides after consulting the affected leads. For art style, the art director decides after consulting the creative director.
The second change is early objection. Its purpose is to move objections before content lock. Its mechanism is that engineering and QA post written objections to any new concept within three working days of its first appearance in a design document. Objections raised later are heard only if they involve a crash or a certification failure. Its owner is the producer.
The third change is a 48-hour clock. Its purpose is to stop disputes from running for weeks. Its mechanism is that any dispute brought to a lead or the producer runs on a 48-hour clock that ends with the named decider's call, recorded in writing. Its owner is the decider named in the table.
The fourth change is a severity rubric. Its purpose is to end the triage argument. Its mechanism is that QA and engineering co-write a one-page rubric defining blocking, major, minor and cosmetic, with examples from the last game. Its owner is the QA lead and lead engineer together.
Each change removes a question the studio currently argues about from scratch every time it comes up.
Cost
The changes add review time: writing and reading early objections, the 48-hour decisions and rubric upkeep. The producer estimates about 330 added hours per milestone across the studio. Rework caused by late objections and reversed decisions cost about 410 hours on the last milestone, measured from reopened tasks. The proposal should save about 80 hours per milestone if it prevents the rework it targets, and more if it also prevents the morale cost of disputes that turn personal.
Pilot
The changes will run for one milestone, about ten weeks, on all teams. Edmondson (1999) linked team learning to whether people believe they can raise problems without penalty, and early objection depends on exactly that belief; the producer will remind teams that early objections are expected and not a criticism of the designer.
Measures Fixed in Advance
Three measures are fixed now, before the pilot, so the results cannot be chosen afterward.
Reopened tasks after content lock, counted from the task tracker. Baseline: 64 on the last milestone. Target: 35 or fewer.
Severity disputes escalated to the producer, counted from triage notes. Baseline: 19. Target: 6 or fewer.
Days from first objection to decision, averaged across disputes. Baseline: about 11. Target: 2.
If all three targets are missed, the changes will be revisited before the next milestone, and the director's original question can be reopened with better evidence.
Risks
Leads may treat the 48-hour clock as a way to rush decisions they dislike. The decider must explain each call in writing. Engineering and QA may object to everything early to avoid blame later. The producer will review objection volume after four weeks. The creative director may resist the feel decision right. The proposal keeps his consultation in the table and his authority over scope intact.
Scope
Roles and reporting lines stay as they are. The lead engineer stays. The proposal also leaves aside relationship conflicts already present, which the producer will handle individually.
References
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999
Hackman, J. R. (2002). Leading teams: Setting the stage for great performances. Harvard Business School Press.
Jehn, K. A., & Mannix, E. A. (2001). The dynamic nature of conflict: A longitudinal study of intragroup conflict and group performance. Academy of Management Journal, 44(2), 238-251. https://doi.org/10.5465/3069453
MT340 Unit 10 instructions, in plain terms
The final unit calls for a remedy to a recurring conflict, built from the analysis of earlier units. The proposal should respond to whatever the decision-maker has asked, even if it argues for something different. Instructors expect the problem to be stated through findings from earlier analysis, each traced to its unit. Changes should be presented separately, each with a purpose, a mechanism and an owner. Costs should be estimated and set against the cost of the problem. Measures should be fixed before any pilot begins, with baselines and targets. Risks and the proposal's scope should be stated. A pilot period with a defined review point is often expected so the organization can test the changes before committing to them permanently.
Inside the MT340 Unit 10 example
The sample first explains why replacing the lead engineer would likely fail, citing Hackman. Three findings from earlier units define the problem, with Jehn and Mannix on late process conflict. Four changes are described with purpose, mechanism and owner, including a decision-rights table set out in prose for five kinds of decision, under the highlighted line that each change removes a question the studio argues about from scratch. Costs compare 330 added hours with 410 hours of rework. A one-milestone pilot is described, citing Edmondson on speaking up. Three measures are fixed with baselines and targets. Risks are paired with responses, and a short scope section states what stays unchanged.
Reading the MT340 Unit 10 grading rubric
Intervention proposals in MT340 are commonly assessed on responsiveness to the decision-maker, grounding in earlier analysis, clarity of each change, honest costing and measures fixed in advance. Graders reward proposals that answer the question asked before offering an alternative. Each change should trace to a finding. Purpose, mechanism and owner should be clear for every change. Costs should include added time, not only savings. Measures should have baselines and targets set before the pilot. Risks should be specific and answered. Scope limits show focus. Theory and research appear in APA 7. Proposals that recommend team-building activities without changing decision rights or procedures tend to score lower in a unit focused on recurring conflict.
MT340 Unit 10 help: mistakes that cost points
Intervention proposals often skip the decision-maker's actual question and present a favorite solution. Another common weakness is a change with nobody named to carry it out. Some proposals count benefits without counting the time the changes will take. Measures are frequently chosen after results are in, which makes any outcome look like success. Before drafting, list the recurring disputes from your earlier units and, for each, the question people keep arguing about. Each question that could be answered once, in writing, is a candidate change, and its current cost in rework gives the proposal its business case.
Get an MT340 Unit 10 example written to your instructions
Gather what your earlier MT340 units found about the team, along with the Unit 10 instructions and rubric, and note what authority you actually hold. A custom intervention proposal tied to that diagnosis, costed and with measures fixed in advance, is returned within 24-48h. The first sample carries no charge. 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 MT340 papers and BS in Business Administration samples
- MT340 Unit 1: Task Conflict Discussion Post
- MT340 Unit 2: Conflict Classification Exercise
- MT340 Unit 3: Team Effectiveness Diagnosis Paper
- MT340 Unit 4: Conflict Style Assessment Paper
- MT340 Unit 5: Negotiation Preparation Plan
- MT340 Unit 6: Committee Deadlock Seminar Reflection
- MT340 Unit 7: Team Development Analysis Paper
- MT340 Unit 8: Virtual Team Conflict Case
- MT340 Unit 9: Conflict Facilitation Plan
- MT330 Unit 10: International Marketing Plan
- MT314 Unit 10: Social Venture Proposal
- MT313 Unit 10: Corporate Responsibility Target Plan
- MT304 Unit 10: Leadership Policy Proposal
MT340 Unit 10 questions, answered
Does the Unit 10 proposal have to build on earlier units?
Many sections design the final unit that way, and proposals drawing on earlier diagnoses tend to be stronger because every change has a documented cause. Where a section treats Unit 10 as standalone, the proposal still needs a short diagnosis first, since an intervention without a named problem reads as a list of preferences.
How should the proposal handle authority the writer lacks?
Openly. Separate the changes the writer can make or pilot within their role from those that need a manager's approval, and address the approval request to the right person. Readers tend to trust a proposal that knows its limits more than one that assumes powers the writer does not hold.
What measures suit a team process intervention?
Something the change should move directly, such as rework hours or late change requests, plus something about the team itself, such as a validated conflict scale taken before and after. Satisfaction with the change is weaker evidence. Fixing the measures before the pilot begins keeps the evaluation from being chosen to fit the result.
Where can I find a free MT340 Unit 10 sample paper?
The complete MT340 Unit 10 intervention proposal is on this page, offering a game studio four process changes instead of a new lead engineer.
How are results judged in the MT340 Unit 10 sample?
Three measures fixed before the pilot: reopened tasks after content lock, severity disputes escalated to the producer and days from objection to decision.