A one-on-one that only covers project status is a meeting that should have been an email. The actual value of a recurring one-on-one is the conversation that cannot happen any other way: coaching on a specific decision, a concern that has not surfaced anywhere else, feedback in both directions, and a check on how someone is actually doing beyond their task list. Running a one-on-one meeting in 2026 that consistently produces that value takes a deliberate structure, not just good intentions and a calendar hold.
Why most one-on-ones drift into status updates
Status updates are the easiest thing to talk about, so without structure, that is where the conversation defaults. It feels productive in the moment because information changes hands, but it is the lowest-value use of the only recurring time a manager and employee have that is not about a specific deliverable. Once a one-on-one becomes a status meeting, it starts to feel skippable the moment either person is busy, and skipped one-on-ones compound into a relationship that only exists at the project level.
A structure that produces real value
- Keep a shared, living agenda doc. Both people add items throughout the week, not five minutes before the meeting. This removes the awkward silence of "so, what is up" and ensures neither side is improvising.
- Split the time on purpose. Reserve the first half for whatever the employee wants to raise, and the second half for anything the manager needs to cover. Doing it in that order matters: employee topics first, manager topics second.
- Ask beyond status. "What is the hardest part of your week right now" and "is there anything you are not telling me" surface things a status update never will.
- Coach on one real decision, not everything. Pick the single most useful thing to dig into rather than skimming across five topics shallowly.
- Close with a stated commitment. Both people should leave knowing exactly what happens before the next meeting, said out loud, not assumed.
- Protect the slot. Move status updates to async channels so canceling a one-on-one for "nothing to report" stops being a reasonable excuse.
| Signal |
Drifting one-on-one |
Working one-on-one |
| Agenda |
Improvised at the start |
Shared doc, built over the week |
| Content |
Mostly project status |
Coaching, feedback, and one real decision |
| Talk time |
Manager talks most |
Split, employee's topics first |
| Ending |
Trails off |
A specific, stated next step |
Common mistakes
- Letting the manager set the entire agenda. A one-on-one that only covers what the manager wants to know stops being about the employee at all.
- Canceling for "nothing to report." The status-free weeks are often exactly when a coaching or career conversation is most needed.
- Multitasking during the meeting. Checking messages during a one-on-one signals it is the least important meeting on the calendar, and people notice.
- Never asking about anything beyond the current project. Career direction, energy level, and team dynamics deserve regular airtime too, not just once a year.
FAQ
How long should a one-on-one be?
Thirty minutes is a solid default. Fifteen tends to compress into status only; sixty needs a genuinely full agenda to justify.
What if my manager only wants to talk about tasks?
Bring your own agenda items to the shared doc anyway. Most managers follow the structure that is put in front of them.
Should one-on-ones happen weekly or biweekly?
Weekly works best for newer employees or fast-changing projects. Biweekly is fine once a working rhythm and trust are established.
What if there is genuinely nothing to discuss?
That is rare once you ask beyond status. Career goals, feedback in both directions, and how someone is actually doing almost always produce something worth ten minutes.
Where to go next
Pair a better one-on-one with running a standup that does not waste time so status stays out of both meetings, use how to ask for feedback proactively to make the most of the time, and bring mentoring habits from how to be a good mentor into the conversation.