Starting as a new manager is one of the most awkward moments in a career. The team has already built something without you. They’ve had a previous manager, or a rotating stand-in, or they’ve been leading themselves. And on day one, you have to walk into that room (or that Slack channel) and say “hi, I’m your new boss” without sounding like you’re auditioning.
The good news: nobody expects a great intro post. They expect a short, warm, non-arrogant one. Below are 30 templates you can steal and adapt. They’re organized by channel and by tone, because a Slack drop is not the same as a 20-person all-hands. Skip to the section you need.
Before You Send Anything: 4 Rules
- Keep it short. 3–6 sentences for Slack, 200–400 words for email. If you’re nervous, you’ll want to write more. Don’t.
- Acknowledge what already exists. The team built something without you. Say so.
- Skip the promises. No “here’s what I’ll change,” no “my leadership philosophy is.” Show, don’t claim.
- Include one small human detail. Not your entire life story. One warm sentence about you-as-a-person. It lands better than any credential.
10 Short Slack Introductions (Day One)
These work as a first post in your team channel. Copy, replace the specifics, hit send.
“Hi team — officially day one. I’m [Name], joining as [Role]. I’m spending my first two weeks mostly listening — 1:1s with all of you, reading the docs, understanding the roadmap. No changes coming, no reorgs. Just excited to meet everyone. If you like coffee (or tea, or a walk), let’s do a 1:1 this week or next.”
“Hey all — new manager here, [Name]. Coming from [Previous Company / Team]. I’ve heard great things about what this team has shipped, and I’m mostly here to learn for the next few weeks. I’ll DM to set up 1:1s. Nice to meet you.”
“Hi team — [Name] here, your new [Role]. I’ve spent the last [X] years working on [area]. My working style: I read more than I talk, I don’t ask for status in 1:1s, and I like written docs over meetings when possible. Outside of work I’m into [hobby]. Looking forward to meeting each of you.”
“Hey team — [Name], your new [Role]. Genuinely excited to be here. My plan for the first 30 days: listen, learn the systems, meet everyone. No changes coming out of the gate. If anything’s on fire, tell me. If nothing’s on fire, also tell me — I’d like to know what’s going well.”
“Hi everyone — I’m [Name], joining as [Role] today. I’ll be pretty quiet this week while I read docs and set up 1:1s. Two things I’d love from you: (1) if there’s something you wish your previous manager had done, tell me in our 1:1; (2) if there’s something they did that you liked, also tell me — I don’t want to break what’s working.”
“Hey team — you already know me, but wearing a different hat starting today. Same goals, same team, slightly different lens. I’ll be reaching out for a proper 1:1 with each of you this week to reset expectations. Nothing else changes yet — we’ve got a good rhythm and I want to protect it.”
“Morning (or afternoon, or evening) team — [Name] here, joining as [Role]. Since we’re distributed across [X] timezones, most of my intro will be async: a Notion doc with my background, working style, and 30-day plan. I’ll DM to schedule 1:1s that work for your timezone. Excited to meet you.”
“Hi team — I know the last few months have been hard. I’m [Name], joining as [Role], and my only priority for the first 30 days is to listen and stabilize. I’m not going to pretend I know what you’ve been through — I’ll ask, and I’ll take what you say seriously. Setting up 1:1s this week.”
“Hi team — this is [Name], your new [Role] two levels up. I know a skip-level manager showing up in your channel is unusual. I don’t want to make it weird. I’ll be relatively hands-off day-to-day; [Their Manager] runs the team. But my door is open, and I’ll be doing informal skip-level 1:1s with each of you over the next quarter.”
“Hey [Name 1], [Name 2] — I’m [Your Name], your new [Role]. Since we’re a small team, no formal intro post — just wanted to say hi in the channel. Let’s grab time this week individually and then together.”
8 Introduction Emails (Longer, Async)
Use these when Slack feels too light or when your team is distributed and needs something they can read later.
“Hi team,
I’m [Name], your new [Role]. I wanted to send a quick note to introduce myself.
A short version of me: I’ve spent the last [X] years working on [area / at company]. Before that, [prior context]. I’m joining because I was excited by [specific thing about this team’s work] — and by the chance to work with all of you.
My first 30 days will be mostly listening. I’ll set up 1:1s with each of you this week or next. I’m not planning changes out of the gate — my only priority is understanding what’s working before I have opinions.
Two personal notes: I’m based in [City], and outside of work you’ll find me [hobby]. Genuinely excited to be here.
[Your Name]”
“Hi team — [Name] here, your new [Role].
Since we’ll be working closely, here’s a quick heads-up on how I operate:
• I prefer written docs to meetings. If we can decide something in writing, let’s.
• My 1:1s are yours, not mine. Bring what you want to talk about — I don’t need a status update.
• I’m OK being interrupted. Slack DM me if it’s urgent.
• I try to respond in under 24 hours during weekdays. If I go longer, ping me again.
• I’m not the person for approval-theater. If you know what to do, do it.
My first two weeks will be quiet. I’ll be reading, listening, and meeting each of you. Looking forward to it.
[Your Name]”
“Hi team,
I’m [Name], starting today as your new [Role]. I’m coming from [Previous Company], where I spent [X] years leading [what]. I’m aware that being an outside hire into an established team is a lot — you had a way of working that worked, and I don’t plan to disrupt it.
What I’m going to do in the first 60 days: listen, read, meet everyone, understand the roadmap, and only then form real opinions. If you notice me trying to shortcut that, please push back — I’d rather be told ‘you don’t have context yet’ than pretend I do.
[Your Name]”
“Hi team — wearing a slightly different hat starting today. I’m still [Your Name], but now your [Role].
Since you already know me, I’ll skip the resume paragraph. What’s changing: I’m responsible for [scope] now, so I’ll be spending more time on planning, hiring, and cross-team stuff, and less time in the code. What’s not changing: I’m still the same person, same working style, same phone number.
I’m going to reset 1:1s over the next two weeks so we can talk about how the reporting relationship might change for each of you.
[Your Name]”
“Hi team,
[Name], your new [Role]. Because we’re spread across [X] timezones, I’m going async by default and want to signal that clearly from day one.
You’ll find in the linked Notion doc: my working hours, how to reach me for different kinds of things, and my 30/60/90 plan. Skim it whenever it’s convenient. I’ll set up 1:1s that work for your timezone — if none of my slots work, please tell me and I’ll shift.
Excited to be here.
[Your Name]”
“Hi team,
I’m [Name], joining as your new [Role]. I know [Previous Manager] meant a lot to this team, and I’m not going to try to replace them — I’m going to be a different person who cares about the same things.
My job in the first 90 days is to earn your trust the same way they did: by showing up, listening, and being useful. I don’t need you to warm up to me on day one. Take the time you need.
1:1s this week and next. Looking forward to meeting each of you.
[Your Name]”
“Hi team — I’m [Name], your new [Role] starting today. My plan for the first month: mostly listening. I’ll DM everyone to set up 1:1s this week. If you’d rather I know something before we meet, just Slack me or drop it in the doc I’ll share.
[Your Name]”
“Hi team,
I’m [Name], your new [Role]. Full disclosure: this is my first management role, and I’m going to make mistakes. My commitment is to name them out loud when I do, ask you for feedback often, and not pretend I have answers I don’t.
What I’m going to focus on in the first month: knowing each of you as a person, understanding the work, and staying out of the way where the team already has rhythm. 1:1s this week.
[Your Name]”
6 All-Hands / Kickoff Meeting Openers
These work as the first thing you say when the team is together for an intro meeting.
“Hi all — thank you for the time. I’m [Name]. I don’t want to spend this whole meeting on me, so here’s the two-minute version: [background]. Now, I want to hear from each of you — what are you working on, what’s working, what’s not?”
“Before we start — a quick note on how I want to run this. I don’t want you to walk out of this meeting thinking you had to perform. I’m here to listen. If you’re quiet in a big group, DM me later. If you’re direct, please be direct. There’s no wrong way to talk to me today.”
“First, I want to name the obvious: change of manager is disorienting, especially when the team is already in the middle of things. I’m not going to pretend it’s not weird. What I can promise is that I’m going to move slowly and ask a lot of questions before I have opinions. If I’m moving too fast in the next 90 days, tell me.”
“Rather than a monologue, I have a question for each of you. What’s something this team does well that you’d be sad to see go? And what’s something that, if we could change it tomorrow, would make your job noticeably better? We’ll go around, no wrong answers.”
“Here’s my plan for the first 90 days, so you don’t have to guess: month one is listening — 1:1s, docs, no changes. Month two is co-drafting a rough plan for what we take on next, with your input. Month three is executing. If any of that changes, I’ll tell you it’s changing before it changes.”
“Before we close — one ask. Send me one thing before our first 1:1: something I should know that isn’t in the org chart or the docs. It can be about the team, the work, a broken process, a person, anything. Two lines is fine. That helps me start our conversation from real ground, not from what I’m guessing.”
6 First 1:1 Openers
The intro post gets the announcement done. The first 1:1 is where you actually build the relationship. These work as the opening moment of that meeting.
“Thanks for the time. Before we get into the work — I’d love to know how you like to work with a manager. What’s something a previous manager did that you appreciated? What’s something you wish they hadn’t done? I’m going to steal the good ones.”
“Before we talk about work, I’d like to know a bit about you as a person. Where are you based? What are you into outside of work? What’s something going on in your life right now that would help me be a better manager to you?”
“Three questions, we can go in any order: What are you working on, what’s in your way, and what do you want the next year of your career to look like? We’ll come back to all of these — I just want a starting map.”
“I’m going to make mistakes with you specifically because I don’t know your context yet. If I’m being unclear, or asking for the wrong thing, please push back. I’d rather hear it from you than find out three months from now that you were quietly annoyed.”
“This 1:1 is yours, not mine. My only agenda item is: I want to earn your trust, and I know that takes time. What’s the version of me showing up as your manager that would help you do your best work?”
“First 1:1s are always a little awkward — you don’t know how I’ll react, I don’t know what’s normal for you. So let’s just get through the awkward together. Tell me the thing you were unsure whether to bring up.”
Culture starts with how the team is led
The way a manager introduces themselves is a preview of how they’ll run the team. Browse companies where engineering leadership actually walks the talk on culture, autonomy, and psychological safety.
Browse Culture Profiles → See Safe-to-Fail Companies →What to Skip in a New-Manager Intro
Some things sound great in your head and land badly in your team’s Slack. A short kill list:
- Long resumes. Nobody wants a 5-paragraph list of your previous roles on day one. Two sentences of background is plenty.
- “My leadership philosophy is…” This lands as performative regardless of intent. Show the philosophy through behavior in month one, not through claims in a post.
- Promises of big change. “We’re going to move faster / ship more / raise the bar” on day one signals that you’ve already decided things without knowing the team. Teams remember this.
- Implicit or explicit criticism of the previous manager. Even “fresh start” framing reads as a subtle diss. If they were beloved, honor them. If they were bad, the team already knows — you don’t need to say it.
- “My previous company did X and it worked great.” The comparison is almost always heard as a suggestion that this team is doing it wrong. Save cross-company insight for later, when you’ve earned the right to bring it in.
- Corporate buzzwords. “Synergize,” “bring my A-game,” “leverage learnings.” If you wouldn’t say it out loud at dinner, don’t Slack it either.
- An overly casual intro if the team is formal, or vice versa. Read the channel history before you post. Match the register.
What Great New-Manager Intros Have in Common
Across dozens of the good ones, the pattern is small: they’re short, they’re specific in one small human way, and they hand agency back to the team. Something like: “I’m [Name], I’m going to spend the first month listening, here’s one small thing about me, DM me if you want to talk sooner.” That’s the shape. You can vary the tone. You can’t skip the humility.
The intro isn’t where you win the team over. That happens over months, through the small stuff: showing up on time, closing loops, defending the team upward, giving credit publicly and feedback privately. The intro is just: don’t start on the wrong foot. Use one of the templates above, take out the word “synergize” if you added it, and hit send.
New Manager Introduction FAQ
Find a role at a company where leadership actually cares
The best intro messages come from managers who work at companies that model good leadership. Browse engineering-first companies vetted for manager quality and team culture.
Browse Jobs → See the Culture Directory →