How to run effective one-on-one meetings

July 31

TL;DR: Effective one-on-one meetings require a shift from status updates to growth coaching, and that shift is only possible when you are fully present. Standardize your cadence to a 30-minute weekly session, let your direct report own the agenda, and maintain a listening-first ratio throughout the conversation. Staying present in the conversation, rather than typing through it, is what makes the difference. An AI notepad like Granola captures device audio directly, so you can focus on your team while still being able to ask what action items came up, with citations back to the conversation.

One-on-ones often struggle with presence and follow-through. Divided attention during note-taking and visible recording bots can shift conversations away from candor. This guide covers the cadence, structure, and habits that address both challenges and shows how to carry context from one check-in to the next.

Key habits for productive one-on-one sessions

The most important reframe: This meeting belongs to your direct report, not to you. Your job is to create conditions for honest conversation, ask questions that surface what is happening, and remove obstacles. That posture is fundamentally different from running a status review, and it is not a calendar obligation but one of the highest-leverage activities you do as a manager.

How to shift focus to growth goals

Most one-on-ones drift toward immediate project deadlines because both parties have clear topics, the conversation fills itself, and nobody has to sit with ambiguity. Tactical updates belong in Slack or a written report. Bringing them into a one-on-one wastes the only scheduled time you have for coaching, career development, and honest feedback.

Redirect the conversation toward longer-term growth regularly. Questions like "What does success look like for you in the next six months?" or "What skills do you have that are not being used in your current role?" shift the register from task completion to growth trajectory. Your direct report cannot answer these off the top of their head, which is why the agenda needs to arrive 24 hours before the meeting.

Establishing clear one-on-one expectations

Unstructured meetings create anxiety for direct reports who cannot predict what will be asked or how candid they should be. Agree on three things upfront: Who owns the agenda (your direct report), how you both want to exchange difficult feedback (directly and in the room, not via email afterward), and what topics are always on the table (career development, personal wellbeing, team dynamics). Clarity on those three points changes the tone of every session that follows.

How to run meaningful one-on-one meetings

Managers often talk too much in one-on-ones. Effective coaching conversations require spending most of the time listening rather than delivering information. Most of your preparation should go into the questions you plan to ask rather than the information you plan to deliver.

Active listening is not passive silence. It means digging deeper with follow-up questions, noticing when someone hesitates or qualifies a statement, and probing that moment rather than moving on.

How to determine your ideal one-on-one interval

Frequency signals priority. A direct report who sees their check-in canceled or pushed repeatedly draws the correct conclusion: Their growth is not a priority for you.

Choosing between weekly and biweekly one-on-ones

Baylor HR guidelines recommend scheduling weekly meetings for 30-60 minutes with each direct report. Weekly touchpoints prevent small issues from compounding into serious problems, and they create enough regularity that direct reports stop hoarding concerns between sessions.

A biweekly cadence may be appropriate for senior staff who operate with significant autonomy and need strategic alignment rather than tactical guidance. For everyone else, weekly is the right default.

Structuring one-on-ones for junior vs senior team members

Junior team members need more frequent direction, clear guardrails, and tactical support. Their check-ins should spend more time on immediate roadblocks, priorities for the week, and specific skill development. Senior team members need strategic alignment, peer-level coaching, and space to think through organizational challenges. The agenda structure stays the same while the depth of each section shifts based on what the person needs.

Deciding when to skip a one-on-one meeting

If you must move a check-in, pick a new time immediately, in the same message where you cancel. That rescheduling action itself signals that the meeting matters. Continually moving a direct report's check-in sends the message that their time is not a priority, which erodes trust faster than most managers realize.

How to structure your one-on-one agenda

A shared agenda prevents the meeting from devolving into a catch-up that covers nothing substantively. It also gives your direct report 24 hours to think through what they want to discuss rather than arriving unprepared and defaulting to status updates.

Defining roles for meeting preparation

The direct report owns the agenda. Your job as the manager is to review it, prepare two or three coaching questions based on what they have shared, and add any topics you need to cover (organizational updates, feedback, specific decisions that require their input). When your direct report owns the agenda, the meeting becomes a space for them, not a check-in you run on them.

Essential topics for your 1:1 agenda

A well-structured agenda covers three layers: Immediate context (how they are feeling, current workload), tactical priorities (blockers, decisions, upcoming milestones), and growth (career development, skill gaps, longer-term goals). Below is a copy-pasteable template you can adapt immediately:

One-on-one meeting agenda template

Pre-meeting (direct report adds 24 hours before)

  • How am I feeling this week (energy, workload, overall)?
  • What is the most important thing I need help with right now?
  • What is one thing that went well since our last meeting?
  • What is one thing that did not go as planned, and why?
  • Any career or growth topics I want to raise?

Manager prep (review agenda, add one coaching question)

  • Open threads from last week's action items: [List]
  • One coaching question based on their agenda: [Prepare this]

During the meeting

Their topics (15 minutes)

  • Blockers and roadblocks: What is stopping you from doing your best work?
  • Current priorities: Are the right things getting your attention this week?
  • Team dynamics: Is there anything affecting collaboration that I should know about?

Your topics (5 minutes)

  • Organizational context or decisions relevant to their work
  • Feedback (specific, behavioral, tied to observable events)

Growth and action items (10 minutes)

  • Career development: What would you like to get better at in the next quarter?
  • Resources or support needed: What would make it easier to do your best work?
  • Action items with owners and deadlines (both of you)

Post-meeting (manager sends within a few hours)

  • Summary of key decisions
  • Action items with named owners and deadlines
  • One-line note on the growth topic discussed

Optimizing time for each agenda item

In a 30-minute session, allocate roughly 15 minutes for their topics, 5 minutes for yours, and 10 minutes for growth discussion and action item assignment. If the conversation regularly runs over on their topics, that is a signal to lengthen the session, not to compress the growth conversation at the end.

Proven habits for productive one-on-one sessions

Good structure is a starting point. The habits you bring into the room determine whether the structure produces real outcomes.

When to probe and when to advise

Resist the instinct to offer solutions early, especially if you were promoted because you were a strong individual contributor. Start by asking clarifying questions: "What have you tried so far?" or "What does a good outcome look like to you?" Probe for several rounds before shifting to advice. This approach helps the direct report develop their own problem-solving, which is more durable than receiving your answer directly.

Capture insights during one-on-one meetings

This is where most one-on-ones quietly fail. The manager either types detailed notes and loses eye contact, or stays fully present and loses the detail. That tradeoff is real.

Bot-free capture solves this. We capture audio directly from your device, transcribe in real time, and then delete the audio. No recording is stored anywhere, and no visible participant joins the call. You jot rough notes during the conversation and we fill in the supporting context afterward. Your notes stay in black. Our AI additions appear in gray. You stay in control of what remains.

It is best practice to make sure participants know when you use AI notetaking tools. Granola offers built-in ways to notify attendees: A visible watermark while transcribing, or an automatic message in the meeting chat. Check with your team admin or legal team on what applies to your organisation.

Assign owners to meeting action items

If you don't assign an owner to a decision, you'll have the same conversation again next week. Before the meeting ends, confirm every action item has a named person responsible for it and a realistic deadline. Reading the list back out loud takes two minutes and prevents the documentation gap that causes most follow-through failures.

Turning meeting insights into tangible actions

The meeting is the easy part. Follow-through is where managers consistently under-invest.

Tracking action items across one-on-ones

For someone running weekly one-on-ones with five or six direct reports, the time spent finding what was agreed last week, checking whether it was done, and preparing for the next session is a real cost that compounds across the week.

Our Chat feature queries across all your past meetings, so you can ask "What action items did I assign to each direct report over the last month?" and get source-linked citations from specific conversations rather than reviewing notes manually. The more one-on-ones you capture, the richer the context available for each next session.

Linking insights across one-on-one meetings

Patterns across one-on-ones carry as much signal as individual sessions. If three different engineers mention in separate check-ins that a particular process is creating confusion, that is a systemic issue. If the same direct report raises their interest in a specific skill area across several sessions, that is a career signal worth acting on.

Our folder-level queries let you search across all your team's one-on-ones simultaneously. A question like "What recurring roadblocks have come up across the team in the last quarter?" returns citations from specific conversations rather than requiring you to review each set of notes individually.

The key to effective one-on-one prep

Our pre-meeting briefs surface open threads, relevant context from your calendar, and recent email (if you opt in) directly in the notepad before the session starts. You open the note as you join the call and see a short brief that gives you the context you need without a manual review.

Fixing the anti-patterns in your one-on-one routine

Even managers with good intentions fall into patterns that undermine one-on-ones over time. These are the most common ones.

Breaking the status update cycle

Status updates belong in written reports or asynchronous tools. When one-on-ones fill with project updates, two things happen: You miss the emotional and career signals underneath the surface information, and your direct report learns that candor is not the point of this meeting. Break the cycle by explicitly redirecting at the start of the session: "I've read your written update. Let's use this time for what's harder to write down."

During high-pressure sprints or burnout phases, consider adapting the format rather than canceling. You might shorten the session to focus on capacity and immediate blockers rather than running a full coaching session when neither party has the bandwidth.

Specific protocols for high-stress periods:

  • Week 1 of a major launch: Replace the growth discussion with a capacity check. Ask "On a scale of 1 to 10, how sustainable is your current workload?" and "What is one thing I can take off your plate this week?"
  • Post-launch recovery: Use the first check-in after a high-intensity sprint to debrief what worked and what burned people out. Capture these observations so you can adjust processes before the next sprint.
  • When someone flags exhaustion: Do not defer the conversation. Clear time immediately to understand whether they need time off, workload redistribution, or a longer conversation about role fit. Burnout compounds quickly, and early signals are easier to address than late ones.
  • Multi-week crunch periods: Consider adjusting to more frequent async check-ins combined with shorter video calls to maintain connection while respecting bandwidth constraints. The key is signaling that the one-on-one adapts to reality rather than disappearing when things get hard. Canceling check-ins during stress tells your team that support evaporates exactly when they need it most.

Eliminating empty one-on-one agendas

"I don't really have anything" is often a sign that the direct report does not feel safe raising what is on their mind, or that they have not had enough time to think. Both are solvable. A set of fallback coaching questions gives you a reliable way to open the conversation when the agenda is thin:

  • What is one thing I could do differently to support you better?
  • Is there anything you have been wanting to bring up that we have not talked about yet?
  • What is the biggest thing standing between you and doing your best work right now?
  • What would you like to get better at over the next quarter?

Any one of those questions can generate 20 minutes of genuine conversation if you follow up on the first answer rather than moving on.

Addressing tough feedback in one-on-ones

Sensitive conversations require discretion at the architecture level. Performance issues, organizational changes, or restructuring discussions involve information that should not be stored on a third-party server or recorded in a way that could resurface unexpectedly. We built Granola's privacy-first approach specifically for these situations: Audio is deleted immediately after transcription, and no recording is retained anywhere. The absence of a visible participant also keeps the conversation feeling like a direct, private exchange rather than a recorded session.

When handling confidential conversations:

  • Performance improvement discussions: Granola captures your notes and lets you keep them out of shared folders, separate from regular check-in notes.
  • Organizational restructuring or role change conversations: Granola captures your notes privately, with no audio retained after transcription and no visible bot joining the call.
  • Executive recruiting or unannounced promotions: When discussing a role change that has not been announced, some conversations should remain entirely off the record until timing aligns. Note only what you need for your own follow-through.
  • Mental health or personal disclosures: If a direct report shares sensitive personal information, ask explicitly whether they want the conversation documented or kept entirely private and respect their answer. For guidance on how formal your post-meeting records need to be across different meeting types, our comparison of meeting minutes vs meeting notes is a useful reference.

Closing the loop on meeting outcomes

Send a brief summary within 30 minutes: Three to five bullet points covering key discussion points, action items with owners and deadlines, and decisions made. Our meeting recap email templates show how to format action items so ownership is clear rather than implied.

Try Granola for free. Download the Mac or Windows app, connect your calendar, and run your next one-on-one to see it in action.

FAQs

Who should own the one-on-one meeting agenda?

The direct report should own the agenda, adding their topics at least 24 hours before the meeting. The manager reviews the agenda and prepares one or two coaching questions based on what the direct report has shared.

How long should a one-on-one meeting be?

Baylor HR guidelines recommend scheduling weekly meetings for 30-60 minutes with each direct report.

What should you do when you need to cancel a one-on-one?

Reschedule immediately in the same message where you cancel. This signals that the meeting matters and prevents the direct report from reading the cancellation as deprioritization of their growth.

How do you handle a one-on-one when the direct report says they have nothing to discuss?

Ask one of these fallback questions: "What is one thing I could do differently to support you better?" or "Is there anything you have been wanting to bring up that we have not discussed?" Both reliably open genuine conversation, and following up on the first answer typically generates another 15 to 20 minutes of substantive discussion.

How does bot-free capture differ from a recording bot?

A bot joins as a visible participant, which means its behavior depends on the meeting platform. Granola captures device audio directly, so it works the same way regardless of where the meeting happens. If you want participants to know Granola is active, the transparency features handle that: an automatic in-chat message or a video watermark lets everyone in the call know transcription is running, without adding a participant to the call.

How do you track action items consistently across multiple direct reports?

Capture notes from every one-on-one in a shared team folder and use folder-level queries to surface open threads across the whole team. Our Chat feature lets you ask what remains unresolved across a set of meetings and returns source-linked citations rather than requiring manual review of each session's notes.

What is the right listening-to-talking ratio in a one-on-one?

Effective coaching conversations typically involve spending most of the time listening rather than talking. If you find yourself speaking for the majority of a check-in, the meeting has shifted from coaching to instruction and your direct report's growth signals are getting lost.

Glossary

One-on-one meeting (1:1): A recurring, scheduled conversation between a manager and a single direct report. Unlike team meetings, the format is designed for coaching, feedback, and career development rather than group status updates.

Agenda ownership: The principle that the direct report, not the manager, is responsible for preparing and submitting the meeting agenda, typically at least 24 hours in advance. This shifts the one-on-one from a manager-led check-in to a space the direct report controls.

Folder-level query: A search run across all meetings organized within a specific Granola folder, returning source-linked citations from individual sessions. Useful for surfacing patterns across multiple one-on-ones without manual review.

Pre-meeting brief: A short, automatically generated summary that appears in Granola before a session begins, surfacing open threads, relevant context from your calendar, and recent email if you opt in.

Bot-free capture: Granola's approach to meeting transcription where audio is captured directly from the device rather than through a bot that joins the call, and audio is deleted after transcription.

Share