How to Prepare for a 1:1: Start With the Last One

Short answer: most advice on how to prepare for a 1:1 is really advice on writing an agenda. The agenda is the easy part, and it should mostly belong to your report. The prep that changes the meeting takes ten minutes and looks backward: what you promised last time, what they raised that you haven't dealt with, what keeps coming up, and the one question you'll ask and then actually wait for.

Here's the uncomfortable truth about 1:1s: your report remembers the last one better than you do. You had six of them that week. They had one. If you said "I'll look into the on-call rotation," they've been waiting for two weeks to see whether you meant it.

So preparing for a 1:1 is mostly remembering the last one.

Step 1: Check what you owe them (3 minutes)

Before anything else, list what you said you'd do. "I'll get you feedback on the promo case." "Let me talk to finance about the headcount." "I'll introduce you to the platform lead."

For each one: done, in progress, or forgotten. If it's forgotten, either do it before the meeting or open the 1:1 by saying so. "I said I'd talk to finance and I haven't. I'll have it by Friday." That sentence costs ten seconds and buys back more trust than anything else you'll say that hour.

Managers usually skip this step, because the commitment was made casually, at the end of a meeting, out loud, and never written down. That's the commitment your report remembers.

Step 2: Reread what they raised (3 minutes)

What did they bring up last time that you didn't resolve? Not the status updates. The concerns. "The design review keeps slipping." "I'm not sure the project is going to matter."

Look for repeats. A concern raised once is information. A concern raised twice is a request. A concern raised three times, with no response, is the moment people stop raising concerns at all. (Here's what that looks like from the other side.)

Step 3: Pick one real question (2 minutes)

Not "how's it going?" A question you don't know the answer to, about something that matters to them. "You've mentioned the on-call load twice now. What would make it sustainable?" "What's the part of this project you'd hand off if you could?"

Then decide, in advance, that you'll wait for the answer. The honest answer to a real question takes a few seconds longer than the safe one, and the pause will feel long. Don't fill it. That pause is the most informative moment in the meeting. (More on the silence.)

Step 4: Choose one thing you'll do differently (1 minute)

You have habits in 1:1s. Maybe you talk more than half the time. Maybe you answer questions your report was about to answer themselves. Maybe you restate your point three times.

Pick one, just for this meeting. "I'll ask one more question before I give an answer." It's much easier to change a behavior you named five minutes before than one you vaguely mean to improve.

Step 5: Leave the agenda to them

If you use a shared doc, a simple structure works: their topics first, then yours, then commitments in both directions. Our 1:1 meeting template has one. But the agenda is theirs. If your prep was good, you'll be ready for whatever they bring, and you won't need to fill the time with status updates you could have read in Slack.

The part after the meeting

The ten minutes of prep for the next 1:1 is only possible if something survives this one. Most managers' notes don't: a few bullets, written later, that capture what was discussed and lose what was promised.

Before you open the next calendar invite, write down three things: what you committed to, what they committed to, and anything they said that you'd want to remember in a month.

Where Fluent fits

Fluent is built for exactly this loop, because it was there for the last conversation. It captures your 1:1s in the room, on your iPhone or a pendant, without a bot or a notepad between you and your report. Then it does the remembering:

People profiles keep what each person raised, cared about, and pushed back on, conversation after conversation. Before the 1:1, you see that Sam has mentioned on-call load twice.
Follow-ups track what you promised, with the quote and the date, so Step 1 is a list you check, not a memory exercise.
Goal tracking turns Step 4 into evidence. Set "ask one more question before answering" and see, meeting by meeting, whether you did.

That's the whole idea of Fluent for managers: a quarter of 1:1s should add up to something, and the best preparation for the next conversation is a reliable memory of the last one.

Frequently asked questions

How do I prepare for a 1:1 with a direct report?

Spend ten minutes on the last conversation, not the next agenda. Check what you promised and whether you did it, what they raised that you haven't addressed, and whether anything has come up more than once. Then pick one real question and decide you'll wait for the answer.

How long should 1:1 prep take?

Ten to fifteen minutes is enough when you have a record of the previous conversation. Most of the time goes on checking your own open commitments, which is the part reports notice most when it's skipped.

Who should own the 1:1 agenda?

Your report. The 1:1 is their meeting. Your prep is about context and follow-through, so you can respond to what they bring rather than fill the time with status updates.

I'm the direct report. How should I prepare for a 1:1 with my manager?

Bring the one thing you need a decision or help on, and say it first. Then check what your manager said they'd do last time; asking about it directly is easier than waiting for it to resurface.