1on1 for New Manager at Amazon AWS: Building Team Trust in First 90 Days

Most new managers fail to establish meaningful trust within their first 90 days at Amazon AWS not because they lack good intentions, but because they misunderstand the fundamental purpose of 1on1s in a high-performance, results-driven culture.

TL;DR

New managers at Amazon AWS consistently misinterpret 1on1s as status updates, missing the critical window to build trust and psychological safety. Effective 1on1s in the first 90 days are not about project progress; they are about understanding individual motivations, career aspirations, and unstated team dynamics. Failing to prioritize this foundational relationship work will lead to disengaged teams and eventual performance issues.

Who This Is For

This analysis is for new or recently promoted managers within Amazon Web Services, particularly those transitioning into a team leadership role with direct reports. It targets individuals who grasp Amazon's leadership principles but need to translate that theoretical understanding into practical, trust-building actions during the critical initial 90-day period. This is not for those seeking generic management tips, but for those who require a precise framework for establishing credibility and influence in a demanding technical environment.

What is the primary purpose of 1on1s for a new manager at Amazon AWS in the first 90 days?

The primary purpose of 1on1s for a new AWS manager is not project alignment but the rapid acquisition of context, surfacing unspoken team challenges, and establishing individual psychological safety. This initial period is a strategic investment in human capital, far more critical than any immediate task-level delivery. The "Ask for Help" leadership principle is often misconstrued as a directive; it is an invitation that requires pre-existing trust, and a manager's first 90 days are about creating the conditions for that invitation to be accepted.

I recall a Q3 performance debrief where an L6 manager's review highlighted his team's low engagement scores, despite his consistent delivery on all critical project deadlines.

The core feedback from skip-level reports and peers was a perceived lack of genuine connection, revealing his 1on1s were strictly operational, focused on "What's done?" and "What's next?" This manager was intensely focused on "Deliver Results" but neglected "Earn Trust," viewing 1on1s as an overhead rather than a foundational activity. The problem was not his intent to deliver, but his judgment in prioritizing task completion over relationship building.

It is not about what you need to tell them, but what they need to tell you. The objective is not about solving immediate problems, but understanding the systemic issues and individual frustrations that lie beneath the surface. True effectiveness in this phase is not measured by efficiency with time, but by the depth of rapport and psychological safety established.

How should a new AWS manager structure 1on1s to build trust quickly?

New AWS managers must structure 1on1s with a clear, consistent agenda that prioritizes the report's perspective, dedicating over 70% of the conversation to their insights, concerns, and career trajectory. This deliberate imbalance signals that the manager's priority is the report's well-being and growth, not merely extracting status updates. The "Dive Deep" leadership principle applies as much to understanding people and their motivations as it does to products and technical architectures. Superficial conversations yield superficial insights, which is lethal to trust in a high-stakes, high-pressure environment like AWS.

During an L7 promotion hiring committee review, a candidate's perceived weakness was his inability to scale his influence beyond his immediate direct reports, despite strong technical acumen and individual contribution.

Further investigation into his management style showed his 1on1s were consistently transactional: "What's blocking you?" and "What's the status on X?" He rarely asked, "What frustrates you about our current process?" or "Where do you see yourself in 18 months at AWS?" He failed to build the deeper, more strategic relationships needed for broader organizational influence, because his 1on1s were not structured to uncover those insights.

The focus isn't on your priorities or what you need them to do, but on theirs – their challenges, their aspirations, their perspective on team dynamics. It is not about solving every problem immediately, but about listening intently, asking probing questions, and validating their experience. The goal is not merely project updates, but fostering a connection that supports their personal and professional growth within AWS.

What specific questions should a new manager ask in early AWS 1on1s?

Effective questions for new AWS managers in the first 90 days must be open-ended, non-judgmental, and designed to uncover historical context, current frustrations, and future aspirations, moving beyond surface-level project updates. These questions signal a genuine desire to understand the individual and the environment, fostering an environment where candor is rewarded, not penalized. Amazon's "Are Right, A Lot" principle does not mean managers possess all answers; it means they possess the judgment to ask the right questions and synthesize information from diverse sources.

I observed a new L5 manager in an AWS service team begin his initial 1on1s by asking each report, "What's one thing I should know about working here that no one tells you?" This direct, unconventional approach cut through the typical pleasantries, immediately signaling his intent to understand the unvarnished truth about team culture, legacy systems, and unaddressed technical debt. The responses provided critical, actionable insights that informed his strategy for the next 60 days, demonstrating "Learn and Be Curious" in practice.

The distinction is not "What's your status on Project Y?" but "What's the biggest challenge you're facing on Project Y that isn't on our team's radar right now?" Not "Any blockers?" but "If you could change one thing about our team's workflow or processes, what would it be and why?" Not "What do you need from me?" but "What's something you've struggled with here in the past, and how did you overcome it? What did you learn?" These questions build context, not just track tasks.

How can a new AWS manager demonstrate follow-through and build credibility from early 1on1s?

Demonstrating follow-through in the first 90 days at AWS requires meticulous note-taking, explicit commitments, and transparent communication regarding progress or roadblocks, even when quick resolutions are impossible. This builds credibility and reinforces the psychological safety established during the conversation itself. The "Bias for Action" leadership principle isn't solely about immediate fixes; it's about making visible progress or providing clear, rational reasons for delays. Ignoring issues raised in 1on1s is a fast path to eroding trust and signals a profound lack of "Ownership."

During a hiring committee discussion for a new Director role in an AWS service team, a candidate's successful integration and rapid team respect were attributed to his consistent follow-through. His strategy involved circulating specific action items from 1on1s (e.g., "Investigate X process improvement," "Connect Y with Z team member for cross-functional knowledge sharing") and then providing updates during subsequent 1on1s. Even if the update was "Still researching, will have more next week," this transparency demonstrated "Commitment" and showed he valued their input, reinforcing his credibility.

It is not about promising everything or solving every problem yourself, but about committing to specific, actionable next steps and clearly communicating their status. It is not about saying you'll look into it, but showing that you did and providing an update, whether positive or negative. True follow-through involves driving the solution or connecting the right people, not just acknowledging the problem.

Preparation Checklist

Review each direct report's previous performance reviews, career development plans, and any available 360-degree feedback to understand their history and aspirations.

Research their past projects, technical contributions, and impact areas to understand their domain expertise and influence.

Prepare a list of 5-7 open-ended, non-judgmental questions designed to elicit qualitative insights about team dynamics, process friction, and individual aspirations.

Allocate 60-90 minutes for initial 1on1s with each report, with subsequent regular meetings set for 30-45 minutes. Schedule these at least twice weekly for the first month.

Work through a structured preparation system (the PM Interview Playbook covers stakeholder management and team leadership dynamics with real debrief examples from AWS and Google).

Outline your personal management philosophy and share it with each report in the first 1on1, clearly stating your expectations, how you intend to support them, and your commitment to their growth.

Establish a consistent, private note-taking system that allows for easy retrieval of commitments, discussion points, and observed themes for future reference and follow-up.

Mistakes to Avoid

Treating 1on1s as Status Updates:

BAD: "So, what's the latest on Project X? Any blockers we need to clear?" (Manager-centric, task-focused, signals a lack of trust in asynchronous updates and misses the opportunity for deeper connection.)
GOOD: "Beyond the daily stand-up, what's one area of Project X that's causing you the most concern or keeping you up at night, and why?" (Report-centric, psychological focus, invites deeper insight into challenges and personal impact.)

Lack of Follow-Through on Commitments:

BAD: "I'll look into that feedback you shared about our deployment process." (Vague, no timeline, often forgotten, eroding trust quickly.)
GOOD: "I've noted your feedback on the deployment process. I'll dedicate 30 minutes this week to investigate the root cause and will follow up with you next Tuesday during our 1on1 on my initial findings and potential next steps." (Specific, time-bound, transparent, demonstrates "Ownership.")

Monopolizing the Conversation:

BAD: A new manager spends 20 of 30 minutes explaining their vision, new initiatives, or giving unsolicited advice on how to improve. (Signals "I talk, you listen," devalues the report's input, and fails to "Dive Deep" into their perspective.)
GOOD: A manager prompts with a thoughtful question, listens actively for 15-20 minutes, asks clarifying questions, and dedicates the last 5-10 minutes to offer support, outline next steps, or share relevant insights. (Signals "I value your perspective," empowers the report, and demonstrates "Learn and Be Curious.")

FAQ

How often should a new AWS manager conduct 1on1s in the first 90 days?

New AWS managers must conduct 1on1s at least weekly for the first 90 days, moving to bi-weekly only after a substantial foundation of trust and understanding is established. Frequency signals investment and priority; anything less than weekly in the initial phase will be perceived as insufficient, impeding rapid trust formation and context acquisition.

What if a direct report is disengaged or reluctant to share during 1on1s?

Disengagement in 1on1s signals a pre-existing lack of psychological safety, not a flaw in the report's character. Your judgment must be to persist with open-ended, non-judgmental questions, demonstrate consistent active listening, and share your own vulnerabilities or challenges to model trust. This process requires patience; trust is earned, not demanded.

Should new AWS managers discuss career development in early 1on1s?

Yes, new AWS managers must discuss career development early and often, ideally in the first 3-4 meetings. Neglecting this signals a transactional approach, not a partnership. Understanding aspirations like promotion to L6 or L7, desired skill acquisition, or interest in specific projects provides crucial context for motivation and alignment, demonstrating genuine investment in their long-term success.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Visit sirjohnnymai.com → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.