GUIDE · NEW MANAGERS
Your first team meeting as a new manager: agenda and what to say
Your first team meeting sets the tone for months. People are not looking for a vision speech. They want to know three things: what kind of manager you will be, what is about to change, and whether it is safe to be honest with you.
Keep it short, say less than you think you should, and leave the team with one clear next step. Here is an agenda that works for a team of three or thirty.
How to organize it: the week before
- Book 45 minutes in the first week, at a time the whole team can make. For a remote or mixed team, put everyone on their own screen so nobody is a voice in the corner.
- Ask your manager what the team already knows about you and the change, so you do not repeat or contradict it.
- Send a short invite with the agenda: “I’d like to introduce myself, hear from you, and agree how we’ll work together. No preparation needed.”
- Prepare your two-sentence introduction and the three things you will say about how you work. Write them down.
- Ask someone to take notes, or plan to write them up yourself straight after.
A 45-minute agenda
- 5 minutes: a short introduction. Your background in two sentences and why you took the role.
- 10 minutes: how you like to work. How to reach you, how often you will meet one-on-one, how you make decisions.
- 5 minutes: what is not changing. People worry most about losing what already works.
- 15 minutes: questions to the team (below). Listen and write things down.
- 5 minutes: what happens next. One-on-ones booked this week, and when you will come back with what you heard.
- 5 minutes: open questions for you.
What to say
For the first month I’m mostly going to listen. I won’t change how we work until I understand why it works the way it does.
I’ll book a one-on-one with each of you this week. It’s your time, not a status update.
If I do something that gets in your way, I want to hear it. You won’t get in trouble for telling me.
Example opening script (about 3 minutes)
“Thanks for making the time. I’m [name], and I’ve spent the last few years [one line on your background]. I took this role because [one honest reason].
Here is how I like to work. You can reach me on [channel], and I’ll reply the same day. I’ll hold a 30-minute one-on-one with each of you every [week or fortnight], and that time is yours. When I make a decision that affects you, I’ll tell you why.
What isn’t changing: [the thing people worry about, such as current projects, shift patterns or who they report to]. For the first month I’m mostly here to listen. So I’d like to spend most of today hearing from you.”
Questions that get the team talking
Ask two or three. Silence is normal; wait longer than is comfortable before filling it.
What is one thing about how this team works that we should definitely keep?
What slows you down most in a normal week?
What do people outside the team not understand about our work?
If you were me, what would you look at first?
What to avoid
- Announcing changes in the first meeting. You do not yet know enough.
- Talking about how your previous team did it.
- Promising things you cannot control, like pay rises or headcount.
- Taking silence as agreement. Follow up in one-on-ones, where quieter people speak up.
After the meeting
Send a short note the same day: thank people, summarise what you heard in a few bullets, and confirm the one-on-ones. Then, about a month in, come back to the team with what you learned and the one or two things you will change first. Doing what you said you would do is what builds trust, not the meeting itself.
Example follow-up note
“Thanks for today. Here is what I heard: we should keep the Friday demo, the approval process slows everyone down, and the team down the corridor does not see how much we handle. I’ve sent each of you a one-on-one invite for this week. I’ll come back to the team by [date] with the first one or two things I’ll work on. If you thought of anything after the meeting, reply here or bring it to your one-on-one.”
Special cases
- You were promoted from inside the team: say it out loud. “Yesterday I was one of you, and this is new for all of us.” Then follow the guide on managing former peers.
- The previous manager left on bad terms: do not criticise them. Say you want to hear what worked and what did not, and listen.
- The team is remote: keep it to 30 minutes, ask everyone to type one answer in the chat before anyone speaks, and hold the one-on-ones on video.
- The team is large (15 or more): keep the introduction the same, but collect the questions in a short form beforehand and pick the three most common to discuss.
Free tools for this
Frequently asked questions
How long should a new manager’s first team meeting be?
About 30 to 45 minutes. Long enough to introduce yourself and ask a few questions, short enough that you do not end up making promises or announcing changes too early.
Should a new manager make changes straight away?
Usually not. Spend the first few weeks listening and understanding why things work the way they do, unless something is clearly unsafe or broken.
What should a new manager say about themselves?
Keep it short: a couple of sentences on your background, why you took the role, and how you like to work, such as how to reach you and how often you will meet one-on-one.
How do you organize a first team meeting as a new manager?
Book 45 minutes in your first week, send a short agenda, prepare a two-sentence introduction and three points on how you work, then spend most of the meeting asking questions. Send a follow-up note the same day and book one-on-ones that week.
Should the first team meeting come before or after one-on-ones?
Hold the team meeting first, ideally in the first two or three days, so everyone hears the same message at the same time. Then hold one-on-ones that week, where quieter people will tell you more.
What if nobody talks in the first meeting?
That is normal. Ask everyone to write one answer on a sticky note or in the chat first, then read a few out. Follow up on the same questions in one-on-ones.
One-minute lessons on this
Read next
More guides
- Stay interview questions: find out why people stay before they leave
- How to manage people who used to be your peers (and friends)
- How to delegate as a manager without losing quality (or sleep)
- Difficult conversations with employees: a simple structure and example scripts
- How to organize and run a team meeting people don’t dread
- How to handle conflict between two employees
- What to do when an employee keeps missing deadlines
- Remote team check-ins: how to stay close without micromanaging
- What to say when an employee resigns (and what to do next)
- Constructive feedback examples: what to say, and how to say it
- How to say no to your boss without damaging the relationship
- Employee recognition examples that people actually remember
- Your first 90 days as a new manager: a week-by-week plan
- How to deliver bad news to your team (with example wording)
- Year-end performance reviews: a 6-week checklist for managers