Strategy Lab
Menu

How to Run Effective 1 on 1 Meetings That Actually Help

A simple 1-on-1 meeting format with sample questions, a worked example, and common mistakes to avoid, so check-ins become real coaching conversations.

Strategy Lab EditorialPublished October 18, 20268 min read

An effective 1-on-1 is a recurring meeting that belongs to your direct report, not to you. Use a fixed structure: a short personal check-in, their topics first, one coaching conversation, then your feedback and clear next steps. Done weekly for 30 minutes, this format catches problems early and builds skill faster than any status meeting.

Most managers already hold 1-on-1s. The problem is that the meetings drift into project updates, get canceled when things get busy, and leave both people feeling like nothing changed. This article gives you a structure that prevents that, plus the questions that make the structure work.

Why most 1-on-1s fail

A 1-on-1 fails when it becomes a status report. If you leave the meeting knowing which tasks are late but not what is blocking the person, you held a stand-up with fewer attendees.

Three patterns cause most of the damage:

  • The manager owns the agenda. Your report waits to be asked questions and answers them briefly.
  • The meeting is the first thing to move. Every cancellation tells your report that their development ranks below everything else on your calendar.
  • There is no follow-through. Good conversations happen, but nothing is written down, so the next meeting starts from zero.

The fix is not more discipline. It is a format that makes the useful conversation the default one.

The set-up: decisions to make before the first meeting

Settle these four things once and the meetings run themselves.

Cadence and length

Weekly for 30 minutes is the right default. Biweekly for 45 minutes works for senior, autonomous people. Anything less frequent than that and you lose the ability to catch small problems while they are still small.

A shared document

Keep one running document per person, visible to both of you. It holds the agenda, notes, and action items. Your report adds topics during the week, so the meeting starts with their real concerns instead of whatever you remember at 9:55.

A fixed slot

Put it on the calendar as a recurring event and treat it like a client meeting. If you must move it, move it the same day, never cancel it. Managers who cancel 1-on-1s during busy periods are canceling the exact moments when people most need support.

Ground rules

Say out loud, once: this is your meeting, status updates go elsewhere, and nothing said here gets repeated without your permission. The last rule matters. If people suspect that candor will travel, they will stay polite, and the meeting will be useless. Our guide on building psychological safety in your team covers how to earn that trust over time.

Step-by-step: the 30-minute format

This is the structure I use and recommend. Times assume a 30-minute meeting.

Step 1: Personal check-in (3 minutes)

Start with the person, not the work. Keep it genuine and short.

  • "How are you actually doing this week, on a scale of 1 to 10?"
  • "What is taking up space in your head outside of work?"

The number is useful. A person who says 7 every week and then says 4 has told you something, and you now have a baseline.

Step 2: Their topics first (10 minutes)

Open the shared document and go through what they added. Do not interrupt to solve. Your job here is to ask, listen, and find out what they actually need from you: advice, a decision, a sounding board, or just to be heard.

A useful opener: "What do you need from me on this?"

Step 3: One coaching conversation (10 minutes)

Pick one thread and go deeper. This is where 1-on-1s earn their keep. Choose a challenge, a decision they are stuck on, or a skill they are building, and coach instead of tell.

Questions that work:

  • "What have you tried so far, and what happened?"
  • "If this goes well in three months, what does it look like?"
  • "What is the part you are avoiding?"
  • "What would you do if you knew you could not fail?"
  • "What is the smallest next step you could take before we talk again?"

Resist giving the answer for the first five minutes. If they stay stuck after that, offer your view as one option, not a verdict.

Step 4: Your topics and feedback (5 minutes)

Now you get airtime. Share context they would not otherwise have, such as changes in priorities, what leadership is thinking, or how their work is landing. Give one piece of specific feedback, positive or corrective. Our article on giving feedback that actually changes behavior shows how to make that feedback land.

Step 5: Close with commitments (2 minutes)

Read back what was agreed. Each action item needs an owner and a date. Include yours. Nothing damages trust faster than a manager who asks for follow-through and has none.

Question bank by purpose

Rotate questions so the meeting stays fresh. Pick one or two per session instead of running through a list.

PurposeSample questions
Surface problems earlyWhat is the most frustrating part of your week? What is slowing you down that I could remove?
Build trustWhat is one thing I could do differently to be more useful to you? When did you last feel stuck and not tell anyone?
Develop skillsWhich part of your work do you want to be better at in six months? Where did you feel least confident this month?
Career growthWhat do you want your role to look like in a year? What work gives you energy, and what drains it?
Check alignmentWhat do you think our top priority is right now? Where do you see us wasting effort?
Improve how you manageWhat should I start, stop, or continue doing as your manager?

Ask the "what could I do differently" questions at least once a month. They feel uncomfortable for the first two times and then become the most valuable part of the meeting.

A worked example

Dana runs a 22-person marketing agency and manages six direct reports. She held weekly 30-minute 1-on-1s, but they were almost entirely client status updates. Marcus, a senior account manager handling 14 clients, kept answering "fine" to everything.

Dana switched to the format above for six weeks. In week two, Marcus added one line to the shared document: "Workload." In the topics block, Dana asked what he needed from her. Marcus said he was spending roughly 12 hours a week on reporting for three low-revenue clients, which together brought in about 9% of agency revenue (around $4,300 a month out of $48,000).

In the coaching block, Dana asked: "If you had those 12 hours back, where would they go?" Marcus said he wanted to build proposals for two larger prospects. Dana did not hand him a solution. She asked what the smallest step was. He proposed moving the three small clients to a templated monthly report and a shared dashboard.

The outcome over the next eight weeks:

  • Reporting time for those clients dropped from 12 hours to about 4 per week.
  • Marcus sent three proposals, and one converted at $6,500 a month.
  • His self-reported check-in number rose from a steady 5 or 6 to 8.

Dana's total investment was three hours a week across six people, which she was already spending. The change was in what happened during those hours.

The most common mistake: turning it into a status meeting

The most common mistake is letting project updates eat the whole slot. It happens because status is concrete and easy, and the person is usually happy to talk about it.

How to avoid it:

  1. Move status elsewhere. Use a written weekly update, a project board, or a team stand-up. If you want a way to structure team-level reviews, see our guide to running a team retrospective.
  2. Ask for blockers, not progress. "What is in your way?" gets you to the real conversation faster than "Where are we on the Henderson project?"
  3. Protect the coaching block. If the first 15 minutes run long, shorten the update, not the coaching.

A second mistake worth naming: solving instead of asking. When you jump to the answer, you get a short-term fix and a long-term dependency. People who are always handed solutions stop developing their own judgment, and you end up the bottleneck. If you find yourself doing this, revisit how to delegate effectively, since the habit usually comes from the same place.

Adapting the format

For new hires

Hold the meeting weekly and lean on clarity. Spend more of the time in Step 4, explaining context, expectations, and how decisions get made. Ask what is confusing and what they wish they had known on day one.

For senior, autonomous people

Shift the balance toward strategy and career. Spend less time on tasks and more on what they see that you do not. Senior people often hold the best information about customers and process problems, and a 1-on-1 may be the only place it surfaces.

For remote people

Keep video on and protect the personal check-in. Remote reports have fewer hallway chances to raise small concerns, so the meeting carries more weight. Ask explicitly about isolation and workload boundaries.

For underperformers

Do not skip the meeting or turn it into an inspection. Keep the structure, but make expectations written and specific in Step 4. A person who is struggling needs more clarity, not more surveillance.

Measure whether it is working

You do not need a survey. Check these every quarter:

  • Cancellation rate. If you cancel or move more than one meeting in ten, the habit is slipping.
  • Who fills the agenda. If your report adds items before most meetings, ownership is real.
  • Surprises. Count how many resignations, conflicts, or missed deadlines caught you off guard. That number should fall.
  • Action item completion. If most commitments get done by the next meeting, the loop is closing.

If you want to record the decisions and agreements that come out of these conversations, a simple decision log keeps them from getting lost.

Key takeaways

  • A good 1-on-1 belongs to your report. They set the agenda in a shared document, and their topics come first.
  • Use a fixed structure: personal check-in, their topics, one coaching conversation, your feedback, and clear commitments with owners and dates.
  • Keep project status out of the meeting. Ask about blockers, and handle updates in writing or in team meetings.
  • Coach before you advise. Ask what they have tried and what the smallest next step is before offering your own answer.
  • Hold the slot weekly for 30 minutes and move it instead of canceling it. Consistency is what builds the trust that makes the questions work.
  • Ask for feedback on your own management at least monthly, and act visibly on what you hear.

Frequently asked questions

How long should a 1-on-1 meeting be?
Thirty minutes works for most weekly meetings, and 45 to 60 minutes works for biweekly ones. Shorter than 25 minutes rarely leaves room for anything beyond status updates. If you routinely run over, you are probably covering project status that belongs somewhere else.
How often should you hold 1-on-1s?
Weekly is the best default for direct reports, especially new hires or people in a stretch role. Biweekly can work for experienced people who are highly autonomous. Monthly is too sparse to build trust or catch problems early.
Who should set the agenda for a 1-on-1?
Your report should own most of it. A shared document where they add topics before the meeting works well, and you add yours underneath. If they never add anything, that is a signal about trust or clarity, not a sign that nothing is going on.
What should you do if your direct report says everything is fine?
Ask more specific questions, since broad ones invite polite answers. Try asking what took the most energy this week or what they would change about how the team works. Also check whether you have made it safe to bring up problems.
1 on 1 meetingscoachingteam leadershipmanagementfeedback
Keep reading

Related playbooks