Skip to main content

One-to-One Meetings That Actually Work: A Manager's Guide

Ask most managers how their one-to-ones are going and they will say something like “good, yeah — we do them most weeks.” Ask their direct reports and you get a different picture: meetings that got cancelled twice in a row, then once more, then quietly stopped; or meetings that happen reliably but consist almost entirely of the manager sharing updates and the employee nodding. Neither version is useless, but neither is what the meeting is for.

The one-to-one is the most powerful tool a manager has — and the most reliably wasted. Not because managers are lazy, but because nobody ever explains what it is actually supposed to do. This guide is an attempt to fix that.

What a one-to-one is not

Before the structure, the principle. A one-to-one is not a status update. If you are running your 1:1s as a progress check on tasks and projects, you have accidentally built a recurring meeting that your employee resents attending and you find easy to cancel when things get busy. Both responses are reasonable, because a status update is exactly the kind of meeting that should be replaced by a written summary or a quick message.

A one-to-one is also not a performance review. If an employee only hears your assessment of how they are doing twice a year, formally, with a form involved, the feedback arrives too late to be useful and in a context that makes it feel like a verdict rather than a conversation.

What it actually is: regular, protected time for the relationship between manager and employee. It exists so that the person can raise things they would not raise in a team meeting, so that you can spot problems and development opportunities early, and so that they feel seen — not as a resource, but as a person whose work and career you are paying attention to. That sounds soft. The business case for it is not: managers who run effective 1:1s have lower attrition, faster identification of problems, and teams that perform better under pressure because the communication channels are already warm.

The basics: cadence and length

The most common question is how often. The honest answer is: more often than you think, especially early in the relationship.

For most direct reports, fortnightly is the minimum. Weekly is better, particularly for new starters, people in stretch roles, or anyone going through a difficult patch. The argument against weekly is usually “I don’t have time,” which often translates to “I don’t yet value this meeting enough to protect it.” Monthly is rarely frequent enough to feel like a genuine relationship; it is frequent enough to feel like an obligation.

Duration: 30 minutes is a floor, not a target. If your 1:1s reliably run to 25 minutes with time to spare, they are probably too shallow. 45 to 60 minutes gives room for the kind of conversation that needs to happen after the surface level — the one where someone admits they are struggling, or says what they really think about the direction the team is going.

The one thing that matters more than frequency or length is consistency. A meeting that is protected and happens reliably is worth ten meetings that get cancelled whenever something urgent comes up. And something urgent always comes up. The meeting that disappears when things get busy is sending a signal — that the person is not the priority when the manager is under pressure — and the person notices.

Who leads the agenda

The employee. This is the most important structural point and the one most frequently ignored.

When the manager owns the agenda, the meeting becomes a manager’s meeting that the employee attends. When the employee owns it — when they arrive knowing it is their time to raise what matters to them — it functions as the thing it is supposed to be. The manager’s job is to hold the space, ask the questions, and contribute where useful, not to fill the hour with their own priorities.

This does not mean the manager never brings anything. It means the employee goes first, and the manager’s contributions are secondary. A simple opening that works: “What’s on your list?” or “What’s most on your mind this week?” — and then listening, properly, rather than waiting for a gap to fill.

Some employees, particularly those who have worked for managers who dominated the agenda, will initially say “nothing much, I’m fine.” They are not being difficult. They have learned that raising things is not particularly productive. Consistency over weeks is what changes this: they learn, through repeated experience, that the meeting belongs to them and that raising things leads somewhere useful.

The questions worth asking

One-to-one conversations tend to find their own shape over time, but some questions are reliably more useful than others.

On the work:

  • What’s going well right now, and what’s making it hard?
  • Is there anything you’re blocked on that I can clear?
  • Is there anything you’re spending time on that you think I should know about?

On the person:

  • What would you find most useful from me at the moment?
  • Is there anything about the way we work together that you’d change?
  • What are you finding most interesting? What’s feeling flat?

On development:

  • Where do you want to be in the next year or two?
  • Is there something you’d like to get exposure to that you’re not getting at the moment?
  • What would make the biggest difference to how you work or grow?

Not all of these in every meeting. A useful habit is to rotate between operational and developmental conversations — the immediate work one week, the longer-term picture the next. Trying to cover everything every time tends to result in nothing being covered properly.

One question that earns its place in almost every conversation: “What’s one thing I could do differently that would help you?” Asked regularly, non-defensively, and followed up on, it is one of the most trust-building questions a manager can ask. It also generates genuinely useful feedback that you would not otherwise receive, because most people will not offer it unsolicited.

The feedback problem

Most managers know they should give feedback in 1:1s. Fewer actually do it, for understandable reasons: feedback is uncomfortable, the moment often doesn’t feel right, and it is easy to decide that the good news outweighs the issue you were going to raise and let it go.

The problem with letting it go repeatedly is that the issue grows. Something that was a small, early observation becomes, by the time it surfaces, either a formal performance problem or a pattern you have been quietly tolerating for months. Neither is a good situation for the manager or the employee.

The SBI framework—Situation, Behaviour, Impact—is useful here, not because it is the only way to give feedback but because it forces specificity. “Your presentation last Thursday (situation) ran 15 minutes over and you skipped the Q&A (behaviour) — I think the audience left before they’d had a chance to engage with the key points (impact)” is more actionable and less personal than “your presentations tend to run long.” The first can be acted on. The second invites defensiveness.

Positive feedback in 1:1s is worth naming explicitly — not “well done” as a reflex, but the specific thing you observed and why it mattered. People who only ever hear what needs to improve, without any sense of what is landing well, stop taking risks. They optimise for not getting it wrong rather than getting it right.

Handling the employee who doesn’t engage

Not every employee takes readily to 1:1s. Some are introverted and find the format uncomfortable. Some come from cultures where direct conversation with a manager is unusual. Some simply don’t trust the meeting yet.

The useful response is not to push harder for openness, but to make the meeting easier to inhabit. Shorter and more frequent can help — 20 minutes weekly feels less exposing than an hour monthly. A shared agenda doc that both parties add to in advance removes the cold-start problem. Starting with something concrete — “walk me through what you’re working on this week” — is lower-stakes than “what’s on your mind.”

For the employee who says everything is fine when it clearly is not: persist, gently. “I want to make sure you feel like you can raise things here — I’d rather hear about problems early than late. Anything I can make easier?” is not a magic question, but asked consistently over several weeks without the sky falling in, it tends to shift the dynamic.

If someone is actively resistant to one-to-ones after a reasonable amount of time and effort, that itself is something to address — directly, in the meeting.

The trap of cancellation

One-to-ones get cancelled for reasons that, individually, are entirely reasonable: a deadline, a client escalation, a sick child, a meeting overrun. The pattern that emerges from those individually reasonable decisions is not reasonable. Cancelled 1:1s compound. Each one signals, a little more clearly, that the meeting is not actually protected — that the relationship comes after everything else.

The antidote is not rigid attendance at all costs. It is the discipline of rescheduling within the same week, every time. A 20-minute call at the end of Thursday is not as good as the full meeting on Tuesday, but it is enormously better than waiting another fortnight. The signal of rescheduling rather than simply cancelling is the point: this meeting matters enough to find.

If you find yourself cancelling 1:1s regularly, it is worth asking whether the meeting is genuinely lower priority than the things replacing it — or whether you are subtly avoiding it for some other reason. Sometimes the meeting feels uncomfortable because there is an unresolved tension with the employee, and the easiest short-term response is not to have it. That is precisely when it needs to happen.

Making notes and following through

Without notes, a 1:1 becomes a pleasant conversation with no memory. With notes — brief, shared, or at least reviewed before the next meeting — it becomes a record of commitments made, things raised, and threads to pick up.

The question “last time you mentioned X — how did that go?” is a small act that has an outsized effect. It tells the person that you were listening, that the previous conversation mattered, and that you hold what they tell you rather than treating each meeting as a blank slate. Most people, most of the time, do not experience that from their managers. Being the manager who does is not complicated. It requires a ten-minute review of last week’s notes before the meeting begins.

Managers who want to sharpen their one-to-one skills alongside other core people management competencies can find structured CPD pathways at SkillsCircle, developed by Accipio. For managers seeking a recognised qualification in leadership and management, Aicura offers CMI-accredited programmes, including levy-funded apprenticeship routes.

Advertisement