Surfacing Risks Early Builds Trust with Amazon Leader

What makes a good CEO? After Amazon, after Vialto, after CBRE and after three years running my own company, I have stopped believing the popular answers. It isn't shouting at your team. It isn't a twenty-eight step morning routine. It isn't a reality distortion field. I think it is four things. One. Customer obsession. When I joined Amazon, they made me go through every leadership principle until I knew them cold. This one connected immediately. I traced it backward: my grandfather had it, without ever using the word. Dyson has it. Apple has had it for fifty years. The companies that last, last for the same reason. Two. Attention to detail. We rebuilt the IRIS development pipeline four times before it worked. Thirty-five quality gates. Every feature passes through every one. It is exhausting. It is the job. Three. Two-way doors. Most decisions a founder makes are reversible. Make them. Keep moving. Can always switch later if you have to. Four. Ownership. At Vialto I managed nearly forty applications across a team of two hundred. When something broke at 11pm on a Sunday, the buck didn't stop with the analyst on call. It stopped with me. It still does. It always does. The rest is performance.

Amazon mandated 5 days in the office. Within weeks 48% of staff had applied for other jobs. They also discovered they didn’t have enough desks. In 7 cities. They issued a culture mandate without auditing the operating model first. This is not an Amazon problem. This is what happens in every organisation that tries to fix culture without mapping the friction underneath it. You cannot mandate your way to a better team. You have to design your way there. If you’re a leader who knows something is off in your team, the next step is not a new policy. It’s an honest look at where your systems are breaking. Comment AUDIT below and I’ll send you the free 5-point self-assessment. No pitch. 10 minutes. Real clarity. #WorkplaceCulture #FrictionAudit #ReturnToOffice #HRLeaders #NeurocultureLab #LeadershipDevelopment #PeopleAndCulture #amazon

At Amazon, the culture was cut-throat. Here’s how I navigated it. When you put thousands of brilliant, ambitious, highly competitive people into an environment where: ↳ expectations are extremely high ↳ resources are limited ↳ timelines are aggressive ↳ and the reward system is tied almost entirely to delivering massive value… competition becomes inevitable. That’s not inherently good or bad. It’s just reality. Some people thrived in that environment. Some burned out. Some became political. Some became exceptional operators. Over 5.5 years, here’s how I learned to navigate it without losing myself: 1/ I focused on being valuable…not visible for the sake of visibility ↳ Loud people got attention ↳ Valuable people got trusted ↳ I focused on: ↳ solving hard problems ↳ reducing friction ↳ making leaders’ lives easier That compounds over time. 2/ I learned to separate competition from emotion ↳ People challenged ideas aggressively ↳ Pushed hard in meetings ↳ Debated constantly ↳ Early on, I took it personally. ↳ Eventually I realized: ↳ high standards create tension naturally You can’t operate emotionally in that environment. 3/ I made my work impossible to misunderstand ↳ Clear updates ↳ Clear metrics ↳ Clear ownership ↳ If your value requires interpretation, someone else controls the narrative. That’s dangerous in competitive environments. 4/ I avoided playing short-term political games ↳ No gossip ↳ No undermining ↳ No performative escalation ↳ I saw people win short-term that way. ↳ I rarely saw it compound long-term. Reputation matters more than moments. 5/ I focused on becoming undeniable ↳ Calm under pressure ↳ Strong communication ↳ Reliable execution ↳ Looking around corners ↳ When you consistently deliver, politics matter less. Not zero. Less. 6/ I protected my identity outside of work ↳ Because environments like that can consume you if you let them ↳ I reminded myself constantly: ↳ this is what I do ↳ not who I am That mental separation mattered more than I realized. Here’s the truth: Amazon wasn’t easy. But it taught me how to: ↳ operate under pressure ↳ compete without losing integrity ↳ and create value in environments where the bar never stops moving And honestly? I’m grateful for that. 📬 I write weekly about leadership, execution, and operating in high-performance environments in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc Have you ever worked in an environment that fundamentally changed how you operate?

The Quote That Changed My Perspective at Amazon I was early in my Amazon career. Overthinking everything. Playing safe. Trying not to fail. I remember sitting with one of my mentors after a tough week. A project felt stuck. I was hesitating on a decision. And I kept explaining all the reasons something might go wrong. He let me talk for a minute. Then he asked one question: “If you knew you couldn’t fail… what would you do differently?” I still think about that sentence. Because I realized almost immediately: I already knew what to do. I was just scared of being wrong. That question changed how I approached work…and honestly, life. Here’s what shifted for me after that: 1/ I started moving before I felt fully ready ↳ Draft the doc ↳ Pitch the idea ↳ Volunteer for the project ↳ Confidence usually comes after action, not before it. 2/ I stopped treating every decision like a one-way door ↳ Most things are reversible ↳ Testable ↳ Adjustable ↳ Waiting for perfect certainty was slowing me down more than mistakes ever did. 3/ I realized failure wasn’t the real risk ↳ Staying invisible was ↳ Playing small was ↳ Watching opportunities pass because I was overthinking was 4/ I started seeing mistakes differently ↳ Not as proof I wasn’t capable ↳ But as reps ↳ Every strong operator I worked with had failed before. ↳ They just didn’t stop moving. 5/ I became more willing to own things before I had the title ↳ I stopped waiting to “officially” be ready ↳ And started acting like someone who could handle bigger responsibility That changed everything. That one question rewired how I thought about growth. Because most of the time… The thing holding you back isn’t capability. It’s fear disguised as caution. 📬 I write weekly about growth, execution, and operating at a high level in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc What’s one thing you’d do differently right now if you knew you couldn’t fail?

I was reading this post and all the comments on it: https://lnkd.in/gryKDX7j It made me think of two individuals I came to admire while I was working at Amazon. I'll say this with 1000% accuracy: I had almost the same experience with many managers at Amazon. They are amazing individuals. First, my hiring manager. The interview process, as we all know, is grueling. The phone interview, the tech interview, then the panel. Dom, my hiring manager, is a great leader. I wish I had worked with him earlier in my career. During the interview I told him I could do anything. I got through the process, was hired, and I was ecstatic and nervous as hell. We were a new team. The guys hired were great and we melded with the other engineers and worked very well together. We were mentored, guided, and taught the Leadership Principles. Amazon was kicking my ass while I came up to speed. During a 1:1, I told Dom that when I was hired I'd said I could do anything... but I couldn't. He said, "That's why I hired you." I realized then that with his guidance, I really could do anything and more. So thanks, Dom. A few re-orgs later, I had a new manager and a new skip-level. Then another re-org. New director. You know how it goes. Sometimes every 18 months, RE-ORG. That's how I came to work under Scott. Scott's reputation, or at least my interpretation of it, was that he was no-nonsense, strong, didn't micromanage, and was intimidating. He relied on the team to do what needed to be done. Scott was another great manager, and I worked with him for several years through all those changes. I remember one time I had an issue with another team's manager. It came down to him wanting something done against policy. Things got heated. I stood my ground and wasn't backing down, and then the threats started. The second he started with the threats, I copied Scott on the email and chat chain. I spoke to him briefly, and he stepped right up. He explained to the other manager in no uncertain terms: NO. This is how things are done. He stood by me and defended me. Later, the other manager apologized in an email and acknowledged I had a manager who stood up for his team. Without going into more detail, I admired Scott a lot more after that. Honestly, I would do anything for him as a manager. Thanks, Scott. And thanks for helping me remember the good times working at Amazon. Scott McIlravie Dominick Talarico Brett Miller, MBA Thanks for this post, it made me think and brought back great memories.

Absolutely agree with this. Great leadership isn’t about adding to the noise or chaos — it’s about creating clarity, stability, and focus for your team. The best leaders protect their teams from unnecessary distractions, provide clear direction on what matters most, deliver direct and timely feedback, and remain composed under pressure. Calm, consistent leadership builds trust — especially during challenging moments. A strong reminder for all of us leading teams today!!

The Best Manager I Had at Amazon I had 11 managers in 5.5 years at Amazon. Different orgs. Different leadership styles. Different expectations. And the best manager I had? He was my hiring manager. And I only worked for him for about 2 months. That’s it. But those 2 months changed how I thought about leadership forever. Here’s why he stood out: 1/ He made me feel trusted immediately ↳ Not micromanaged ↳ Not “prove yourself for 6 months first” ↳ He gave me ownership early ↳ And treated me like someone capable of handling it That confidence changes how people operate. 2/ He created clarity without overcomplicating things ↳ Every conversation came back to: ↳ “What problem are we solving?” ↳ “What matters most?” ↳ No unnecessary noise ↳ No corporate theater Just focus. 3/ He protected the team from unnecessary chaos ↳ Amazon can become a constant stream of urgency ↳ But he filtered what actually mattered ↳ He knew when to escalate pressure ↳ And when to absorb it That balance is rare. 4/ He gave direct feedback without making it personal ↳ If something wasn’t good enough, he said it ↳ Clearly ↳ Quickly ↳ Respectfully ↳ No guessing games ↳ No passive aggression You always knew where you stood. 5/ He modeled calm under pressure ↳ Deadlines moved ↳ Things broke ↳ Leadership escalated ↳ He never spiraled And that steadiness spread to the team. The funny part? He probably has no idea how much impact he had on me. That’s the thing about great managers. Sometimes it’s not the amount of time. It’s the consistency of how they show up. I’ve forgotten plenty of meetings from Amazon. I haven’t forgotten those 2 months. 📬 I write weekly about leadership, execution, and career growth in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc Who was the best manager you ever had…and what made them different?

Twelve years inside Amazon and your network is deep. Cross-functional leaders, GMs, VPs who've seen your work up close. It's also almost entirely internal. When you start thinking about what's next, the first thing that hits isn't "I don't know what I want." It's "I don't know who to call." This is incredibly common for long-tenure Amazonians. Opportunities came through your skip-level, a restructure, a tap on the shoulder. You didn't need LinkedIn because the next role was already in the building. Now you're looking outside and the muscle hasn't been used in a decade. Here's what I'd reframe: you're not starting from zero. Every person you've worked with who left Amazon in the last five years already has a mental model of what you're capable of. You don't need to "network." You need to remind people you exist. One move this week: pick three former colleagues who left in the last two years. Send a genuine, no-ask message. Just reconnect. The relationships are already there. They're dormant, not dead.

"How is Amazon so innovative"? My colleagues and I have been getting questions like this for many years now. Other than our leadership principles https://lnkd.in/gewZeMV9, I point our customers, partners, students and larger developer community to this book - https://amzn.in/d/00gh5k6g - Working Backwards by Bill Carr and Colin Bryar. It's like an authoritative user manual, if you will. Thanks Sakshi Bholowalia for giving me my copy couple of years ago! It's a permanent fixture in my bag   Most people think Amazon’s success is about luck or being in the right place at the right time. It’s actually about rigorous, repeatable processes. The authors (both long-time Amazon execs) pull back the curtain on the "Amazon Way."   Key lessons:   1. Ban PowerPoint (Seriously): Amazon replaced slides with 6-page narratives. Every meeting starts in silence while everyone reads. Why? Because bullet points can hide weak logic. Narratives force clarity and ensure the best idea wins—not the loudest voice in the room. 2. The "Single-Threaded" Rule: We’ve all seen projects die by "too many cooks." Amazon’s solution? Give one person one goal and a dedicated team. If they have to coordinate with five other departments to get a "yes," the process is broken. Communication is often a sign of dysfunction; autonomy is the goal. 3. Begin with the End in mind (PR/FAQ): Before building a single feature, Amazon teams write a Press Release and a FAQ for the future launch. If the "future" value doesn't sound exciting to the customer today, they don't build it. They work backward from the customer's needs, not forward from a technical capability 4. The "Bar Raiser" Hiring Hack: Hiring managers are often desperate to fill a seat, which leads to "compromise hires." Amazon uses a Bar Raiser—an objective third party who has total veto power. If they don't think the candidate is better than the top 50% of the current team, they’re out. No exceptions. Being a Bar raiser myself, I've seen this first hand play out. 5. Focus on Input Metrics (things you can control, like delivery speed or price) rather than Output Metrics (stock price or revenue). If you nail the inputs, the outputs take care of themselves.   #Leadership #WorkingBackwards #AmazonWay #BusinessStrategy #ProductManagement Navdeep Sandeep Aamir Satinder Neeraj Dale Madhusudhan Vaishali Vaishali Puneet Sandeep Rajeev Nitin Kamlesh Harpreet Harjyot Karthik Rajat Vijay Guru Neha Naveen Preetam