The one-on-one is in the calendar every other week. Most of them get moved. The ones that happen turn into a status update: what is going on in the project, what is blocking, what is due Friday. Twenty minutes later both people go back to work, and nothing was said that could not have been said in the team meeting.
That is the most common way one-on-ones fail. Not by being skipped, but by being held about the wrong things.
This guide covers what a one-on-one meeting is for, why it is the most important recurring meeting a manager has, how often to hold one and how long it should be, how to structure 30 minutes, what to talk about, and the mistakes that empty it of meaning. The questions to ask and ready-made agendas are in separate articles linked along the way.
What a one-on-one meeting is
A one-on-one is a regular, private conversation between a manager and a team member about the team member's work, wellbeing and development. It is short, usually 20 to 30 minutes, and frequent, usually every one to two weeks. It belongs to the team member: the topics are theirs, the manager listens and asks.
It is different from two meetings it is often confused with:
- Not a status update. Project status belongs in the team's own routines. If a one-on-one is spent on tasks and deadlines, the team member loses the only regular time they have to talk about how the work feels and where it is heading.
- Not the development discussion. The development discussion, in Finland the kehityskeskustelu, is a longer conversation once or twice a year about direction, skills and growth. The one-on-one is the lighter conversation in between, in which the agreements of the development discussion are followed up. How to run that longer conversation is covered in development discussion: what it is, why it matters and how to do it well.
Why one-on-one meetings matter
The case for one-on-ones rests on one finding that keeps repeating in engagement research: the manager is the single biggest factor in whether an employee is engaged, and regular conversation is the mechanism. According to Gallup, employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not.
Three things happen in a good one-on-one that do not happen anywhere else.
The manager hears what is actually going on. In team meetings people report what is safe to report. In a private conversation with a manager who listens, they say what is frustrating them, what they are unsure about and what they are considering. A manager without one-on-ones leads on assumptions.
Small problems stay small. Workload that is creeping up, a collaboration that is turning sour, a skill gap that is becoming visible. Caught every two weeks these are conversations. Caught once a year they are resignations.
Agreements get followed up. A development discussion produces one or two agreed actions. Without a regular place to return to them, they are forgotten by November. The one-on-one is that place.
How often, and how long
The honest answer is: often enough that nothing important waits more than two weeks, and short enough that the meeting never gets moved because it is too big.
- Every week or every two weeks is the range that works for most teams. Weekly for new team members, remote teams and periods of change. Every two weeks once things are steady.
- 20 to 30 minutes is enough when the structure is clear. Longer meetings drift into status updates. If 30 minutes is regularly not enough, the topics belong in a separate conversation, not a longer one-on-one.
- Same slot, never cancelled, sometimes shortened. Moving a one-on-one tells the team member they are lower priority than whatever moved it. If there is nothing to discuss, hold a ten-minute check-in and end early.
A useful comparison between the two conversation types:
One-on-one meeting
- Every 1 to 2 weeks, 20 to 30 minutes
- Time horizon: the coming weeks
- Topics: how everyday work is going, obstacles, feedback, wellbeing
- Outcome: one or two agreed actions, followed up next time
Development discussion
- Once or twice a year, 45 to 90 minutes
- Time horizon: the current and the coming year
- Topics: direction, skills and development
- Outcome: a written development plan
How to structure 30 minutes
A one-on-one needs a light structure, or it becomes whatever is loudest that week. The structure below fits in 30 minutes and leaves the topics to the team member. Ready-made agendas for weekly, monthly and first one-on-ones are in one-on-one meeting template: three agendas that fit in 30 minutes.
- Check-in, 3 minutes. How are things, really. Not the project. The answer often decides what the rest of the meeting is about.
- The team member's topics, 12 minutes. Whatever they brought. If they brought nothing, ask what has been on their mind since last time. Their topics always come before the manager's.
- The manager's topics, 7 minutes. Feedback, something observed, a heads-up about what is coming. Short and specific.
- Follow-up on last time, 5 minutes. What was agreed, what happened. Skipping this step is how agreements die.
- Agreements, 3 minutes. One or two things, written down so both see the same text, with a date.
The times are indicative. If the check-in reveals that a person is heading for burnout, the rest of the meeting is spent on that.
What to talk about
The best one-on-one topics come from the team member, and the manager's job is to ask the follow-up questions: how do you notice that, give me an example, what should be done about it. Thirty example questions grouped by situation, for a new team member, a quiet team member or a meeting where nothing came of last time's agreements, are in one-on-one meeting questions.
Topics that belong in a one-on-one: how the work feels, what is getting in the way, workload and energy, feedback in both directions, collaboration inside and outside the team, learning and next steps.
Topics that do not: task status, pay, and anything that needs a decision from someone who is not in the room. Those get their own meeting.
The most common one-on-one mistakes
It becomes a status update. The manager asks about the project, the team member reports, the meeting ends. The fix is a rule: status has its own place, and the one-on-one starts with the check-in, not the backlog.
The manager talks. If the manager talks for more than half the time, it is not a one-on-one but a briefing. A good rule of thumb: the team member talks two thirds of the time.
No notes, no follow-up. Without a shared record, each one-on-one starts from zero and the same topics come up month after month. One line per agreement, with a date, visible to both.
It gets moved. Once is fine. Regularly means the meeting has no value in the manager's calendar, and the team member notices.
Only problems. A one-on-one that only ever covers what is wrong becomes something to dread. Ask what went well, and say what you noticed going well.
One-on-ones with cards
Everything above can be done with a notebook and a calendar invite. Still, most managers know the two hardest parts are getting a quiet team member to bring topics, and keeping their own talking to a third.
Topaasia One-on-One is a one-on-one in which the team member picks from the cards the topics that feel important right now and explains their choices. The manager acts as the game master: listens, asks and writes down. The session ends with one most important thing and a concrete action, and the documentation is created during the conversation. No preparation is needed from either side.
Saranen Consulting holds one-on-ones with the cards every other week. According to team manager Mia Santala, 45 minutes was enough for the conversation, the insights and agreeing on actions, and the cards made it easier for her to hold back from advising and let the team member reach their own conclusions. The full story is in Saranen's customer story. At Entteri the cards replaced a form that some team members left blank, and the conversations flowed even with the quieter ones: Entteri's story.
More than 1,310 development discussions and one-on-ones have been played with Topaasia, with a participant rating of 4.59 out of 5. How it works and what it costs is on the development discussions page.
Frequently asked questions about one-on-one meetings
What is a one-on-one meeting?
A regular, private conversation between a manager and a team member about the team member's work, wellbeing and development. It is short and frequent, and the topics belong to the team member.
How often should one-on-ones be held?
Every week or every two weeks. Weekly for new team members, remote teams and periods of change. What matters most is that the slot is fixed and not moved.
How long should a one-on-one be?
20 to 30 minutes is enough with a clear structure. If it is regularly not enough, the extra topics belong in a separate conversation.
Who sets the agenda?
The team member. The manager adds their own points after the team member's topics, not before.
What is the difference between a one-on-one and a development discussion?
A one-on-one is a short, frequent conversation about the coming weeks. A development discussion is a longer conversation once or twice a year about direction, skills and growth. In a good model the one-on-ones follow up on what was agreed in the development discussion.
Should I take notes in a one-on-one?
Yes, but only the agreements: one line each, with a date, visible to both. Not a transcript.
The one-on-one is the manager's most important half hour
Everything a manager knows about their team member that is not visible in a meeting comes from the one-on-one. It does not need a form. It needs a fixed slot, a short structure, the team member's topics first, and a record of what was agreed that both people can see.
Sources
- Gallup (2015). Employees Want a Lot More From Their Managers.