Resources
Guide · 6 min read

How to prepare a better 1:1

The weekly 1:1 is the most-scheduled and least-prepared meeting on a manager’s calendar. You walk in blank, your report fills the silence with status, and the conversation that mattered never gets had. Here’s how five minutes of memory changes the next thirty.

There’s a particular kind of meeting that happens when neither person prepared. You sit down, you say “so, how’s it going,” and your report, sensing the vacuum, fills it with a recitation of what they’re working on. The deploy went out. The vendor is being slow. The thing from last week is still the thing. You nod. You ask a follow-up that sounds engaged. Thirty minutes later you both leave feeling vaguely productive, and nothing has happened that couldn’t have happened in a two-line message.

This is the default state of the 1:1, and most managers have made a quiet peace with it. The meeting exists, it recurs, it is rarely terrible. But “rarely terrible” is a low bar for the one recurring hour you have with the person whose work and career you’re supposed to be steering. The problem isn’t that you don’t care. It’s that you walk in empty, and an empty manager gets a status update, because status is the thing a nervous report can always produce on demand.

A status update is the failure mode, not the format

Let’s be honest about what a status update is for. It’s for the manager who hasn’t been paying attention and needs to be caught up. The moment your 1:1 becomes a place where you get caught up, you’ve told your report, without saying it, that this is a reporting meeting, and they will calibrate accordingly. They’ll bring you the surface. They’ll bring you the things that are easy to say out loud. They will not bring you the thing they’re quietly worried they’re getting wrong, because that’s not what this meeting is for anymore.

The good version of a 1:1 is the opposite of a status meeting. Status is what you can get from the board, the standup, the pull requests, the channel. The 1:1 is the one place you can get the things that don’t show up anywhere: how they’re actually feeling about the work, where they’re stuck in a way they haven’t admitted, what they want next that they haven’t told anyone, whether the thing you asked for three weeks ago landed as support or as pressure. None of that surfaces if you open with a question that invites a progress report. And you will open with that question if you walk in not knowing anything else to ask.

The five minutes that change the thirty

Here is the entire trick, and it is almost insultingly simple: before the meeting, spend five minutes remembering what has actually happened with this person since you last sat down.

Not “remembering” in the loose, ambient sense, the warm fog of “she’s doing well, I think.” I mean actually reconstructing it. The presentation she gave to the partner team that you heard went sideways. The fact that he picked up the on-call shift nobody wanted and never mentioned it. The offhand thing she said two meetings ago about wanting to do more design work, which you met with “let’s talk about that” and then didn’t. The deadline you moved on them at the last minute and never circled back to acknowledge. The disagreement in the architecture review where they held their position and turned out to be right.

Five of those, specific and dated, and your whole posture changes. You no longer need to ask “how’s it going” because you already half-know how it’s going. You have somewhere real to start. “I heard the partner presentation got rough. What happened in the room?” is a different meeting than “anything you want to talk about?” The first tells your report you were watching, that the hard moment registered, that you’re not going to make them perform a synopsis of their own life for you. The second tells them to start reading the changelog aloud.

What’s actually worth reviewing

Not everything is worth dragging into the room. The standup told you the tickets moved; don’t re-litigate the tickets. What you’re looking for in your five minutes is the stuff that has weight and no natural home: the moments that mattered to them and would otherwise evaporate.

I’d review four things. First, the wins that didn’t announce themselves: the quiet save, the cleanup nobody asked for, the help they gave someone else on the team. The loud wins take care of themselves; the quiet ones are exactly what you’ll have forgotten by review season, and they’re disproportionately done by the people least likely to remind you. Second, the open loops: things they raised that you said you’d handle and didn’t, because nothing erodes trust in a 1:1 faster than a manager who keeps a mental list and then quietly drops it. Third, the friction: the moment in the week where you noticed a flicker (a terse message, a pulled punch in a meeting, a sudden quiet) that you didn’t have time to chase down then. And fourth, the things you changed on them: the reprioritized sprint, the moved deadline, the new stakeholder. People absorb a lot of whiplash silently and resent it privately, and naming it yourself is most of the cure.

You’ll notice none of this is an agenda template. Templates organize a conversation you’re already prepared to have. They do nothing for the manager who arrives knowing nothing, which is the actual disease. A blank agenda with the right five facts behind it beats a beautiful agenda with nothing behind it, every time.

Why this is harder than it sounds

If the fix is this simple, why doesn’t everyone do it? Because the raw material is gone by the time you need it. The presentation that went sideways happened on a Thursday three weeks ago, between two other fires, and the version of you that witnessed it didn’t write anything down. By the time the 1:1 rolls around, that you is unreachable. What’s left is the fog. And the fog is democratic in the worst way. It keeps the loud and forgets the quiet, it holds onto the last thing and loses the middle, and it quietly shortchanges exactly the people who don’t campaign for your attention.

So the real discipline isn’t the five minutes before the meeting. It’s the ten seconds in the moment, when you notice the thing, to put it somewhere you’ll find it again. A single line, tied to that person, dropped wherever you happen to be standing when you see it. This is, more or less, the bet behind Notivo: that if jotting held her ground in the arch review, turned out to be right against someone’s name costs less effort than the thought of doing it, you’ll actually do it, and your five-minute review will have something true to look back on instead of fog. The tool only matters because the habit is hard to keep by hand. The point was never the tool.

The point is that the best 1:1 you’ll ever run isn’t the one with the cleverest questions. It’s the one where the person across from you can tell, in the first sentence, that you remembered them between meetings. That’s most of the job, when you get down to it. Show up knowing, and the conversation that matters will finally have room to happen.

Frequently asked questions

How long does it take to prepare for a 1:1?

About five minutes, if you have something real to look back on. The work is not building an agenda. It is recalling what actually happened with this person since you last met: a quiet win, an open loop you promised to close, a moment of friction, a change you made on them. Find five specifics and your first question stops being “how is it going” and starts somewhere true. The five minutes only work when the raw material exists, which is why a per-person, dated note kept in the moment matters more than any prep ritual.

What should a manager review before a 1:1?

Skip the status the board already tells you and look for the things with weight and no natural home. Four are worth reviewing: the quiet wins that did not announce themselves, the open loops you said you would handle, the friction you noticed but did not chase down, and the changes you made on them like a moved deadline or a reprioritized sprint. Reviewing the last of these and naming it yourself is most of the cure for silent resentment.

How do I stop my 1:1 from turning into a status update?

A status update is what a nervous report produces when the manager walks in empty. The fix is to arrive knowing something. If your first question shows you already half-know how the week went, your report stops reciting the changelog and starts telling you the things that do not show up anywhere: where they are stuck, what they want next, whether your last ask landed as support or pressure. You get there by remembering specifics, not by opening with a question that invites a progress report.

Why do I forget what happened between 1:1s?

Because the moment that mattered happened on a Thursday between two fires and nothing got written down. By the next meeting the fog has set in, and the fog keeps the loud and forgets the quiet, which shortchanges exactly the people who do not campaign for your attention. The real discipline is not the prep before the meeting. It is the ten seconds in the moment to drop one dated line against that person, so your five-minute review has something true to read instead of a blur. A per-person memory like Notivo is built to make that line cheap enough that you actually keep it.