Resources
Guide · 6 min read

What to write after a feedback conversation

You just had a good, honest conversation with someone on your team. In six days you’ll remember that it went well and almost nothing else. The fix is a five-minute habit most managers never build.

The conversation goes better than you expected. You’d been dreading it for a week, and then the two of you actually talk, and somewhere in the middle the person stops being defensive and says the thing you were hoping they’d see for themselves. You walk back to your desk a little lighter. You think: that mattered. You will remember this.

You will not remember this. Not the shape of it, anyway. In a few days you’ll retain a vague warm residue, a sense that it landed, and maybe one phrase that stuck. What you said and why, the specific example you reached for, the exact thing they agreed to do differently, the small flinch when you got to the hard part, the favor you promised in return so they wouldn’t feel cornered. Most of that evaporates faster than you’d believe. By the time it matters again, you’re reconstructing it from a feeling.

So the work isn’t over when the conversation ends. There’s one more small thing to do, and almost nobody does it: sit down, before you open your laptop to anything else, and write the conversation down.

The five minutes nobody spends

I mean five literal minutes, while the kettle’s still warm. Not a formal record, not something you’d ever show the person. A few honest lines for one reader only: yourself, six months from now, tired, trying to be fair under pressure.

That future reader is the whole reason to do it, and the reason most after-notes are useless. People write to perform, even alone. They reach for the rounded, defensible phrase, the kind of thing that would survive being read aloud in a hearing. “Discussed prioritization; alignment achieved.” That sentence has never once helped anybody. It records that a meeting occurred. It captures none of what the meeting was.

Write for the tired version of yourself instead, and the prose changes. You stop summarizing and start remembering. You write the thing she actually said, not your tidy gloss on it.

What to put down

Start with what you observed, and the specific example that prompted you to raise it. This is the load-bearing part. Not “needs to communicate proactively” but “didn’t flag the vendor delay until the Thursday standup, and by then we’d already promised the client a date we couldn’t hit.” The judgment without the example is a label. The example is the thing you can stand behind later, the thing that survives the person saying when, exactly?

Then what you asked them to do, in the plain words you used, not the upgraded version. Then what they committed to, in their words, which are often narrower or more conditional than you’d like, and that gap is exactly what you want on the record. Then what you promised: the intro you’d make, the cover you’d give them with the wider team, the thing you said you’d stop doing. A feedback conversation is a trade, and you are a party to it. Notes that only track their half are quietly dishonest.

And then the one line that’s easy to skip and worth the most: how they took it. Relief. A jaw that tightened on a particular word. The quick agreement that felt more like wanting the conversation over than actually agreeing. You’re not diagnosing. You’re recording a reaction you witnessed, because next time you raise something hard you’ll want to know which doors open easily and which ones you have to knock on twice.

What to leave out

Just as much craft lives in the restraint. Leave out the speeches you gave yourself in your head and the verdicts about who they are as a person. “Defensive by nature” is not an observation; it’s a sentence you’ve handed down, and it will quietly poison every future note you write about them. Record the behavior and your read of the moment. Let the pattern earn its name across several entries, if it earns it at all.

Leave out anything you couldn’t say to their face. The test is simple: if a line would embarrass you to have them read, the problem is usually the line, not the risk of exposure. A private note is a place to be candid, not a place to be unkind in a way you’d never own.

Why the record beats the impression

Here is what the discipline buys you. Six months on, when you’re writing a review or making a case for someone, you are not fishing in a warm fog for evidence. You have the conversation from February, and the one in April where she’d clearly taken it on board, and the example that proves the arc. You can show movement instead of asserting it. You can be generous with specifics, which is the only generosity that survives scrutiny.

It also protects the people who don’t market themselves. The colleague who quietly fixed the thing and never mentioned it again gets credit, because you wrote it down when it happened, not at review season when the loudest wins are freshest. The record is more honest than memory, and memory always tilts toward whoever talked most recently.

And it changes how it feels to give feedback at all. When you can stand behind what you said because you have the actual record of saying it, you stop second-guessing whether you were fair. You were. It’s written down. That steadiness is hard to fake and impossible to borrow.

This is the unglamorous spine of managing people well, and it’s mostly a writing habit. A private notebook where a manager can jot the line the moment the door closes, file it under that person, and find it whole months later when it matters is roughly the whole idea behind Notivo: it gives your judgment a memory, so the year doesn’t blur into I think she did well. The tool only matters because the habit does.

The conversation will fade by Friday. What you write tonight is the only version that lasts. Make it the true one.

Frequently asked questions

What should a manager write down after giving feedback?

Capture five things while it is fresh: the specific behavior or example that prompted the feedback, the plain words you used to raise it, what the person actually committed to (in their words, not your upgraded version), what you promised in return, and how they took it. The example is the load-bearing part. A dated, behavior-based line is something you can stand behind months later; a label like "needs to communicate more" is not.

How soon after a feedback conversation should I write the note?

Before you open your laptop to anything else. Five minutes while the conversation is still warm beats an hour of reconstruction next week. The specifics that make a note useful (the exact phrase, the small flinch, the precise thing they agreed to) are the first things memory loses. If you wait until review season, you are working from a feeling, not a record.

What should I leave out of a feedback note?

Leave out verdicts about who the person is. "Defensive by nature" is a sentence handed down, not an observation, and it will color every note you write about them afterward. Record the behavior and your read of the moment, and let any pattern earn its name across several entries. A good test: if a line would embarrass you to have the person read it, the problem is usually the line, not the privacy.

Where should feedback notes live so I can find them later?

Keep them per person and dated, so months of conversations sit in one timeline you can read in order. This is what Notivo is built for: type one line, tag the person with @their-name, and it files itself into their timeline automatically. At review time you open the name and read the year instead of fishing for it. Notes are private by default and account-scoped, stored on secured infrastructure (platform-level security, not end-to-end or zero-knowledge encryption).