| Course | BU 502 Leadership and Team Dynamics |
|---|---|
| Unit | Unit 4 |
| Paper type | Conflict episode analysis |
| Length | About 830 words, 6 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for BU 502 Unit 4
Three Trucks for the Last Saturday in March: A Conflict Episode Analysis on a Composite Moving Company's Coordination Team, Including the Lead Who Settled It Badly
Student Name
Business, Herzing University
BU 502: Leadership and Team Dynamics
Instructor Name
April 27, 2026
Three Trucks for the Last Saturday in March: A Conflict Episode Analysis on a Composite Moving Company's Coordination Team, Including the Lead Who Settled It Badly
Bounding the Episode
This paper analyzes one disagreement on the move coordination team described in earlier units. It began at 11:05 a.m. on Thursday, March 12, 2026, when the lead estimator added a three-truck job to Saturday, March 28, a day the senior dispatcher had closed. It ended, in the sense that nobody discussed it openly again, at about 2:15 p.m. the same day. Its effects lasted longer. The parties appear by role. The episode was chosen because it is the clearest instance of the book-first, fit-later pattern identified in Unit 3, and because I took part in it.
The Reconstruction
The sequence below records moves rather than motives. Times come from my log, the board history and the messages I saw. The direct messages between the estimator and the dispatcher are reconstructed from what each showed me afterward, with their agreement.
| Time | Move |
|---|---|
| 8:20 | In the huddle, the senior dispatcher reports that March 28 is closed: nine jobs, every crew assigned, no trucks spare. |
| 10:40 | The lead estimator, surveying a home, offers the customer March 28, the day the customer's house sale closes. |
| 11:05 | The estimator adds the job to March 28 on the board with the note that the customer's date is fixed. |
| 11:20 | The dispatcher messages the estimator that the day is closed and the job has to move. |
| 11:45 | The estimator replies that the date cannot move and that the general manager has approved it. |
| 1:30 | In the Thursday planning session the dispatcher raises the job; the estimator joins by phone. |
| 1:40 | The dispatcher says that adding three trucks means pulling crews from two other jobs or calling a subcontractor, and that it is the dispatcher's name on Saturday when it goes wrong. |
| 1:42 | The estimator says Saturdays may need to be planned differently. |
| 1:43 | The dispatcher stops speaking and leaves the session at 1:50, before it ends. |
| 2:10 | I authorize a subcontracted truck and office overtime and tell the dispatcher to make the day work. |
Three Layers of the Disagreement
The stated issue
On the surface the disagreement was whether one job fit one day. That question had a factual answer, and the answer was no without additional resources. Neither party disputed the facts: the estimator did not argue the day was open, and the dispatcher did not argue the customer's date was movable.
The interests underneath
Fisher et al. (2011) distinguish the positions people take from the interests that lead them there. Each party here said enough to identify their interests without guessing at motives. The estimator said the customer's closing fixed the date and that the general manager had approved it; the interests visible in those words are keeping a promise already made to a customer and keeping a booking that counts toward the estimator's monthly result, as described in Unit 3. The dispatcher said that the change meant pulling crews or calling a subcontractor and that the dispatcher's name would be on the day; the interests visible there are a plan crews can actually run and not being held responsible for failures someone else set up.
The question of standing
Beneath both sat a question nobody asked aloud: who decides what goes on a closed day? Jehn (1997) separated relationship conflict and task conflict from process conflict, disagreement about who does what and how work is coordinated. The March 12 episode began as a task question and was really a process question. The estimator's remark that Saturdays might need planning differently challenged the dispatcher's authority over the plan, and the dispatcher's silence that followed is consistent with hearing it that way. That is an inference from the sequence, and the dispatcher has not said so.
What Kind of Conflict This Was
The episode shows how a process conflict can turn relational. Until 1:42 the exchange was about trucks and crews. After it, the dispatcher's conduct changed in a way that looks relational: for nine working days the dispatcher answered direct questions in the huddle but raised nothing, where the log shows an average of two contributions a morning in the previous five weeks. De Dreu and Weingart (2003) found, pooling many studies, that task conflict, like relationship conflict, tended to go with lower team performance and lower satisfaction among members, which cautions against assuming that a disagreement about work is harmless because it is about work.
My Own Response
Thomas (1992) arranges conflict-handling modes along two dimensions, concern for one's own aims and concern for the other party's. Judged on those dimensions, my 2:10 decision was not a compromise, though it felt like one. I gave the estimator everything the estimator asked for, imposed the cost on the dispatcher and the budget, and told the dispatcher to absorb it. I settled the stated issue with money and settled the question of standing by default, in the estimator's favor, without saying that I was doing so or asking anyone whether that was the right rule.
I also missed the moment that mattered. At 1:43 the conflict was visibly changing character, and I continued the session to the next item. A short pause to name the process question would not have solved it, but it would have shown both parties that the question had been heard. The dispatcher's quiet in the following days is part of the episode's cost, and some of it is mine.
What the Episode Shows
The episode confirms the sequence described in Unit 3 under close observation: an offer made in the customer's home, a post-close addition, an appeal to the general manager and a rescue by the dispatcher paid for by the lead. It adds two things the earlier unit could not see. The pattern produces relational strain, not only evening work, and the lead's habit of resolving such episodes with resources is one of the reasons the question of standing never gets settled. Unit 6 returns to the dispatcher's silence as evidence about psychological safety on the team.
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
Fisher, R., Ury, W., & Patton, B. (2011). Getting to yes: Negotiating agreement without giving in (3rd ed.). Penguin Books.
Jehn, K. A. (1997). A qualitative analysis of conflict types and dimensions in organizational groups. Administrative Science Quarterly, 42(3), 530-557. https://doi.org/10.2307/2393737
Thomas, K. W. (1992). Conflict and conflict management: Reflections and update. Journal of Organizational Behavior, 13(3), 265-274. https://doi.org/10.1002/job.4030130307
BU 502 Unit 4 instructions, in plain terms
Unit 4 in BU 502 asks students to analyze a single conflict episode closely. The instructions typically call for bounding the episode in time, reconstructing it as a sequence of moves, separating the issue people argued about from the interests underneath, applying an attributed conflict framework, and reporting your own conduct honestly. One episode is expected, not a history of a difficult relationship. Episodes that ended badly often make stronger papers because there is more to learn from them. Motives may only be inferred from what people said and did, and the inference should be labeled. A dispute still live at work, or one involving a formal complaint, is better avoided because the paper leaves your control once submitted.
How the BU 502 Unit 4 example is put together
The example opens by bounding the March 12 episode and explaining why it was chosen. A ten-row timeline then records moves from the morning huddle to the lead's decision, with a note on how the private messages were obtained. Three run-in subsections take the layers in turn: the stated question of fit, the interests visible in each party's words, and the process question of who controls a closed day. A short section uses De Dreu and Weingart to show how the episode turned relational, measured by the dispatcher's huddle contributions afterward. The lead's own response is analyzed with Thomas's two dimensions, and the paper closes on what the episode adds to the Unit 3 pattern.
BU 502 Unit 4 rubric: what full points look like
Herzing's rubric for the conflict episode usually awards points for bounding, reconstruction, layered analysis, framework application, self-reflection and writing quality. Bounding gains credit when start, end, trigger and parties are clear. The reconstruction criterion rewards a sequence a reader can follow without the writer's interpretation. Layered analysis is where the higher scores sit, distinguishing positions, interests and underlying questions of standing or workload. Frameworks score when they are attributed and applied to the moves already recorded. Self-reflection carries real weight in graduate grading, rewarding a writer who treats their own response as a decision with consequences. Labeled inference about motives tends to be credited over confident mind reading.
BU 502 Unit 4 help: mistakes that cost points
Conflict papers drop marks when the writer narrates a feud rather than an episode, or tells the reader who was right. Motives asserted as facts are another weak spot; the sample states only what each party said and flags its one inference. Many writers leave themselves out or appear only as a neutral referee, which misses the reflection criterion. Some pick a dispute that is still open at work and write about it in detail, which is risky. Frameworks pasted in at the end without touching the timeline earn little. If your episode is messy, our writers can help you bound it, rebuild the sequence and draft the analysis from your notes.
Get a BU 502 Unit 4 example written to your instructions
Everything we need for Unit 4 sits in the instructions and the BU 502 rubric your classroom carries, plus whichever conflict framework your section teaches. We write a custom example that bounds the episode, reconstructs the moves before assigning motive, separates stated issue from interest and holds the writer to the same standard. First custom sample free, returned in 24 to 48 hours.
More BU 502 papers and MBA samples
- BU 502 Unit 1: Team context and evidence base
- BU 502 Unit 2: Development stage analysis
- BU 502 Unit 3: Behavioral diagnosis
- BU 502 Unit 5: Leadership style assessment
- BU 502 Unit 6: Psychological safety analysis
- BU 502 Unit 7: Intervention design
- BU 502 Unit 8: Team development plan
- BU 525 Unit 4: Critical role identification
- BU 530 Unit 4: Self-assessment with limits
- BU 531 Unit 4: Risk appetite statement
- BU 506 Unit 4: Improvement design
BU 502 Unit 4 questions, answered
Should I pick a conflict that ended badly?
An episode with a clean resolution often gives less to analyze, but a disaster is not required either. The useful choice is one you can reconstruct in detail and one where the stated issue and the real issue clearly differed. Say in a line why the episode was selected, since that reasoning frequently carries part of the criterion.
How do I write about motives without claiming to read minds?
Attribute them as inferences and show the evidence. Writing that a colleague repeatedly returned to who had been consulted, which suggests the concern was standing rather than schedule, is defensible. Writing that the colleague felt undermined is not. The hedge is not weakness here; markers treat a stated inference as more careful work than a confident assertion.
Is a live dispute at work safe to use?
Treat it as off limits while it is active, particularly if any formal process has opened. Grievance records, investigation notes and correspondence held by your organization are its documents, not yours to submit. A concluded episode written from your own recollection, with everybody carried by role and the workplace unidentifiable, keeps the paper defensible and the analysis just as sharp.
Where can I find a free BU 502 Unit 4 sample paper?
A complete BU 502 Unit 4 conflict episode analysis is free on this page, including the minute-by-minute timeline, the three layers and the lead's own conduct, with margin notes. For your episode, email the prompt and a short account and a custom paper comes back free, often within 48 hours.
Should I include my own mistakes in BU 502 Unit 4?
Yes, as decisions with effects rather than as apologies. The sample shows the lead settling the dispute with a subcontracted truck and, in doing so, deciding the ownership question without saying so.