New Manager at Amazon: First Team Meeting Agenda Template

The first team meeting you run as an Amazon manager will define how your team perceives your leadership for the next 12 months. Not your competence, not your strategy — your presence in that room. Most new managers at Amazon waste their opening meeting on status updates and slide decks when they should be doing one thing: earning the right to lead.

This is not about what you say. It is about what you signal.

I have watched hiring committees at Amazon debate candidate leadership styles for hours. I have sat through debriefs where strong technical performers were rejected because they could not articulate how they would build trust with a new team. The first meeting is not a formality. It is the opening move in a long game that your team is already watching.

The template below is not a checklist. It is a framework for judgment. You will need to adapt it to your team’s size, your org’s rhythm, and the specific dysfunctions you inherit. But the sequence matters. The silence after you ask for questions matters. The way you close the meeting matters more than the way you open it.

What Should I Cover in My First Team Meeting at Amazon?

The answer is simpler than most new managers expect: cover three things and three things only. You are not there to impress anyone with your knowledge. You are there to demonstrate that you can create clarity under pressure.

First, acknowledge the transition. Name that you are new. Name that they have context you do not yet have. This is not weakness. At Amazon, candor is a leadership principle. Teams that sense a new manager is performing rather than being authentic will spend the next quarter testing boundaries instead of shipping code.

Second, state what you know about the team’s current work. Not what you assume — what you have been told by your manager, read in documentation, or observed in your first week. If you do not know something, say so. Amazon managers who pretend to know more than they do get found out in the first 30 days, and the correction is painful.

Third, outline the next 30 days. Not the next 90 days. Not the year. The next 30 days. What will you be doing to understand the team? What will you not be doing? When will you schedule 1:1s? When will you hold the next all-hands? Specificity at this stage signals organizational control.

The meeting should run no longer than 45 minutes. If you need more time, you are trying to do too much.

How Do I Establish My Leadership Style Without Overstepping?

The mistake most new managers make is arriving with answers. They walk into the first meeting having already diagnosed problems, already formed opinions about processes, already decided what needs to change. This is not leadership. This is theater.

Your team has context you do not have. They have watched previous managers come and go. They have seen initiatives launched and abandoned. They have institutional knowledge that took years to accumulate. Walking in with a preset agenda signals that you are here to execute your vision, not to serve the team.

The counter-intuitive truth is this: the fastest way to establish your leadership style is to lead with questions, not answers. In your first meeting, spend at least 15 minutes on what I call “discovery framing.” Ask the team what is working. Ask what they would change if they had the authority. Ask what they need from you that they did not get from your predecessor.

This does not mean you are indecisive. It means you are intellectually honest. Amazon’s leadership principles include “disagree and commit” and “have backbone.” Neither requires you to have all the answers in week one. Both require you to listen before you lead.

One specific script for this section: “I want to be direct about my approach. I have opinions, and I will share them. But my opinions in week one are worth exactly what you paid for them — which is not much yet. Over the next 30 days, my job is to earn context. Your job is to tell me when I am wrong. If I am doing either of those things badly, I need you to tell me directly.”

What Ground Rules Should I Set in the First Meeting?

Ground rules are not optional, but they are often set wrong. Most new managers default to generic rules from management training: be on time, come prepared, respect each other. These are not ground rules. They are kindergarten rules. Your team has been in corporate environments for years. They know how to behave.

The ground rules that matter are the ones that create psychological safety for hard conversations.

Rule one: we will have direct discussions without going through back channels. If someone has feedback about me or about the team, they bring it to the room. We do not talk about each other in hallways.

Rule two: I will share context that most managers hold close. I will tell you what I know about priorities, resourcing, and roadmap decisions. In return, I expect you to flag when you see risks I am not seeing. I will not punish you for surfacing problems early.

Rule three: decisions can be revisited, but not relitigated. Once we commit to a direction, we execute. If new information changes the calculus, we discuss. But we do not reopen decisions because someone disagree with them in hindsight.

These three rules, stated explicitly in your first meeting, create a framework for accountability that most teams do not have. You are not just managing. You are designing the operating system for how this team makes decisions.

How Do I Handle Existing Team Dynamics as a New Manager?

You do not fix them in the first meeting. You do not even diagnose them in the first meeting. Your job in the first meeting is to establish that you are aware they exist and that you will address them on a timeline that makes sense.

In one Q2 debrief I observed, a new engineering manager at Amazon walked into her first team meeting and immediately addressed a known conflict between two senior engineers. She had been briefed by her director. She thought she was showing that she was prepared. What she demonstrated was that she had already taken sides before she understood the situation.

The room went silent. One of the engineers resigned three weeks later. The other spent the next six months documenting every decision she made for a future HR complaint.

The correct approach: in your first meeting, acknowledge that you know the team has history, and state that you intend to earn the right to understand that history before forming opinions. Do not pretend you do not know. Do not pretend you know too much. Say something like: “I know that every team has dynamics, and this one is no exception. I am not here to adjudicate history. I am here to build forward. If there are things I need to understand to lead this team effectively, I will ask for them directly. If there are things you need from me to feel effective, I need you to tell me.”

This is not avoidance. It is sequencing. You cannot fix what you do not understand. And you cannot understand what you have not earned the right to see.

What Should I Do After the First Meeting?

Send a written summary within 24 hours. Not a transcription. A synthesis. Three to five bullet points on what was discussed, what was decided, and what happens next. This is not bureaucracy. This is a trust-building mechanism.

Amazon managers who follow up in writing demonstrate organizational discipline. Your team will forward that summary to stakeholders. They will quote it in meetings you are not in. The quality of your written communication in the first 30 days sets the standard for how information flows through your organization.

Schedule your first round of 1:1s within the first week. Do not wait until the second week. The longer you wait, the more distance you create between yourself and your direct reports. In your 1:1s, do not start with status updates. Start with one question: “What do I need to know about this team that I do not know yet?”

Listen more than you talk. Take notes. Follow up on commitments. If you say you will look into something, look into it and report back. If you do not follow through on small commitments in week one, you will not build the credibility needed for larger conversations in month three.

Preparation Checklist

Review the team’s quarterly objectives and key results before the meeting. You do not need to have answers, but you need to demonstrate that you have done the homework.
Confirm the attendee list with your own manager. Make sure you are not blindsiding anyone by calling on people who should have been briefed first.
Prepare a written agenda and send it 48 hours in advance. At Amazon, surprise agendas signal disorganization.
Write out your three ground rules in advance. Practice saying them in under two minutes. Hesitation undermines authority.
Identify one question you will ask the team that demonstrates you are listening rather than performing. The best questions come from things you observed in your first week.
Work through a structured preparation system for your first 30 days. The PM Interview Playbook covers leadership transitions with real debrief examples from Amazon hiring committees, including how to handle the first meeting when you are walking into a team with existing dysfunction.
Prepare a one-page summary document you will send within 24 hours after the meeting. Draft it before the meeting so you know what structure you are working toward.

Mistakes to Avoid

BAD: Arriving with a presentation deck and walking through 20 slides of your vision for the team.

GOOD: Keeping your opening remarks under 10 minutes and spending the majority of the meeting on questions and discussion. The first meeting is not about you. It is about establishing that you can create space for others.

BAD: Pretending you are not new or that you already have answers.

GOOD: Stating explicitly that you are earning context and that your early opinions are subject to revision. This is not humble-bragging. It is accurate. And your team will respect you more for saying it than for pretending otherwise.

BAD: Setting ground rules that sound like rules for behavior rather than rules for decision-making.

GOOD: Ground rules that address how the team will handle disagreement, how information will be shared, and how commitments will be honored. These are the rules that actually matter.

FAQ

How long should my first team meeting at Amazon run? Keep it to 45 minutes maximum. If you cannot convey what you need to convey in 45 minutes, you are trying to do too much. The goal is not to cover everything. The goal is to establish a framework for how you will work together. Additional context can come in 1:1s and follow-up meetings.

Should I address my predecessor’s performance in the first meeting? No. Do not praise your predecessor excessively, do not criticize them, and do not position your arrival as a correction. Your team has relationships with the previous manager. You do not. Earning the right to have opinions about the team’s history takes months, not days.

What should I do if the team is hostile or disengaged in the first meeting? Note it without reacting to it. Hostility or disengagement in a first meeting is data, not a verdict. Your job is to stay composed, deliver your structured opening, and follow up in 1:1s where the real conversations happen. If the pattern persists across multiple 1:1s, escalate to your own manager with specific examples, not interpretations.amazon.com/dp/B0GWWJQ2S3).