One-to-one meetings: how to run a 1:1 worth the hour

One to one meetings are worth the hour when they do three things nothing else in the week does: remove an obstacle, deliver feedback close enough to the event to be useful, and surface what the person actually thinks. They are not for status, because status can be read. The difference between the two versions comes down to who brings the agenda and what the manager asks in the first five minutes.

Ask a manager what their one-to-ones are for and you usually get a pause. Ask the person on the other side and you get a clearer answer: it is where they tell their manager what they have been doing. That is a status meeting, and it is the reason one-to-ones are the first thing cancelled when a week gets busy. Nobody protects a meeting whose value they cannot name.

A 30-minute one-to-one meeting template

A script is worth more than a form. This one fits inside half an hour, puts the obstacle question before the conversation fills with updates, and leaves the manager somewhere to put what they need to say.

Two of those five slots belong to the other person by design. That single choice does most of the work, and it is nearly free.

How often should one-to-ones happen?

Fortnightly for most people, weekly for anyone who joined in the last three months and anyone in difficulty. Weekly for everybody stops being sustainable somewhere around six direct reports, and unsustainable cadences get cancelled rather than shortened. A protected thirty minutes every two weeks is worth more than an hour a week that slips one time in two.

Decide what it is for

A one-to-one is the only recurring slot where four things can happen that happen nowhere else: an obstacle gets removed, feedback arrives close enough to the event to be useful, someone says what they actually think, and development gets more than a passing mention.

Status is not on that list, because status can be read. If the meeting is being spent on what happened, it is doing a job a written update does better and cheaper.

The agenda belongs to the other person

The person being managed brings the agenda. The manager brings whatever they need to add and holds the last third of the time.

It matters for a reason that is not obvious: when the manager owns the agenda, the meeting is optimised for what the manager needs to know. When the other person owns it, the meeting surfaces what they are stuck on — which is the thing the manager is actually there to unblock, and the thing they will otherwise find out about three weeks late.

Four questions that carry most of it

A template is less useful than a small number of questions a manager can return to when the conversation stalls.

1. What is in your way? The most valuable minute of the meeting. Ask it early, before the conversation fills with updates.
2. What are you unsure about? Different from the first question, and harder to ask for. It surfaces the decisions someone is quietly avoiding.
3. What have I got wrong? Uncomfortable, and the fastest route to the things people do not volunteer. It only works if the answer is never punished.
4. What do you want to be better at? The development question. Asking it once a quarter is enough; never asking it is what makes development conversations feel like an annual performance ritual.

A manager who has never run one of these conversations does not learn it from a template. They learn it by practising on real cases, which is why it belongs in new manager training rather than in a document.

Length, notes, and cancelling

What to do when it keeps slipping

Repeated cancellation is rarely about time. It is usually one of three things, and they have different fixes.

• The manager has too many reports. Below about six, one-to-ones fit around the work. Above nine or ten they compete with it, and the calendar decides for you. That is a structure problem, not a discipline problem.
• The meeting has no value to protect. If it has been a status meeting for six months, cancelling it is a rational act. Change the meeting before asking for the commitment.
• There is something unsaid. A manager avoiding a conversation will find scheduling reasons indefinitely. This is the case worth naming directly, because it does not resolve on its own.

A one-to-one that is cancelled twice in a row has already communicated something. The question is whether the manager knows what.

Why this is a company decision, not a personal one

Left to individual preference, one-to-one meetings vary more than almost anything else in a company. Two people doing the same job in adjacent teams can have entirely different experiences of being managed, and the difference is invisible until one of them resigns.

That is why the format belongs in a company-wide set of Leadership & Management Routines rather than in each manager's judgement: not to standardise the conversation, but to make sure everyone is having one.