One-on-Ones: Running Them So People Tell You the Truth

One-on-Ones

The one-on-one is the highest-leverage recurring meeting a manager has, and most of them are wasted. They get cancelled when things are busy, they turn into status updates that a written report would cover better, and they produce a cheerful "everything's fine" from someone who resigns six weeks later.

What makes the difference is a single structural choice: it's their meeting, not yours. The moment you use it to get project updates, you've taught your report that this is a reporting meeting, and they'll prepare accordingly — which means preparing a status summary rather than raising the thing that's actually bothering them. Status belongs in writing, in standup, in a tracker. The one-on-one is for the things that don't fit anywhere else: growth, friction, frustration, ambition, and the problems nobody has named yet.

The second thing that makes the difference is consistency. A one-on-one cancelled twice stops being a reliable channel, and the information you'd have gotten from it doesn't arrive by another route — it just doesn't arrive.

TL;DR

It's their meeting. They set the agenda; you bring questions, not a status checklist.
Weekly for 30 minutes is the default. Biweekly for very senior people; never less than that.
Never cancel. Reschedule if you must — cancelling signals it's the lowest priority.
Status updates don't belong here. Put them in writing and reclaim the time.
Take notes and follow up. A commitment you forget is worse than one you never made.
Silence is a tool. Wait five seconds past comfortable; the real answer comes after the first one.
Give feedback as close to the event as possible, not saved for this meeting.
Skip-levels surface what your directs won't tell you about themselves or about you.

Structure

The ordering is deliberate. Starting with your agenda means their topics get whatever time is left, which is usually none — and they learn to stop bringing things.

A shared running document works well: both parties add items during the week, notes and actions are recorded in place, and there's a visible history of what was discussed and what came of it. It also means neither of you arrives with nothing.

Core Concepts

Cadence

More than about eight direct reports and weekly thirty-minute meetings consume a full day plus preparation, which is a signal about org structure rather than about scheduling. See Team Topologies.

New reports need more frequency at first — a weekly hour for the first month builds the relationship faster than three months of thirty-minute meetings.

Getting past "everything's fine"

The default answer is a social reflex, not information. Better questions are specific, hypothetical, or oblique:

Then wait. The first answer is the polite one. Count to five past the point where the silence is uncomfortable — this is the single most effective technique in the whole topic, and it feels wrong every time.

If someone consistently has nothing, that's data. Either they don't trust the channel yet, or they don't believe raising things changes anything. Both are worth addressing directly: "I notice we mostly cover status — what would make this useful for you?"

Feedback

Give feedback close to the event, not saved for the meeting. A one-on-one is a good place for patterns and growth, not for something that happened Tuesday and should have been addressed Tuesday.

Specific, observed, and about behavior rather than character. "You're dismissive" is an accusation; "you interrupted twice and she stopped talking" is something a person can act on.

Then ask. "How did you see it?" — sometimes there's context you're missing, and asking makes the difference between a conversation and a verdict.

Ask for feedback on yourself, every time, and act on some of it visibly. A report who has never seen you change something in response to their feedback will stop giving it, correctly concluding that it doesn't matter.

What not to use it for

Using the one-on-one as a catch-all is how it becomes another meeting. Its value comes from being reserved for what nothing else covers.

Skip-levels

Meeting your reports' reports, roughly quarterly. Two things surface here that won't in a normal one-on-one: how the team actually experiences their manager, and what people think of you filtered through one fewer layer.

The trust condition is absolute: if something said in a skip-level gets back to the manager attributed, you'll never get honest input again — from anyone, because people talk.

Best Practices

Never cancel; reschedule instead

The signal a cancellation sends — "this is the thing I drop when I'm busy" — is much larger than the meeting you missed. Rescheduling within the same week preserves the message that it matters.

Let them talk first, and more

A rough target is 70/30 in their favor. If you're doing most of the talking, it's a briefing, not a one-on-one. Silence you're comfortable holding is the main tool.

Take notes and follow up on commitments

"I'll find out about the conference budget" is a promise. Forgetting it teaches your report that things said in this meeting don't lead anywhere, which is precisely the belief that makes one-on-ones useless. Track actions and close them out visibly.

Ask about the person, not just the work

Career direction, energy levels, what they're enjoying, what they're dreading. Someone who's disengaged rarely says so — it shows up as reduced ambition, avoided conversations, and shorter answers, months before anything else.

Vary the questions

The same three questions every week produce the same three answers. Keep a list, rotate through it, and occasionally ask something that changes the frame — "what's the dumbest thing about how we work?" gets different material than "any blockers?"

Occasionally change the setting

A walk, a coffee, a different room. Different physical context reliably produces different conversation, and for some people a side-by-side walk is much easier than sitting across a table.

Prepare, briefly

Five minutes before: what did they raise last time, what did I commit to, what feedback do I owe them, what's changed organizationally that they should know. Showing up cold makes it their job to fill thirty minutes.

Make no-surprises the rule

Nothing in a performance review should be new information. If someone is struggling, they should have known for weeks. If someone is doing exceptionally, they should have heard it. The one-on-one is where that ongoing calibration happens.

Common Mistakes

Turning it into a status meeting

Cancelling when busy

Doing most of the talking

Saving feedback for the meeting

Not following up on commitments

Surprising someone in a performance review

FAQ

How long should they be?

Thirty minutes weekly is the standard and works for most relationships. New reports, people in a new role, or anyone going through something difficult warrant an hour. Consistency matters more than duration — a reliable thirty minutes beats an occasional ninety.

What if my report has nothing to talk about?

Bring questions, and treat it as a signal rather than a scheduling problem. Common causes: they see it as a status meeting (change how you open it), they don't believe raising things changes anything (find something small to fix visibly), or the relationship isn't there yet (it takes months, not weeks). Asking directly — "what would make this time useful for you?" — usually gets a real answer.

Should tech leads have one-on-ones?

Yes, though with a different purpose. A tech lead isn't responsible for compensation, performance, or career ladders, so their one-on-ones are about technical growth, unblocking, and mentoring. Coordinate with the manager so the two conversations complement rather than duplicate — and be careful not to become the channel for issues that belong with the manager.

How do I handle a report who's clearly unhappy?

Ask directly and then listen without defending. "You seem frustrated — what's going on?" Resist the urge to solve it in the moment; understanding it fully is more valuable than a fast fix, and the stated reason is often not the whole one. Then act on what you can and be honest about what you can't. Unhappiness you address is often recoverable; unhappiness you notice and don't address becomes a resignation.

Should I take notes during the meeting?

Yes, and say why. "I'm writing this down so I don't forget to follow up" makes note-taking a signal that they're being taken seriously rather than that they're being recorded. A shared document works well because they can see the notes and add to them, which also removes any ambiguity about what's being written.

Are one-on-ones different for remote teams?

They're more important and harder. Remote removes all the incidental contact — the hallway, the lunch, the desk-side chat — that would otherwise surface small things, so the one-on-one is often the only channel. Turn video on, protect the time more carefully, and expect to invest more deliberately in the relationship because none of it happens by accident.