One-on-ones are their meeting

Thirty minutes, every week, that belongs to one other person.

Most managers say some version of "my door is always open" and believe they've solved this. They haven't. An open door assumes the person already feels safe enough to walk through it, with whatever they're carrying. Most people don't, not with their manager, not about the thing that's actually bothering them. The one-on-one is how that safety gets built in the first place, not a reward for already having it.

Skip that meeting for a month and watch what happens. Not much, on the surface. The work still gets done. What you lose is invisible until it isn't: the small frustration that would have surfaced in week two instead compounds through week six, and by the time it reaches you it's a resignation letter or a performance problem, dressed up as if it arrived suddenly. It didn't. You just weren't in the room when it was still small.

What it's for

Use the time to actually know them. Not their ticket count. Them.

That sounds soft and isn't. Hard conversations are much easier to have inside a relationship where you've already established that you'll be straight with each other. If the first honest thing you've ever said to someone is "this isn't working," you've skipped every step that would have made them able to hear it. The one-on-one is where those steps happen, quietly, most weeks, when nothing is on fire.

So the content is theirs. Their growth, what's frustrating them, where they're stuck, what you could be doing better. Status belongs somewhere else: a standup, a written update, a Slack thread. If you're spending the thirty minutes asking where a project stands, you've turned their meeting into your meeting, and you'll never notice, because it still feels productive.

I've done this wrong myself, more than once, on days when I walked in without having looked at my own notes and just asked "so, how's it going," which is a status question wearing a growth question's clothes. It gets a status answer back. The person isn't being evasive. You asked a shallow question and got a shallow answer, and it's on you, not them.

The mechanics that make it real

Keep a shared running document, not something you open five minutes before the meeting starts. Both of you add to it all week, whenever something worth discussing occurs to either of you, so by the time you sit down there's already an agenda and neither of you built it under pressure. Then let them drive. Aim for something close to twenty percent of the talking being yours and eighty percent theirs, a ratio that will feel wrong the first few times, especially if you're used to leading a room. Let it feel wrong. If you're doing most of the talking, you're using their time to think out loud and calling it their meeting.

A quiet agenda doesn't mean there's nothing to discuss, usually the opposite: whatever matters most hasn't been said out loud yet, because saying it takes a nudge. That's what the questions further down are for.

Write down what either of you commits to, and actually follow through, because a one-on-one that generates promises nobody tracks trains people to stop bringing things up. Don't move it and don't cancel it. Be present when you're in it, phone down, door closed, and if something genuinely has to give, find another time that same week rather than letting it slip. A meeting that gets bumped twice in a row tells someone exactly where they rank against whatever bumped it, whether that's what you meant or not.

Adapt to how someone communicates without lowering what you expect of them. Some people think out loud and need space to ramble toward the point, others need a direct question before they'll say anything real. Neither is a reason to skip the hard topic. It's a reason to ask it differently.

Don't save feedback for this meeting either. Say the thing while it's still fresh, then use the one-on-one to follow up on how it landed and whether anything changed. Batching feedback into a weekly slot turns it stale and turns the meeting into something people brace for.

Listen to understand, not to prepare your next line, which is the hardest one on this list and the one managers fail without noticing. A manager who's already composing the response is unmistakable to the person across the table, even when nothing on their face says so. And be human about the rest of it. Ask about their life in whatever way comes naturally to you, and respect what they'd rather keep private. You're not entitled to the details. You're allowed to care that there are some.

Questions worth having on hand

Not a script. A set of doors, for the weeks when the running document is thin.

What's the most important thing we should talk about today.

What are you proud of since we last talked.

What's been frustrating, or harder than it should be.

What do you wish you had more time for.

What are you doing right now that you'd like to stop, hand off, or change.

What conversation are you avoiding at the moment.

Where do you need more clarity, more support, or more authority.

What could I be doing better for you.

That last one is the one people skip, usually because they're afraid of the answer. Ask it anyway. Then do something about whatever comes back, and follow up on it later, out loud, so they know you actually acted on it. Asking for feedback and then changing nothing is worse than not asking, because now they know the question was decorative.

New hires and the cadence question

For at least the first thirty days, meet weekly, no exceptions, regardless of how confident they seem. New hires under-report confusion because they don't yet know what's normal to be confused about, and a weekly slot catches it before it calcifies into a bad habit or a quiet resignation to not understanding.

After that, agree the cadence together rather than defaulting to whatever you do with everyone else. Some people want weekly indefinitely. Some settle into fortnightly once they're established and would find weekly smothering. Ask, don't assume.

It isn't only for reports

Peers deserve this too, and so does whoever you partner with most closely on the other side of the building, your Product counterpart if you have one. Your calendar is where your real priorities live, whether you admit it on paper or not, and a standing slot with the people you depend on but don't manage says, honestly, that the relationship matters enough to protect.

With peers, the ratio flips less predictably. Sometimes the most useful thing you can do in that half hour is talk less than usual and just listen, because nobody else is asking them what's actually going on.

Most of those questions come from a leadership guide a former colleague wrote at CircleCI.

The test

At the end of any given one-on-one, ask yourself one question: did I learn something I didn't already know.

If the answer is no, week after week, the meeting has quietly turned into a status update, whatever you're calling it, and the fix isn't cancelling it. It's asking better questions, and then actually being quiet long enough to hear the answers.