How often should you hold one-on-ones: weekly or every two weeks?

Dongyoung Kim, CPO

The baseline for one-on-ones is weekly or every two weeks, for about 30 minutes each. When the gap stretches toward a month, feedback comes too late and conversations drift toward whatever happened most recently. You do not need the same cadence with everyone: meet new hires and people in new roles more often, and experienced team members every two weeks. If you are just starting, fix it at 30 minutes every two weeks and revisit the cadence with each team member after three months.

What research says: weekly or every two weeks

The most cited research on one-on-one frequency comes from Steven Rogelberg, a professor at the University of North Carolina at Charlotte. Over three years he ran a global survey of 1,200 knowledge workers, a US survey of 250 employees, and interviews with about 50 top leaders at Fortune 100 companies (Rogelberg, 2024). Three conclusions bear on frequency.

  • Weekly or every two weeks fits the evidence best. Rogelberg sums up the science as most aligned with a weekly or every-other-week approach.
  • Monthly meetings drift to recent events. Meeting once a month, people mostly discuss what happened recently rather than looking back over the whole month.
  • The team member should talk more. Rogelberg puts the ideal share of talking by the direct report at 50 to 90 percent.

Gallup's research points the same way. Introducing its State of the American Manager report, Gallup found that employees whose managers hold regular meetings with them are almost three times as likely to be engaged as those who do not (Gallup, 2015). Gallup also says 15 to 30 minutes is enough for a meaningful conversation, but only if it happens frequently, and that 80% of employees who received meaningful feedback in the past week are fully engaged (Gallup, 2023).

These figures show the effect of regular, meaningful conversations; they do not compare weekly against biweekly. What matters more than the cadence you pick is keeping it without skipping. For the overall flow of a one-on-one, start with How do you run a one-on-one (1on1)?.

How long should a one-on-one be?

Thirty minutes is the baseline. The more often you meet, the shorter each meeting can be; the longer the gap, the more there is to catch up on. Orblit recommends the following.

CadenceLengthFits
Weekly20-30 minNew hires, people taking on new work, fast-changing teams
Every two weeks30-45 minMost experienced individual contributors, teams just starting one-on-ones
Monthly60 minDirection and career conversations with senior members and sub-team leads

By Rogelberg's count, 30 minutes a week with one team member adds up to about 25 hours a year (Rogelberg, 2024). Small amounts of time, often, change more than one long meeting. You do not have to fill the slot: if the team member's topics are covered and next steps are agreed, it is fine to end early.

Setting the cadence by each team member's situation

Set the cadence per person, not for the whole team. In High Output Management, Intel's Andy Grove advised meeting often with someone inexperienced in the task at hand and less often with an experienced veteran. Even the same person becomes less experienced again when they take on a new project. Building on this, Orblit recommends the following cadences.

SituationCadenceLengthFocus
First three months after joiningWeekly30 minSettling in, expectations, where they are stuck
New role or projectWeekly, then every two weeks once settled30 minPriorities, support needed
Experienced individual contributorEvery two weeks30-45 minGrowth, feedback, collaboration
Senior member or sub-team leadEvery two weeks (monthly at most)45-60 minDecision rights, direction, developing others
Performance issue or signs of burnoutWeekly for a while20-30 minFinding the cause, small agreements, checking progress
Remote or hybrid workWeekly and short20-30 minSharing work context, checking for isolation

It is tempting to space out meetings with senior people, but beyond a month you hear about important decisions too late. More in How do you run one-on-ones with senior employees?. If you are new to managing, focus on the order of the conversation over your first three months rather than changing the cadence: listening first, then aligning expectations, then growth and feedback, as laid out in How should a new manager start one-on-ones?.

Budgeting one-on-one time on a larger team

Before choosing a cadence, work out how much time one-on-ones will take each week: number of direct reports × length of each meeting ÷ cadence in weeks.

Direct reportsWeekly, 30 minEvery two weeks, 30 minEvery two weeks, 45 min
42 h/week1 h/week1.5 h/week
63 h/week1.5 h/week2.25 h/week
84 h/week2 h/week3 h/week
105 h/week2.5 h/week3.75 h/week

For a team lead who also does hands-on work, Orblit sees 2 to 3 hours a week as a realistic ceiling. With more than eight direct reports, adjust like this.

  1. Make 30 minutes every two weeks the default, and keep only new hires and people with open issues weekly.
  2. Move status reporting to team meetings or a work board, and use one-on-ones for where the work is stuck and what help is needed.
  3. If you have sub-team leads, hand them some of the one-on-ones, and meet the sub-team leads every two weeks yourself.

Avoid switching everyone to monthly because time is short. As above, monthly conversations drift to recent events, and small problems surface only after they have grown.

Four rules for keeping the cadence

Keeping a cadence is harder than setting one. Agree on these four things as well.

  1. Use a fixed slot. Pick a day and time, such as every other Tuesday at 10, and make it a recurring event. If you schedule each one separately, the busy weeks drop out first.
  2. Reschedule, do not cancel. If something urgent comes up, rebook within the same week. When the leader keeps cancelling first, team members read one-on-ones as a low priority.
  3. Book long conversations separately. As one-on-ones become short and frequent, conversations that need more room, such as career talks or mid-cycle performance feedback, are better held separately every month or quarter. For how one-on-ones differ from reviews, see How is a one-on-one different from a performance review?.
  4. Review the cadence every three months. Ask the team member directly: "Is our current cadence right, or would meeting more or less often be better?" "What conversation in our recent one-on-ones helped you most?"

The shorter the cadence, the more notes matter. Start each one-on-one by checking the action items agreed last time, so the conversation carries on. A format for the notes is in How do you structure a one-on-one doc?.

Frequently Asked Questions

Q.Do one-on-ones have to be weekly?
No. The research treats both weekly and every two weeks as a good range. Start weekly with new hires and people taking on new work, and every two weeks with everyone else.
Q.Do monthly one-on-ones work?
They beat none at all, but conversations drift to recent events and feedback comes late. If you must stay monthly, add a short 15-minute check-in in between.
Q.If time is tight, is 15 minutes enough?
Yes. Gallup considers 15 to 30 minutes enough for a meaningful conversation. But the shorter the meeting, the more often you should meet, and the team member should write down topics in advance.
Q.What if I keep cancelling one-on-ones?
It may be a sign the cadence is too short for the current workload. It is better to move from weekly to every two weeks and keep that without fail. Other reasons for repeated cancellations are covered in Why do one-on-ones fail?.
Q.What if a team member says there is nothing to talk about and wants fewer one-on-ones?
Rather than cutting them right away, shorten them to 15 minutes and keep the cadence. "Nothing to talk about" often means the one-on-one has turned into a status report. Try shifting to other topics such as growth or collaboration.

ORBLIT

How Orblit helps

To make it easier to put this article into practice, Orblit helps in these ways.

  • 01A different cadence for each person

    Once you set a one-on-one cycle, Orblit keeps track of recurring meetings with email and push notifications. It also works with Google Calendar and Google Meet.

  • 02Start from last time's commitments

    Record the conversation and AI organizes it into a summary and action items, which carry over into preparing the next one-on-one.

  • 03Make short one-on-ones count

    Team members write their prep before the meeting, with an AI chatbot helping them organize it, so even a 15- to 30-minute one-on-one gets straight to the point.

  • 04Help the team member talk more

    AI leadership coaching shows the speaking ratio of leader and team member, and analyzes what the leader said to point out strengths and areas to improve.

Sources

  1. Unlocking the Potential of 1:1 Meetings · Next Big Idea Club (Steven Rogelberg) · 2024-01-09
  2. Employees Want a Lot More From Their Managers · Gallup (Jim Harter, Amy Adkins) · 2015-04-08
  3. A Great Manager's Most Important Habit · Gallup · 2023-05-29
  4. High Output Management · Andrew S. Grove

Read next

How do you run a one-on-one (1on1)?

Fix the schedule, have the team member write their topics in advance, and after the conversation record what you agreed so you can check it at the next meeting. If you are new to one-on-ones, start with 30 minutes every two weeks, then adjusting the cadence and length to how familiar each person is with their current work. What matters most is that the meeting is not canceled and keeps a predictable rhythm.

Dongyoung Kim, CPO

How do you structure a one-on-one doc?

A one-on-one doc is where you prepare for and record the meeting, and it needs only three parts: the prep the team member writes in advance, notes taken during the meeting, and the action items you agree on. Questions to ask are better chosen for each situation than fixed in the doc. Keep it short and use the same frame every time, starting each meeting by checking last time's action items.

Dongyoung Kim, CPO

How do you run one-on-ones with senior employees?

Use one-on-ones with seniors to align decision scope and direction rather than to check progress. Talk about how far they decide on their own, what they see in the team and organization, and what role they want next, and record the help they give colleagues and the team so it is reflected in reviews. Do not stretch the gap between meetings too far just because they are experienced.

Dongyoung Kim, CPO