Quick Answer

You will fail your first week as a manager at Amazon if you treat your former peers the same way you did as a peer. The shift is not about authority—it’s about accountability. Your success hinges on redefining relationships within 72 hours, setting asymmetric expectations, and anchoring to leadership principles without over-indexing on consensus.

Managing Former Peers: How to Lead Your First Week as a New Amazon PM Manager

TL;DR

Not sure what to bring up in your next 1:1? The Resume Starter Templates has 30+ high-signal questions organized by goal.

Who This Is For

This is for senior product managers promoted internally at Amazon—typically Level 5 or early Level 6—who now manage a team they were just on equal footing with 10 days ago. You’ve shipped features together, vented about leadership in Slack threads, and split burritos after sprint reviews. Now you must shift from camaraderie to calibration without alienating the team.

How do I establish authority without looking power-hungry?

You establish authority not by asserting control but by exercising restraint. In your first one-on-ones, do not give answers—ask for feedback on your own priorities. This reverses the power script: you’re not claiming dominance, you’re institutionalizing accountability.

During a promotion debrief last year, the hiring committee rejected a candidate because he said, “I told my old team I’d keep things running smoothly.” That signaled maintenance, not leadership. The acceptable answer was, “I let them know the context had changed, and so would our operating rhythms.” One phrase signals continuity; the other, ownership.

The problem isn’t that former peers resist your authority—it’s that they’re waiting to see whether you’ll flinch when results demand trade-offs. At Amazon, authority flows from judgment, not org charts. If you delay a launch to fix a critical reliability gap, even if the team resists, you earn credibility. If you skip a deep dive on a P0 metric because “we’re still getting used to things,” you lose it.

Not leadership, but stewardship. Not trust based on friendship, but trust based on consistency. Not alignment through voting, but alignment through context-sharing followed by clear decision calls.

> 📖 Related: meta-vs-amazon-career-compare-2026

What should I do in the first 72 hours as a new manager?

Within 72 hours, you must complete three irreversible actions: redefine the feedback loop, reset communication norms, and isolate emotional debt.

By hour 24, schedule individual one-on-ones—no group messages, no all-hands warm-up. Each call must be 30 minutes, no agenda shared in advance. Your opening line: “What’s one thing I should start, stop, or continue doing as your manager?” This forces specificity and surfaces silent expectations.

By hour 48, publish a lightweight team charter—three pages max. It includes: (1) how decisions will be made, (2) escalation paths, (3) meeting cadences, and (4) your management philosophy. At Amazon, this document replaces “we’ll figure it out.” One manager I reviewed in Q2 wrote, “I default to written narratives over verbal updates,” which clarified process immediately. Another wrote, “I will read your PRFAQs before our sync and send feedback 24 hours in advance”—this raised team preparation quality overnight.

By hour 72, host a 60-minute team reset meeting. No metrics, no roadmap. Focus only on interaction patterns. Say: “Our relationship has changed. I will now give you feedback you may not like. I expect you to do the same to me.” Then pause. Let the silence land. This is not theater—it’s boundary-setting.

One former peer later told me, “I didn’t respect my new manager until she gave me negative feedback in week one.” Delay erodes legitimacy. Speed establishes it.

How do I give feedback to someone I used to grab coffee with?

You give feedback the same way Amazon evaluates bar-raisers: with data, not tone. Personal history makes emotional neutrality your competitive advantage—not a liability.

Two weeks after a peer promotion last year, a new manager avoided correcting a teammate’s misaligned OKR. He said in the HC, “I didn’t want to seem harsh so early.” The committee shut it down: “Your job isn’t to be liked. It’s to prevent drift.” At Amazon, failure to correct misalignment in the first 30 days is treated as managerial neglect.

Your script: “Here’s what I observed. Here’s the impact. Here’s what I’d like to see differently.” No “I feel,” no “we,” no “maybe.” Example: “You presented the roadmap update without referencing the customer pain score. That increases the risk of misprioritization. Next time, lead with the data.” Cold? Yes. Clear? Also yes.

The feedback isn’t about the act—it’s about the precedent. If you let one deviation slide because of history, others will test boundaries. Amazon’s leadership principles reward high standards, not harmony.

Not empathy as avoidance, but empathy as precision. Not “I know this is hard,” but “I know you can meet this bar.” Not softening the message, but sharpening the expectation.

When a former peer pushed back during a 1:1, one successful manager replied: “I’m not holding you to a new standard. I’m holding you to the same standard I’m holding myself to now.” That reframed fairness as shared burden—not favoritism.

Should I have skip-levels in my first week?

No. Wait until week three. Conducting skip-levels in week one signals distrust in your direct reports and fractures team cohesion.

I sat in an HC where a new manager claimed credit for “immediate skip-level engagement.” The bar-raiser responded: “You haven’t even built trust with your directs. Why are you mining their teams for intel?” The promotion was put on hold.

Skip-levels are not fact-finding missions—they’re trust audits. You conduct them to validate patterns, not to hunt for problems. At Amazon, initiating skip-levels too early is interpreted as managerial insecurity, not diligence.

By week three, you should have: completed all 1:1s, reviewed current deliverables, and sat in two team meetings. Only then do you schedule skip-levels—30 minutes each, optional for the employee. Your opening: “I’m not here to hear about your manager. I’m here to understand your work and where roadblocks exist.”

One L6 manager delayed her first skip-level by five weeks. When asked why, she said: “I needed to earn the right to ask those questions.” The committee praised that restraint.

Not access, but earned legitimacy. Not transparency as dumping, but transparency as pacing. Not bypassing, but reinforcing the chain.

Amazon’s managerial model assumes that the direct report is the primary insight source. If you go around them too soon, you break the chain before it’s tested.

How do I align with my own manager in week one?

You align by shipping a written context memo within 48 hours of stepping into the role. This is not optional. It is your first deliverable as a manager.

The memo has three sections: (1) my understanding of team priorities, (2) proposed 30-day focus areas, and (3) open questions. It should be 4–6 PR/FAQ style paragraphs, no bullets. At Amazon, writing is thinking. If your memo is muddy, your thinking is muddy.

One new manager submitted a 12-bullet slide deck. His skip-level wrote in the HC packet: “Does not operate at narrative depth. Relies on fragments.” He was required to resubmit as prose.

Your manager will expect you to reference Leadership Principles—specifically Deliver Results, Insist on the Highest Standards, and Earn Trust. But do not name-drop them. Embed them. Example: “I’ll measure progress weekly against customer outcome metrics, not just delivery velocity,” signals Insist on the Highest Standards without saying it.

Schedule a 45-minute sync after they’ve read it. Come prepared to defend trade-offs. One manager proposed pausing a low-impact initiative to rebalance engineering capacity. His boss approved it—not because the idea was brilliant, but because the rationale was clear and customer-centric.

Not alignment as approval, but alignment as shared context. Not “checking in,” but “setting trajectory.” Not consensus-driven, but decision-ready.

At Amazon, your first week isn’t about proving competence—it’s about proving operating model clarity.

Preparation Checklist

Schedule and complete individual 1:1s with each direct within 72 hours—no group overrides
Draft and share a team operating charter by day three, covering decision rights and feedback norms
Write and send a context memo to your manager within 48 hours of role start
Plan your first team meeting as a reset on roles, not a victory lap on past work
Block time for deliberate silence—60 minutes daily—to process inputs without reaction
Work through a structured preparation system (the PM Interview Playbook covers peer-to-manager transitions with real debrief examples from Amazon leadership committees)
Identify one peer relationship that will be most strained and plan a dedicated conversation for week two

Mistakes to Avoid

BAD: Sending a team-wide message saying, “I’ll always have an open door and want your feedback.”

GOOD: Saying in 1:1s, “I welcome feedback, and I’ll give you direct input too—it won’t always be easy, but it will be timely.”

Why: Open-door platitudes invite chaos. Structured reciprocity builds accountability. At Amazon, feedback is a two-way performance requirement, not a culture slogan.

BAD: Delaying a decision on a staffing conflict because “I want the team to work it out.”

GOOD: Gathering data, consulting your manager, then making the call—even if unpopular.

Why: Leaders are paid to decide. Amazon’s Leadership Principle “Have Backbone; Disagree and Commit” applies to managers too. Indecision in week one compounds.

BAD: Hosting a team lunch in week one to “keep things normal.”

GOOD: Holding a focused 60-minute meeting to reset expectations, then socializing later.

Why: Rituals without purpose accelerate role confusion. Clarity before camaraderie. Your job is no longer to blend in—it’s to elevate output.

FAQ

You must reset peer relationships immediately because Amazon measures managerial impact from day one. Waiting to “let things settle” is read as avoidance. The Leadership Principle “Ownership” means you act like it’s your problem, not someone else’s. Former peers will test boundaries within 10 days—preempt with structured expectations.

You should not redistribute responsibilities in week one because you lack context. Any reorg before 30 days is seen as power signaling, not strategy. Amazon values deliberate change, not disruption for its own sake. Use the first month to observe patterns, then act.

You earn trust by being predictably rigorous, not personally warm. Amazon teams respect managers who protect customer outcomes over team comfort. Share context proactively, give feedback fast, and escalate only when blocked. Trust is built through consistent execution, not likability.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.