How to Run a One-on-One Meeting: A Manager's Guide

What a one-on-one is actually for

A one-on-one is a recurring, private meeting between you and one direct report, and its job is everything that doesn't fit anywhere else. Project channels handle status. Team meetings handle coordination. The 1:1 is for the things people won't raise in a group: the simmering frustration with a peer, the career itch, the "I'm drowning and haven't told anyone," the feedback you owe them and the feedback they owe you.

Andy Grove made the case in High Output Management decades ago: the one-on-one is one of the highest-leverage things a manager does, because a modest investment of your time improves the quality of a report's work for weeks afterward. That leverage comes from four jobs the meeting does at once:

• Early warning. Problems show up here weeks before they show up in metrics — blockers, conflicts, quiet disengagement, the first signs of burnout.
• Coaching. This is where you help someone get better at their job, not just get through it.
• Trust. Weekly private time compounds. It's what makes the eventual hard conversation possible.
• Alignment. Ten minutes of context about where the company is headed saves your report weeks of guessing.

Notice what's not on the list: project status. If your 1:1 could double as a status email, it isn't a 1:1 yet — more on that trap below.

Pick a cadence you can actually protect

Default to weekly, 30 minutes. Weekly is frequent enough that topics stay fresh and small problems surface before they compound; 30 minutes is long enough to get past small talk. If your team is large or a report is very senior, biweekly for 45–60 minutes can work — but weekly is the default you should have to argue your way out of, not into.

The cadence matters less than what you do when it slips. Rescheduling a 1:1 says "this week is chaotic." Repeatedly canceling one says "you are the most droppable thing on my calendar" — and your report hears exactly that. If you must move it, move it, don't kill it: "Today's blown up — can we do Thursday at 2 instead?" Same week, every time. Team size, seniority, and remote setups all shift the math, and how often to hold one-on-ones walks through those trade-offs.

Structure the meeting: their agenda first

The single biggest upgrade to most 1:1s is a shared running agenda that either of you can add to during the week, with the report's items always first. When topics get written down on Tuesday instead of half-remembered on Friday, the meeting starts at the real conversation instead of spending ten minutes finding it.

For a 30-minute meeting, here's a shape that works:

1. Minutes 0–10: their topics. Whatever they put on the agenda, in their order. You mostly listen and ask follow-ups.
2. Minutes 10–20: your topics. Feedback, context from leadership, an early heads-up on changes, a question you've been sitting on.
3. Minutes 20–30: the longer arc. Rotate through career progress, how they're really doing, and feedback on you. This is the third that always gets squeezed — protect it, because it's the third that makes the meeting worth having.

You don't need to reinvent this structure every week. Grab a one-on-one agenda template and adapt it until it fits the way you two actually talk.

Before the meeting: five minutes of prep

You don't need thirty minutes of prep for a thirty-minute meeting. You need five, done deliberately:

• Skim the shared agenda and add your items the day before, so your report isn't ambushed by "we need to talk about the launch" with zero warning.
• Reread last week's notes. Nothing says "I wasn't listening" like asking about the thing they already answered — and nothing says "I was" like following up on their kid's recital or their stalled code review unprompted.
• Check the action items from last time — yours especially. Arriving having done what you said you'd do is most of what reports mean when they call a manager reliable.
• Pick one real question. Not "any updates?" — something specific: "Last week you sounded flat when we talked about the migration. What was going on there?"

During the meeting: listen like it's your job

Open with a genuine check-in, then get out of the way. "How are you, actually?" with an extra beat of silence gets a different answer than "how's it going" fired off while you're still opening your laptop.

• Take their items in their order. Resist the urge to jump to the one you find most interesting.
• Ask the second question. The first answer is usually the rehearsed one; "what makes you say that?" — or plain silence — gets you the real one.
• Name things you notice. "You've seemed quieter in standups lately — what's up?" is a gift, even when the answer is "nothing."
• Take light notes, visibly. It signals the conversation matters. Save the full transcription for court.
• End with a recap: "So I'm doing X by Friday, you're talking to Priya about Y — did I miss anything?"

If the conversation keeps stalling at "everything's fine," the problem is usually your questions, not their openness. Keep a handful of better one-on-one questions in your back pocket and rotate them so the meeting never calcifies into a script.

After the meeting: where trust is won or lost

The follow-through is the meeting. Two minutes after every 1:1, jot down the decisions made, the action items with owners, and anything you promised to chase. Next week, open by closing those loops. Do this for a month and watch how much more your report brings to the meeting — people open up to managers who visibly do things with what they hear.

This is also the part most managers do worst, because it depends on memory and goodwill against a calendar that's actively hostile to both. Write action items in the same shared doc as the agenda so they're staring at both of you next week — a tool like Teammons keeps the running agenda and carries unfinished action items forward automatically. However you handle it, the standard is simple: what gets agreed in a 1:1 gets tracked and closed, every time.

The three ways one-on-ones die

Most bad 1:1s fail in one of three predictable ways. Diagnose yours:

The status-report trap. The meeting becomes a project update with eye contact. It happens because status is easy and comfortable for both sides — there's always material, and nobody has to be vulnerable. The fix: move status somewhere async (a written Friday update, a project channel) and open the 1:1 with "I read your update — what's not in it?" If a topic could be an email, it doesn't get 1:1 airtime.

The manager monologue. You arrive with context to share, decisions to explain, wisdom to dispense — and suddenly it's minute 25 and your report has said forty words. The fix is mechanical, not motivational: put their agenda first, ask a question before you share anything, and check the airtime split honestly. Half, at most.

Death by a thousand cancellations. Skipping one for a genuine fire is fine. Skip three in a month and you've taught your report to stop preparing, stop bringing real topics, and quietly conclude they don't matter. The fix: reschedule within the same week, never just delete. And if you notice you're always the one canceling, treat that as data about your priorities — because your report already has.