The library-fines team only emails long rebuttals after a disagreement. What should the coach do?
Select an answer to reveal the explanation.
Short Explanation
A twelve-message rebuttal thread is a duel by PDF. The library-fines fight belongs in a live, facilitated conversation where people can hear tone and check meaning. Email just adds another layer of armor.
Full Explanation
When the library-fines team only emails long rebuttals after a disagreement, the coach should move the conflict into a live facilitated conversation instead of growing the email thread. Long rebuttal chains harden positions, invite wider CC warfare, and delay decisions that affect patrons waiting on fine disputes or renewals. Encouraging longer emails so the paper trail becomes the official record mistakes documentation volume for resolution and often inflames tone. Blind-copying the Release Train Engineer on every rebuttal until someone concedes turns the train into a silent tribunal and teaches escalation theater. Banning all talk until the next PI Planning freezes a present conflict across a municipal cycle and lets resentment accumulate. Exam caveat: SASM prefers facilitated live conversation for team conflict over email escalation theater and PI-deferred silence. Operational check: stop the rebuttal chain, schedule a short facilitated session with the people in the disagreement, agree decision criteria for the fines policy or story, and write the outcome once where the team can see it. Verify the email thread ends after the live close, that patron-facing work unblocks, and that the next disagreement starts in a conversation rather than another twelve-message chain.