One on one meeting notes: what to write down (and what not to)

A report once asked me what I had written down after our previous 1-1. I could remember the broad topic: she was frustrated about a project. I could not remember the promise I had made at the end of the conversation, and my notes were no help. They said: ‘Talked about platform work. Follow up.’

That note recorded the subject and lost the useful part. Which platform project? What was frustrating? Who had agreed to do what? By when? I had written enough to feel organised and not enough to act like I was.

Good one on one meeting notes are not minutes and they are not a transcript. They are a small bridge between one conversation and the next. Their job is to bring back the context, the commitment, and the question that was still open when the meeting ended.

There are three different kinds of notes

A lot of bad advice starts by treating every written record as the same thing. It is not. Before writing anything, decide which of these three records it belongs in.

• Shared notes. Decisions, agreed actions, links, dates, and an agenda both people can see. Write these as if the other person is reading over your shoulder, because they are.
• Private manager notes. The context you need to prepare well next time: an ongoing career thread, a concern to revisit, your own observation, or a question you did not have time to ask. Private does not mean unrestrained.
• Formal company records. Performance warnings, accommodations, investigations, and anything your company requires HR or legal to handle. Put these in the approved system, not in a personal 1-1 document.

The distinction matters because a private note is still a written record. It may be exported, disclosed, or read months later without the tone of the original conversation. If a sentence would look cruel, speculative, or impossible to defend without your voice explaining it, rewrite it or leave it out.

The one on one meeting notes template

After trying longer formats, I landed on five lines. They fit below each date in the running log. Some meetings need only two of them; a difficult meeting may use all five.

• Context: what changed since the last conversation.
• What mattered: the one or two topics with real weight behind them.
• Their words: a short phrase worth preserving accurately, not a full transcript.
• Commitments: owner, action, and date.
• Next time: the question or thread to reopen.

This is deliberately narrower than my full one on one meeting template. That template describes the permanent page I keep for each report. These five lines are the dated entry I add after a single conversation.

A filled-in example

Here is a fictional example based on a common conversation with a senior engineer. It is specific enough to be useful and short enough that I would actually reread it before the next meeting.

17 Sep. Context: Priya has been covering release coordination since Marco moved teams. What mattered: the interruptions are making the staff project feel impossible; she is not asking to drop it, but needs protected time. Her words: ‘I am doing the senior work and the glue work, and only one of those is visible.’ Commitments: I will move release ownership into the rotation and confirm by Friday. Next time: did the rotation start, and what would make the staff project credible again?

Notice what is not there. There is no judgment that Priya is disengaged. There is no guess about whether she plans to leave. There is no biography of her mood. The note keeps the situation, her meaning, my promise, and the next useful question.

Take fewer notes during the meeting

Typing throughout a 1-1 changes the conversation. The other person watches their words become a record in real time. A pause starts to feel expensive. Something personal gets softened before it is said. Even when you are taking excellent notes, it can look as if you are doing a different job behind the screen.

I write fragments during the meeting only when accuracy matters: a date, a name, or a sentence I promised not to distort. Then I spend two minutes immediately after the call turning those fragments into the five lines above. Immediately matters. After the next Slack message, the sharp edges of the conversation start disappearing.

If you need help getting the conversation moving before there is anything to record, use the one on one meeting questions guide or build a smaller set with the free 1-1 question generator. Do not try to ask twelve good questions in thirty minutes. One honest answer is enough material for a useful note.

What not to write down

The test is not whether a detail is interesting. The test is whether remembering it helps you support the person or keep a commitment. I leave out four categories almost every time.

• Medical or family detail beyond what you need to act with care. ‘Needs flexibility through October’ is usually more useful than a diagnosis or a relative's private history.
• Speculation presented as fact. ‘Seemed quieter than usual; ask how things are next time’ is an observation. ‘Has mentally checked out’ is a verdict you cannot support.
• Labels. Difficult, emotional, low energy, not leadership material. Labels harden a temporary moment into a story about the person.
• Gossip and allegations you have not verified. If something serious needs action, follow the company process. Do not create a shadow investigation in your meeting notes.

I also avoid recording every personal detail just because someone shared it. Remembering that a report has a child starting school can help you ask a human question next month. Keeping a detailed private chronology of their home life does not make you a more attentive manager.

Write commitments so they can close

Most notes fail at the verb. ‘Follow up on promotion’ sounds like an action until two weeks pass and nobody knows what done would have meant. A commitment needs an owner, a visible action, and a date.

• Weak: look into platform opportunities.
• Useful: I will ask the platform EM about a six-week rotation and reply by 24 Sep.
• Weak: revisit workload.
• Useful: Priya will list the recurring release tasks; I will assign owners before Friday planning.

Before the next 1-1, scan the commitments first. Close what is done. Explain what slipped before the report has to ask. Then read the last question you left for yourself. That is enough preparation to make the next meeting feel connected to the previous one.

A note is useful only when it comes back

A perfectly written note that disappears into a folder has no value. The habit has two halves: write for two minutes after the meeting, then reread for two minutes before the next one. Most systems focus on the first half because capture is visible. Trust is built in the second half, when you return with the promise and the context intact.

A document can do this if you keep it tidy and remember to open it. LeaderCues is the version I built when I stopped remembering: a private page per person, dated notes, open follow-ups, and a prep that brings old threads back before the next 1-1. The tool is optional. The return is not.