Key Takeaways

  • Jeff Bezos never gave positive praise in reviews. He read the proposal, identified three items to correct, and told teams to get moving.
  • When a team brought flawed work to a meeting, Bezos stopped the room and asked if the A-team was available because this was clearly the B-team.
  • Success warped Bezos's judgment over time, creating an echo chamber that produced the Fire Phone flop.
  • Bezos built his legendary pattern recognition across 10,000 hours of reading proposals for 20 minutes and diagnosing weak assumptions.
  • Executive rage often comes from self-blame: Evans noted Bezos's attack mode was him punishing himself for allowing a mess to develop, while taking the team down with him.

The Room Where Praise Did Not Exist

Ethan Evans spent years inside Amazon's executive ranks watching Jeff Bezos run product reviews. The culture was efficient, brutal, and devoid of applause.

Bezos never opened with a compliment. He never closed with one either. As Evans described it: “Jeff was not mean, but very demanding and never said anything good. He just would come in and be like, 'Okay, I see your idea. Here's the three things to fix. Get moving.'”

If the work fell below his bar, the response was sharp. During one product review, Bezos stopped the presenters mid-pitch. He looked around the table and asked: “Is the A team for this project available, because this is clearly the B team?”

That environment produces fast corrections, but it creates a fragile culture. When managers never validate what works, teams learn to hide their doubts. They stop taking creative bets that might invite executive wrath.

The Trap of Being Right Too Often

Founders who win repeatedly start mistaking their past hits for infallibility. Evans watched this exact dynamic trap Bezos on hardware.

“Jeff fell into the flaw of every great man, which I think is having been right a lot,” Evans said. “He started to believe his vision was perfect and that's what led to the Firephone disaster.”

Amazon poured hundreds of millions into the Fire Phone, packing it with gimmicks like dynamic perspective cameras that customers never requested. Because Bezos believed his instincts trumped market tests, nobody pushed back hard enough to stop it. He had spent 10,000 hours reading six-page memos across logistics, AWS, and retail, which gave him real diagnostic instincts. But reading documents is not the same as testing consumer demand.

When a founder believes their track record protects them from user testing, they end up with expensive inventory nobody wants.

Understanding Attack Mode

When an operation broke or customer trust slipped, Bezos entered what Evans termed attack mode. He became relentless, interrogating teams until people broke down.

Evans spotted the root cause behind the hostility: “What that really was, yes, he was frustrated with the team who screwed up, but he was also frustrated with himself that he let it get that way. But he would just be relentless and it was like beating himself up and you with him.”

Most founders recognize that spiral. You see an operational failure, you realize your own hiring or oversight let it happen, and you direct that self-directed anger outward at the people in the room. It feels like high standards. In reality, it is emotional venting that paralyzes the employees who need to fix the problem.

What to Do With This

Audit your last five team syncs. If you gave zero positive reinforcement and only handed out lists of defects, change the balance tomorrow by stating what parts of the project met the bar before assigning fixes. Next, check your current roadmap: find the one project you approved purely on your own gut, and demand three pieces of disconfirming customer data before funding another week of work.