1. Mediation Frame And Limits This session addresses a conflict between a product manager and an engineering lead on a product team, arising during a time-sensitive release. A manager will facilitate an initial informal conversation. Both participants state they want the release to succeed. Stated purpose: clarify communication and decision rights, create a short release working agreement, preserve disputed accounts, and flag any need for HR review. Constraints: this is an informal conversation, not a formal proceeding. Missing information includes: the content and timing of any communication about scope changes, who made the final decision on scope, and whether impact estimates were ever delivered or reviewed. This framework cannot determine who was at fault, whether either party acted appropriately, whether policy was violated, or what disciplinary or employment action (if any) is warranted. 2. Evidence And Perspective Ledger Topic Observed evidence Participant A (Product Manager) perspective Participant B (Engineering Lead) perspective Shared point Unresolved point Missing information Scope changes Project board shows three scope changes in final two weeks Changes were needed after customer feedback Changes arrived late, created unplanned work Scope changed three times late in the cycle Whether timing was reasonable given customer feedback Timestamp/content of customer feedback Notification of engineering No document confirming notification Believes engineering was informed Says changes arrived late without adequate notice — Whether/how notification occurred Communication record (email, chat, meeting) Impact estimates Meeting notes record request for impact estimates, no final decision shown Not specified Not specified A request for estimates was made Whether estimates were delivered, and outcome of any decision Follow-up notes or decision record Release date Shared chat message states release date is fixed Not specified Not specified Release date was communicated as fixed Whether fixed date was reconciled with scope changes Any discussion of date flexibility Formal complaint status No formal complaint filed — — No formal complaint exists — — 3. Neutral Issue Map Communication: Uncertainty about whether/how scope-change information was conveyed to engineering (linked to: absence of documented notification, disputed accounts). Workflow: Impact-estimate request recorded but no decision documented (linked to: meeting notes). Decision rights: Unclear who has authority to approve scope changes near a fixed release date (linked to: project board scope-change entries, chat message on fixed date). Workload: Engineering reports unplanned work resulting from late changes (linked to: engineering lead's stated position; no independent workload documentation supplied). Timing: Three scope changes occurred within final two weeks of a fixed-date release (linked to: project board). Expectations: Differing assumptions about what "informed" means and what triggers a corresponding process (linked to: disputed accounts, no shared definition supplied). 4. Assumption And Escalation Check Unsupported assumptions: That engineering was "informed" in a way both parties would recognize as sufficient; that customer feedback necessitated the specific changes made; that a formal decision was reached on scope after the impact-estimate request. Conflicting accounts: Product manager states engineering was informed; engineering lead states changes arrived late and unplanned. This conflict is preserved, not resolved. Facts needing verification: Content/timing of any communication about scope changes; whether impact estimates were completed and reviewed; whether the fixed release date was formally reaffirmed after scope changes. Escalation triggers: If either participant raises a concern about retaliation, harassment, or safety, or if disagreement about decision-making authority reflects a broader unresolved role/policy question, this should be routed to HR or an appropriate reviewer to determine role definitions — without this framework concluding that such a trigger is proven. 5. Facilitation Priority Register Issue Evidence basis Why it blocks progress Facilitation priority Clarifying question Owner Escalation condition Scope-change notification Project board, disputed accounts Parties disagree on basic facts of communication High "Walk me through what was communicated, when, and through what channel?" Facilitator If evidence suggests a pattern beyond this release, consider HR review of communication norms Decision rights on scope Chat message on fixed date, project board Unclear who approves changes near deadline High "Who has final say on scope changes once a release date is fixed?" Facilitator/Manager If role ambiguity reflects unaddressed organizational policy gap, route to management/HR Impact estimate follow-through Meeting notes Unclear if estimates informed any decision Medium "What happened after impact estimates were requested?" Facilitator None identified from current evidence Workload impact Engineering lead's stated perspective Unverified impact could affect trust Medium "Can you describe the unplanned work in concrete terms?" Facilitator If workload concerns suggest capacity/safety issues, flag for management review 6. Structured Conversation Agenda Opening and norms (5 min): Facilitator states purpose, confidentiality expectations, and ground rules (no interruption, focus on shared goal of successful release). Separate listening time (10 min each): Each participant shares their account without rebuttal; facilitator takes notes only. Fact clarification (10 min): Facilitator reviews project board, meeting notes, and chat message with both parties to establish agreed facts and identify remaining disputes. Issue framing (10 min): Facilitator names issues neutrally (communication, decision rights, workflow) without assigning fault. Option generation (15 min): Both parties propose options for future scope-change communication and decision processes. Agreement testing (10 min): Facilitator checks proposed options against both parties' constraints and the release timeline. Follow-up (5 min): Agree on a check-in date and any next steps, including whether further review is needed. 7. Working Agreement Draft Outline Shared objective: Successful release completion with clearer scope-change communication. Behaviors or process changes: e.g., defined channel and timing for scope-change notifications; agreed decision point for changes once release date is fixed. Owners: To be assigned by participants during the session. Timing: To be defined relative to remaining release schedule. Check-in method: e.g., brief sync at a defined interval before release. Evidence of progress: e.g., documented scope-change log with timestamps and sign-off. Unresolved questions: Whether prior communication was adequate; whether this reflects a broader process gap needing HR or management attention. 8. Facilitator And Reviewer Brief Supported by evidence: Three scope changes occurred in the final two weeks; a request for impact estimates was recorded without a documented final decision; a fixed release date was communicated via chat; no formal complaint has been filed. Disputed: Whether engineering was adequately informed of scope changes; whether resulting work was reasonably foreseeable or unplanned. Top questions: What communication occurred and through what channel? Was a decision made after the impact-estimate request? Who holds authority over scope changes near a fixed date? Information to request: Any written or chat record of scope-change communication; any documentation of the impact-estimate outcome. Questions for qualified reviewers: Should this be treated as an isolated incident or does it indicate a broader need for a documented change-control process? (No conclusion reached here.) This is a neutral mediation-preparation framework, not an investigation, HR determination, employment decision, legal opinion, medical assessment, or mental-health advice. Qualified professionals must handle formal review and decisions.