You have been given the role. The announcement went out, the org chart updated, and now you are the manager. But the title is the easy part. The harder part is the first few days when your team is sizing you up and you are still trying to understand what you have walked into. Getting the introduction right is not about charm or grand speeches. It is about showing the team, early and consistently, that you are someone worth trusting. That takes more than a single message in Slack.
The teams that trust a new manager quickly are not the ones who heard the most inspiring vision. They are the ones whose manager asked good questions and then actually listened to the answers.
What your team is actually wondering
Most of the things running through your team's minds when a new manager arrives have nothing to do with your CV. They are wondering whether their day-to-day work will be disrupted, whether you will be fair, and whether it is safe to be honest with you. Understanding this changes how you walk in. You are not filling a blank slate. You are walking into a group of people who already have opinions, habits, and anxieties - and your job in the first few weeks is to work with that, not over it.
What they say
What they are really asking
You will not be able to answer all of these directly in a first meeting. But you can answer them indirectly by the way you show up: whether you talk more than you listen, whether you make announcements or ask questions, whether you seem genuinely curious about the team or already have the answers. These signals are louder than anything in your introduction.
What to say in your first team meeting
Your first team meeting is not the time for a vision speech. Keep it short - fifteen to twenty minutes at most. The goal is not to impress. The goal is to give the team just enough context to feel settled, and to frame the next few weeks clearly so they know what to expect from you. Three things to cover, and nothing more.
First team meeting - a simple agenda
Who you are (briefly)
Relevant context, not your whole career. Two or three sentences on your background and why you are here.
How you plan to work in the first few weeks
You are in a listening phase. You will be scheduling 1:1s with everyone. You want to understand before you decide.
What you are NOT doing immediately
No restructures. No process overhauls. You are here to learn before you act.
Leave time for questions. Answer honestly. It is fine to say "I do not know yet".
The most important phrase you can use is a version of: "I am going to spend the first few weeks understanding how things work here before I make any significant decisions." This is not weakness. It is the single most reassuring thing a new manager can say, because it tells the team that their knowledge and experience will be taken into account rather than steamrollered.
Common mistakes in first team meetings: talking for thirty minutes about your background, making promises about things you cannot control, and announcing changes you plan to make before you have asked whether those things actually need changing. All three send the same signal: this person arrived with their mind made up.
Your first round of 1:1s
Book your first 1:1 with every direct report within the first two weeks. Do not wait until you feel ready or until you have learned enough context. These conversations are how you learn the context. The first round of 1:1s is not a check-in on their work. It is a listening session designed to understand the person and build the beginning of a relationship.
Questions that work well in a first 1:1
What is working well that you would not want to see change?
Surfaces what they value. Sets a signal that you are not here to disrupt everything.
What is frustrating you or slowing you down?
Gives you early signal on real problems. Shows you are interested in removing blockers.
What do you need from your manager that you are not getting right now?
Tells you where the last manager fell short and what this person needs to do their best work.
What should I know about the team that might not be obvious from the outside?
Invites honesty about dynamics, history, or context that would take months to discover otherwise.
Take notes in every session. Not to document ammunition, but to show that you were paying attention. Use the Catchups feature in Manager Toolkit to log the key points from each conversation and create follow-up Actions so that anything you committed to gets tracked. Following up on something someone mentioned three weeks ago - unprompted - says more about your leadership than any first-meeting speech ever will.
Some people will be guarded in a first 1:1. That is normal. Do not push. The fact that you showed up, asked thoughtful questions, and listened without immediately countering everything is itself a signal. Trust is built in layers, and the first layer is just showing up consistently.
Setting your tone, not rushing decisions
The first 30 days are for listening. The next 30 are for making sense of what you heard. By 90 days, you should have enough context to act on the things that genuinely need changing - and the credibility to do it. This is not a rigid rule, but a useful frame. It stops you from confusing the impulse to feel useful with the actual need to change something. Most new managers who act too quickly do so because doing nothing feels uncomfortable, not because the situation demanded speed.
A useful early-days frame
Listen
Run your first 1:1s. Watch how work flows. Ask more than you answer. Resist changing anything unless it is urgent or harmful.
Understand
Identify patterns across the conversations and your observations. What is a one-off? What is systemic? What did multiple people mention independently?
Act
Start making changes with context and credibility. Share your observations with the team. Act on the things with the clearest signal and the broadest support.
Your tone in the first few weeks becomes your reputation. Are you someone who follows through on small things? Who asks thoughtful questions? Who admits what you do not know yet? These habits, repeated consistently, tell your team more about who you are than any introductory presentation. As you settle in, revisit the new manager survival guide for what to focus on through your first 90 days and beyond.
If you are taking over an existing team rather than building one from scratch, the dynamic is more delicate still. People have loyalties to the previous manager, habits that are not written down anywhere, and a particular way of working that you need to understand before you can improve it. The listening phase is even more important in that context. The good news is that teams know when a new manager is doing the work of actually understanding them - and they respond well to it.
Frequently asked questions
Start every catchup prepared
Track your first 1:1 notes and follow-ups in one place so nothing you promised gets forgotten.