How to run a 1:1 meeting that actually matters

A good 1:1 isn't a status update with extra steps. Here is how to run a 1:1 meeting that builds trust, surfaces problems early, and leaves you both with something to act on.

Most 1:1s drift into a verbal version of the project tracker: what's done, what's next, who's blocked. That information matters, but you can get it from a written update. The 1:1 is the one recurring slot where your report has your full attention as a person, not a set of tasks. Used well, it's where you catch a frustration before it becomes a resignation, hear an idea that never makes it to a group thread, and build the kind of trust that makes hard feedback land later. Here is how to make that happen.

Set a cadence and protect it

Weekly is the default for most direct reports. Every other week can work for senior people who need less air traffic control, but going monthly almost always means the relationship runs on fumes. Thirty minutes is plenty if you use it well; an hour if the person is new or going through something.

The single most damaging thing you can do is cancel. When you bump a 1:1 for a "more important" meeting, the message your report hears is that they are the lowest priority on your calendar. If you genuinely can't make it, reschedule it within the same week rather than skipping. Treat the slot as the floor of your management, not the part you cut when things get busy.

Use an agenda that isn't a status update

The fastest way to keep a 1:1 from collapsing into status is to make it their meeting. The agenda should be driven by what's on the report's mind, with your topics layered in second. A shared running doc both of you can add to during the week works better than reinventing the agenda live.

A simple structure that holds up:

• Check in as people (2–3 min). A genuine "how are you, really?" Not a formality — you're calibrating their energy before you read anything into their work.
• Their topics first (10–15 min). What they want to raise: blockers, decisions they need from you, friction with another team, something they're stuck on.
• Your topics (5–10 min). Feedback, context they're missing, a heads-up about something coming.
• Growth and the bigger picture (5 min). Not every week, but often: where they want to go, what they're learning, how the current work connects to it.
• Commitments and close (2 min). Say out loud what each of you will do before next time.

Mind your listening ratio

A rough rule: in a healthy 1:1, the report talks more than you do. If you're filling 70% of the air, it has quietly become your meeting. Watch for the habit of answering your own question before they've finished thinking. Silence after you ask something is not awkward — it's the sound of someone actually considering their answer. Let it sit.

Ask open questions that can't be closed with "fine":

• "What's been frustrating this week, even if it's small?"
• "Where do you wish you had more support from me?"
• "What's something we're doing that doesn't make sense to you?"

For a deeper bank of these, see our list of one-on-one meeting questions.

The point of a 1:1 isn't for you to find out how the work is going. It's for them to find out you're listening.

Capture commitments — both directions

The fastest way to erode trust is to forget what someone told you. If your report mentions they're overwhelmed, or asks for a tool, or says they want to lead the next project, and it never resurfaces, they learn the 1:1 is theater. Write down what each of you agreed to do, in plain language, with a rough date. "I'll get you the headcount answer by Friday" is a commitment. "We'll see" is not.

Keep your own commitments visible too. When a report watches you reliably follow through on the small things you promised, they extend you credit on the big things.

Follow up before the next one

The work of a 1:1 happens between 1:1s. Before each meeting, take two minutes to reread the last one. Did you do what you said? Did the thing they were worried about resolve? Opening with "Last time you mentioned the handoff with design was rough — how did that land?" tells them their words stuck. Over a year, those small callbacks compound into a record of the person's real wins, struggles, and growth — which, not coincidentally, is exactly what you'll wish you had when it's time to write their review.