How to Run a One on One Meeting With Your Team 2026

A one-on-one meeting is a recurring, private conversation between you and one direct report, focused on that person’s work, growth, blockers and wellbeing rather than on project status. To run a good one on one meeting with your team: set a fixed cadence, let the employee own the agenda, prepare two or three questions, spend most of the time listening, and close with written action items you both revisit next time.

Most managers were never taught this. You were probably promoted out of an individual contributor role and handed a calendar full of one-on-ones with no instructions, which is exactly why so many of them turn into status meetings that both sides quietly resent.

The research on this topic is consistent, and so is the failure pattern. On r/EngineeringManagers, one post described the classic loop perfectly: fifteen minutes of project status, five minutes of uncomfortable silence, and two people who both felt the time was wasted. That is not a conversation problem. It is a structure problem, and structure is fixable.

Here is what works, step by step, including a copy-paste agenda you can use with your team this week.

What You Need

You do not need a template software budget or a new HR system to run an effective one-on-one. You need four things ready before the first meeting of the month, and most managers already own three of them.

A recurring calendar slot that cannot be squeezed out

Put the meeting on both calendars as a repeating event with a real end time, not a rolling 30-minute hold. If you have six direct reports and you schedule weekly 1:1s, that is three hours a week protected before you accept anything else. Managers who cannot find the time usually have no team-wide block, so every 1:1 loses to whatever meeting lands first.

A shared agenda the employee writes into

A one-page document, a shared note, or a board with two columns is enough. The employee adds topics first, the manager adds theirs second. When the agenda lives in one place, neither of you arrives with a mental list and the conversation stops being about whoever talks longest.

Include one standing line at the top: add anything you want to talk about. Managers report the ones with a visible invitation get topics they never would have raised out loud.

Something concrete to write down

Whatever you use for notes, the meeting ends with a written record: decisions, action items, owners, dates. A three-line recap message sent within the hour does more for trust than any conversation technique, because it proves the meeting produced something.

Privacy, and a clear frame

Private means private. Not a public cafe table, not a phone call the employee takes while walking to their car. And open with an explicit line: this is not a performance review, and if something is genuinely a performance issue we will schedule time for that separately. Employees on r/cscareerquestions describe the opposite experience, where a one-on-one got hijacked by an IT ticket follow-up and the real career topic never happened.

Two or three questions in your back pocket

Preparation here is light. Scan your notes from the last meeting, glance at what the person actually shipped, and pick two or three questions you genuinely want their opinion on. That is enough to arrive curious instead of empty.

Step-by-Step: How to Run a One-on-One Meeting With Your Team

How to run a one on one meeting with your team: prepare the conversation

Five minutes of preparation changes the whole meeting. Reread the action items from last time and check what actually happened, because that check is the single strongest trust signal available to a manager, and skipping it is the fastest way to prove the meeting was theatre.

Then pick one or two things you want to raise. Not a list of seven items, not a performance rundown. If you have several, put them in priority order and agree with your report on which one matters most this month.

Finally, add your items to the shared agenda and ask your report to add theirs. Give them a real window, at least a day if you can, so the meeting is not decided before they open the document.

Create a comfortable opening

The first ninety seconds set the tone for everything after them. Start with a human check-in and get something specific out of it. “How are you doing, today?” works far better than “how are you going,” and it is a reframing that r/ProductManagement and r/projectmanagement threads keep circling back to, because the vague version reliably produces the perfunctory answer.

Ask about the last two weeks rather than the general state of things. People remember specifics: a rough week, a deadline that moved, a colleague who was hard to work with. Those specifics are where the useful conversation hides.

Then say one honest sentence about yourself. Managers who admit they had a hard week, or that they are behind on something, make it safer for the other person to be honest too.

Listen actively and understand the full picture

Active listening in a one-on-one is not silence plus nodding. It means reflecting back what you heard in your own words and checking whether you got it right: so the blocker is not the project itself, it is that nobody outside the team knows the deadline moved.

Watch for the difference between a support need and a performance issue. Someone who lacks context, tooling, or authority needs you to remove an obstacle. Someone who has the tools and is not using them needs feedback, and that is a different conversation with a different follow-up.

Ask clarifying questions before you solve. What have you already tried, who else has a stake in this, what does success look like in a week. Ten minutes of genuine curiosity buys you far more accurate information than ten minutes of proposing fixes.

Discuss work, progress, and obstacles

Work still belongs in the conversation, but in the right shape. Instead of a full status rundown, ask about the one thing that is hardest right now and the one thing you would drop if you had to. Those two questions surface overload, which is often the real conversation a busy employee cannot start on their own.

Watch for the pull toward project mechanics. On r/womenintech, the advice that comes up repeatedly is that a 1:1 should be about the person’s career and goals, not a hidden standup, and that project deadlines belong in a project meeting. If a work topic is going to take more than ten minutes of back-and-forth, park it and schedule the deep dive separately.

Give clear, specific feedback

Useful feedback has three parts: the observable behaviour, its impact, and a conversation about what changes. “Your updates have been thinner lately and I had to chase two decisions last week” is workable. “You need to communicate more” is not, because the person cannot act on it.

Describe what happened rather than what you think of the person. Then invite their view, because you are frequently missing context: the request was ambiguous, another team changed scope, they were covering an absence nobody told you about.

Agree on one concrete change and describe what it looks like next time. Not “be more proactive” but “send me a two-line summary in the shared doc before Thursday standup, even if there is nothing new.”

Set one or two development goals

Development is the part that gets squeezed out when the meeting runs long, so protect it deliberately. Pick one or two goals tied to where the person wants to go, not where the team happens to have a gap this quarter.

Make them observable and time-bound. Shadowing a customer call twice before the end of the quarter is a goal. Learning more about forecasting is a wish. Then name the support you will provide, because a goal without resources is just pressure.

Set the review date at the moment you set the goal, not at the end of the quarter when everything competes for attention.

Handle disagreement or difficult subjects

Disagreement is a good sign. It means the other person is still thinking rather than complying, and a relationship where nobody pushes back is a relationship with no candor in it.

Slow the pace down. Ask for the reasoning rather than reacting to the conclusion, and separate what you know from what you are assuming. When an assumption turns out to be wrong, say so plainly. Acknowledging the impact of your own misstep buys more honesty than being right ever will.

If a topic genuinely needs a formal process, such as a sustained performance concern or a compensation conversation, name it and give it its own meeting with the right preparation on both sides. Do not let it ambush either of you inside a standing slot.

Close with ownership and follow-up

Save the last five minutes. Summarise the decisions out loud in plain language, name an owner and a date for each action item, and ask your report to confirm they sound right. That last bit catches misunderstandings while they are still cheap.

Confirm the next meeting is on the calendar before you finish, not after. A one-on-one without a booked next session is an event, and events stop happening.

Send the recap the same day while it is still accurate. Two or three bullets is plenty.

How Often and How Long Should a One-on-One Meeting Be?

Pick a cadence you can hold for six months, not a heroic one you will abandon in March. Consistency beats intensity, and the most common failure is not a bad agenda but a manager who cancels repeatedly until people stop taking the slot seriously.

Situation	Cadence	Length	Why
New hire, first 90 days	Weekly	30 minutes	Frequent early feedback prevents small problems from setting in
Individual contributors on a stable team	Weekly	30 minutes	Keeps blockers visible while they are still cheap to fix
Team leads and senior ICs	Biweekly	45 to 60 minutes	More room for coaching, workload and career conversations
Fully remote or distributed team	Weekly	30 to 45 minutes	Regular contact offsets the physical distance
Managers with 20+ direct reports	Biweekly rotating	20 to 30 minutes	Every person gets a predictable slot, not an occasional one
Active performance concern	Weekly until resolved	30 minutes	Short, frequent, documented check-ins on specific behaviours

A note on length: thirty minutes is genuinely enough for most people most of the time. If your meetings routinely run to an hour and a half every week with every report, the problem is usually that status updates are living in the wrong meeting.

One-on-One Meeting Agenda Template

Copy this into a shared note, keep the same headings every time, and let both of you rearrange the order. Consistency is what makes it a template rather than another form to fill in.

1. Check-in (2 to 3 minutes). How are you doing today, specifically? Anything outside of work that will affect your week?
2. Their topics (10 to 15 minutes). Everything the employee added to the agenda, unhurried and in their order.
3. Progress, priorities and obstacles (10 minutes). What moved, what is stuck, what is hardest, and what would you drop.
4. Feedback (5 to 10 minutes). One specific observation, its impact, and the change you are both agreeing to.
5. Growth (5 to 10 minutes). One or two development goals, plus what support they need from you.
6. Actions and close (3 minutes). Read back every action item with an owner and a date, confirm the next meeting.

If you only keep five things, keep these: a personal check-in, their topics, blockers, one piece of feedback, and one development goal. That is the spine of a one-on-one meeting agenda that does its job.

Questions to Ask in a One-on-One Meeting

Questions do the work that status updates used to do. Pick two or three per meeting rather than firing the whole list, and follow the thread that comes back instead of moving on down the page.

Check-in and presence

• How are you doing today, and how has the last two weeks actually felt?
• What has taken more energy than expected this week?
• Is there anything outside work that is getting in the way right now?

Work, priorities and blockers

• What is the hardest part of your job this month?
• Where are you stuck, and what have you already tried?
• If you could delete one recurring task from your week, which one?
• What decision are you waiting on, and from whom?

Feedback and growth

• What is one thing I do as your manager that helps you most?
• What is one thing I should start, stop or change?
• What skill would make the biggest difference to your work this year?
• What would you like to be doing more of in six months?

Career and motivation

• Does the path you are on still look right to you, now that you have seen more of it?
• What do you want to be doing in two years, and what stands in the way?
• Whose career here do you find interesting, and why?
• What have you seen in this organisation that worries you?

Wellbeing and team dynamics

• How is your workload right now, honestly?
• Is there anyone on the team making your work harder than it needs to be?
• What does a good week look like for you?
• What am I doing that quietly makes your job harder?

Get their opinion before you give yours. In the r/managers and r/ProductManagement threads this comes up again and again: people open up when they feel consulted rather than informed.

The 40/20/40 and 10-10-10 Rules

What is the 40/20/40 rule for meetings?

The 40/20/40 rule is a simple split for how you spend one-on-one time: 40% listening to your report, 20% sharing your own perspective or context, and 40% talking through the topics they brought. The point is not precision, it is noticing your own ratio. Most new managers land somewhere near 70% talking, then wonder why their people bring thinner topics each week.

What is the 10-10-10 rule for meetings?

The 10-10-10 rule is a career-conversation tool borrowed from onboarding practice: ask what the person wants to be doing in 10 minutes, in 10 months, and in 10 years. It is a fast way to surface a mismatch between their current work and their direction without making it a heavy career conversation, and it usually produces the most thoughtful answers in the whole meeting.

A related rule you will meet in the same searches is the 30-60-90 split for new hires, which maps the first week, the first two months and the first quarter to different expectations. It is useful for your first one-on-one with a new report, though it does not replace a normal conversation.

One-on-One vs Standup vs Team Meeting vs Performance Review

Most 1:1s fail because they are being used to do another meeting’s job. This table settles what each one is for.

Meeting	Who attends	Core purpose	Frequency	Never used for
1-on-1 meeting	Manager and one report	Their work, growth, blockers, wellbeing	Weekly or biweekly	Announcements the whole team needs
Daily standup	Whole team	Coordination and immediate blockers	Daily, 15 minutes	Career development or feedback
Team meeting	Whole team	Decisions, planning, priorities	Weekly or monthly	Anything personal to one person
Performance review	Manager and one report, plus HR process	Rated performance over a defined period	Twice a year, or on schedule	Routine support or venting
Skip-level	Manager’s manager and the report	Unfiltered view of the team	Quarterly	The manager’s own performance feedback

One practical rule keeps the lines clear: anything the whole team needs goes in a channel or a team meeting, and anything about a person’s performance or career stays in the one-on-one.

Running One-on-Ones With Remote and Large Teams

Remote teams lose their one-on-ones quietly. Nobody cancels them on purpose, they just drift as the calendar fills with shared calls nobody can escape. Put a team-wide block in the calendar, keep the camera on, and stay present for the full thirty minutes.

Virtual meetings also bring specific etiquette problems worth naming. No driving while on the call, no scrolling through your phone with the camera on, and if you are walking, say so at the start so the conversation stays honest. Nobody can think properly while pretending.

For managers with 20 or more direct reports, weekly 1:1s across the whole team is roughly seventeen hours a week, which is not a scheduling problem, it is a design problem. Group direct reports into cohorts of four to six, rotate the cohorts through your recurring slot, and protect a longer one-on-one session for each person every month or two. Everyone gets a predictable slot and you get a rhythm that survives a bad week.

Common Mistakes

Almost every bad one-on-one traces back to one of these, and nearly all of them are fixable this month.

You cancel or move it constantly. Two cancellations in a row and people stop preparing. If the meeting is unimportant, stop scheduling it. If it is important, treat the slot like a customer appointment and decline anything that conflicts.

You do most of the talking. Ask yourself what share of the last ten minutes was you. If you cannot tell, ask your report what percentage of the last three meetings you spoke in. The answer is usually humbling and immediately actionable.

It becomes a status meeting. Move project updates into your project channel or standup and say so out loud. It feels like removing something, but it is what makes the slot worth keeping.

Your feedback is vague. “Needs to be more proactive” gives nobody a next action. Replace adjectives with observable behaviour, the impact it had, and the specific change you want to see.

You skip the follow-up. Starting last meeting’s action items is the cheapest trust signal available. If an action item has been dragging for three meetings, say that and deal with it instead of skipping past it again.

You discuss something sensitive in public. Never in an open office, never on a speakerphone in a corridor. Move to a private room or a call, and if it is genuinely a performance matter, give it its own scheduled meeting.

You let the employee run the time and never bring anything. Owning the agenda does not mean the manager arrives empty. Bring two questions and one topic of your own, every time.

You treat the slot as optional when things are busy. The weeks you most need the conversation are the weeks you are most tempted to skip it. The inverse relationship is real and everybody notices it.

Signs of a bad one-on-one meeting

• You spend most of the time on project status that belongs in a team meeting.
• Your report asks what the point of the meeting is.
• There are long silences that nobody fills.
• Nothing from three meetings ago was ever revisited.
• The employee arrives visibly relieved when it ends.
• The only time you speak about their work is when something has gone wrong.
• They bring you nothing, every week, and you never ask why.

There is a fair argument against the whole practice, usually raised on r/scrum: routine one-on-ones can become a crutch that suppresses open communication in the team, with people only saying what they think their manager wants to hear. That criticism is fair when the meeting is used for performance management in disguise. Fix that by keeping hard conversations out of the standing slot and naming them plainly when they need their own setting.

Frequently Asked Questions

Start with one person this week. Book a recurring 30-minute slot, send a shared agenda with the line “add anything you want to talk about”, and open with “how are you doing, today?” Then do the part almost nobody does: at the next meeting, start by reading back what you committed to. That single habit is where the trust comes from.