Yes, document a difficult conversation when it involves an agreement, performance concern, safety issue, or recurring conflict. A brief, factual record helps everyone remember what was discussed and what happens next.
Documentation is part of responsible management, especially when emotions are high or several people are involved. Follow your organization’s policy, use approved systems, and keep sensitive information limited to people who need it.
What should I write down after the conversation?
Start with observable details while they are fresh. Record:
- The date, time, participants, and general topic
- Specific observations or examples that were discussed
- The impact on work, customers, coworkers, safety, or deadlines
- The employee’s perspective, including any obstacle or context they shared
- Agreements, expectations, support offered, and who owns each next step
- The follow-up date and what you will review then
Use neutral language. “The report was submitted two days after the agreed deadline” is more useful than “Jordan was careless.” If the conversation included a concern that may involve harassment, discrimination, retaliation, threats, or another serious issue, contact HR or the designated resource promptly and preserve the record according to policy.
Choose Your Attitude gives this process its FISH! lens. Before writing, notice the mood you are carrying from the conversation and decide what attitude will serve the people and the work. That may be steadiness, fairness, curiosity, or respect. The choice is practical: it helps you separate what you observed from the story you are tempted to tell about the person.
The practice also continues after the note is written. If the conversation went poorly, pause before drafting so frustration does not become permanent language. Ask yourself, “Who am I being while I am documenting this?” A leader’s record can either support a clear next conversation or make the person feel judged before that conversation begins.
How can I make the record fair and useful?
Use this short check before saving it:
- Facts: Could another manager understand what happened from the examples provided?
- Balance: Did I include the employee’s explanation and any support discussed?
- Purpose: Does each sentence help clarify expectations, risk, accountability, or follow-up?
- Tone: Would I be comfortable reading the note aloud in a respectful review?
- Next step: Is there a specific owner and date for what happens next?
For example, after a missed handoff, write: “On May 6, we reviewed the missing inventory update, which delayed the afternoon order. Sam explained that the reporting access had failed. I will confirm access by May 8; Sam will send the update by 3 p.m. on May 9. We will review the process on May 12.”
A good record keeps the conversation clear while leaving room for improvement, support, and a fair next step.
Questions like this one, and many more about communication and feedback, are explored in the FISH! Philosophy upgraded trial, which gives your team 30 days of access to the FISH! film and its digital guides.
