How to Run Your First 1-on-1 as a New Manager: A Practical Template

13 min read

Your first 1-on-1 as a new manager is usually scheduled in a rush, ten minutes before it happens, with someone you have never formally sat across from in that configuration before. You have half an hour on the calendar. You have no template. You have a vague memory of what your last manager did, which was mostly not useful. You have a conference room, or a Zoom window, and the specific form of stage fright that only comes from knowing the other person is watching you figure this out in real time. It is a close cousin of the imposter syndrome most new managers carry through their first year.

This letter is the template we wish we had been handed. It is not the only way to run a 1-on-1. It is a way that works, particularly for a first meeting, that you can modify once you have enough reps to know what you would change.

first 1-on-1 template guide for new managers

What a 1-on-1 Is Actually For

The most common first-1-on-1 mistake is turning it into a status update. Your direct report walks you through what they are working on, you ask some questions about the work, you offer some suggestions, and the meeting ends feeling like a standup with one person. This is the default because work is the easy thing to talk about, and because both of you are nervous and work is a safe subject.

A 1-on-1 is not a status update. A 1-on-1 is a recurring, protected conversation where the person who reports to you gets to raise the things they need to raise, and you get to raise the things you need to raise, in a setting that is not built around a shared deliverable. Status belongs in Slack, in your team standup, in project channels. The 1-on-1 is the only dedicated space in the week where the agenda is the relationship itself.

If you remember only one thing from this letter, remember that. A 1-on-1 that produces a task list is a 1-on-1 you probably ran wrong.

Before the Meeting: Five Minutes of Prep

You do not need to overprepare. Five minutes the morning of is enough. Specifically, answer three questions in a note you keep for yourself.

What do I want this person to know that they probably do not know yet? This is usually context they are missing: a decision that is being made above their head, a piece of feedback that has come up about them in passing, something the organization is about to change that affects them.

What do I want to understand about this person that I do not understand yet? This is where your curiosity earns its keep. What motivates them, what drains them, what they are quietly hoping for, what they are quietly afraid of. You will not get all of it in one meeting. The point is to have the question in front of you so you listen differently.

What is one thing I could give them that would make this week easier? Not a gift. A piece of context, a removed obstacle, an introduction, a decision you have been sitting on, a clear answer to a question they have asked twice without getting a clean response.

That is the entire prep. Write it down, put the note on your second monitor or a piece of paper, and walk in.

The First Meeting: A Specific Script

For your very first 1-on-1 with a new report, or your first as a new manager, skip your prep questions for a minute and use a specific opening. It sounds small. It matters.

Open by saying, roughly: “I want this time to actually be yours. I will bring things sometimes, but the default is that this is your space to raise whatever is useful, including things you would not raise in a regular meeting. If you ever want to skip a week or turn it into something else, tell me. If you ever want to spend the whole time on one topic, tell me. I would rather this feel like a useful hour for you than a scheduled check-in.”

Then ask one of two opening questions, not both. Either “How is the job actually going, underneath the surface?” or “If we repeat this meeting every week for a year, what would make it worth your time?”

Then stop talking. This is the part that is uncomfortable and the part that matters. The first silence after the opening question can last ten or fifteen seconds. Do not fill it. Most managers fill it, because silence feels like the meeting failing, and the instinct to rescue the moment is strong. The silence is the meeting succeeding. It is the first time this person has been asked a real question in a one-to-one professional setting where there was no correct answer and no one was rushing them. Let them answer.

The Middle of the Meeting: A Template That Scales

Once you have had the first meeting, every subsequent 1-on-1 can follow a loose structure. this is a template repeatedly cited by experienced managers as effective for the first 1-on-1. It is not rigid. It is a default to return to when you are not sure what to do.

Minute 1 to 5: Their agenda. “What is on your mind this week?” They talk. You listen. You ask follow-up questions that make them go one level deeper than their first answer.

Minute 6 to 15: The thing that is actually bothering them. This is almost never the first thing they bring up. The first thing is usually a safe proxy. If you ask good follow-up questions, something else will surface around minute 7. That is what this meeting is for. Stay with it.

Minute 16 to 25: Your agenda. Your three prep items. The context they need. The question you are curious about. The thing you can give them. If you have feedback, deliver it here, specifically and without softening it to the point where it stops being feedback.

Minute 26 to 30: Logistics, follow-ups, and one forward-looking question. “What would make next week better than this week?” Not “any action items,” which is the Slack version. A question about their week, not your project.

If the meeting goes somewhere unexpected, abandon the template. The template is there to keep you from defaulting to status update. If the conversation is doing its job, the template gets out of the way.

Questions That Actually Work

The quality of a 1-on-1 tracks closely with the quality of the questions the manager asks. Most manager questions are too small (“how is the project going?”) or too abstract (“how are you?”). The middle band is where the useful answers live.

A short list, drawn from common practice across experienced managers, intended as a well to go to rather than a script when stuck. What is the thing you are dreading most this week, and can we do something about it together. Where are you spending time you do not think you should be spending. Who, on this team, do you find hardest to work with, and what would make that easier. What feedback have I not given you that you would want me to. What feedback have I given you that has not landed or has not been useful. What do you wish I understood about your job that I probably do not. If you had one thing you could change about how we work as a team, what would it be.

Pick one or two. Do not go through the list. The point of these questions is that they open doors. You only need one door open per meeting.

The Specific Things Not to Do

A few patterns to avoid, each of which we have done ourselves in the first year and regretted.

Do not cancel or reschedule unless genuinely necessary. This is one of the top self-sabotage patterns we see in new managers. The reliability of the meeting is doing more work than anything that happens inside it. Canceling teaches the team that the 1-on-1 is negotiable, which means the harder conversations will never start because they will never feel safely parked in a recurring structure.

Do not take notes during the meeting in a way that breaks eye contact for more than a few seconds. If you need to remember something, jot a two-word reminder and go back to listening. Full note-taking turns the meeting into a transcript and teaches the other person that everything they say will be recorded, which changes what they say.

Do not solve problems too fast. The first time a direct report brings you a problem, the temptation is to solve it right there to demonstrate that you are a useful manager. Often the better move is “that sounds hard, what do you think the right move is?” and stay with their reasoning before offering yours. They will grow faster, and you will preserve your capacity to be useful on the problems where they genuinely need you.

Do not turn 1-on-1s into performance reviews. Performance feedback belongs in 1-on-1s as a running thread, not as a formal event. If you are waiting for the 1-on-1 to deliver major performance news, you have already waited too long.

After the First Few Meetings

After four to six weekly 1-on-1s, you will have enough pattern recognition to know where this relationship needs to go. Some relationships use the hour for career conversations. Some use it to debrief hard projects. Some use it as a place where the direct report thinks out loud in front of a trusted listener and leaves calmer than they arrived. All of these are correct uses.

The signal that it is working is that you learn something in the meeting that you could not have learned in any other meeting. If that is not happening for two or three weeks in a row, the meeting has drifted, and the fix is usually a different opening question or a candid conversation about what the meeting is for.

The 1-on-1 is not a glamorous meeting. Nobody posts about the 1-on-1 they had this week. But this is the meeting that makes everything else in your job possible. If your 1-on-1s are good, almost everything else bends in your favor. When they are bad, you usually find out months later, when a direct report resigns and you realize you never actually knew what was going on with them. If they are bad, no amount of process or strategy or offsite planning fixes the underlying distance between you and your team.

Your first one is going to be awkward. Run it anyway. The awkward first 1-on-1 is the price of having a real relationship on the other side of it.


Going through something as a new manager? Send us a letter. The best ones become the next letter.


Keep reading

For a broader view on this topic, see Harvard Business Review on effective 1-on-1s.

Frequently asked about 1-on-1 meetings with direct reports

How often should you have 1-on-1 meetings with your employees?

Weekly, for 30 minutes, is the default that works across most teams. Biweekly is acceptable for senior ICs who prefer more autonomy, but weekly signals investment and catches issues before they calcify. Monthly or less is not a 1-on-1, it is a status check, and it is what managers who do not want to know what is actually happening on their team tend to schedule.

What should you NOT ask in a 1-on-1 with your employee?

Do not open with “how are things going?” It is the question that produces nothing. Avoid status update questions (“how is project X going?”) because those belong in a standup, not a 1-on-1. Never ask about another teammate in a way that invites gossip. And do not ask anything that would be more honestly discussed via email, because you are wasting the one private, real-time channel you have with this person.

What is the best first question to ask in a 1-on-1?

What is one thing on your plate this week that you are not sure how to handle? This question does three things at once. It gets you into their real work immediately. It gives them permission to admit uncertainty, which most employees will not do unsolicited. And it tells you where your help is most valuable without making the conversation feel like a performance evaluation.

How long should a 1-on-1 meeting last?

Thirty minutes. Not less (not enough time to get past surface-level), not more (past 30 minutes, the conversation drifts and nothing productive happens in the last 15). If you consistently need more than 30 minutes, you do not have a 1-on-1 problem, you have a meeting problem. Split the additional work into separate dedicated sessions with clear agendas.

What do you do if your employee has nothing to say in a 1-on-1?

Silence in a 1-on-1 is not empty space, it is signal. Either the employee does not yet trust you enough to surface real issues, or their work is boring them and they have nothing to share. Both are solvable. For the first, stop filling silences with your own updates and wait. For the second, use the session to ask about growth and stretch projects. You are looking for either a concern that needs air or a next challenge that needs finding.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

404 - LETTER NOT FOUND

The letter you were looking for is not at this address.

It may have been moved, retitled, or queued for a future Tuesday. Try one of the four topic hubs below, or head back to the full archive.

MANAGING UP

Bosses, politics, and visibility

DIFFICULT CONVERSATIONS

Feedback, firings, and firsts

FIRST 90 DAYS

Onboarding yourself into the role

BURNOUT

Energy, motivation, and limits

Browse the full archive