Running Effective One-to-Ones

Good one-to-one meetings do three things a group meeting cannot: they surface problems while they are still small, they give someone a place to say the thing they will not say in front of eight colleagues, and they let you talk about a person's work over months rather than sprints. If your one-to-ones are mostly you asking for a project update, none of those three are happening and you would get the same information faster from a written status.

The most common way these meetings fail is not neglect but drift. They start well, then a busy quarter arrives, the manager begins each session with 'so, where are we on the migration?', and within two months the meeting has quietly become a status review with an audience of one. The report notices this before the manager does, and stops bringing anything that is not a project update, which confirms the manager's belief that there is nothing else to discuss.

This guide covers what a one-to-one is actually for, the cadence and length that hold up, who should own the agenda, a thirty-minute shape you can reuse, the questions that get past 'yeah, fine', what changes for remote and cross-time-zone reports, how to run the first one with a new starter, and what to do when the meeting has gone stale.

What a one-to-one is for, and what it is not

The purpose is early signal. Most of what goes badly wrong on a team is visible to somebody months before it becomes a crisis, and that somebody is usually not the manager. A recurring, low-stakes, private conversation is the cheapest mechanism available for moving information from the person who has it to the person who can act on it, and it works precisely because it does not require anyone to declare an emergency.

It is also the only meeting in most people's week that is about them rather than about the work. Career direction, whether the current role is still the right shape, what someone wants to be doing in a year, the manager who is slightly difficult to work with - none of these fit into a standup or a project review, and none of them announce themselves. They come out in the fourth or fifth session, in the gap after a question, once the person believes the meeting is genuinely for them.

What it is not: a status update, a task-assignment meeting, a place to deliver a performance rating for the first time, or an opportunity to catch up on a project you have not been following. Status belongs in writing. Performance conversations need their own scheduled slot and no surprises. Using the one-to-one for either is not a small compromise - it displaces the thing the meeting is uniquely able to do, and there is no other slot in the week that can pick it up.

Two things follow from that. First, the meeting is not optional when things get busy; busy is when the early signal is worth the most. Second, its value is cumulative rather than per-session. A single one-to-one is often unremarkable, and it is the twentieth in a row that produces the sentence you needed to hear six weeks earlier.

Cadence and length: pick one and defend it

Frequency matters more than duration. A weekly thirty-minute conversation catches things a monthly hour never will, because the question 'has anything odd happened since Tuesday?' has a much better hit rate than 'has anything odd happened since the fourteenth of last month?'. People do not store minor irritations for four weeks; they either forget them or escalate them, and neither outcome helps you.

The rule that matters more than the cadence is this: never cancel, only move. Cancelling a one-to-one because your day is full communicates, accurately, that this person's time with you is the lowest-value thing in your calendar. Moving it to Thursday communicates the opposite for the same amount of effort. If you have cancelled twice in a row, the next session should open with an apology and no agenda of your own.

If you have more than about eight direct reports, the maths stops working and you should say so out loud rather than quietly degrading everyone's cadence. Eight weekly thirty-minute sessions plus preparation and follow-up is a day a week, and a manager who pretends otherwise ends up running eight bad conversations instead of five good ones.

Who owns the agenda

The report owns the agenda. This is the single structural choice that separates a one-to-one from a status meeting, and it is easy to get wrong while believing you have got it right - most managers who say the meeting belongs to their report still open it with their own question.

In practice, keep a shared running document per person. Your report adds items during the week as they occur; you add yours at the bottom before the session. Starting from the top means their items get the fresh half of the meeting and yours get whatever is left, which is the correct priority almost every week.

The awkward version of this is the empty agenda. Do not fill it with a project update out of discomfort. An empty agenda from someone who usually brings three items is itself a signal worth asking about, and a genuinely quiet week is a fine reason to finish in twelve minutes. Ending early occasionally is what proves the meeting is not ceremony.

The shape of a good thirty minutes

Thirty minutes goes faster than managers expect, which is why the order is doing so much work. Their agenda before yours; the open question before your items; the actions written before you leave rather than reconstructed later.

The five-minute open question is the block that gets cut when the conversation runs long, and it should be the last thing you sacrifice. Everything on either agenda is something one of you already knew about. The open question is the only part of the meeting designed to produce something neither of you arrived with.

If you consistently overrun, the problem is usually that you are solving in the room. Take the two items that need real thought, name them as topics for a separate half hour, and move on. A one-to-one that becomes a working session displaces the conversations that have no other home.

Questions that get past 'yeah, fine'

'How's it going?' is answered honestly by roughly nobody, because it asks the other person to choose a topic, judge whether it is worth your time, and take the social risk of raising it, all in the two seconds before the pause gets awkward. Specific questions do that work for them.

Pick one per session and change it every few weeks. Asking the same question every Tuesday turns it into a ritual with a rehearsed answer, and a rehearsed answer is worth nothing. Keep a short list, rotate through it, and note which ones actually produced something for that particular person.

Then leave the silence alone. Most managers fill a three-second pause, and three seconds is roughly when someone is deciding whether to say the real thing. Count to ten in your head. It is the highest-return skill in the whole meeting and it costs nothing to practise.

The first one-to-one with a new report

The first session sets the pattern for everything after it, and the strongest signal you can send is spending the whole half hour on how you will work together rather than on the work itself. There is always a temptation to get straight into projects because it feels productive. Resist it once; you have every other week for projects.

Where the status update goes instead

If you strip status out of one-to-ones, you need somewhere for it to go, or it will come back within a month. The usual answer is a short written update on a fixed rhythm - three lines per person or per workstream, posted the same day each week, in a place the whole team can read rather than a private message to the manager.

Written status is better on its own merits. You can read it before the meeting rather than during it, it is searchable in three months, and colleagues see each other's work, which is the part that private verbal updates structurally cannot deliver. It also removes the awkward performance of narrating a week to someone who has been in most of the same meetings.

Keep the format brutally short. Three lines: what moved, what is stuck, what I need from someone. Anything longer stops being written weekly, and a status format that gets abandoned in month two just pushes status back into the one-to-one.

For team-level questions - how loaded people feel, whether priorities are clear, how the last release actually went - a short recurring pulse works better than either format. Ask two or three questions, keep responses anonymous, and share the results with the team. This is the one place a tool like Session Flo genuinely earns its keep in this workflow: not inside the one-to-one, which needs no software beyond a shared document, but in the team-wide signal that individual conversations cannot give you.

Remote, hybrid and cross-time-zone one-to-ones

Remote one-to-ones matter more than in-person ones, because they are carrying weight that used to be spread across corridor conversations and lunch. When a manager and report share an office, a fortnightly slot is topped up by twenty incidental exchanges a week. Remove those and the scheduled conversation is close to the entire relationship, which argues for weekly rather than fortnightly and for protecting the slot harder.

Cameras on for one-to-ones is a reasonable default and a bad rule. You lose real information without a face - hesitation, discomfort, the pause before an answer - but insisting on it during a hard week makes the meeting more expensive to attend. Say you prefer cameras, then let people turn theirs off without explaining why, and notice if it becomes permanent rather than policing it.

Across time zones, rotate the pain. If one of you is always taking the call at seven in the evening, that person will start finding reasons to move it, and the moving will look like disinterest. Alternate which side gets the awkward hour, or find a window that is merely mildly inconvenient for both rather than perfect for one.

Walking one-to-ones translate surprisingly well to audio-only calls, and are worth trying with someone who goes quiet on video. No screen, no shared document, no note-taking - just a phone call and a walk, with actions typed up afterwards. Some people say things on a walk they will not say to a camera.

When one-to-ones go stale

Staleness has recognisable symptoms: the meeting reliably finishes in eleven minutes with nothing raised, the agenda document has been empty for a month, the answers have become fluent and identical, or you find yourself relieved when it gets moved. None of these mean the relationship is bad. They usually mean the format has calcified.

The fix is to name it and change something concrete. 'These have got a bit routine - what would make them more useful?' is a fair question, but it often gets a polite non-answer, so bring an option with you. Change the cadence, change the venue, drop the standing questions for a month, or spend one entire session on the next twelve months rather than the next two weeks.

A specific and effective reset is to give the whole session over to a single topic chosen a week in advance. One session on how their role should change. One on a piece of work that went badly, with no blame attached. One on what they would do if they had your job for a month. Topic-led sessions break the update-shaped groove that recurring meetings settle into.

If the sessions are stale because there is genuinely nothing to discuss - a stable role, a stable project, an experienced person - then reduce the cadence rather than continuing to hold empty meetings. Fortnightly with real content beats weekly with none, and you can always go back to weekly when something changes. What you must not do is quietly let the meetings lapse without saying anything, because the report will read that as a message about their standing.

What one-to-ones cannot fix

One-to-ones are excellent at surfacing individual problems and poor at surfacing systemic ones. A person tells you they are overloaded; you have no way to know from that conversation whether one person is overloaded or nine are, and the private nature of the meeting means you will hear the same problem five times in five separate rooms before you notice the pattern.

Adopt a simple trigger: if you hear the same thing from three different people, it stops being a one-to-one topic and becomes a team topic. Take it to the whole group, say you have heard it three times, and ask everyone to respond at once - anonymously if it is about workload, priorities or a decision people have doubts about. That is a five-minute activity, and it converts five private grumbles into one shared, actionable fact.

The other thing one-to-ones cannot do is manufacture trust that the rest of the week is dismantling. If someone is talked over in every team meeting, told their concerns are being handled and then sees nothing change, no amount of skilful questioning in a private half hour will get you an honest answer. The meeting reflects the relationship; it does not substitute for one.

Which is the honest limit of any advice about format. Cadence, agenda ownership, good questions and written actions will reliably make a decent working relationship more useful. They will not repair a broken one, and treating the one-to-one as the repair mechanism tends to make both people dread it.