Most 1:1s start the same way: a recurring invite on the calendar, no agenda, and a vague sense that something useful is supposed to come out of it. Some weeks it does. Other weeks you spend the first five minutes trying to remember what you covered last time, and the conversation never quite recovers.
Usually the meeting just doesn’t have a process behind it yet. A few pieces, decided ahead of time, turn a 1:1 from a loose check-in into something you can run the same way every week, for every person on your team.
Keep a record of what’s said
Start with the part most managers skip: writing down what was said, not what you remember an hour later. Memory is unreliable, and it gets worse the more people you manage. The detail that mattered to one report blurs into the detail that mattered to another, and six months later neither of you can point to when a concern first came up.
A tool for 1:1 meeting insights handles this part for you. It joins the call, records it, and turns the conversation into a transcript and a set of notes tied to that specific meeting, so neither of you has to choose between listening and taking notes.
You can either build your own or buy off the shelf. If you decide to roll your own, Recall.ai is an API for meeting recording that’s used by thousands of companies. It captures recordings, transcripts, and metadata from all major meeting platforms as well as in-person meetings. Recall.ai offers a startup program where early-stage companies can get their first 10,000 hours at a rate of $0.25 an hour.
Decide what each 1:1 is for
Before you fix the format, fix the purpose. A 1:1 with a new hire in their first month is doing different work than a 1:1 with someone who’s been on your team for three years. The first is mostly onboarding and confidence-building. The second is mostly career development and catching problems early.
Write down, for each person, what you want their 1:1 to accomplish over the next quarter. One sentence is enough: get comfortable owning the onboarding project, or figure out whether she wants to move into a lead role. That sentence is what you check the conversation against later, not a script to follow every week.
This matters more than it sounds like it should, because it changes what you listen for. A manager running a 1:1 with no stated purpose tends to default to status updates, since that’s the easiest thing to fill the time with. A manager who’s written down “catch disengagement early” for a specific report will notice a flat answer to “how’s it going” in a way the status-update version of the meeting never catches.
Build a short agenda template
A 1:1 without any structure drifts toward whatever is loudest that week, usually a deadline or a fire that needs putting out. That’s useful information, but it crowds out everything else if nothing else is competing for airtime.
A simple template fixes this without turning the meeting into a form to fill out. Three questions cover most of it: what’s going well, what’s stuck, and one thing the employee wants to raise that isn’t already on your radar. Send the template a day ahead so people can think about the third question instead of answering it cold.
The third question is the one worth protecting most, since it’s the only slot in the meeting that belongs entirely to the employee. Everything else tends to get set by whatever’s urgent that week. Without a reserved spot for it, the topic an employee wants to raise, a frustration with a teammate, an idea for a process change, a question about where their role is heading, can get pushed out for three or four weeks running without either person noticing it happened.
Keep the template the same across your reports so you can compare notes later, but let what fills it in vary completely. The structure is for your own tracking; the conversation itself doesn’t need to follow it word for word.
Turn notes into action items
Notes that sit in a document nobody reopens aren’t worth much more than no notes at all. The useful version of a 1:1 record has two layers: what was discussed, and what happens next because of it.
After each 1:1, pull out anything that needs a follow-up, a promise you made, a resource you said you’d send, a decision you need to check on, and put it somewhere you’ll see it again before the week is out. A task list, a shared doc, whatever system you already use for your own work, works fine. What matters is that a commitment made in a 1:1 shows up again before the next one, instead of only coming back up if the employee happens to raise it twice.
Say you agreed to look into a transfer to another team. If that note lives only in your head, it surfaces again only if the employee brings it up, and by then it can read as a complaint rather than a follow-up on something you already agreed to do. If it lives on a list you check weekly, you’re the one bringing it back, which is a different conversation entirely.
This is also where a written transcript earns its keep. If someone asks months from now whether a raise was discussed, or when a particular concern first came up, you have the actual record instead of two competing memories of the conversation.
Set a cadence for stepping back
Weekly or biweekly 1:1s are good at catching what’s happening right now. They’re not naturally good at showing you the pattern across the last ten meetings: the same blocker coming up for the third time, or a steady drop in how someone talks about their workload.
Pick a point, once a quarter works for most teams, to reread the last few months of notes in one sitting rather than one meeting at a time. That’s a different kind of reading. You’re looking for trends, not individual updates, and trends are exactly what gets lost when each 1:1 only gets compared to the one right before it.
What it takes is deciding, once, what each piece of the 1:1 is for, writing that decision down somewhere durable, and running it consistently enough that it becomes the default instead of something you have to remember to do.