How to Run One-on-Ones People Don't Dread

You have thirty minutes on the calendar with each person every week or two. What happens in those thirty minutes is a status readout: they walk you through their list, you nod, you ask about the two items you were already worried about, and somebody mentions the weather. Nobody leaves changed. Half the time you cancel it because something more urgent appeared, and nobody objects, which you take as a sign that it wasn't important.

Then someone resigns and tells you in the exit conversation that they'd been unhappy for five months. You had roughly twenty one-on-ones in that window, and not one of them surfaced it.

Three structural reasons. First, the manager owns the agenda, so the meeting covers what the manager already knows to ask about. Everything outside your awareness — which is exactly the information you need — never comes up. Second, the meeting rewards reporting over disclosure. A person who spends twenty-five minutes proving their week was productive has no remaining minutes and no remaining appetite for raising a problem. Third, cancellations. Every cancelled one-on-one teaches the person that this time is the first thing to go, which means it isn't safe to save anything important for it.

There's also a quieter reason: many managers are uncomfortable with silence and fill it. Real disclosure almost always comes after a pause you didn't rush.

The same half hour should not look the same for everyone. A person in their first six months needs direction, context, and frequent correction, and they will not ask for any of it, so you supply the structure. A person three years in needs obstacles removed and decisions unblocked, and the most useful question you can ask them is what is in their way that only you can move. A person at the top of their craft needs a peer conversation about where the team is going, and treating that person like they need supervision is the surest way to lose them.

Remote makes all of this harder in one specific way: you lose the incidental information you used to get from proximity. Nobody drops by your desk to mention the thing that is bothering them, so the only channel left is the scheduled one, which is exactly why cancelling it costs more than it used to. If your team is distributed, treat the one-on-one as the entire relationship rather than a supplement to it, and add ten minutes rather than trimming five.

And keep one slot in the quarter deliberately unstructured. No agenda, no items, no notes — just a conversation about how the job is actually going. Some of the most important things you will ever hear from your team arrive in a session that had no purpose on the calendar.

The shared doc has items in it before you open the meeting. That single detail tells you whether the person is banking things for this conversation or waiting to be asked.

You start hearing about problems while they are still small. A team that only surfaces issues at the point of failure does not have a communication problem; it has a one-on-one problem.

Someone answers the question about what you are doing wrong with something real. When that happens, resist every instinct to explain yourself. Say thank you, write it down, and change one thing.

Ask 'what's one thing I'm doing that makes your job harder' every single month, and then actually change one of the things. The first two times you ask, you'll get nothing. The third time, if you've shown you can hear an answer without punishing it, you'll get the real one — and that answer is usually worth more than everything else said in the previous ten meetings combined.