Skip to content
Kayley HartThe Small Team Builder

Managing People

How to Run Effective One-to-Ones With Your Team

10 min read · Published 3 August 2026 · Last reviewed 11 August 2026 · Written by Kayley Hart

The short answer

Run a short, regular, protected one-to-one — thirty minutes, fortnightly is a workable default for a small team — that opens with their agenda, not yours, covers progress and feedback both ways, and ends with a short list of agreed actions. It should almost never be cancelled: cancelling it repeatedly signals that it isn't actually a priority.

Guide action map

Illustrative framework

How to Run Effective One-to-Ones With Your Team

How to Run Effective One-to-Ones With Your TeamA practical four-part route through this topic. Use the guide’s detailed sections to turn each stage into a decision, a written rule and a repeatable routine.1DecideClarify the outcome2DocumentMake the rule visible3DoUse it in real work4ReviewCheck the evidence
A practical four-part route through this topic. Use the guide’s detailed sections to turn each stage into a decision, a written rule and a repeatable routine.

Reviewed by a qualified professional

James Whitfield — FCCA, Chartered Certified Accountant — 18 years advising UK SMEs on employment costs, payroll and business finance. Reviewed 5 August 2026.

Author: Kayley Hart

Editorial policy & fact-checking apply.

What you will take away

  • • A one-to-one that only covers task status is a status meeting wearing a one-to-one's name.
  • • Their agenda comes first, before yours, in every session.
  • • Protect the slot — repeated cancellation does more damage than most founders realise.
  • • Fortnightly, thirty minutes is a workable default; adjust cadence to role and experience, not to how busy you feel.
  • • Write down agreed actions before the conversation ends, not from memory afterwards.
  • • A one-to-one is where small problems get raised before they become resignations.

What a one-to-one is actually for

A one-to-one is not a project update dressed up as a meeting. Its real purpose is to create a reliable, predictable space where the other person can raise what's actually on their mind — a blocker, a concern about direction, a personal issue affecting their work, feedback they're not comfortable raising unprompted — without needing to request a special meeting to do it.

In a small team, this matters more than in a large one, because there's often no HR function, no peer group of other managers, and no anonymous survey to surface problems. The one-to-one is frequently the only structured channel that exists, so if it degrades into a status check, real issues have nowhere left to surface until they've grown much larger.

Setting the cadence and protecting it

Thirty minutes, fortnightly, is a workable starting point for most small-team roles. Someone new to the role, or going through a difficult patch, may benefit from a shorter, more frequent cadence — weekly for a few weeks — before settling back to the default. Someone experienced and steady in role can sometimes move to monthly, but be cautious about stretching the gap too far in a small team where problems tend to compound quickly if unaddressed.

The single most damaging thing you can do to a one-to-one is cancel it repeatedly for other priorities. Even one or two cancellations send a clear signal about where the person actually sits in your priorities, however unintentional that message is. If you must move it, move it — don't simply let it disappear from the calendar.

A structure that keeps it a conversation, not a status report

A simple, repeatable structure prevents the one-to-one from drifting into whatever feels urgent that day. Start with their agenda — genuinely ask what's on their mind before you bring your own list — because if you open with your topics, theirs will get pushed to the end or dropped altogether, and over time they'll stop bringing anything at all.

After their items, move to progress against current work, then feedback in both directions, then development — anything they want to grow into or learn — and finish with a short written note of agreed actions before either of you leaves the room or call.

  1. Their agenda first: what's on their mind, blockers, questions
  2. Progress: what's moved forward since last time, what hasn't
  3. Feedback: from you to them, and genuinely invite it from them to you
  4. Development: anything they want to grow into or learn
  5. Actions: a short written note of what's agreed before you both finish

If you notice every one-to-one is just you reading through a task list together, you've drifted into a status meeting — deliberately leave space for what isn't on the list.

Genuinely inviting feedback upward

Most first-time managers ask for feedback as a formality — 'anything for me?' — in a tone that signals they'd rather not hear it, and most employees pick up on that instantly and say no. If you actually want to hear how you're doing as a manager, ask a specific question rather than an open one: 'is there anything I did in the last fortnight that made your work harder?' tends to produce a real answer far more often than a general invitation.

When you do get feedback, resist the urge to explain or defend immediately. Thank them, ask a clarifying question if needed, and take it away to consider properly. Defending yourself in the moment teaches people that offering feedback upward isn't actually welcome, and they'll stop doing it.

What to do when nothing comes up

New managers often worry when a one-to-one feels quiet — nothing raised, no issues, a short conversation. This is not automatically a problem; some fortnights genuinely are uneventful. But if it happens consistently over several sessions, it's worth checking whether the person actually feels able to raise things, rather than assuming everything is fine.

A useful check is to ask a specific, low-stakes question rather than a general one — 'what's the most frustrating part of your week at the moment' tends to surface something even when 'is everything okay' doesn't.

Remote and asynchronous one-to-ones

For remote or hybrid teams, the one-to-one carries even more weight, because it may be one of the only points of unscheduled, non-task conversation in the working relationship. Keep the camera on where practical, protect the time as firmly as you would an in-person meeting, and resist the temptation to multitask during it — the person can usually tell.

Sending a brief written agenda prompt beforehand ('anything you want to raise before we speak?') can help people who think better in writing prepare properly, and it reduces the chance that something important gets forgotten in the moment.

Common mistakes that undermine one-to-ones

A small number of habits reliably erode the value of one-to-ones even when the intention behind them is good.

  • Cancelling or repeatedly shortening the meeting when things get busy
  • Opening with your agenda instead of theirs
  • Turning every one-to-one into a review of open tasks only
  • Reacting defensively to feedback, which trains people to stop offering it
  • Not writing down agreed actions, so nothing from the conversation is actually followed up

Do it now, with a tool

One-to-One Meeting Builder

Builds a repeatable one-to-one agenda and a record of agreed actions.

Open the tool (3 minutes)

Delegation Ladder Builder

Sets the authority level for each task, from 'do exactly this' to 'decide and act, tell me quarterly'.

Open the tool (4 minutes)

Frequently asked questions

How long should a one-to-one last?

Thirty minutes is a workable default for most small-team roles. Shorter tends to squeeze out real conversation; much longer tends to drift without a clear structure. Adjust based on what the relationship actually needs, not a fixed rule.

What if the person says they have nothing to raise?

Accept it some weeks, but if it becomes a consistent pattern, ask a more specific question rather than a general one, and consider whether something about how the meeting runs is discouraging openness.

Should one-to-ones be documented?

A short note of agreed actions is worth keeping, both so nothing gets forgotten and because a simple record is useful if a performance or conduct issue ever needs to be evidenced later. It doesn't need to be a formal minute of the whole conversation.

Is it okay to combine one-to-ones with project updates?

A brief progress check is fine as one part of the structure, but if it becomes the whole meeting, the space for anything else disappears. Keep progress as one section among several, not the entire agenda.

How do I run one-to-ones with someone I'm close friends with outside work?

Keep the structure the same and be explicit that it's a working conversation, not a catch-up, even if the relationship is warm. This protects both of you if a genuine performance issue ever needs to be raised later.

Sources & Citation

Cite this guide

Hart, K. (2026) "How to Run Effective One-to-Ones With Your Team". The Small Team Builder. Available at: https://www.kayleyhart.co.uk/guides/how-to-run-effective-one-to-ones-with-your-team

Rates, thresholds and rules change. Confirm anything financial or legal on the source before you act on it.