A one-on-one is a recurring private meeting between a manager and a direct report, focused on the report's work, growth, and blockers.
A one-on-one (1:1) is a private, recurring meeting between a manager and a direct report. It is the report's meeting — their agenda, their topics, their signal. The manager's job is to listen, unblock, and give feedback the report can act on. Andy Grove's High Output Management framed 1:1s as the highest-leverage activity a manager does; nothing you can build in an hour else yields the same information density about your team's actual state.
Weekly, 30-45 minutes, is the default that works for most manager-report relationships. Bi-weekly is acceptable for senior reports with a stable working relationship; anything less frequent means surprise becomes the norm and feedback loses timeliness. Never cancel; reschedule instead. A canceled 1:1 sends the message that the manager's time matters more than the report's work — which is not a message any manager intends to send.
The report owns the agenda. If the manager sets every topic, the meeting becomes a status update — which the manager could get from any async channel. The report should come with 2-5 items: what they're working on, what's stuck, what they need input on, what's frustrating them, what they're thinking about longer-term. A shared doc where both parties add items during the week works better than 'let's see what comes up.'
Good 1:1 topics: hard decisions the report is weighing, interpersonal friction, career questions, unclear priorities, feedback in both directions, project blockers that require the manager's context. Bad 1:1 topics: status updates already in the standup or project tracker, gossip about other teams, purely tactical questions that should be answered in Slack. If a 1:1 consistently fills with status, the report isn't using it well and the manager should coach them on what 1:1 time is for.
Give feedback in the 1:1 — not months later in a review, not in a Slack DM, not never. Structure: specific behavior, specific impact, specific ask ('When you interrupted Priya three times in the design review, she stopped contributing. Try letting her finish her thought before responding.'). Praise in public, correct in private. Feedback should be a normal weekly rhythm; when it only happens at review time it becomes an event, and events are terrifying.
(a) Skipping when 'nothing to discuss' — the value is in the consistency, not the topics of any single meeting. (b) Turning the 1:1 into a status meeting — kills all the actual signal. (c) Manager dominating the conversation — the report should talk 60-70% of the time. (d) No notes, no follow-through — commitments made in 1:1s should show up in the next 1:1. (e) Same 1:1 template for every report — a senior report and a new hire need very different conversations.
Investor directory · Fundraising library · Articles A–Z · Company funding database