Managing Former Peers at Amazon: How to Survive Your First 30 Days as a New Manager

Managing Former Peers at Amazon: How to Survive Your First 30 Days as a New Manager

TL;DR

Managing former peers at Amazon is a trust reset, not a title event. The first 30 days are not about proving you were promoted for a reason, but about making the team believe your judgment is stable, legible, and fair.

In a Q3 debrief, I watched a newly promoted manager try to preserve the old peer dynamic and lose the room in 10 minutes. The problem was not the relationship history. The problem was that nobody could tell when he was acting as a colleague and when he was acting as the decision owner.

If you want the clean verdict, here it is: reset expectations privately, be boringly consistent publicly, and use Amazon’s Leadership Principles as your operating language. Not charm, but clarity. Not closeness, but credibility. Not speed, but a sequence the team can predict.

Running effective 1:1s is a system, not a talent. The 0→1 SWE Interview Playbook (2026 Edition) includes agenda templates and question banks for every scenario.

Who This Is For

This is for the person who just moved from individual contributor to manager and now leads people who used to sit beside them in the same Slack channel, same planning meeting, same hallway conversation.

It is also for the Amazon manager who came in through a five to seven interview loop, passed the bar for judgment, and then discovered the first 30 days are harder than the interview because the team watches your decisions in real time.

If you still want everyone to feel comfortable, you will stall. If you turn the first month into a performance of authority, you will also stall. This article is for the manager who needs to become legible fast, especially at Amazon L5 or L6, where old peers will test whether you can run the mechanism without becoming theatrical.

How do you manage former peers without losing authority?

You manage former peers by making the role change explicit and the behavior change measurable. The team does not need a speech about your promotion. It needs to see that your decisions are consistent, your feedback is direct, and your standards no longer depend on old friendship.

In a Monday staff sync, I watched a new manager laugh off a former peer’s interruption because he wanted to seem relaxed. The room read it as weakness. Two weeks later, the same manager overcorrected in public and became brittle. The insight is simple: people do not want a fake boss, but they also do not want a boss who still behaves like a peer.

The move is private reset, public neutrality. Say it one-on-one: “Our relationship is still intact, but my job changed.” Then act like it changed. Not a speech, but a boundary. Not a friendship audit, but a role definition.

Amazon makes this harder because the culture rewards ownership and speed, but punishes ambiguity. If a former peer can still negotiate every decision in the room, you do not have a team. You have a social circle with a manager present.

The first month should not be about proving you are tougher. It should be about proving you are harder to misread. Not equal treatment, but fair treatment. Not being liked, but being trusted. Not winning every moment, but making each decision easier to predict.

What should you do in the first 7 days?

The first 7 days are for mapping the system, not changing it. Your job is to learn where decisions live, which rituals matter, and where the team is silently carrying friction that nobody named.

In practice, I expect a new Amazon manager to spend the first week in one-on-ones, document review, and calendar archaeology. Who owns what. Which metrics get reviewed. Which escalations always come back unresolved. Which former peer is already acting like the unofficial lead. Those are the real facts. The org chart is only the wrapper.

The useful question in each 1:1 is not “How are you feeling?” It is “What is broken, what is unclear, and what would you fix if I disappeared for 30 days?” That gives you signal without forcing theater. It also tells former peers that you are not auditioning for control. You are auditing the mechanism.

By day 7, you should know three things. First, where the team actually gets stuck. Second, which decisions are reversible and which are not. Third, which people need directness and which people need time before they speak candidly.

The counterintuitive part is that the fastest way to earn authority is to ask better questions than the person who used to outrank you informally. Not more questions, but sharper ones. Not a grand vision, but a map of the current machine.

How do Amazon Leadership Principles change your first month?

Amazon’s Leadership Principles are not branding. They are the language people use to judge whether your decisions belong in the org.

In a senior manager review, vague language dies quickly. “I think the team is struggling” gets ignored. “We are missing the customer commitment because the handoff between design and ops is unclear” gets traction. That is the point. Amazon does not reward vague concern. It rewards mechanism-level judgment.

Use the principles as filters. Customer Obsession means you can name the customer pain, not just the internal inconvenience. Ownership means you stop bouncing issues around the org. Dive Deep means you can distinguish symptom from cause. Disagree and Commit means you can move the team forward after the debate is done.

The mistake is not mentioning the principles. The mistake is reciting them without translating them into decisions. Not slogans, but tradeoff language. Not a list of values, but a way to explain why one issue gets priority over another.

If a former peer is underperforming, do not hide behind “I want to support growth.” Say what the gap is, what the impact is, and when you will revisit it. Amazon respects compassion when it is paired with clarity. It has little patience for vague kindness that delays reality.

The deeper organizational psychology here is simple: people read your use of LPs as a proxy for whether you understand the culture or are merely borrowing its vocabulary. If your first month sounds like a deck, the room will discount you. If it sounds like a decision memo, they will listen.

When should you change the team, the process, or nothing at all?

You should change less than you think in the first 30 days. The best first-month managers at Amazon do not arrive with a renovation impulse. They arrive with a diagnostic discipline.

I have seen new managers blow up trust by changing meeting cadence, doc templates, approval paths, and reporting structure before they understood the hidden dependencies. The team did not experience that as leadership. It experienced it as insecurity wearing a management badge.

The right sequence is observe, simplify, then adjust. Use the first 14 days to understand what is noise. Use the next 10 days to remove one or two obvious friction points. Use the last 6 days to codify what will stay. That is enough. Anything more usually reflects ego, not judgment.

Not every problem is a process problem. Sometimes the issue is a person avoiding ownership. Sometimes the issue is a priority that was never truly settled. Sometimes the issue is that the team has learned to wait for the old peer who used to be the real decider. Changing the template will not fix that.

The counterintuitive move is to leave some things alone on purpose. That signals discrimination. It tells the team you can tell the difference between legacy clutter and useful structure. At Amazon, restraint reads as maturity when it is paired with precise intervention.

If you need a simple test, ask whether the change would make the next decision clearer. If it would not, do not touch it yet. Not motion, but leverage. Not visible activity, but visible judgment.

What should you say in one-on-ones and team meetings?

You should speak in commitments, risks, and decisions. If your language is still social and indirect, former peers will keep treating the transition as temporary.

In one-on-ones, the most useful sentence is often the plainest: “I want you to tell me what I am missing, and I will tell you what I need to decide.” That creates a manager relationship without humiliating anyone. It also avoids the false intimacy of pretending nothing changed.

In team meetings, do not overtalk to prove you belong. Summarize the decision, the owner, the date, and the risk. If the room leaves without knowing who owns the next move, you failed. A team meeting is not a group therapy session. It is a coordination device.

One of the cleanest lines I have heard from a new Amazon manager was this: “I am not here to relitigate our old peer relationship. I am here to make the work easier to execute.” That line worked because it was not defensive. It was directional.

The deeper principle is that meetings are a signal of your operating model. If you wander, the team learns that ambiguity is acceptable. If you close decisions cleanly, the team learns that execution will not drift. Not friendliness, but predictability. Not inclusiveness as performance, but clarity as service.

By day 30, former peers should be able to predict how you respond to blockers, missed dates, and conflict. If they still cannot, your title exists on paper but not in the org’s behavior.

Preparation Checklist

• Schedule 1:1s with every former peer in your first week, and make the conversation explicit: role changed, relationship intact, expectations updated.
• Review current goals, open escalations, metrics, and recurring meetings before you propose any change.
• Identify the three behaviors you will be unwavering about: response time, decision clarity, and how feedback gets delivered.
• Decide which parts of the current operating rhythm you will not touch in the first 30 days.
• Write a 30-day note for your manager that spells out what you are learning, what you are changing, and what you are leaving alone.
• Work through a structured preparation system (the PM Interview Playbook covers Amazon-style Leadership Principles tradeoffs and debrief examples, which is the same judgment muscle you need here).
• Pick one former peer to ask for blunt feedback after day 14, then act on the signal instead of performing gratitude.

Mistakes to Avoid

The first month fails for three predictable reasons. Each one looks reasonable on the surface and expensive in practice.

• Mistake: using friendship as a management style.
• Bad: “We have history, so let’s keep this informal,” while avoiding direct calls on ownership.
• Good: “We have history, and that is exactly why I will be direct with you when work is slipping.”

• Mistake: changing too much too early.
• Bad: rewriting meeting formats, reassigning work, and changing docs before you understand the bottleneck.
• Good: fix one broken mechanism, then wait for the effect before touching the next one.

• Mistake: giving soft feedback to protect the relationship.
• Bad: “Let’s all be more proactive.”
• Good: “When the draft slips a day, I need you to flag it immediately and name the new owner.”

The pattern underneath all three is the same. The problem is not your intent. The problem is that your behavior still signals peerhood when the role requires authority.

FAQ

Should I tell former peers I am nervous about the transition?

Yes, but only once and only briefly. Nervousness is human; uncertainty is contagious. Tell them the role change matters to you, then move on to how you will run the work. Not a confession, but a reset.

Should I move a former peer off my team if the dynamic is awkward?

Only if the awkwardness is blocking execution or feedback. Discomfort by itself is not a reason. If you move people just to avoid learning the role, you are outsourcing the hard part. Not conflict avoidance, but deliberate org design.

How hard should I push in the first 30 days?

Hard enough to make expectations real, not so hard that you turn every interaction into a test. The right level is calm, direct, and repetitive. If the team can predict your standards after 30 days, you are on track. If they are still guessing, you are not leading yet.

---

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.