Managing

How to run effective one-on-ones

A one-on-one is your direct report's meeting, not your status update. Thirty minutes, same slot every week or fortnight, an agenda they mostly own, and you listening for more of it than you talk. Everything below is the detail: what to say in the first five minutes, which questions get past "all good", and what to do when the conversation stalls.

Most managers inherit one-on-ones as a recurring calendar invite and no instructions, so they fill the time with the only thing they know how to do in a meeting: they go through the work. Six months later the report calls the 1:1 "a status update I could have sent in Slack", and the manager is surprised by a resignation.

The fix is not more empathy. It is structure, a few reusable sentences, and the discipline to hold the slot when the week is busy.

What a one-on-one is actually for

Status belongs in your tracker. The 1:1 is for the things that never make it into a tracker:

If you are talking for more than a third of a one-on-one, it has quietly turned back into a status meeting and nobody will tell you.

A 30-minute agenda you can reuse every week

Same shape every time. Predictability is the point: people prepare for a meeting they can anticipate.

  1. Minutes 0-3. Open and hand over. "What's on your list today?" Then wait. Do not rescue the silence.
  2. Minutes 3-15. Their agenda. Whatever they brought, in their order. This is the largest block and it stays that way even when your own list is longer.
  3. Minutes 15-22. Your agenda. Two or three items, maximum. Feedback, context from above, one thing you want them to pick up.
  4. Minutes 22-27. One step back. A career, growth or energy question. One is enough. Rotate them so it does not become a ritual.
  5. Minutes 27-30. Close with actions. "So: you're talking to Priya about the data, I'm unblocking the budget by Thursday. Anything I've missed?"

If they bring nothing, that is a signal, not a gap. Say: "Nothing on your list is fine, but it usually means either everything's genuinely smooth or this meeting doesn't feel worth preparing for. Which is it?" Ask it lightly, then wait.

Say this, not that

Most 1:1 damage is done by ordinary phrasing that lands differently than intended. The difference is usually one clause.

Instead ofSayWhy it lands better
"Any updates?""What's the thing you've been chewing on this week?"Invites the real problem rather than a progress report
"How's the project going?""Where is the project most likely to slip, and what would you need from me to stop that?"Names the risk without asking them to confess to one
"Everything okay?""You're normally quick on email. It's been slower this fortnight. What's going on?"A specific observation beats a yes/no question they will always answer yes to
"You need to be more proactive.""In Tuesday's review you had the answer and waited to be asked. I'd rather you led with it. What stopped you?"Behaviour, moment, effect, question — not a personality verdict
"Let me know if you need anything.""What's one thing I could take off you this week?"Offers a specific door instead of a vague one nobody walks through
"We should catch up on your career sometime.""Next 1:1, let's spend the whole thirty minutes on where you want to be in two years. Come with a rough answer, even a wrong one."A date and a task, so it actually happens

The first five minutes

Open the same way every time so they stop having to read your mood. Something plain: "Right, your half first. What's on your list?" Then close the laptop, visibly. If you take notes, say once why: "I take notes so I remember what I promised you, not for anything else."

Then the hardest skill in the whole meeting, which is doing nothing. Ask, then stay quiet for a full four or five seconds. Most managers fill silence at about two. The thing people say after the pause is almost always more useful than the thing they said before it. This is the practical core of active listening, and it is much harder than it reads.

One more opening move worth stealing: when they raise something, do not solve it immediately. Say "Are you thinking out loud, or do you want my opinion?" It takes three seconds and prevents the most common 1:1 failure, which is a manager solving a problem the person only wanted to describe.

Questions that get past "all good"

You do not need forty questions. You need six or seven you can rotate without sounding like a form. Pick from these.

To surface the real blocker

To get feedback on yourself

For career and growth

The second set is where most managers flinch. Ask it anyway, and then say nothing while they decide whether you meant it. The first time you get a real answer, thank them and change something visible within a fortnight. That single act does more for psychological safety than any statement about open doors.

Raising something difficult

Feedback belongs in the 1:1, in small pieces, close to the event. The sequence matters more than the wording.

  1. Signpost it. "I want to talk about yesterday's client review, about ten minutes in." Nobody hears the content if they are still working out where this is going.
  2. Describe the moment, not the trait. "When Anna asked about timelines, you said we'd confirm later, and the room went quiet."
  3. Name the effect. "They read it as us not having a plan. I had to send a follow-up."
  4. Stop and ask. "How did it look from where you were sitting?" Then genuinely listen; roughly a third of the time you learn something that changes your read.
  5. Agree the next version. "Next time, give a date and a caveat rather than nothing. Does that work?"

That is the SBI model with a pause bolted into the middle. If you want the longer treatment, see how to give constructive feedback at work. For the coaching half of the conversation, GROW gives you a structure that stops you answering your own questions.

When it goes wrong

Four failure modes cover almost everything.

"All good" every single week

Usually means the meeting has no history of being useful. Recovery: change the question. "Skip the update. Tell me about the most annoying thing that happened this fortnight." Then fix one small annoying thing and mention that you fixed it. Usefulness is what earns you candour, not rapport.

It has become a status review

Recovery: say it out loud. "I've turned this into a project check-in and that's on me. From next week I'll get status from the board. Your half first, and I'll go second." Then hold to it for three sessions, because they will not believe you until you have proved it more than once.

They only ever vent

Listening is not endless. Around the second repetition, move the frame: "I think this is the third time we've come back to this. Do you want to keep venting, which is fine, or do you want to do something about it?" If they choose action, one small step is enough.

You keep cancelling it

This is the loudest message you send all fortnight and it is entirely unintentional. Recovery: shrink rather than cancel. "Fifteen minutes today instead of thirty, and I'll owe you the full slot on Friday." A short 1:1 held beats a long one moved twice.

The boring logistics that decide everything

Why reading this will not be enough

You have now read a set of sentences. That is not the same as saying one of them out loud to a person who has just crossed their arms, while your own heart rate is up. The gap between knowing the script and delivering it is the whole skill, and it closes through rehearsal and feedback, not more reading.

That is what experiential learning is for. Managers run the difficult version aloud, get it wrong where it costs nothing, hear how it landed, and go again. Two rounds of that does more for a manager's communication than a year of good intentions.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.

Questions

How to run effective one-on-ones FAQs

How often should you have one-on-ones?

Weekly for new starters, anyone struggling, or anyone in a fast-changing role. Fortnightly is fine for experienced, steady reports. Monthly is usually too far apart: problems either get solved without you or grow past the point where a conversation fixes them. Whatever cadence you pick, protect the slot rather than cancelling it.

What should you talk about in a 1:1 meeting?

Blockers, feedback in both directions, career direction, how the person is genuinely doing, and context from decisions made above them. Project status belongs in your tracker or a team meeting. A useful split is roughly half their agenda, a quarter yours, and a quarter on something bigger than this week's work.

How long should a one-on-one be?

Thirty minutes is the workable default, with the first half belonging to your report. Forty-five works for senior reports or fortnightly cadence, where more accumulates between sessions. Fifteen minutes is enough to hold the relationship in a brutal week and is far better than cancelling, which reads as a message whether you intend it or not.

Who should set the one-on-one agenda?

Mostly the direct report, in a shared document both of you add to between sessions. You bring two or three items of your own. If they consistently arrive with nothing, treat it as information rather than laziness: it usually means the meeting has not yet been useful enough to be worth preparing for.

What questions should I ask in a one-on-one?

Rotate six or seven rather than reciting a list. Good ones: "What's slower than it should be right now?", "What are you working around instead of fixing?", "What's something I do that makes your job harder?" and "Which part of the last month would you want more of?" Then stay quiet for a full five seconds.

Should performance feedback happen in a one-on-one?

Yes, in small pieces, close to the event. The 1:1 is where feedback stays cheap. Signpost it first, describe the specific moment and its effect, ask how it looked from their side, then agree the next version. Formal reviews should then contain no surprises, which is the main test of whether your 1:1s are working.

Keep reading

Related reading

Get in touch

Build it with your team.

Book a 30-minute discovery call and we'll shape an experiential programme around your goals.

Book a discovery call