Ethan Evans on the Magic Loop, Career Growth, and Lessons from Amazon
Ethan Evans — Lenny’s Podcast · ~2023 · Source
Ethan Evans, former Amazon VP (15 years; Prime Video, Appstore, Prime Gaming, Twitch Commerce, 800-person org) and executive coach, shares his framework for career advancement — the Magic Loop — alongside a detailed failure story involving Jeff Bezos, a method for systematic invention, and insights on the SM→Director transition. The episode is a sequel to an earlier Lenny appearance; the Magic Loop newsletter post became the 6th most popular in Lenny’s 300+ post history.
Key ideas
-
The Magic Loop. Five-step reciprocal career-growth framework. (1) Do your current job well. (2) Ask your manager “How can I help?” — rare enough that it immediately sets you apart. (3) Do whatever they ask, even if unglamorous. (4) Return and ask: “I’d love to keep helping you — is there something you need that would also help me reach [your stated goal]?” (5) Repeat. Works because managers help those who help them; management is lonely and most manager–employee relationships are unnecessarily oppositional. Advanced mode: as trust compounds, move from asking to suggesting to just doing and keeping the leader in the loop.
-
The SM→Director choke point. Senior managers get stuck because functional excellence — the skill that got them there — stops compounding. Directors are hired for influence, coordination, and strategic framing, not execution depth. Structural reality: a director may have 6–8 direct reports; far fewer director slots exist than senior manager slots. The action: begin demonstrating next-level skills now, form a partnership with your leader on a strategic project, and make yourself the obvious choice when the slot opens. Reference: Marshall Goldsmith’s What Got You Here Won’t Get You There.
-
Systematic invention. Evans holds 70+ patents accumulated over 15 years at Amazon — not via inspiration but via method. Three requirements: (1) domain expertise (without it, combination is random); (2) scheduled thinking time — just two hours once a month, away from devices, with a specific problem; (3) combine two existing ideas from different domains. His drone + aircraft carrier → mobile truck drone hub is a worked example. The key insight: you need very few good ideas if you spend years executing them. Prime is still being built 20+ years on.
-
Recovering from public failure (the Bezos story). App store launch (2012): test drive feature had a database failure at 6AM, Jeff Bezos’s launch letter was already live emphasising the feature. Evans’s recovery protocol: (a) own it immediately and unconditionally; (b) provide structured hourly updates to buy incremental trust; (c) accept lateral help (AWS engineers fixed the design); (d) move towards the person — Evans deliberately sat next to Bezos at the next in-person meeting, which allowed the relationship to reset. Jeff Wilke’s coda: Evans was spared not because the failure was minor, but because he had known he was gambling when he chose to hit the date. Two years later he was promoted to VP. Key regret: he failed to reassure the junior engineer whose code contained the bug, who subsequently left Amazon.
-
Amazon leadership principles — ownership. Evans contributed the phrase “An owner never says that’s not my job” to the official LP text — proposed in a director-level meeting with Jeff Wilke after a draft revision had accidentally dropped ownership from the consolidated list. Evans estimates these seven words are the most widely-read thing he has ever written, given Amazon’s 1.5 million employee base. Favourite LP: bias for action — speed matters in business; many decisions are reversible.
Related
- Ethan Evans — speaker page
- The Magic Loop — concept page derived from this episode
- notes/Ethan Evans on the Magic Loop, Career Growth, and Lessons from Amazon — deep-ingest notes (Adler frame, glossary, mechanics)
- Alisa Cohn on Executive Coaching, Inner Critic, and From Startup to Unicorn — parallel theme: executive coaching and leader development
- Claire Hughes Johnson on Scaling People, the Company Operating System, and Explicit vs. Implicit — parallel theme: scaling yourself and direct reports explicitly