What is a one-on-one (1on1)?

What is a one-on-one?

A one-on-one (1on1) is a regular conversation in which a leader and a team member meet one-to-one to talk about work and growth. Depending on the organization, it is also called a 1:1, a one-to-one, or a one-on-one meeting.

Practices differ from company to company, but a conversation needs these three conditions to count as a one-on-one.

1. It has a set time. It is scheduled in advance and repeats, rather than happening only when someone is called in.
2. It is just the leader and the team member. It is a space for concerns and opinions that are hard to raise in a team meeting.
3. It is two-way. It is not a place to announce review results or instructions; the leader listens to the team member's situation and thinking, and together they decide the next step.

This article uses these three conditions to compare one-on-ones with conversations that are easy to confuse with them, and then covers topics, cadence, and how to get started.

What a one-on-one is not

Measured against those three conditions, some conversations look similar but are hard to call one-on-ones. Here are four that leaders and team members often confuse with them.

Similar names, but who calls the meeting and why changes the mood. Even if you call it a one-on-one, a meeting that happens only when something goes wrong is still a summons to the team member.

For examples of how tea time and a one-on-one differ in practice, see our Korean blog post Tea time vs. 1on1.

What do you talk about in a one-on-one?

Once you know what sets a one-on-one apart, the next question is what to talk about. There is no fixed answer. Harvard Business Review describes managers' goals for one-on-ones as aligning on expectations and building trust with team members, and says they can be used to give and receive feedback, set individual goals, and troubleshoot roadblocks (HBR, 2024). Building on that, the topics commonly covered fall into five groups.

• Work: what is in progress, what is blocked, priorities
• Expectations: whether goals and roles point in the same direction
• Feedback: from the leader to the team member, and from the team member to the leader
• Growth: what they want to learn, career concerns, the support they need
• Wellbeing: workload, engagement, working relationships

If the list feels long, you can group it under two questions: is the work running well, and is the person doing it okay? The first covers progress against goals, what is stuck, and the weight of the work; the second covers energy, the people they work with, and what they want to learn. Questions for checking each are collected by topic in the one-on-one questions list.

A one-on-one where the team member brings the topics is ideal, but it rarely starts that way. Team members new to one-on-ones often do not know what to raise and answer that nothing much is going on. For the first few, the leader can hand over the running order and a short set of questions, then pass the topics to the team member once they are used to it. An example of a form the team member can fill in beforehand is in the one-on-one doc.

How often should you hold them?

A question asked as often as what to talk about is how often to meet. There is no single standard. Orblit recommends repeating one-on-ones on a short cycle, from one week to one month, because long gaps such as twice a year or once a year make it easy to miss changes in between. Gallup recommends that managers have meaningful conversations with employees every week (Gallup, 2026).

In a 2015 Gallup analysis, employees whose managers hold regular meetings with them were almost three times as likely to be engaged as employees whose managers do not (Gallup, 2015). That is a correlation, though: it shows the two go together, not that regular meetings cause engagement.

If you are new to one-on-ones, start with 30 minutes every two weeks. Then adjust by how familiar the person is with their current work: weekly for a while with a new joiner or someone on new work, and less often, every two to four weeks, with a veteran. What matters more than the number is that the meeting is rarely canceled and repeats predictably. Guidelines for setting cadence and length by team size and how familiar people are with their work are in a table in how to run a one-on-one.

How to get started

Once you understand the definition, topics, and cadence, it is time to set up the first one-on-one. Start with these four steps.

1. Fix the schedule first. Set it as a recurring event, and if you must postpone, reschedule instead of canceling.
2. Share the purpose and ground rules with the team member. Make clear that it is not an evaluation and that the team member can choose the topic first.
3. Prepare ahead. The team member notes what they want to discuss beforehand, and the leader rereads the notes and commitments from the last conversation.
4. Write it down afterward. Record what you discussed and what each of you promised so the next conversation can pick up from there.

If you need more detail on any step, read on. The order of the conversation is in how to run a one-on-one, what to ask is in the one-on-one questions list, and forms for preparation and notes are in the one-on-one doc.

In practice, conversations often go well but leave no commitments behind, so each new one starts from scratch. The burden of preparing and taking notes is also a common reason one-on-ones stop. That is why Orblit has AI help with preparation, recording, summaries, and action items. Learn more at Orblit 1on1.

How Orblit sees one-on-ones

So far we have looked at the commonly used definition and how to run one-on-ones. Finally, here is how Orblit sees them. Orblit defines a one-on-one as any one-to-one conversation between a leader and a team member held to improve the organization's performance. Where the common definition above centers on the team member's growth, Orblit follows that growth through to the team's performance.

If one-on-ones are introduced only as time for a team member's growth, busy leaders tend to see them as something extra on top of the work, and it is hard to explain to executives why the company should adopt them. Growth matters in itself. But when it carries through to the team's performance, a one-on-one stops being an extra task squeezed in and becomes central to the leader's role.

Performance comes from conversation and follow-through

When a leader and a team member talk openly, and what they agree on actually gets done, the team member starts raising difficulties and the support they need earlier and more honestly. The leader can spot problems early and help, and that carries through to the team member's growth and the team's performance. Of course, many factors outside one-on-ones affect team performance, so a one-on-one alone does not guarantee it.

There is no single right way to talk

Coaching, where questions help the team member find their own answer, is not the only good one-on-one. If it helps the team's performance, each of these is a one-on-one too.

• Explaining and teaching how the work is done to someone who just joined
• The leader giving a concrete way through work that is stuck
• Coaching with questions so the team member finds the solution themselves
• Checking in on someone whose motivation has dropped or who is going through a hard time
• Light small talk that builds trust and makes hard topics easier to raise

Which approach fits depends on the person and the situation. Someone new to the work may need the leader to explain things thoroughly, while an experienced team member may get more from questions that draw out their thinking. Even with the same person, clearing a blocked task and thinking through a career call for different conversations. Reading the team member's situation and adjusting how you talk is leadership, and it is how one-on-ones are done well. The test is a single one: does the conversation help the team member grow and the team perform?