How to Run a One-on-One That Isn't a Status Update

The default state of a 1:1 is that it becomes a status meeting. The report runs through their projects. The manager nods. Both parties leave feeling that something productive happened. Almost nothing did.

Status, as a category of information, has no business in a synchronous meeting. Status is a written artifact. It is what Slack updates and Linear tickets and Friday wrap emails exist for. The moment you spend a 1:1 listening to someone walk through their project list, you have spent thirty minutes doing what a paragraph of writing could have done in four. Worse, you have used up the only slot in the week that's reserved for the conversation that can't happen anywhere else.

So the first rule of running a useful 1:1 is to ban status from it. Either the report sends a written update beforehand and you both come prepared, or you start the meeting by saying, explicitly, that you don't want to spend it on what they're working on. You want to spend it on what they're stuck on, what they're worried about, and what they think you don't know.

Those are the three questions that justify the meeting.

What they're stuck on

Not what's behind. Stuck. There's a difference. Behind is a scheduling problem. Stuck is a thinking problem, or a political problem, or a sometimes a confidence problem. Behind can usually be solved by Slack. Stuck almost always needs a conversation, because the report often doesn't know they're stuck until they hear themselves describe it out loud.

The manager's job in this part of the meeting is mostly to ask the next question. What's the actual blocker. What have you tried. Who else has an opinion. What would have to be true for this to move. The discipline is to resist the urge to solve. Most of what gets called managerial coaching is just impatience wearing a suit.

What they're worried about

This is the question almost no manager asks, because the answers are uncomfortable. The honest answers are usually about people: a colleague who's not pulling weight, a counterpart in another team who's being political, a sense that the org chart is about to change in a way that will make their job harder. Sometimes the answer is about the report themselves — that they don't think they're growing, or that they're starting to wonder if this is the right role.

The reason to ask anyway is that worry, left unspoken, compounds. People who are worried for a quarter without telling anyone are people who, by the end of the quarter, have decided to leave. The cheapest possible intervention is a manager who asks, monthly, what's worrying them, and is willing to sit with whatever the answer turns out to be.

What they think you don't know

This is the most valuable question and the hardest one to ask without it sounding like a trap. The framing matters. "What's something happening on your team or in the company that you think isn't getting through to me?" — and then sit with the silence until they answer. The first answer is usually a small thing. The second answer, if you ask "and what else?", is the one worth having driven across town for.

Reports almost always know things their managers don't. The org is too big, the manager's calendar is too full, and the report is closer to the actual work. The 1:1 is the only structured opportunity to get that information out into the open. Wasting it on a status update is, in pure information-theoretic terms, an act of self-harm.

The mechanics

Thirty minutes is enough. Forty-five is plenty. An hour is too long and turns into theater. Same time every week, and don't move it for anything short of a board meeting — the cancelability of 1:1s is the single strongest signal a manager sends about how much they actually care about their team.

No agenda doc with five sections. The three questions above are the agenda. Take notes on what you commit to doing as a result, and follow up on those notes by the next 1:1. The single fastest way to lose a report's trust is to hear something important in a 1:1 and visibly do nothing with it.

The 1:1, done right, is the highest-leverage thirty minutes in a manager's week. Done as a status meeting, it is the lowest. The difference is almost entirely in what you ban from it.