How to Run a One-on-One Meeting

There is no single correct frequency. What matters is that the cadence is predictable and that it holds.

Culture Amp suggests not going longer than two weeks without checking in, even if that means a short catch-up paired with a deeper monthly session. Time is Ltd. recommends biweekly meetings of thirty minutes to an hour as a default, and warns that daily one-on-ones can signal micromanagement. If a manager cannot fit reasonable one-on-ones for everyone into the week, Time is Ltd. points out that the span of control may simply be too large.

Ask the person what they want. Elevate suggests a direct question such as "How do you feel about doing an hour every other week instead of 30 minutes weekly?" Giving people a say in the rhythm increases their ownership of the time.

Two practical points on scheduling:

1. Spread the meetings across the week. Elevate warns against stacking every one-on-one on one day, because the fifth person of the day gets a tired, flat manager.
2. Pick a private place. Lattice recommends a quiet room or a video call with headphones, since the conversation often covers sensitive topics. For remote teams, video helps you read tone and expression. A walking call can also work, because side-by-side conversation often feels less confrontational than sitting across a desk.

The most common failure mode, according to Elevate, is arriving and asking "So, what do you want to talk about?" followed by silence. The fix is an agenda that both people write before the meeting, with the direct report driving it. Time is Ltd. goes further and argues that the employee, not the manager, should usually be the organizer of the meeting.

A shared document that persists from meeting to meeting works better than a fresh agenda each time. It holds the history, the open actions and the topics that were deferred. A simple template:

ONE-ON-ONE: <name> and <manager>, <date>

WINS SINCE LAST TIME
-

THEIR TOPICS (added before the meeting)
-

MY TOPICS
-

OPEN ACTIONS FROM LAST TIME
- [ ] <action>, <owner>, <due>

NEW ACTIONS
- [ ] <action>, <owner>, <due>

Rotate the deeper topics over the month rather than forcing every theme into every meeting. Lattice lists productivity and projects, feedback and coaching, career growth, and wellbeing as the core themes, and suggests covering each regularly. Culture Amp adds alignment with the company's direction and relationships with the rest of the team.

LifeLabs Learning offers a compact checklist it calls CAMPS: certainty, autonomy, meaning, progress and social inclusion. It suggests asking people to rate each area from 1 to 10 from time to time. A low certainty score points to unclear expectations. A low social inclusion score points to isolation. The scores give you a starting point when the person says "everything is fine".

A predictable structure removes the awkwardness of deciding what to do next. Here is a 30-minute plan that adapts to longer meetings.

Start with the person, not the work. Culture Amp recommends a personal check-in at the start of every meeting, because knowing someone's state gives context for everything after it. LifeLabs suggests asking for small wins early, since recognizing progress is a strong motivator.

Put their topics before yours. If your topics come first, they tend to fill the time. If you have something urgent, say so at the start and agree on how much time it gets.

Talk less than you think you should. Elevate summarizes research by organizational scientist Steven Rogelberg (read on 2026-10-17) that the strongest predictor of a one-on-one's value is the direct report's active participation, with the ideal being that the direct report speaks between 50% and 90% of the time. If you notice you have been talking for five minutes straight, stop and ask a question.

When someone brings a problem, the manager's reflex is to solve it. Sometimes that is right, especially when the person is new or the stakes are high. Most of the time, solving it for them teaches them to bring every problem to you.

Elevate recommends the GROW model as a structure for coaching conversations:

• Goal: "What do you want to achieve here?"
• Reality: "What is actually happening right now?"
• Options: "What could you do? What else?"
• Will: "What will you do, and by when?"

LifeLabs teaches a similar sequence it calls SOON: success, obstacles, options and next steps. The names differ but the shape is the same. You help the person describe the goal, look honestly at the current state, widen the options, and commit to a step.

Good questions are specific. Lattice suggests following up on something the person told you last time, such as "You mentioned you shared the first draft with the leadership team. What responses have you had?" A specific follow-up shows you listened and gets a better answer than "How is the project going?"

A short bank of questions that work in most meetings:

• What is the biggest thing in your way right now?
• What would you change about how the team works if you could?
• When do you feel you are at your best, and what conditions create that?
• What skill do you want to get better at in the next few months?
• What should I start, stop or continue doing as your manager?
• Is there anything we did not get to today that you want to cover next time?

A one-on-one without written actions is a pleasant conversation that changes nothing. Lattice recommends ending every meeting with specific next steps, owners and deadlines, and keeping notes so the next meeting has continuity. LifeLabs suggests a closing recap: summarize the action items, preview topics for next time and thank each other for the time.

Write the actions in the shared document while you are both still in the room. Read them back. Each one needs:

1. A verb and an object. "Send the hiring brief to recruiting", not "hiring stuff".
2. One owner. If it belongs to two people, it belongs to nobody.
3. A date. "By Thursday" is better than "soon".

Then start the next meeting by checking them. Lattice warns that forgetting to follow up on your own commitments undermines trust and makes people less likely to come to you for help. The manager's actions matter more than the direct report's here, because they show whether the meeting has any power.

Feedback belongs in the one-on-one too, in both directions. Elevate recommends reserving time for specific praise that names the behavior you want more of, such as "I appreciated how you worked with the sales team to unblock that deal", rather than a generic "good job". Ask for feedback on your own management as well, and on the meeting format itself.

Cancellation deserves extra attention. Elevate cites a study finding that nearly 30% of one-on-ones are cancelled and more than 40% are rescheduled each week (as reported by Elevate Leadership, read on 2026-10-17). Lattice notes that a cancelled meeting sends a clear message: "I don't have time for you." If you must move it, explain why and offer a new time in the same message. The one acceptable skip is when you have both looked at the agenda in advance and agreed there is nothing to discuss.

Once you manage managers, your direct one-on-ones tell you less about what is happening further down. Jade Rubick describes skip-level one-on-ones as a way to sense the organization: meetings with your reports' reports, rotating through everyone over time.

Skip-levels have a different purpose from regular one-on-ones. They are for learning how well your managers are managing, how people feel about recent changes, and what is getting in the way. Rubick's practical advice:

• Set expectations in the invite. Say it is a skip-level, list the kinds of things people might raise, and tell your managers you are doing them.
• Ask specific questions. "What problems are you seeing with this reorganization?" gets better answers than "Any feedback on the reorganization?"
• Use them to test communication. Ask about things you believe you have already explained. You will often find they did not land.
• Watch for patterns, carefully. The same concern from several people is a signal, but a vocal person can spread a worry that is not representative.
• Do not take over. The person reports to someone else. Usually the right move is to redirect them to their manager and offer help if that fails.

Rubick keeps the load to one or two skip-levels a week, which means a full rotation through a larger group can take months. That is fine. The point is a steady sample, not a census.

If you lead a team that also works with AI agents, the same rhythm applies to reviewing their output: a regular slot, a running log and written follow-ups. Quanta Intelligence publishes leadership playbooks that turn routines like this into repeatable checklists, but a shared document and a calendar invite are enough to start.