MLDR 6175 Week 2 Conflict Case Description Example

Managing, Mediating, and Resolving Conflict Walden University Free custom sample in 24 to 48h

This MLDR 6175 Week 2 case description example sets out a theater company's stage calendar dispute so that both department heads could read it without objecting. Walden MLDR 6175 asks students to describe a conflict fairly before analyzing it, so the composite case is written as a dated sequence through Pondy's five stages: latent conditions such as a calendar with no owner, the weeks when each head perceived and felt the clash, the manifest staff meeting and an aftermath not yet reached. Each department's account follows in its own vocabulary and at matching length. An appendix lists the verbs used for each party, checking that neither is described with words that imply fault. Jehn on process conflict and Rahim on shaping the conditions of conflict explain why the missing calendar owner is treated as a condition rather than as background, in a description built for the MS in Leadership.

CourseMLDR 6175 Managing, Mediating, and Resolving Conflict
WeekWeek 2
Paper typeCase description
LengthAbout 850 words, 6 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramMS in Leadership
UpdatedOctober 2026

Free sample paper for MLDR 6175 Week 2

1

A Case Description Both Department Heads Could Read Without Objecting: The Lantern Hall Calendar Dispute as a Dated Sequence Through Pondy's Five Stages, With Each Side's Account in Its Own Words

Student Name

Walden University

MLDR 6175: Managing, Mediating, and Resolving Conflict

Instructor Name

Month Day, Year

What this page is doingThe title states the standard the description is written to meet before it names the method.
2

A Case Description Both Department Heads Could Read Without Objecting: The Lantern Hall Calendar Dispute as a Dated Sequence Through Pondy's Five Stages, With Each Side's Account in Its Own Words

Orientation

Lantern Hall Theater Company, a composite nonprofit, runs a 640-seat main stage and a 120-seat studio with 46 staff. Its development department, led by the development director, Celia Marsh, raises about 40 percent of the annual budget through donations, sponsorships and events. Its production department, led by the production manager, Owen Brandt, builds and runs every show, manages the crew and controls the technical schedule. Both report to the managing director, Paul Ainsley. This description sets out the dispute over the week of October 12 as a dated sequence, organized by the five stages of a conflict episode that Pondy (1967) described: latent, perceived, felt, manifest and aftermath.

What this page is doingThe orientation describes both departments by what they are responsible for, without evaluating either.
3

Latent Conditions

The conditions for the dispute existed before anyone disagreed. First, the main stage calendar has no single owner. Development, production, education and rentals each keep their own calendars, and the company manager merges them when asked. Second, on March 4, development confirmed with the season's lead sponsor, a regional credit union, that the annual donor gala would take place on the main stage on Thursday, October 15. At that time, the musical that opens the season had been chosen, but its technical schedule had not been drawn up. Third, the production department's practice, for at least six seasons, has been to close the main stage to outside events during technical rehearsals.

Perceived and Felt Conflict

On June 9, the production department circulated the musical's technical schedule, which set technical rehearsals from October 12 to 18. Owen Brandt saw the conflict with the gala on June 10, when the company manager merged the calendars. He did not raise it with development at that time. On July 21, Celia Marsh learned of the overlap when the company manager asked her about load-in times for the gala. She emailed Owen the same afternoon, writing that the gala date had been "promised to our lead sponsor since March" and asking production to "work around a three-hour evening event." Owen replied on July 23 that the technical week "cannot accommodate outside events" and that the gala "should never have been booked without checking with production." Over the following week, four more emails passed between them, each copied to more colleagues than the last.

What this page is doingEach stage is dated to when it happened, because a date is easier for both parties to check than a motive.
4

Manifest Conflict

The dispute became open at the staff meeting on August 4. When the managing director asked for updates, Owen, according to the minutes, compared development's use of the stage to renting out a hall. Celia answered that production had never considered where the company's money comes from. The managing director ended the discussion and asked both to meet him separately. No decision has been made. The gala invitations are scheduled to go to print on September 1.

Development's Account

From development's side, the gala was booked properly. In March, the stage was free on October 15, and no one had told development that technical rehearsals would fall that week. The credit union's sponsorship, worth about $85,000 this season, depends on the gala taking place on the main stage, where the sponsor's name is on the proscenium. The development director's concern is that moving or shrinking the gala would embarrass the sponsor and the board chair, who personally invited the credit union's president, and would put next season's renewal at risk. Development sees production's position as treating the stage as its own, without regard for the revenue that pays for every production.

What this page is doingEach department's account is written in its own vocabulary and runs to the same length as the other's.
5

Production's Account

From production's side, the technical week is not optional. The musical has 31 scene changes and a crew of 22, and technical rehearsals are when lighting, sound, automation and actors are put together for the first time. Losing an evening means compressing the schedule into longer days, raising overtime costs and fatigue at the point when injuries are most likely. The production manager's concern is that the gala would require striking and reinstalling scenery, adding crew hours and safety risk. Production sees development's position as booking the stage without asking the people responsible for using it safely.

Aftermath, Not Yet Reached

Pondy's aftermath stage, in which a conflict episode leaves conditions that shape the next one, has not yet arrived. Whatever is decided about October 15 will become part of the latent conditions for the next dispute, which is why the description records the conditions in detail. Jehn (1995) found that conflict about how work is organized can damage a group even when the task disagreement is settled; the description therefore treats the missing calendar owner as a condition, not as background. Rahim (2002) argues that organizations manage conflict best by shaping the conditions that produce it, and a calendar with no owner is exactly such a condition.

Word Check

Table 1

Verbs Used for Each Party in This Description

DevelopmentProduction |
confirmed, raises, learned, emailed, responded, seessaw, circulated, replied, said, needs, sees |

Each party's account was checked to ensure neither was described with verbs implying fault, such as "ignored" or "demanded."

References

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

Pondy, L. R. (1967). Organizational conflict: Concepts and models. Administrative Science Quarterly, 12(2), 296-320. https://doi.org/10.2307/2391553

Rahim, M. A. (2002). Toward a theory of managing organizational conflict. International Journal of Conflict Management, 13(3), 206-235. https://doi.org/10.1108/eb022874

MLDR 6175 Week 2 instructions, in plain terms

Week 2 asks you to describe a workplace conflict as fairly as you can before you analyze it. Open with a brief orientation naming the organization, the parties and what each is responsible for, without judging either. Organize the account as a dated sequence, using a model of conflict stages such as Pondy's, so the dispute can be seen developing. Report what people said, quoting where you can. Let each side tell its story in its own vocabulary, with roughly equal space. Finish with a check on your own language, looking for verbs or adjectives that tilt the description toward one side, and correct any you find before submitting.

Inside the MLDR 6175 Week 2 example

The description opens with a paragraph on the theater, its two departments and the managing director. Latent conditions follow: a calendar with no single owner, a gala booked in March and production's long practice of closing the stage during technical rehearsals. Perceived and felt stages are dated to June 10 and July 21, with the emails that followed. The manifest stage reports the August 4 staff meeting from the minutes. Development's and production's accounts appear in matching sections. A short section on the aftermath stage cites Jehn and Rahim. A table lists the verbs used for each party. Each stage carries the date on which it began, so either head could check the sequence against their own email.

MLDR 6175 Week 2 rubric: what earns full marks

Case descriptions are judged mainly on fairness and accuracy. An orientation that describes responsibilities without evaluation earns credit. A dated chronology organized by conflict stages shows method and lets both parties check the account. Quoting what was said, instead of characterizing it, is weighted heavily. Matching accounts for each side, in each side's own vocabulary, demonstrate the neutrality the course expects. A language check that looks for loaded verbs shows care. Descriptions that open with a diagnosis, give one party more space or use words such as "refused" for one side and "explained" for the other tend to score lower. Readers also check that the aftermath stage is treated honestly as not yet reached, rather than filled in with a guess about how things will end.

MLDR 6175 Week 2 help: mistakes that cost marks

Build a timeline first, with dates, using emails, minutes and calendars wherever possible. Then sort the timeline into stages: the conditions that existed before anyone disagreed, when each person noticed the problem, how they felt about it and when it became open. Write each party's account as if they were reading over your shoulder, and keep the two accounts the same length. Finally, list every verb you used for each party and look for patterns. Students often describe their own side's actions with neutral verbs and the other side's with loaded ones without noticing. If you are close to the dispute yourself, our writers can read your draft as an outsider and flag any tilt.

Get a MLDR 6175 Week 2 example written to your instructions

Share the Week 2 prompt and rubric along with the assigned case or a short outline of your own dispute, and the completed description arrives within 24 to 48 hours, with the opening request free. Details that could identify a real workplace can be swapped for neutral ones before sending, and the draft is built on those.

More MLDR 6175 papers and MS in Leadership samples

MLDR 6175 Week 2 questions, answered

Where can I find a free MLDR 6175 Week 2 sample paper?

Every section of the case description, appendix included, is free to read below.

How is the MLDR 6175 Week 2 description organized?

As a dated sequence through Pondy's five stages of a conflict episode.

What latent conditions does it identify?

A stage calendar with no owner, a gala booked before any technical schedule existed and a long practice of closing tech weeks.

How are the two sides presented?

In matching sections, each in its own vocabulary and at similar length.

What does the appendix check?

The verbs used for each party, so neither is described with words that imply fault.