One-on-Ones vs Group Meetings: Different Notes, Setup

Most people point one notetaker configuration at every meeting on their calendar and never revisit it. That setup was almost certainly tuned for group meetings, and it serves a one-to-one badly, because the two produce fundamentally different things. A group meeting produces decisions. A one-to-one produces context. A summarizer built to extract the first will reliably flatten the second into something useless, and no amount of re-generating fixes a category error.

Decisions versus context: two different outputs

In a group meeting, the valuable residue is a short list of things that were settled and who owns them. That is a compact, extractable output, and it is what these tools are built for.

A one-to-one is different. What matters is rarely a decision. It is that someone is quietly frustrated with a project, that they mentioned wanting to move toward a different kind of work, that the reason a deadline slipped was a dependency they did not want to name in front of the team. None of that is a decision, and most of it is not even a clearly marked statement. It is context, accumulated over months, and its value is in the pattern rather than any single line.

This is why a generated 1:1 summary so often reads like "discussed workload, career development and current projects." Every word is true and the entire substance is gone.

Why a group-meeting setup fails a one-to-one

Three specific mismatches.

It extracts action items that do not exist. A one-to-one may legitimately produce no tasks at all, and a tool determined to find some will manufacture them from passing remarks. That fills your task list with things nobody committed to, which is the failure covered in turning a transcript into action items people actually do.

It summarizes by topic, not by significance. The tool reports what was discussed and for how long. In a 1:1 the important moment is often ten seconds long and deliberately understated, which is the weighting problem covered in fixing a bad AI meeting summary.

It keeps everything by default. A group meeting record is mostly harmless. A year of transcripts of a colleague's candid conversations about their career and their frustrations is a genuinely different kind of file to be holding.

The case for not recording one-to-ones at all

This is the honest recommendation for a lot of people, and it is worth putting plainly rather than burying.

A one-to-one works when the other person speaks freely. A recorder makes that harder in exactly the conversations where candor matters most: when someone wants to raise a problem, admit they are struggling, or say something about a colleague they would not put in writing. If your one-to-ones are working, a recorder risks the thing that makes them work.

There is also a power asymmetry. Someone who reports to you is the least likely person to object even when they want to. The consent question that raises is covered in telling people you are recording, and it is the reason many managers land on not recording these at all.

Against that, the honest case for recording: if you hold ten one-to-ones a fortnight, you genuinely cannot carry the context, and a searchable record means the thing someone told you in March is not lost by June. That is a real benefit and it is why this is a judgment call rather than a rule.

The middle path most people land on: do not record by default, and take notes yourself. Where a specific conversation is purely practical, such as a working session on a project, recording is unremarkable. Reserve the tool for those.

If you do record: what to change

Do not just leave the group settings on. Four changes:

• Turn off automatic action-item extraction, or plan to delete the invented ones. A 1:1 with no tasks is a normal 1:1.
• Set a short retention period. This is the meeting type where an indefinite archive is least justified and most sensitive. See where your meeting recordings live for how to find and set it.
• Check who else can see it. If your notetaker uses a shared team workspace, a 1:1 transcript may be visible to colleagues by default. Verify this rather than assuming; it is the single most important setting on this page.
• Make stopping normal. Agree with the person that either of you can say "let's not record this one," and make sure it actually happens sometimes. If it never has, the option is not real.

Templates, and why this is where they earn their keep

Templates are usually oversold, but the one-to-one is the case where they genuinely help, because the shape of a useful 1:1 record is stable and it is not the shape of a meeting recap.

A useful structure is closer to: what is going well, what is blocked, what they raised, what I committed to, and anything to follow up next time. That last item is the one that makes a series of one-to-ones cumulative rather than a set of disconnected conversations.

Tools where your own typed notes steer the output suit this far better than pure transcription, because you can mark the significant moment as it happens rather than hoping a summarizer finds it. The human-in-the-loop model described in our guide to Granola is a good structural fit for exactly this reason.

What to keep, and what to delete afterward

Be deliberate, because the default is to keep everything forever.

Worth keeping: what you committed to, anything about their development or goals that you will want in six months, and anything you need to act on. This is usually a short paragraph.

Worth deleting: the full transcript, in most cases. Once you have extracted what matters, a verbatim record of someone's candid conversation has little ongoing value to you and meaningful downside to them.

That practice, keeping a short summary and discarding the raw record, resolves most of the tension in this article. You get the continuity you needed and you are not accumulating an archive of your colleagues' unguarded remarks.

Skip-levels, reviews and the meetings to leave alone

Some conversations should not be recorded regardless of your general policy: performance reviews, anything about compensation, a grievance or complaint, a conversation about someone's health or personal circumstances, and skip-level meetings where the entire purpose is that someone can speak freely about their own manager.

In each case the recording changes the conversation into a different and less useful one, and in several the sensitivity of the resulting file is its own problem. Take notes by hand and keep them where you keep sensitive things.

Tool settings, workspace defaults and template options change with updates. Confirm current behavior in your own tool before relying on any specific detail here. If you are still choosing, the hub guide on how to choose an AI meeting note taker covers the criteria.

FAQ

Should I record one-to-ones with my team?
Many managers choose not to, and that is a defensible default. A recorder discourages candor in the conversations that most depend on it, and someone who reports to you is unlikely to object even if they want to.

Why is my AI summary of a one-to-one useless?
Because it is built to extract decisions and topics, and a 1:1 mostly produces context. The result is an accurate summary like "discussed workload and career goals" that contains none of the substance.

What should I change if I do record one-to-ones?
Turn off automatic action items, set a short retention period, check whether colleagues can see the notes in a shared workspace, and make stopping a normal thing that actually happens.

Can my colleagues see my one-to-one notes?
Possibly. Many notetakers default to a shared team workspace. Check that setting before recording anything sensitive, because it is the one most likely to cause harm.

Which meetings should never be recorded?
Performance reviews, compensation discussions, grievances, anything touching someone's health or personal circumstances, and skip-levels, where speaking freely about a manager is the entire point.