All posts

The one-on-one is the most underrated meeting in a knowledge worker's calendar. Done well, it is the single highest-leverage thirty minutes in a manager's week: the place where problems surface before they become crises, where careers get shaped, where trust gets built. Done badly, it is a status update, delivered by the person who least needs to hear it, to the person who cares about it least.

The difference between the two versions is almost entirely about what the manager does. Not what the report does. Not the meeting template. Not the tool. The manager. What follows is the realistic guide to the version that actually works.

The One-on-One Is Not a Status Update

The single most common failure of one-on-ones is that they are treated as status meetings. The report walks through the week's work, the manager nods, and both parties leave feeling like the time was spent. It was not. Status belongs in writing, in a shared doc or the team's tracking tool, and should not consume a thirty-minute synchronous slot.

The purpose of a one-on-one is the things that are harder than status. It is for:

If the thirty minutes is used for anything on this list, the one-on-one is working. If it is used for status, the thirty minutes is wasted, regardless of how productive it feels.

It Is Their Meeting, Not Yours

The most common rookie-manager mistake is driving the agenda. The one-on-one should be driven by the report, with the manager as a supporting presence. The report picks the topics. The report decides what matters. The manager shows up to listen, respond, and occasionally steer when something important is not being surfaced.

This matters because the topics that most need discussion are the ones the report is least comfortable raising unprompted. If the manager fills the time with manager-picked topics, those important-but-uncomfortable topics never come up. The signal is lost.

Practically, this means a shared doc where the report adds topics in advance, and the meeting flows through their list. The manager can add items too, but the report's list comes first.

The Right Opening Question

"How are you doing?" is a useless opener because the social script is "fine." It trains the conversation into safe territory before any real topic surfaces.

A better opener: "What is on your mind this week?" This question has no social script and no default answer, so the report actually has to think about what they want to bring. The most important topics surface in the first ninety seconds more often than not.

Another good opener, used selectively: "What is not going well right now?" This one requires trust to use — the first time you ask it, the honest answer may not come — but over time it becomes the question that extracts the most useful information.

Listen More Than You Talk

Aim for a 70/30 split in the other direction. Your direct report talks 70% of the time. You talk 30%. This feels uncomfortable for new managers, because the manager often has strong opinions and the impulse to share them. Resist. The value of the meeting is in the information flowing toward you, not the information flowing from you. You have plenty of other channels to share your views.

A simple tactic: after your report finishes a thought, pause. Count to two. Most of the time they will continue, and the second sentence is usually more important than the first. The first sentence was the rehearsed version. The second sentence is what they actually think.

The Five Questions That Actually Work

The right questions in a one-on-one are the ones that surface information the manager would not otherwise get. In rough order of usefulness:

  1. What is making you hesitate right now? This one surfaces the stuck things, the unaddressed doubts, the things the report has not yet brought up because they are still unsure.
  2. What have I missed? An invitation to tell you something you are wrong about, which people rarely volunteer without being explicitly asked.
  3. What would make this week significantly worse? Surfaces the risks they are anticipating but have not flagged.
  4. Who is being difficult? Sometimes people. Sometimes processes. The question prompts interpersonal issues to surface before they become conflicts.
  5. What would you want to do more of, if you had the space? A career-development question that does not require the report to have a five-year plan. Lower stakes, more honest answers.

You do not use all five every week. You use one or two, and rotate. The goal is to keep the conversation from defaulting to status.

Feedback, Given and Received

One-on-ones are the best place to give specific feedback on specific work, because the context is fresh and the cost of being honest is low in a private setting. The practical rule: if you have feedback that has been waiting more than a week, bring it to the next one-on-one. Not the next all-hands. Not a Slack DM. The one-on-one.

Even more importantly, one-on-ones are where you ask for feedback from your report on you. Most managers under-index on this because the power dynamic makes the answers feel rehearsed. Over time, with consistent asking, reports do start sharing real feedback, and the compounding effect on the manager is enormous. Try: "Is there something I have been doing that has not been helpful? Or that I should do more of?"

Expect thin answers the first few times. Keep asking. By the tenth time, the real answers come.

The most important thing that happens in a great one-on-one is not what the manager says. It is what the report finally feels safe enough to say.

Note-Taking, Lightly

You need notes. Your report needs notes. But heavy note-taking during a one-on-one kills the conversational quality. The manager should not be typing furiously while their report is talking.

The lightweight version: a shared doc per report, with the week's topics and action items at the top. During the meeting, you listen, make eye contact, and jot only the key things that need to survive past the call. After the meeting, you spend three minutes dictating a fuller set of notes into the doc while the context is fresh.

That post-meeting dictation is where voice capture tools earn their place. Three minutes of dictated reflection produces a richer record than ten minutes of typed notes taken during the meeting, and the meeting itself was not diminished by the note-taking. Voice Keyboard Pro at voicekeyboardpro.com is free to install and works for this kind of rapid post-meeting capture on a Mac.

Cadence

Weekly is the right default for most reports. Every other week works for senior reports who are largely autonomous. Daily stand-up style is almost never the right format for one-on-ones — those are status meetings, not relationship meetings.

Do not cancel one-on-ones casually. The message sent by a canceled one-on-one is louder than the message sent by a canceled team meeting. If you must reschedule, reschedule within the same week. Canceling outright, especially repeatedly, communicates that the report is not a priority — whether you mean that or not.

Duration

Thirty minutes is the right default. Forty-five is too long for most weeks — the conversation dilutes. Fifteen is too short for anything other than a quick check-in when both parties have already had a longer conversation that week.

For new reports or reports going through a difficult stretch, bump to 45 or 60 minutes temporarily. Return to 30 when the extra time is no longer needed.

The Skip-Level

If you manage managers, add a quarterly skip-level with each of their reports. Keep it brief — 30 minutes — and make clear that it is not a bypass of their manager. The goal is to hear directly from the people doing the work, get a sense of the team's pulse that filters differently through a layer of management, and give the reports a low-stakes opportunity to say things they might hesitate to say to their direct manager.

Skip-levels are controversial in some cultures and totally standard in others. If they are standard in your culture, run them. If they are not, have the conversation about installing them as a quarterly norm — the value is high, and the friction evaporates once the first round happens without incident.

Common Failure Modes

Talking About Your Problems

The one-on-one is not the place to vent about your own workload, your boss, or your stress. It inverts the dynamic and makes the report responsible for managing you. Save those conversations for peers or your own manager.

Skipping the Hard Conversations

If there is feedback you have been avoiding, the one-on-one is where it happens. Not the performance review. The report should never be surprised by their annual review, which means every important piece of feedback must have already been given in a one-on-one first.

Letting the Meeting Become Status

If a one-on-one has drifted into status, the meeting is broken. Reset it explicitly: "I realize we've been doing status here, and I think we should save that for writing. Next week let's come with one or two real topics instead." The reset feels awkward the first time. Within a month the meeting is materially better.

The Long Game

A manager who runs great one-on-ones for two years will have a team that is noticeably different from one who does not. People will trust them more, leave less often, surface problems earlier, and grow faster. These effects are largely invisible on a quarter-by-quarter basis, which is why most managers under-invest in them.

The thirty minutes a week per report is not the expensive part. The expensive part is doing them well, which requires attention, preparation, and genuine curiosity about the person on the other side of the call. When you get that right, everything else about management gets cheaper.

Great one-on-ones are not a management technique. They are the practice of taking the other person seriously, week after week, until it compounds into a relationship that actually functions.