How often should you run 1:1s with your team?

A manager who asks "How often should I run 1:1s?" is asking a good question. In fact, only 50% of employees meet their manager for regular 1:1s.

But that's only the beginning. They should also ask: "What am I doing to make this ritual genuinely set the rhythm of how we work together?"

And the answer is to make the meeting completely reliable. 1:1s are the last slot you sacrifice.

Reliability beats frequency

A weekly 1:1 you push or cancel the moment the calendar gets tight is worth less than a biweekly one that always happens. The value of a 1:1 comes from being able to count on it: 1:1s are part of the report's and the manager's rhythm, and they should be a formal ritual that's there for the long haul.

When the report knows the meeting will happen, they make a point of stepping back to prepare for it, and that preparation already accounts for 80% of the value of a 1:1. A fixed slot like this keeps the focus on what actually matters to the report.

This is the basis of a rule many managers get backwards. When the week is overloaded, the common instinct is to protect the team meeting and sacrifice the 1:1s, because an individual slot feels easier to move than a group one.

It should be the other way around. The team meeting can often be handled in writing or condensed; the 1:1 is where the signals that go unsaid in a group come out, and it's exactly when the pace picks up that you need it most. So the 1:1 should be the last thing you move, and you move it rather than cancel it.

A cadence then comes down to a simple test: not the ideal interval on paper, but the one you'll keep nine weeks out of ten. Half an hour a week that actually happens beats an hour scheduled and honored every other time. Promising a cadence you don't keep sends a worse signal than committing to a lighter one: it tells the report the conversation doesn't really matter.

Choosing your cadence by context

The right frequency depends on a few variables: the person's autonomy, the stability of their scope, their seniority in the role, and distance. A new hire or someone wrestling with a new difficulty needs closer contact than an experienced report on a topic they've mastered. A distributed team has to make up for the absence of informal contact with stricter regularity.

Rather than reproduce a grid here, the 1:1 in the OKR glossary presents a cadence by context (direct manager, distributed team, skip-level, onboarding, cross-functional mentoring) that serves as a starting point. The key is the principle: cadence isn't a setting you fix once and forget, but a decision you adjust as the situation changes.

The signals that it's time to change cadence

Several signs call for tightening the rhythm:

• Topics pile up and each meeting overflows without your being able to cover everything.
• Blockers are discovered too late, once they've already hit execution.
• The report keeps catching their manager outside the 1:1, more and more often, for important but non-urgent topics, a sign that the current slot no longer holds everything they have to say.
• Or the context has just changed, through a new role, a new scope, a sensitive project, or a visible difficulty, all moments where more frequent contact helps for a while, before you ease off again.

Other signs point the other way, toward spacing things out.

• Meetings regularly end early, for lack of substance.
• The person has become highly autonomous on a stable scope and contact happens naturally elsewhere.
• Or most of what's said in the 1:1 could just as well be handled in the team meeting.

This last case deserves particular attention, because it doesn't necessarily mean you should space out: if the 1:1 largely overlaps the group ritual, it's often the split of roles between the two that needs revisiting, not the cadence. The team meeting syncs the collective; the 1:1 handles what doesn't get said in a group. This boundary is detailed in weekly rituals.

So cadence isn't a setting you lock in at hiring and forget. It's a decision you revisit at each change of context, and the right move is to treat it that way rather than wait for something to break before noticing.

Protecting the slot: what the data says

Protecting the 1:1 isn't just a matter of principle, it can be measured. Gallup finds that reports whose manager holds regular meetings are nearly three times as likely to be engaged as the others. An analysis published by Harvard Business Review points the same way: employees who get little or no one-on-one time with their manager are markedly more prone to disengagement, while those who get twice as much 1:1 time as their peers are 67% less likely to be disengaged.

These figures confirm the intuition: the effect comes from the time actually spent together, so from the meetings that actually happen, far more than from the cadence on paper. It's also what ties frequency to execution: a blocker spotted in a weekly 1:1 is handled earlier than one that waits for the next review, and that head start pays off directly on the trajectory of the team's objectives.

At Serendly, we help hold this regularity over time and tie each 1:1 to the team's objectives, so the conversation stays continuous. To understand how, discover our approach to 1:1s.