The 1:1 Meeting Guide: Structure, Questions, and Follow-Up
The 1:1 is the only meeting on a manager's calendar whose entire purpose is the relationship with one person. Done well, 1:1s surface problems months before they become resignations, build the trust that makes hard feedback possible, and give quiet team members a channel they will never use in a group setting. Done badly, they become status updates that duplicate the standup.
The structure that works
- The report owns the agenda: the 1:1 is their meeting. The manager's topics come second.
- 30 minutes weekly beats 60 minutes monthly: frequency builds trust more than duration. A monthly hour becomes a performance review; a weekly half-hour becomes a conversation.
- Status updates are banned: anything visible in the task tracker does not belong in the 1:1. The time is for what is not visible — concerns, ambitions, friction, ideas.
- End with actions: a 1:1 that surfaces a problem should end with who does what about it.
Questions that actually open people up
- What's been more frustrating than it should be lately?
- If you ran the team for a month, what would you change first?
- What are you not getting from me that you need?
- What part of your work do you want more of? Less of?
- Is there anything you've been hesitating to bring up?
The follow-up problem
The most common 1:1 failure is dropped follow-up: the report raises something important, the manager nods, and three weeks later nothing has happened. That pattern teaches people to stop raising things. Keeping a running record of commitments — and reviewing them at the start of each 1:1 — is what separates managers people trust from managers people manage upward around.
A note on recording 1:1s
1:1s are the meeting type where AI transcription requires the most judgment. For coaching and career conversations, a transcript can help both sides remember commitments. For sensitive conversations, the presence of a recording changes what people say. MeetOye leaves this to the host: Oya can be disabled per meeting, and workspace admins can set defaults. The right pattern for most teams is notes on by default for regular 1:1s, off for sensitive ones — announced clearly either way.