A one-on-one meeting is a regular, private conversation between a manager and a direct report covering progress, obstacles, feedback and development. It is typically held monthly for frontline teams and weekly or fortnightly for desk-based roles, and is the foundation of continuous performance management.
One-on-one meetings explained
A one-on-one is not a status update. If the conversation only covers what happened operationally, it duplicates a report and should be cancelled in favour of reading the report.
What makes it a one-on-one is that the agenda belongs at least as much to the employee as the manager, and that it covers things a status update cannot: what is getting in the way, how the person is finding the work, what they want to learn, and what the manager could do differently.
Why one-on-ones matter more than any other performance practice
The relationship with the direct manager is the strongest single predictor of whether an employee stays. The one-on-one is where that relationship is built or neglected.
It is also the earliest warning system an organisation has. Disengagement almost always shows up in a one-on-one months before it shows up in a resignation, but only if the conversation is happening and the person feels safe being honest.
How to run a one-on-one
Use the same four questions each time so the conversation compounds: what went well, what got in the way, what feedback do you have for me, and what do you want to learn next.
Keep notes and carry them forward. A one-on-one that starts from a blank page each month is a series of unrelated conversations rather than a developing relationship.
Protect the time. The one-on-one is the first thing cancelled in a busy week, which means it disappears exactly when it is most needed.
Fifteen minutes done consistently beats an hour done occasionally.
One-on-ones vs performance reviews
The one-on-one is frequent, informal and forward-looking. The review is periodic, documented and retrospective.
Where one-on-ones happen properly, the review contains no surprises and takes half as long, because it summarises a documented record rather than testing two people's memories.
Common mistakes
- Letting it become a status update that could have been an email
- Cancelling whenever the week gets busy
- Talking for most of it — the employee should be doing more of the talking
- Never asking for feedback upward, which caps how honest the conversation can become
- Keeping no record, so every conversation restarts from nothing
Frequently asked questions
A regular private conversation between a manager and direct report covering progress, obstacles, feedback and development.
Monthly is the practical minimum for frontline teams. Weekly or fortnightly suits desk-based roles, and weekly is worth it for new starters in their first ninety days.
Fifteen to thirty minutes. Consistency matters far more than length.
What went well, what got in the way, what feedback the employee has for you, and what they want to learn next. Keep the same questions so the conversation builds.
Both, but the employee should have at least equal input. A manager-only agenda produces a status update rather than a conversation.