The New Manager's First 1-on-1 Template

Published on August 13, 2026

Most first 1-on-1s go the same way. The manager talks for most of it, covers logistics, maybe mentions a project or two, and closes with some version of "let me know if you need anything." It feels productive in the room. Three weeks later, neither person actually knows much more about the other than they did before the meeting happened, and the second 1-on-1 opens with the same amount of guessing as the first.

This applies whether the report is brand new to the company or has been on the team for years and you're the one who's new, promoted into the role or handed the team after a reorg. Either way, the relationship is starting from close to zero, and the first meeting is the only one where that's true. If you're also new to managing in general, the Engineering Manager's First 90 Days covers the wider arc this meeting kicks off. What follows is a structure for this one specific conversation, and why each part matters.

1. Contract the Relationship, Both Directions

A first 1-on-1 that's just the manager stating expectations is a briefing, not a conversation. It sets a tone where one person defines the terms and the other one listens, which is a strange way to start something that's supposed to be collaborative for the following two or three years. Asking what the report needs from a manager, before saying anything about your own expectations, signals something real about how the relationship is going to work.

What to actually cover:

• Ask what they need from a manager to do their best work, and actually wait for a real answer instead of moving on after a generic one.
• Share your own working style and what they can expect from you, specifically enough that it's useful rather than a vague reassurance.
• Agree out loud that this is a two-way conversation from here on, not just checking in on their side of things.

2. Learn How They Actually Work

Every manager eventually figures out how a report likes to receive feedback, whether they think out loud or need a minute before answering, what kind of update actually reassures them versus what reads as micromanaging. The only question is whether that gets learned deliberately in the first few weeks or by trial and error over the first few months, usually after a few avoidable misunderstandings.

What to actually cover:

• Ask directly how they prefer to get feedback, in the moment or with time to think it over first, in writing or out loud.
• Ask what kind of communication feels like support to them and what starts to feel like being watched too closely.
• Write down what they tell you. This is exactly the kind of thing that's obvious in week one and easy to forget by week six.

3. Get Their View of the Landscape Before Forming Your Own

This matters most when you're the one who's new, stepping into a team through a promotion or a reorg rather than the report being the new hire. It's tempting to arrive with early opinions about what needs to change, formed from a few weeks of observation or whatever the previous manager mentioned on the way out. Someone who's actually been doing the work usually has a clearer, more specific view, and asking for it before sharing your own read keeps you from anchoring the team to a guess.

What to actually cover:

• Ask what's working well on the team right now, specifically enough that it's not just a polite non-answer.
• Ask what they'd change if it were up to them, and let a real answer sit rather than immediately explaining why it isn't that simple.
• Hold off on stating your own opinions about the team in this meeting. There will be time for that once you've heard more than one perspective.

4. Set the Cadence and Ground Rules for Every 1-on-1 After This One

The first 1-on-1 is also the only natural moment to talk about the meeting itself before it becomes a routine nobody questions. Length, day, who's expected to show up with something to talk about, what happens on a week where nothing urgent comes up, all of this is easier to agree on explicitly now than to renegotiate later once a pattern's already set in.

What to actually cover:

• Agree on a day, time, and length that actually fits both calendars, not just whatever slot happened to be open.
• Decide who's expected to bring the agenda by default, and what to do on a week where neither person has much to raise.
• Say plainly that this meeting is theirs as much as yours, and that it's not just a status update for your benefit.

5. Leave With One Concrete, Visible Next Step

A first meeting that ends on trust-building alone, with no follow-through anyone can actually see, risks feeling like it didn't mean much once the next few weeks get busy. Closing with one small, specific thing, something that visibly happens because of this conversation, is what tells the other person the meeting actually changed something rather than just being a nice introduction.

What to actually cover:

• Pick one small, concrete thing to follow through on within the next week, ideally something they'll notice without having to ask.
• Say exactly what it is and roughly when it'll happen, not a general intention to "keep this in mind."
• Open the next 1-on-1 by checking back on it before moving to anything new. That's what makes the first one feel like the start of a pattern instead of a one-off.