One-on-One Meeting Notes: What to Write (and What to Skip)

Why notes matter more than the meeting itself

A weekly one-on-one is 30 minutes out of roughly 2,400 working minutes. The meeting alone can't carry your relationship with a report — the continuity between meetings does, and notes are that continuity. When you open with "last week you said the design handoff was grinding — did the new process help?", you've just proven you listened, you cared, and you remembered. No engagement initiative beats that.

Notes also do something your memory can't: surface patterns. One mention of feeling stretched thin is a Tuesday. The same mention three weeks running is a trend — possibly one of the early signs of burnout — and you'll only catch it if past-you wrote it down. Without notes, a year of 1:1s is 52 disconnected chats. With them, it's one long conversation that compounds.

Run two layers: a shared doc and a private one

The most common notes mistake is keeping everything in one place. Keep a single private notebook and your report never sees decisions or commitments written down, so accountability evaporates. Keep a single shared doc and you either self-censor or write things you shouldn't. The fix is two layers with a clear rule for what goes where.

• Shared notes, visible and editable by both of you: the agenda, key topics, decisions made, and follow-ups with owners and dates. This is the official record, and your report should add to it before the meeting. If you don't have a format yet, start from a simple one-on-one agenda template.
• Private notes, yours alone: observations about energy and mood, coaching hypotheses ("I think he avoids conflict with senior engineers — watch for it"), patterns you're tracking across weeks, and reminders to yourself. This is your thinking space, not the record.

The shared layer builds trust and accountability — nobody can misremember who owned what. The private layer makes you a better coach without publishing half-formed theories about someone's inner life.

The four-part note: topics, decisions, follow-ups, signals

After each 1:1, spend 90 seconds capturing four things. That's the entire system.

• Topics — what you actually talked about, in a few words each: "Q3 scope creep, conference talk idea, friction with data team." This is what you'll scan before next week.
• Decisions — anything resolved, with one line of reasoning: "She'll lead the migration; it's a stretch but she asked for it." Six months from now, the reasoning matters more than the decision.
• Follow-ups — who does what by when, specific enough to be checkable: "Me: intro to Priya by Thursday. Her: draft one-pager by next 1:1." Vague follow-ups are where accountability goes to die — there's a whole discipline to tracking action items from 1:1s.
• Signals — the private part: energy, mood, hesitation, what wasn't said. "Flat when we discussed the promo timeline — third week in a row. Ask directly next time."

Topics, decisions, and follow-ups go in the shared doc. Signals go in your private layer. Once the habit exists, the split costs you zero extra effort — and the signals column is where most of your best management moves will come from.

What never goes in your notes

Here's the part most managers learn the hard way: your notes — including the private ones — are discoverable. If there's ever a termination dispute, a discrimination claim, or an internal investigation, anything you wrote about a report can end up in front of HR, lawyers, and a jury. That's not a reason to stop taking notes; managers who consistently document facts are far better protected than managers who wing it. It is a reason to keep five things out entirely:

• Medical or psychological speculation. Never write "seems depressed," "probably burned out," or any armchair diagnosis. You're not qualified, and written health speculation creates real legal exposure. Write observable behavior instead: "Missed two deadlines; said she's exhausted; suggested she take Friday off."
• Protected-class details. Pregnancy plans, religious observance, health conditions, a family member's illness. If a disclosure requires action, note the action, not the disclosure: "Adjusted sprint load through March per our conversation" — not why.
• Character judgments. "Lazy," "difficult," "not leadership material." Behavior with dates survives scrutiny: "Third missed standup this month" is a note; "checked out" is an opinion that will be read back to you.
• Secondhand gossip stated as fact. "Marcus says she's impossible to work with" is hearsay in your handwriting. "Received peer feedback on collaboration; will observe over next two sprints" is documentation.
• A secret performance file. If you're documenting problems, your report should already know the problems exist — that requires a direct, honest conversation, not a hidden dossier. Surprise documentation destroys trust and looks terrible in any dispute.

One more boundary: if your report asks you not to write something down — a family situation, a health matter — honor it. Say "I won't note the details, just that we adjusted the plan." The fastest way to end candor in your 1:1s is for someone to discover their vulnerable moment sitting in a doc. And none of this is legal advice; when in doubt, your HR and legal teams own the specifics.

The five-minute review that makes you look like you never forget

The payoff of notes isn't writing them — it's reading them. Before each 1:1, spend five minutes on three scans:

• Open follow-ups from last time. If you owed something and didn't deliver, open the meeting by saying so. Modeling accountability beats pretending.
• Last week's topics and decisions. Pick one to reopen out loud: "You were going to talk to Sam about the on-call load — how did that land?"
• Your private signals. If you flagged something two weeks ago, this is when you check it: "You've seemed flat the last couple weeks when the roadmap comes up. What's going on there?"

Then, once a month, zoom out: skim the last four to six weeks of notes in one sitting and look for repeats — the same blocker, the same name, the same sigh. Week to week those patterns are invisible; in a monthly skim they jump off the page, and they're usually the agenda for your next career or growth conversation.

This is also where tooling earns its keep. If your notes live across a paper notebook, three Google Docs, and a Slack DM with yourself, the five-minute review takes twenty-five. A tool like Teammons keeps the running shared history in one thread per person, so the scan actually takes five.

How to take notes without killing the conversation

A 1:1 where you type nonstop feels like a deposition. A few mechanics keep the note-taking invisible:

• Jot keywords live, write the note after. During the meeting, capture ten words at most — names, dates, phrases. Then block five minutes immediately after to turn them into the four-part note. Two hours later, half of it is gone; two minutes later, all of it is there.
• Narrate the important writes. When you capture a follow-up, say it out loud: "Writing that down — I owe you the intro by Thursday." It reads as commitment, not distraction.
• On video calls, name what you're doing. Your report can't see your screen, and typing looks like multitasking. One sentence fixes it: "I'm taking notes, not checking email."
• Put the pen down when it gets human. If someone tears up, vents, or shares something raw, stop writing. Capture the signal privately afterward. Nobody wants to watch their bad day get transcribed in real time.

Add it up: 90 seconds of writing after each meeting, five minutes of review before the next. Call it seven minutes per report per week to make every conversation you'll ever have with them compound. Few habits in management pay better.