Quick Answer

Most new managers at Amazon fail their first 90 days not from lack of skill, but from misaligned priorities. The real work isn’t building plans — it’s diagnosing cultural and operational debt. Your first 30 days must be a structured intelligence-gathering mission, not a sprint to deliver results.

Template: First 30 Days as a New Manager at Amazon – Daily Action Plan

TL;DR

Not sure what to bring up in your next 1:1? The 0→1 PM Interview Playbook (2026 Edition) has 30+ high-signal questions organized by goal.

Who This Is For

This plan is for external hires and internal promotions stepping into a people management role at Amazon for the first time — especially those transitioning from individual contributor roles in tech, product, or operations. If you’re walking into a team with existing headcount, P&L exposure, and a 14-week business cycle, this is your protocol.

What should I do on day one as a new manager at Amazon?

Your first day is not about introducing your vision. It’s about starting your listening tour with deliberate structure. Arrive early, review your manager’s 30/60/90-day memo, and confirm your access to AWS, Slack, and internal wikis. By 10:00 a.m., send a team-wide intro email — brief, humble, and focused on learning.

The problem isn't your message — it’s your timing. Sending a “here’s how we’re going to win” email on day one signals disregard for context. Not inspiration, but arrogance.

In a Q3 debrief last year, a hiring committee rejected a candidate for leadership escalation because their onboarding story began with “I presented my 90-day transformation plan on day two.” The feedback: “They didn’t earn the right to change anything.”

Your real goal on day one: schedule 1:1s with every direct report within the first five days. Block two hours daily for documentation. Use Day 1 to read the team’s last three Quarterly Business Reviews (QBRs) and the most recent bar-raiser feedback on hiring.

Judgment signal: You’re not here to fix. You’re here to understand.

How should I structure my first two weeks as a new Amazon manager?

Weeks 1–2 must be 80% intake, 20% alignment. Conduct 1:1s with each report, but don’t just ask “How are you?” Ask: “What’s one thing we should stop doing? One thing to start? And what’s a metric the team is pressured to hit but doesn’t move the needle?”

Not engagement, but exposure. You’re not measuring morale — you’re mapping political and operational risk.

In a hiring committee discussion last year, a manager was flagged for “context blindness” because they launched a reorg in week three based on “what worked at Google.” The team had legacy reporting lines tied to compliance systems; the reorg triggered an audit. The HC noted: “They didn’t read the org’s immune system before injecting change.”

Pair each 1:1 with a follow-up: shadow a stand-up, sit in on a PR/FAQ review, or attend a delivery war room. Take notes in Confluence, tag them “DayOneObservations,” and share the link with your skip-level.

By day 10, draft a “Context Document” — no longer than four pages — summarizing team goals, known bottlenecks, and stakeholder dependencies. Share it with your manager and ask: “What did I get wrong?”

This isn’t about accuracy. It’s about signaling you’re synthesizing.

What should I focus on in weeks 3 and 4?

Weeks 3–4 shift from intake to hypothesis testing. You now have enough data to identify one leverage point — not a fix, but a testable assumption. Is velocity slow because of tooling? Approval chains? Hiring gaps?

Not execution, but diagnosis. Your job isn’t to solve — it’s to isolate variables.

In a debrief for a L6 TPM hire, the committee praised her week-three move: she didn’t push for faster CI/CD deployments. Instead, she mapped every approval required for a production push and found that 70% of delays came from a single compliance checkpoint owned by a sister team. She scheduled a joint session — not to demand change, but to ask: “What risk are you trying to prevent?”

That question passed the bar. It showed systems thinking.

Use day 18 to schedule your first team meeting — not to announce changes, but to present your Context Document and ask for corrections. Frame it: “Here’s how I see the world. Where am I off-base?”

Invite your manager and skip-level. This is your first leadership moment: demonstrating intellectual humility under visibility.

By day 25, identify one small win — something that takes less than two weeks to resolve and has visible impact. It could be automating a weekly report, unblocking a long-pending tool request, or clearing technical debt flagged in code reviews.

Not scale, but signal. The win isn’t the outcome — it’s showing you listen and act.

> 📖 Related: Amazon PM Vs Comparison

How do I build credibility with my team in the first 30 days?

Credibility at Amazon isn’t earned through charisma or vision — it’s earned through follow-through and judgment. You build it not by doing big things, but by doing small things reliably.

Not presence, but precision.

In a recent HC discussion, a candidate was dinged for “over-indexing on visibility.” They hosted weekly all-hands, sent motivational emails, and set up “idea boxes.” But they missed two 1:1s and failed to escalate a critical path blocker for three weeks. The feedback: “They confused activity with leadership.”

Your credibility comes from three behaviors:

Consistency in 1:1s — never cancel, always take notes, and close the loop on action items within 48 hours.
Relentless escalation — if you bump into a roadblock outside your span, write the email to your manager and cc the stakeholder. Do it fast.
Bias for action — make a call even if it’s reversible. Amazon rewards motion, not perfection.

One L5 manager last year gained immediate trust by resolving a six-month-long access request for a junior engineer. The fix took one email to SRE. The signal: “My manager gets stuff done.”

That’s the bar. Not strategy. Not vision. Unblock the unblockable.

How do I align with my manager and skip-level in month one?

Your manager doesn’t need updates — they need confidence you’re navigating complexity. Your skip-level doesn’t need visibility — they need assurance you’re not creating risk.

Not reporting, but calibration.

In a Q2 HC, a candidate was rejected because their skip-level said, “I didn’t know they existed until week five.” The manager hadn’t initiated contact, hadn’t read past QBRs, and hadn’t asked for context. The HC ruling: “They treated onboarding as a solo mission.”

Start with your manager: schedule a weekly 30-minute sync from day one. Agenda: here’s what I learned, here’s what I’m prioritizing, here’s what I need from you.

By day seven, request a 15-minute intro with your skip-level. Bring one insight — not a problem, not a proposal — just an observation. Example: “I noticed our team spends 20 hours a week on ad-hoc reporting for finance. Is that time allocation expected?”

That question does three things: shows observation, tests priority alignment, and invites guidance.

By day 21, draft a 30/60/90-day plan — but don’t present it as final. Frame it as “working hypotheses” and ask: “What should I deprioritize?”

This isn’t about approval. It’s about exposing your mental model.

Preparation Checklist

Schedule 1:1s with all direct reports by Day 5
Read last three QBRs, PR/FAQs, and team goals by Day 3
Set up Confluence page for daily notes and share with manager by Day 2
Shadow at least three key team rituals (stand-ups, reviews, war rooms) by Day 10
Draft and socialize Context Document by Day 14
Identify and close one small operational win by Day 25
Work through a structured preparation system (the PM Interview Playbook covers Amazon’s 14 leadership principles with real debrief examples from actual hiring committee discussions)

Mistakes to Avoid

BAD: Launching a reorg or process change in week two because “that’s what we did at Meta.”

GOOD: Mapping decision rights and escalation paths first, then testing one assumption with a pilot.

BAD: Sending a “vision memo” on day three outlining transformation goals.

GOOD: Sharing a “Here’s what I think I understand” doc by day ten and inviting corrections.

BAD: Skipping 1:1s to “focus on deliverables” in week one.

GOOD: Treating 1:1s as intelligence collection — taking notes, tracking action items, closing loops.

FAQ

What if my team is underperforming in the first 30 days?

Your job isn’t to fix performance in month one — it’s to diagnose root causes. Jumping to PIPs or reorgs without context fails HC reviews. Instead, document patterns, align with your manager, and escalate blockers. Leadership expects judgment, not speed.

Should I set goals for my team in the first 30 days?

No. Amazon teams run on existing OKRs and business cycles. Your role is to adopt, not reset. Setting new goals signals you don’t trust prior work. Wait until day 45 to propose adjustments — and only after socializing data.

How much time should I spend with my manager weekly?

Minimum 30 minutes one-on-one, plus async updates. More importantly, escalate early. Managers expect new leads to surface risks, not sit on them. If you haven’t sent a “FYI, this could become a blocker” email by day 10, you’re under-communicating.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.