Section 1
Conflicts persist on missing information
Take a familiar case. Sales committed a delivery date. Engineering says nobody consulted them. Sales remembers a Slack thread where an engineer said it was probably fine. Engineering remembers that thread as a caveated guess about a different scope. Both accounts are honest, and neither is complete. Most escalation processes go straight to a ruling: agree a new date, tighten the approval step, move on. The ruling holds until the next similar situation, because the mechanism that produced the failure was never described. Getting each side to lay out its account in sequence, without interruption, is slower and it surfaces the gap that a ruling papers over. The organisational habits that make this possible are the same ones described in [How to Lead Organizational Change Through Storytelling](/blog/how-to-lead-organizational-change-through-storytelling).
Section 2
The restatement test
Before anyone proposes a resolution, each person should be able to restate the other's account well enough that the other agrees it is fair. Not agrees with it. Agrees that it is accurately represented. This is uncomfortable and it works, because it is difficult to hold a caricature of someone's position while being required to voice it accurately. It also exposes where the disagreement actually sits. Often the parties turn out to agree on the events and disagree on a priority, which is a manageable problem. Sometimes they turn out to disagree on a fact that can be checked in five minutes, which several weeks of tension had obscured.
Section 3
Sequence, facilitator, and written record
Three structural choices carry most of the value: each side speaks uninterrupted, a neutral third party holds the sequence, and the agreed account is written down afterwards so it does not drift. Teams that already practise shared storytelling find this easier, which is one reason [Building Community Through Shared Stories](/blog/building-community-through-shared-stories) is a preventive investment rather than a soft one.
Section 4
Running the session without making it worse
Hold it early, while the disagreement is still about the work. Once it has been reframed as a character issue, an account-sharing session becomes a performance in front of a manager. Set the frame explicitly: the goal is a version of events both people accept, not a verdict. Then keep the facilitator out of the content. If the facilitator is also the person who will decide the outcome, both parties will tell the story to the decision rather than to each other. Where that is unavoidable in a small company, separate the two meetings in time so the account-building session is not conducted as an argument for a ruling that follows it immediately.
Section 5
Where this approach does not belong
Shared storytelling is a tool for disagreements between people with roughly equal standing. It is the wrong instrument for harassment, discrimination, safety incidents or anything with a legal dimension, where asking a person to sit and hear the other side's account is itself harmful. Those go to a formal process, immediately. It also fails where one party has already decided the other should leave. The session then becomes documentation rather than resolution, and everyone in the room can tell. Where the underlying disagreement is about whether a change produced results, the argument is usually settled by evidence rather than dialogue, and [Before-and-After: ROI Stories from Automated Startups](/blog/before-and-after-roi-stories-from-automated-startups) is the kind of record that ends it.