How to Run 1on1 as First-Time Manager at Amazon AWS: Guide

TL;DR

First-time AWS managers who turn 1:1s into status updates usually get polite silence, not truth. The job is to surface blockers, risk, and decisions early, then close the loop in writing. In the first 90 days, 30-minute weekly 1:1s with a fixed agenda beat improvisation, because trust at Amazon is built on consistency, not charm.

Who This Is For

This is for the new Amazon AWS manager who just inherited a team, has a reputation to establish, and cannot afford to look either absent or controlling. You are probably managing engineers, TPMs, or a mixed delivery team, and you already feel the pressure to sound decisive in every conversation. The wrong move is to overperform authority; the right move is to create a predictable forum where your people bring hard truths before the org chart does.

What Should a First 1:1 Actually Cover?

A first 1:1 should cover blockers, expectations, and risk, in that order. If you start with rapport and end with logistics, you will get a pleasant meeting and weak management.

In a Q3 debrief at AWS, the manager who opened every 1:1 with “How are things?” had nothing useful to defend when the team suddenly slipped. The manager who asked, “What is blocked, what is unclear, and what are you not saying in the group meeting?” already knew the answer before the calendar review. That is the point. Not a status meeting, but a signal extraction meeting. Not a friendship ritual, but a management control point.

The useful frame is simple: current work, future risk, and growth. Current work tells you whether the team is moving. Future risk tells you where the org will be surprised. Growth tells you whether the person has a reason to stay. Amazon rewards managers who make those three dimensions visible early, because “Dive Deep” is not a slogan when a launch date is real.

A strong first 1:1 also needs a boundary. Do not spend 20 minutes talking about your own background. Do not turn the meeting into a personal therapy session. Do not treat it like a performance review in disguise. The point is to learn how this person thinks under pressure, what they need from you, and where the team is carrying hidden cost.

Use 30 minutes. Give the employee 10 minutes to set the agenda, 10 minutes for your questions, and 10 minutes to agree on next steps. If the meeting regularly runs longer than that, the problem is usually not too much to discuss. The problem is that the manager has no structure.

> 📖 Related: [](https://sirjohnnymai.com/blog/amazon-vs-apple-pm-role-comparison-2026)

How Do You Build Trust Without Becoming Too Casual?

Trust comes from consistency, not warmth. In Amazon-style organizations, people do not trust the manager who is fun in the room. They trust the manager who remembers last week’s blocker and closes the loop this week.

In one skip-level conversation, a senior engineer described a manager as “easy to talk to” and then immediately admitted he never raised hard issues there. That is not trust. That is social comfort. The manager who earns trust is the one whose reactions are predictable, whose notes are accurate, and whose follow-through is boringly reliable. Not friendly, but dependable. Not open-ended, but steady.

The organizational psychology is straightforward. People disclose risk when they can predict the reaction to bad news. If a direct report believes every admission will become a lecture, they will sanitize the truth. If they believe every problem will be escalated theatrically, they will delay disclosure. The first job of a first-time manager is to reduce that uncertainty.

Send a short recap within 24 hours. Keep it factual. Name the issue, the owner, the date, and the expected outcome. That written trail matters more than the tone of the meeting. At Amazon, memory without documentation is how managers create arguments later.

Trust also breaks when the manager confuses transparency with over-sharing. You do not need to narrate every uncertainty in your own head. You do need to be clear about priorities, tradeoffs, and decision rights. The team does not need your anxiety. It needs your judgment.

How Do You Handle Hard Feedback In 1:1s?

The 1:1 is the right place for hard feedback, but only if the feedback is specific, timely, and tied to behavior. Vague concern is managerial laziness. Clear observation is leadership.

In a promotion packet discussion, the manager who waited until the formal review had nothing usable except a general feeling that “the bar was not quite there.” The manager who addressed the pattern in the 1:1 had the examples, the impact, and the next checkpoint already on paper. That is the difference between surprise and management. Not criticism after the fact, but correction before the verdict.

Use this sequence: observed behavior, business impact, expected change, next review date. If you skip the observed behavior, the feedback sounds personal. If you skip the impact, it sounds abstract. If you skip the next review date, it becomes a speech instead of a management action. The employee should leave knowing exactly what has to look different in the next 2 weeks or 30 days.

Do not soften hard feedback into confusion. Do not say “I just want to make sure you’re aware” when the issue is already visible. Do not wait for a quarterly review to address a pattern that showed up three 1:1s ago. The longer the lag, the less credible you become.

A first-time manager often tries to protect the relationship by being vague. That is the wrong instinct. The relationship is protected by honesty with a clean process, not by pretending the problem is smaller than it is. At Amazon, people respect directness when it is disciplined.

What Should You Ask Senior Direct Reports?

Senior direct reports do not want interrogation. They want judgment and room. If you ask them 14 questions in one meeting, they will conclude you are trying to control the work instead of understand it.

In an org review, a new manager spent the first 1:1 with a senior engineer drilling into every task on the sprint board. The engineer left with one clear impression: the manager wanted compliance, not insight. The better move was simpler. Ask what is stuck, what is changing, and what decision they need from you. Then stop talking long enough to hear the real answer. Not more questions, but better questions. Not proof that you are engaged, but proof that you can discern.

The psychology here is status-sensitive. Senior people read the quality of your questions as a proxy for your competence. A shallow question signals insecurity. A precise question signals that you know where the leverage is. That is why top managers do not try to sound busy in 1:1s. They try to sound exact.

Give senior people autonomy inside clear boundaries. Ask for decision points, not task-by-task narration. If the person is already strong, your role is to remove friction, challenge assumptions, and surface hidden tradeoffs. You are not there to re-run their job.

A useful rule is three questions max for the first half of the meeting. After that, listen. If you keep asking, you are probably compensating for discomfort rather than extracting value. In a strong 1:1, silence is not a failure. It is often where the useful answer appears.

How Do You Keep 1:1s from Turning Into Status Theater?

You keep 1:1s from becoming theater by moving status out of the meeting and decisions into the meeting. If the same information can be read in a written update, it does not belong in the 1:1.

In a weekly ops review, the manager who repeated Jira tickets line by line in every 1:1 wasted the only time that should have been used for judgment. The manager who used the meeting to ask why two priorities were still in conflict got an answer that changed the plan. That is the right use of the room. Not a dashboard recital, but a decision review. Not reporting, but interpretation.

The principle is simple. Meetings should create irreversible value. If the conversation does not change a decision, remove a blocker, or reveal a risk, it belongs elsewhere. Amazon organizations move fast enough that low-value repetition becomes a tax on everyone. First-time managers often keep status in 1:1s because it feels safe. It is not safe. It is waste.

A better mechanism is one written update before the meeting and one decision log after it. The written update captures the facts. The 1:1 handles ambiguity, conflict, and tradeoffs. That split preserves the meeting for what only a manager can do. Decide, unblock, or challenge.

In the first 60 days, keep weekly 30-minute 1:1s. If the relationship is stable and the work is not changing much, some managers can move to every 2 weeks. Do not do that early just because the calendar is crowded. A collapsed cadence is usually a sign that the manager is underusing the meeting, not that the team no longer needs it.

Preparation Checklist

Preparation is what stops a 1:1 from becoming improvised social management. The best managers show up with a structure, a note trail, and a decision they are ready to make.

Set a fixed 30-minute cadence for each direct report for the first 60 days, then only relax it if the conversation is already stable and useful.
Keep one running note with three fields: blockers, decisions, and follow-ups.
Start every 1:1 with the direct report’s agenda, not your status update.
Close every meeting with one owner and one date. If there is no owner and no date, there is no commitment.
Ask for one risk that is not showing up in the team meeting. That is where the real management work lives.
Work through a structured preparation system (the PM Interview Playbook covers judgment signals, conflict handling, and debrief examples that map cleanly to Amazon-style 1:1s).
Review your last two follow-ups before the next meeting. If you missed one, say so directly.

Mistakes to Avoid

The biggest mistakes are predictable, and they come from insecurity, not effort. First-time managers usually do too much talking, too little closing, and too much smoothing.

BAD: “How’s everything going?” GOOD: “What is blocked, what is unclear, and what do you need from me this week?”
BAD: “I just want to be supportive.” GOOD: “Here is the behavior I saw, here is the impact, and here is the change I need by next Friday.”
BAD: “We’ll revisit this later.” GOOD: “You own X by Thursday, I own Y by Tuesday, and we will review both in the next 1:1.”

Another mistake is treating every issue as equal. It is not. A missed update is not the same as a recurring pattern that threatens delivery or promotion readiness. Good managers separate noise from risk. Bad managers make every conversation feel urgent and then wonder why nobody trusts their priorities.

The final mistake is believing a warm tone substitutes for management clarity. It does not. A manager can be kind and still be ineffective. A manager can be direct and still be trusted. In Amazon-style environments, the second combination usually survives. The first usually does not.

FAQ

How long should a first-time manager’s 1:1 be at AWS?

Thirty minutes is the right default for the first 60 days. Fifteen minutes is too short unless the relationship is already mature. Sixty minutes usually means the meeting has no structure.

Should 1:1s be employee-led?

Mostly, yes, but not entirely. Employee-led agendas surface real issues, while manager-owned closing questions prevent drift. If the employee brings nothing for multiple cycles, that is not a quirk. It is a signal.

What if my direct report never brings up problems?

Treat that as a management problem, not a personality trait. The usual causes are low trust, unclear expectations, or a manager who has trained silence. For 2 or 3 cycles, set the agenda yourself and ask for one risk they have not raised elsewhere.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.