| Course | MT340 Conflict Management and Team Dynamics |
|---|---|
| Unit | Unit 7 |
| Paper type | Team development analysis |
| Length | About 1,100 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 MT340 Unit 7
From Silent Reviews to Six Objections a Read: An MT340 Unit 7 Team Development Analysis of a Narrative Team
[Student Name]
Purdue University Global
MT340: Conflict Management and Team Dynamics
Unit 7 Team Development Analysis
[Instructor Name]
[Date]
The studio, team and figures are composite; the models, scale and research cited are real.
Evidence of Change
The narrative team formed fourteen months ago: a lead writer, two senior writers and two junior writers, writing dialogue and story scenes for a role-playing game. Its main ritual is the table read, where a script is read aloud and discussed.
Meeting notes record the number of objections raised aloud at each table read. In the first six months, the average was about one objection per read, and most reads ended with polite approval. In month six, a publisher playtest found that players were confused by the second act, and several playtesters said characters "contradicted themselves." Every scene in that act had passed the table read without objection. After month seven, objections averaged between six and nine per read and stayed there.
The producer also ran an anonymous pulse survey twice, using the seven questions Edmondson (1999) wrote to gauge psychological safety, once in month five and again in month twelve. The team's average rose from 4.1 to 5.6 out of seven.
Testing Tuckman
The four-stage model Tuckman (1965) built from a review of group research places open conflict in its second stage, storming, before a group settles how it will work.
This team's sequence was different. It formed quickly in the first month. It then moved directly to polite norms: reads were courteous, and disagreement was kept private, if it was voiced at all. Open disagreement, which looks like storming, arrived only after month six, and it arrived alongside better work rather than before it. Storming came after norming.
Tuckman's model therefore fits only partly. The stages appeared, but in a different order, and the "norming" stage contained a norm, avoid disagreement, that held performance back.
A Better Fit: A Midpoint Transition
Gersick (1988), studying project teams, found that many did not move through gradual stages. Instead, they kept an early pattern for about half of their time and then changed sharply around the midpoint, often triggered by an external event or deadline. The narrative team's change came after an external shock, the failed playtest, and was abrupt rather than gradual. Gersick's account explains the timing better than Tuckman's.
The team did not argue less as it matured; it argued more, once it learned that silence had a price.
What Changed in the Format
After the playtest, the lead writer changed the table read in three ways.
First, her own pages are read first, and she names one weakness in them before anyone else speaks. Before, her pages had been read last and rarely questioned. Starting with the most senior writer's admitted weakness changed what was safe to say.
Second, a rotating skeptic role was added. At each read, one writer is assigned to find the strongest objection to the script, whatever their own view. The role made disagreement a duty rather than a personal choice, so no writer had to decide alone whether an objection was worth the awkwardness.
Third, objections are recorded on a shared board during the read, with the writer's response beside each. Before, comments were given privately afterward, if at all.
Edmondson (1999) reported that the teams which learned were those whose members believed a mistake would not be held against them, and the team leader's conduct did much to set that trust. The lead writer's change in her own behavior is consistent with that finding.
The Psychological Safety Measure
The rise from 4.1 to 5.6 on Edmondson's scale fits the change in behavior. The largest rise was on the item about taking risks in front of teammates. The smallest was on the item about whether members reject others for being different, which was already high in month five.
An Alternative Explanation
Another explanation is possible: the team argued more because the junior writers had gained experience and confidence, not because the format changed. If so, objections should have come mainly from the junior writers and risen gradually as they grew. The notes show otherwise. Objections rose sharply in month seven, not gradually, and came from all five writers, including the two seniors, who had been silent in the first six months. Experience may have contributed, but it cannot explain a sudden change across the whole team.
A second alternative is that the producer's survey made the team aware of safety and changed behavior on its own. But the survey's first administration came in month five, before the change, and objections did not rise in month six.
The Cost of the Polite Period
The six months of silent reviews had a measurable cost. The confused second act required rewriting fourteen scenes and re-recording dialogue for three characters, about five weeks of the team's time and an unplanned voice-actor budget. Every one of those scenes had passed a table read without objection. In the year since the format changed, no act has failed a publisher playtest for coherence, and the junior writers say they now hear about problems in their pages at the read rather than in a note weeks later.
What the Studio Can Learn
The narrative team spent six months at a polite norm that cost the game a confusing second act. Jehn (1995) found that task conflict can help groups doing nonroutine work, as long as it does not become personal. The narrative team's work is nonroutine, and its early silence suppressed the very task conflict that would have caught the problem. Other teams at the studio, especially the art and level design teams, run review meetings that resemble the narrative team's early format. They might adopt the skeptic role and the lead-first reading without waiting for a playtest to fail.
Limits
The data come from one team's meeting notes, which were kept by different writers at different times. The psychological safety survey had only five respondents, so a single person's change could move the average. The analysis cannot separate the effect of the format change from the effect of the playtest itself.
Conclusion
The narrative team moved from silent reviews to open disagreement, but not in the order Tuckman predicts. Its change came abruptly after an external shock, as Gersick's work suggests, and was sustained by format changes that made disagreement safe and expected. The rise in psychological safety and the evidence from all five writers support that account over the alternatives.
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
Gersick, C. J. G. (1988). Time and transition in work teams: Toward a new model of group development. Academy of Management Journal, 31(1), 9-41. https://doi.org/10.2307/256496
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
Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384-399. https://doi.org/10.1037/h0022100
MT340 Unit 7 instructions, in plain terms
Unit 7 asks students to analyze how a real team developed over time, using models from the reading. The paper should open with evidence that something changed, such as counts from meeting notes or survey results, before offering any explanation. Instructors expect at least one development model to be tested against the team's actual sequence rather than assumed to fit. Where a second model fits better, it should be introduced with its evidence. The analysis should describe what changed in the team's practices and connect those changes to the research. Alternative explanations should be considered and tested against the evidence. A cost or benefit of the change helps show why it matters. Limits, especially small survey samples, should be acknowledged.
How the MT 340 Unit 7 example is put together
The sample opens with counts of objections per table read before and after month six and with the two survey results. Tuckman's model is tested and found to fit only partly, with storming after norming. Gersick's account of midpoint transitions is introduced as a better fit. Three format changes are described, and Edmondson's findings on leaders and learning connect them to the survey, under the highlighted line that the team argued more once silence had a price. The survey items that moved most are noted. Two alternative explanations, growing junior confidence and the survey itself, are tested against the timing. A section prices the polite period at five weeks of rewriting, and Jehn supports lessons for other teams.
Reading the MT340 Unit 7 grading rubric
Team development analyses are typically marked on evidence of change, critical testing of models, connection between practices and research and treatment of alternatives. Papers that assume Tuckman's sequence and fit the team into it miss the unit's purpose. Evidence should be quantitative where possible. A model that fits poorly should be named as such, and a better one offered with reasons. Format or practice changes should be described concretely. Alternative explanations should be tested, not merely listed. Putting a cost on the earlier period shows business relevance. Small samples should be acknowledged. Development models and research belong in APA 7. A timeline helps the reader follow the team's history.
Common MT340 Unit 7 mistakes, and how to avoid them
Development papers often describe a team's history and label each period with one of Tuckman's stages without checking whether the order fits. Another common weakness is offering no evidence that the team actually changed. Some students credit change to a new leader or new members without testing that explanation. Costs and benefits are rarely shown. Before drafting, find a record the team kept over time, such as meeting notes, review comments or survey results, and count something that reflects how the team works. A clear before-and-after count gives the paper its spine and makes the models testable rather than decorative.
Get an MT340 Unit 7 example written to your instructions
Pick a team whose way of disagreeing changed while you were part of it, for better or worse, and note roughly when and why. Attach the Unit 7 instructions and grading rubric. A custom analysis applying your section's development model to that history is returned within 24-48h, and your first request is free. 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 8: Virtual Team Case
- MT340 Unit 9: Facilitation Plan
- MT340 Unit 10: Intervention Proposal
- MT330 Unit 7: Export Landed Cost Model
- MT314 Unit 7: Social Venture Funding Strategy Memo
- MT313 Unit 7: Stakeholder Salience Analysis
- MT304 Unit 7: Technology and Decisions Memo
MT340 Unit 7 questions, answered
Is Tuckman's model required in the Unit 7 analysis?
Many MT340 sections expect it, often alongside a second framework. Tuckman is useful as a vocabulary even when the case departs from its sequence, and a paper that shows where the team diverged from it generally earns more than one that forces a fit. Edmondson's psychological safety research pairs well when the question concerns how disagreement became possible.
What counts as evidence of team development?
Anything observable over time: meeting notes, counts of objections or decisions, survey results taken at two points, or documented episodes before and after a change. Memory alone is weaker, though still usable when described honestly. Two or three kinds of evidence pointing the same way make a far stronger case than a single impression.
Can the analysis cover a team that got worse?
Yes, and some sections welcome it. Development runs in both directions, and a team that lost the ability to disagree safely raises the same analytical questions: what changed, when, and which arrangements caused it. The writing tends to be harder, since it often involves decisions the writer supported at the time.
Where can I find a free MT340 Unit 7 sample paper?
The complete MT340 Unit 7 team development analysis is here, tracing how a narrative team moved from silent reviews to open disagreement.
Which model fits best in the MT340 Unit 7 sample?
Gersick's punctuated equilibrium, since the change came abruptly after a failed playtest rather than through Tuckman's gradual stages.