Weekly or Biweekly? Choosing the Right 1:1 Frequency

The short answer: weekly by default

For most manager-report pairs, a weekly 30-minute 1:1 is the right answer. Not because more meetings are better — they usually aren't — but because a week is roughly the interval at which small problems are still small. A confusing priority, a simmering conflict with a peer, a blocked decision: catch any of these within seven days and it's a five-minute conversation. Catch it at day 25 and you're doing damage control.

Andy Grove's framing in High Output Management is still the most useful one: frequency should track what he called task-relevant maturity — how experienced this person is at the specific work in front of them right now. Not their years of experience, not their title. A staff engineer who just inherited an unfamiliar legacy system has low task-relevant maturity for that work and needs more of your time, not less. This is why 'senior people need fewer 1:1s' is a half-truth that gets managers in trouble.

The three-factor framework

When you're deciding between weekly and biweekly for a specific person, run them through three factors:

• Tenure on your team. Under six months with you: weekly, no exceptions. Tenure elsewhere doesn't transfer — they're still learning how you operate, what you care about, and what 'good' looks like here.
• Autonomy of their current work. If they own a scope end-to-end, make most decisions without you, and mostly use 1:1s to keep you informed, that's a vote for biweekly. If their work needs frequent unblocking or direction from you, weekly.
• Rate of change around them. A reorg, a new product direction, a role change, a struggling project — any of these resets the clock to weekly, regardless of tenure or seniority. Stability is a prerequisite for biweekly, not a personality trait.

Score it simply: biweekly requires all three — tenured, autonomous, stable. Two out of three is still weekly. That's deliberately conservative, because the cost of over-meeting is mild boredom and the cost of under-meeting is finding out about problems from someone else.

What monthly actually costs

Monthly 1:1s sound efficient — twelve meetings a year per person, tidy. In practice, a month is long enough that the meeting stops functioning as a 1:1 at all. With four-plus weeks between conversations, anything urgent finds another channel (or worse, no channel), feedback arrives as ancient history instead of coaching, and small frustrations have time to harden into a decision to leave. Managers who lose someone 'unexpectedly' are very often managers on a monthly cadence — the signals were there, but there was no room on the calendar for them to show up.

Monthly meetings also collapse into status reviews by necessity. Too much has happened to talk about anything but the work, so career growth, energy levels, and the awkward stuff never make the cut. It's exactly the cadence at which you'll miss the early signs of burnout, because those show up as small week-to-week shifts in tone, not one dramatic announcement.

The one place monthly makes sense is when you're not the direct manager. Skip-levels and dotted-line relationships run fine on a monthly or quarterly rhythm, because someone else holds the weekly one.

Shorten before you cancel

The most common cadence failure isn't picking the wrong frequency — it's the slow-motion cancellation spiral. Crunch hits, the 1:1 looks like the most movable block on the calendar, and it gets bumped 'just this once,' then again. Your report reads each cancellation exactly the way you'd read your own manager canceling on you: as a ranking. Two skips in a row and the meeting has effectively changed frequency without anyone agreeing to it.

So when time pressure is real, downshift the length, never the rhythm:

• Cut 30 minutes to 15: what's the top thing on their mind, the top thing on yours, and what they need from you this week. Done.
• Move it within the same week instead of skipping. Same-week reschedules are hygiene; next-week ones are cancellations wearing a costume.
• If you truly must skip, replace it with something async — two or three specific written questions with real answers, not a 'we good?' thumbs-up.

A tight 15 minutes still lets the important stuff surface, especially if you keep a running agenda so neither of you burns half the meeting reconstructing context. And if you notice you've shortened six weeks in a row, that's not a scheduling problem — that's a signal to renegotiate the cadence honestly instead of quietly starving the meeting.

How to renegotiate cadence explicitly

Cadence changes go badly when they happen implicitly — cancellations pile up, or a weekly quietly becomes 'whenever.' Make it an explicit, two-way conversation, and put a review date on it so it's an experiment rather than a verdict.

Downshifting to biweekly, the script sounds like: 'You've been running your area end-to-end for a while, and our last month of 1:1s has been pretty light — which is a good sign. Want to try biweekly for a quarter? If anything feels off, we go straight back to weekly. This is me trusting your autonomy, not deprioritizing you.'

Upshifting is even easier to get wrong, because it can read as alarm. Anchor it to circumstances, not the person: 'With the reorg landing, I want to move us to weekly through the end of the quarter so nothing gets stuck.' Nobody hears that as a performance concern when the reason is external and the end date is stated.

Two details that matter: ask for their preference and actually weigh it — some people genuinely work better with denser or looser contact — and write the review date down. 'Let's try it' with no checkpoint is how experiments become permanent by accident.

A cheat sheet by situation

• New hire, first 90 days: weekly, 45 minutes to start. Your first 1:1 with a new employee sets the template for everything after.
• Internal transfer, new to your team: weekly, 30 minutes. Their company tenure doesn't cover learning how you work.
• Tenured, autonomous senior report with stable scope: biweekly, 45 minutes. The longer block keeps room for career and growth topics that die in short biweeklies.
• A manager reporting to you: weekly 30 during any org change; biweekly 45 in calm waters.
• Someone struggling or on a performance plan: weekly, non-negotiable, however senior they are.
• Remote reports: bias one notch more frequent than the framework says. Remote 1:1s carry the load that hallway conversations carry in an office.
• Skip-levels: monthly or quarterly is fine — you're not their manager, and someone else holds the weekly rhythm.

Revisit it twice a year

Cadence isn't a setting you configure once. Put a recurring reminder — every six months is plenty — to ask whether each 1:1's frequency still fits. The signals are readable if you look. Too infrequent: you keep getting surprised in other meetings by things you should have heard first, your report shows up with a 40-minute backlog of topics, or your feedback keeps landing weeks after the moment it describes. Too frequent: agendas from both sides have been thin for a month straight, meetings routinely end early, and a cancellation quietly relieves you both.

Your notes are the best evidence you have. If the last six weeks of notes run three lines each, the meeting may have room to stretch; if every meeting spills over, it needs more room, not less. A tool like Teammons keeps the running agenda and note history in one place, which turns this call into an observation instead of a guess. However you track it, decide on purpose — the worst cadence is the one nobody chose.