A one-on-one that becomes a status update is a wasted meeting — that information belongs in a written update or a team standup. The purpose of a one-on-one is the conversation that would not happen otherwise: blockers the person has not raised anywhere else, feedback in both directions, and career progress that gets no other dedicated time on the calendar.
What changed in 2026
- Shared living documents replaced fresh agendas. Most teams now use a single running doc per person rather than starting from a blank agenda each meeting, which preserves context and open threads across weeks.
- Async pre-fill became standard practice. Direct reports are increasingly expected to add topics before the meeting starts, shifting the manager's role from agenda-setter to facilitator.
- Skip-level and peer feedback got folded into the cadence. More organizations now build in a periodic skip-level 1:1 or peer check-in alongside the standard manager 1:1, rather than leaving it purely reactive.
The structure that works
A good one-on-one has three loose zones, not a rigid script: what the direct report wants to raise, what the manager needs to raise, and a forward-looking career or growth check-in. The direct report's items go first — if the manager leads, the meeting defaults to their priorities by default, and the report's real topics get squeezed into the last two minutes or dropped entirely.
Cadence and length compared
| Cadence |
Length |
Best for |
| Weekly |
20-30 min |
New reports, fast-moving projects, early relationship-building |
| Biweekly |
30-45 min |
Established reports with a steady workload |
| Monthly |
45-60 min |
Senior reports who are largely autonomous |
| Ad hoc only |
Varies |
Rarely works well — issues surface too late without a standing slot |
Consistency matters more than the exact interval. A meeting that gets rescheduled repeatedly signals it is low priority, which erodes the trust the meeting exists to build.
A starter question bank
- "What is going well that I might not be seeing?"
- "What is blocking you that you have not raised yet?"
- "Is there anything I did or said recently that landed wrong?"
- "Where do you want to be in six months, and what would help you get there?"
- "Is your workload sustainable right now?"
Rotate these rather than asking all of them every time — a one-on-one that feels like a fixed script loses the openness that makes it useful.
Common mistakes
Letting status updates fill the whole meeting. If project status keeps crowding out everything else, move it to a written async update and reclaim the meeting for what only happens face to face.
Canceling when things get busy. Busy weeks are exactly when blockers and misalignment are most likely to surface — canceling removes the safety valve at the worst time.
Only talking about the present. Without a recurring career or growth question, that conversation quietly never happens, and reviews become a surprise rather than a checkpoint.
One-on-ones work best alongside a broader system: pair them with regular onboarding practices for new hires and a structure for mentoring junior employees so growth conversations have somewhere to lead.
FAQ
Who should set the one-on-one agenda?
The direct report, primarily. A shared doc where they add items before the meeting keeps the conversation theirs, with the manager adding their own items alongside.
What if my direct report has nothing to bring?
That is common, especially early on. Use the question bank to prompt rather than sitting in silence, and over time most reports start bringing their own topics as trust builds.
Should one-on-ones ever be skipped?
Occasionally, for a genuine scheduling conflict, but repeated cancellations signal deprioritization. If a full meeting cannot happen, a shorter check-in is better than none.
How is a one-on-one different from a brainstorm or team meeting?
A one-on-one is private, ongoing, and relationship-focused. A brainstorm is group-focused and idea-generating. They serve different purposes and should not be merged.
Where to go next