A project handoff has gone wrong, and the preparation note begins, “We need to talk about your attitude.” That opening does not identify the work issue or the information needed to understand it. It also introduces a judgment before the other person has described their account.
In the fictional example below, two teams expected different people to send a final project file. The file was not sent when expected. Preparing for the conversation means identifying the event, the uncertainty and the question that needs answering. It does not mean deciding in advance who is at fault or scripting a confession.
Describe the work issue without a character label
Write a description that another person could connect to a specific event. In the example, the project file was expected by the receiving team on Thursday afternoon, but the shared record contains no completed handoff at that time. Check the record and the stated expectation before using either in the discussion.
Then separate the event from labels about the people involved. “Nobody took ownership” is an interpretation. It may conceal several different questions: whether responsibility was assigned, whether the assignment was understood and whether the file was ready to send.
A useful opening identifies the subject: “I want to understand what happened with Thursday's file handoff.” The wording is direct without claiming an explanation. If the issue falls within a formal workplace process, use the responsible team's guidance rather than treating a general conversation example as a substitute.
List what you know and what you need to ask
Make two brief lists. The first contains the information you can trace to a record or direct observation. The second contains what you need to clarify. Keep second-hand reports attributed to their source rather than moving them into the first list as established facts.
For the fictional handoff, the manager may have a message asking for the file and a later message saying it has not arrived. Neither message necessarily establishes who accepted responsibility for sending it. That missing agreement is a question to investigate.
Check for information that could change your initial view. An approval may have remained pending, a file may have been sent through a different agreed route or the expected time may never have been confirmed. These are possibilities to ask about, not alternative explanations to declare true before the conversation begins.
Prepare an open question about the work
Start with a question that allows the other person to describe the sequence. “What was your understanding of the handoff arrangement?” is different from “Why did you ignore the handoff?” The latter assumes both responsibility and a motive.
Listen for the details relevant to the work issue. If the person describes waiting for approval, ask which approval they understood was needed and what happened next. Keep the follow-up close to their account instead of introducing a theory about another team's behavior.
Ask one question at a time. A question that combines responsibility, timing, intent and consequences can be difficult to answer clearly. If a point remains uncertain, name the uncertainty and return to it. The aim is to understand the reported work process, not to obtain agreement with every sentence in the preparation note.
Distinguish listening notes from decisions
Record the person's account as their account. A statement that they believed another team owned the handoff is relevant context; it does not by itself establish what the other team agreed. Keep those two questions distinct in the note.
If a record needs checking, identify the record and the reason for the check. Avoid turning a tentative recollection into a definitive sequence because the meeting summary needs to be concise. The summary can preserve uncertainty in a short, accurate sentence.
Separate this listening record from any decision that belongs to an authorized process. A discussion note should not silently become a disciplinary finding or an assessment of someone's character. If the issue requires formal review, retain the relevant information through the appropriate route and let the responsible people determine the next step.
Record the next step that was actually agreed
Before ending, identify what the conversation actually resolved. In the fictional example, the teams might agree to confirm the sender in the next project handoff record. That can be documented without pretending it answers every question about the earlier event.
Record who agreed to do what, any agreed timing and what remains open. Read the proposed summary back in ordinary language so inaccuracies can be corrected. Do not add a deadline afterward merely to make the note look more complete.
At the next check, look for the agreed action rather than assuming the conversation produced a lasting change. This article's questions and record structure are original fictional examples, not claims about exact product contents. They offer a way to prepare a work discussion around a clear question and a faithful account of the answer, without promising that one conversation will resolve a conflict.
Review the Difficult Conversations Toolkit and its listed format and scope.