How to Run Your First Team Meeting as a New Manager

Your first team meeting as a new manager sets the tone for every meeting that follows. How you run it communicates something about who you are, how you use people’s time, and what kind of manager you’ll be. Most first meetings are either over-scripted or underprepared. Here’s a better approach.
Key takeaways
The first team meeting isn’t about impressing your team — it’s about beginning to understand them and signaling what kind of manager you intend to be
Keep the first meeting relatively short and agenda-light — the goal is connection and orientation, not coverage
What you say about decision-making, communication, and feedback in the first meeting is what the team will hold you to from that point on
Blomma helps you prepare for the parts of the conversation you haven’t thought through yet
On this page:
What Your First Team Meeting Is Actually For
The first meeting is not a state of the union. It’s not an introduction presentation. It’s the beginning of a working relationship, and the purpose is to signal to the team: what kind of manager am I, what do I care about, and what do I expect? That’s it.
Your team is assessing you. Not critically, but instinctively — they’re forming an impression in real time about whether you’re worth trusting, whether you know what you’re doing, and whether things will get better or worse under your management. The best thing you can do is be clear, be calm, and be genuine.
What to Prepare Before You Arrive
Preparation for this meeting isn’t about a polished deck — it’s about clarity on a few questions:
What are 2-3 things you want the team to take away from this meeting? Not an agenda — the actual takeaways.
What do you genuinely want to learn about this team right now? Have a real question or two — not rhetorical ones.
What, if anything, do you want to signal about how meetings will run going forward? If you’re inheriting a culture of long, unfocused meetings, this is an early moment to signal something different.
What to Cover in the Meeting
A simple structure that works well:
Brief introduction: Who you are, a bit of relevant background, and — importantly — what you don’t know yet. “I’m still learning the specifics of what you’re working on” is more credible than pretending you’ve already done that homework.
Statement of intent: What do you care about as a manager? How do you want the team to work? What are you coming in to change, if anything, and what are you coming in to support? Be specific, not inspirational.
A genuine question: Ask something you actually want to know. “What’s working well on this team that I should be careful not to disrupt?” or “What’s the one thing you wish the last manager had done differently?” Listen. Don’t immediately respond.
How you’ll work individually: Let them know you’ll be scheduling 1-on-1s with each of them and that those conversations are theirs to use. It signals investment before you’ve done the actual work.
What Not to Do in Your First Team Meeting
Don’t announce major changes. The first meeting is not the time to restructure processes, reassign ownership, or signal that things were broken before you arrived. Listen before you change.
Don’t over-promise. Statements like “I’ll always have your back” or “things are going to be different around here” create expectations you may not be able to meet. Mean what you say and say less.
Don’t run long. Respect their time from the first meeting. A crisp 30-45 minutes signals competence. Ninety minutes of stream-of-consciousness does not.
Don’t pretend to have answers you don’t have. “I don’t know yet, but I’ll follow up” builds more trust than confident-sounding guesses you’ll need to walk back.
How Blomma Helps
Blomma’s coaching helps you think through the parts of the first meeting you haven’t fully worked out — what statement of intent feels authentic, what question you genuinely want to ask, how to handle the moment that goes off-script. Preparing in coaching is different from preparing with notes: it gets to the actual uncertainty, not just the agenda.
For what comes after — the ongoing rhythm of 1-on-1s that deepen the relationship the first meeting opens — [how to run better 1-on-1s with your team](../for-teams/how-to-run-better-one-on-ones) is the natural next step. For the full arc of the first weeks in the role, [first-time manager: a 30-60-90 day survival guide](../for-teams/first-time-manager-guide) gives you the broader context.
Frequently Asked Questions
How long should the first team meeting be?
30-45 minutes is usually right. Long enough to cover what matters; short enough to show you value their time. Save the longer conversations for individual 1-on-1s where they can be honest.
What if the team is skeptical or disengaged in the meeting?
Don’t try to win them over in the first thirty minutes. Skepticism from a team that’s had poor management before is reasonable and predictable. Your job is to behave consistently over time. The 1-on-1s that follow will do more to shift the dynamic than any group meeting.
Should I mention the changes I want to make?
Not yet, unless something is actively broken and needs immediate addressing. Your first meeting is for listening and orienting. Make changes after you understand what you’re changing and why.
First impressions compound. The credibility you build by being clear, calm, and genuinely curious in the first meeting makes every subsequent conversation easier.
