掌控你的职业发展 | Ethan Evans(Amazon)
Taking control of your career | Ethan Evans (Amazon)
Ethan Evans: People think invention takes all this time, but you only need two hours once a month. The thing is, once you have one good idea, it often takes years to express that.
So you had the idea to have a newsletter. I know some of the history of your newsletter. You’ve been working on the expression of that idea for years now. Jeff and Amazon had ideas like, “Let’s have Prime shipping.” Prime is still getting better and still being worked on. It’s a 20 some year old idea. The Kindle, a decades old idea now still getting better. The point here is you don’t need very many good ideas to be seen as tremendously inventive.
The Magic Loop
Lenny: Today my guest is Ethan Evans. Ethan is a former vice president at Amazon, executive coach, and course creator focused on helping leaders grow into executives. Ethan spent 15 years at Amazon, helped invent and run Prime Video, the Amazon Appstore, Prime Gaming, and Twitch Commerce, which alone is a billion-dollar business for Amazon. He led global teams of over 800, helped draft one of Amazon’s 14 core leadership principles, holds over 70 patents, and currently spends his time executive coaching and running courses to help people advance in their career, build leadership skills, and succeed in senior roles.
In our conversation, Ethan shares an amazing story of when he failed on an important project for Jeff Bezos and what he learned from that experience. We spent some time on something called The Magic Loop, which is a very simple idea that I guarantee will help you get promoted and advance in your career. We also get into a bunch of other career advice, primarily for senior ICs, any managers. We get into advice for standing out in interviews, plus some of Amazon’s most important and impactful leadership principles and much more. I learned a lot from Ethan and I’m excited to bring you this episode. With that, I bring you Ethan Evans after a short word from our sponsors.
Let me tell you about our product called Sidebar. The best way to level up your career is to surround yourself with extraordinary peers. This gives you more than a leg up. It gives you a leap forward. This worked really well for me in my career and this is the Sidebar ethos. When you have a trusted group of peers, you can discuss challenges you’re having, get career advice, and just gut check how you’re thinking about your work, your career, and your life. This was a big trajectory changer for me, but it’s hard to build this trusted group of peers.
Sidebar is a private, highly vetted leadership program, where senior leaders are matched with peer groups to lean on for unbiased opinions, diverse perspectives, and raw feedback. Guided by world-class programming and facilitation, Sidebar enables you to get focused tactical feedback at every step of your career journey.
If you’re a listener of this podcast, you’re already committed to growth. Sidebar is the missing piece that catalyze your career. 93% of members a sidebar helped them achieve a significant positive change in their career. Why spend a decade finding your people when you can meet them at Sidebar today? Join thousands of top senior leaders who have taken the first step to career growth from companies like Microsoft, Amazon, and Meta, by visiting sidebar.com/lenny. That’s sidebar.com/lenny.
Let me tell you about a product called Sprig. Next gen Product teams like Figma and Notion rely on Sprig to build products that people love. Sprig is an AI powered platform that enables you to collect relevant product experience insights from the right users so you can make product decisions quickly and confidently.
Here’s how it works. It all starts with Sprig’s precise targeting, which allows you to trigger in-app studies based on users’ characteristics and actions taken in product. Then Sprig’s AI is layered on top of all studies to instantly surface your product’s biggest learnings. Sprig’s surveys enables you to target specific users to get relevant and timely feedback. Sprig replays enables you to capture targeted session clips to see your product experience firsthand.
Sprig’s AI is a game changer for product teams. They’re the only platform with product level AI, meaning it analyzes data across all of your studies to centralize the most important product opportunities, trends, and correlations in one real-time feed. Visit sprig.com/lenny to learn more and get 10% off. That’s sprig.com/lenny.
Ethan, thank you so much for being here and welcome to the podcast.
Step 4: Making the Magic Happen
Ethan Evans: Lenny, thank you a ton for having me. I’m super excited to talk about some of the things we have teed up today and to help people.
Step 5: Repeat the Loop
Lenny: The first thing I thought we could chat about is The Magic Loop. So you wrote this guest post from my newsletter sometime earlier this year. It is, I don’t know if you know this, but it’s currently the sixth most popular post of all time on my newsletter across 300 plus posts. Did you expect this advice to resonate the way that it did, and why do you think it resonated as much as it did?
Ethan Evans: So the competitive part of me really wants to analyze spots one to five and figure out, do they have an unfair advantage that they had more time? But I was very hopeful that the advice would resonate that way, because I put a lot of work into simplifying it and making it really easy to understand and follow. So I’m very pleased it has, but I was hopeful it would do so well.
Why This Matters
Lenny: Well, I will say sometimes they keep growing, so this isn’t necessarily the terminal point for the post.
Ethan Evans: The final position. Yeah.
Real-World Examples
Lenny: Okay. So for people that haven’t read this post, or maybe for folks that have and maybe could use a refresher, let’s spend a little time here. Could you just briefly describe this idea of The Magic Loop that you wrote about?
Ethan Evans: Yeah, absolutely. So The Magic Loop is how to grow your career in almost any circumstance, even with a somewhat difficult manager. It does assume that you’re working in some environment, normally as an entrepreneur or with a boss. But the basic idea of The Magic Loop is five steps and they’re very easy.
The first one is you have to be doing your current job well. It’s not possible to really grow your career if you’re not considered at least performing at a solid level. Now, it doesn’t mean you have to be the star on the team at this point, but what you can’t have is your boss wishing that you were different. Like, “Ethan’s not very good.” So you have to talk to your manager and find out how you’re doing and address any problems. So step one is do your job well.
Then step two is ask your boss how you can help. Speaking as a manager, and I’ve talked to hundreds of managers, very few people go and ask their manager, “What can I do to help you? What do you need?” And so just asking sets you apart, and it begins to build a relationship that we’re on the same team, that I’m here as a part of your organization to make you successful, not just myself.
Step three is whatever they say, do it. So you dig a big hole. If you say, “What could I do to help you?” And they say, “Well, we really need someone to take out the tray sheets day,” and you’re like, “Oh, I didn’t mean that. I wanted exciting work. I don’t want to do sort of this maintenance work or whatever.” So do what they ask, help out even if it’s not your favorite work.
Once you’ve done that though, and maybe you do that a couple times, the fourth step is where the magic comes in. You go back to your manager and say, “Hey, I’m really enjoying working with you. I’m wondering is there some way I could help you that would also help me reach my goal?” And whether that goal is to change roles or get a raise or get a promotion, you say, “My goal is I’d really like to learn this new skill. Is there something you need that would also help me learn this new skill?” And the reason this works is managers help those who help them. It’s just human nature. We all do that.
Generally, they’re very open to meeting you halfway and saying, “Sure, I need this. We can rearrange it. We can find a way to meet your goals over time.” Now for step four to work, you do have to know what is your goal, so you have to be clear on what it is you want. Well, that part’s up to you.
And then step five is the easiest step of all. It’s just repeat. So like lather, rinse, repeat with your shampoo. Step five is once you’re working with your manager towards your goal and discussing where you’re going, and you’re helping each other, the magic of the loop is just go around and around.
Why the Magic Loop Works
Lenny: I was going to ask you, why is it that you call it The Magic Loop? Also, we kind of dived right in, but what is the goal of this? I guess it’s pretty clear maybe at this point of this helps you advance in your career, but whatever you want to share along those lines.
Ethan Evans: Yeah, okay. Very fair. So I called it The Magic Loop because I pioneered it with my audience a few years ago. And it works so well, that people were writing back in and saying, “How do I turn this off? I’m in over my head now. My boss has asked me to do all these cool things, and I feel like I can’t catch up, and I’ve already been promoted once and I need time to digest it.” And it just seemed like it worked like magic. It worked in almost every circumstance.
There are of course exceptions where you have very exploitative managers who are like, “Oh, it’s great. You’re working harder, keep doing that, and they won’t do anything for you.” But those are rare. And then the purpose, yeah, to help you get satisfaction in your career. A lot of people are unhappy with their jobs. Many people want to move up a level or get paid more. Not everyone. Some people want to change what they’re doing, they’re bored. This is a path to all of that, because it’s forming a partnership with your leadership to say, “Look, I’ll help you, but I need you also to help me.” And most good managers are very open to that.
Recapping the Magic Loop
Lenny: When we were working on this, one of the pieces of feedback I had was I feel like I could just tell my manager, “Hey, I want to grow my career. What can we work on to help me get there?” And your feedback was like, most managers are not that good and not that thoughtful about their employee’s careers. Can you just talk a little bit about that? People may be hearing this and be like, “Why do I need to do this? This seems like a lot of work.”
Ethan Evans: If you have a great manager, you may not need to do nearly as much formality. They may have given you good feedback, so you don’t need to ask for feedback. They may have offered you opportunities to step up, and you’ve said yes to some and maybe no to others. That’s fantastic. I designed The Magic Loop for the people who either don’t know what to do or their manager is either not that good or just very busy.
Remember, lots of managers have great intentions to help their employees, but they get busy with their own lives, their own work, all the things they’re focused on, even also their own career. The manager is often busy thinking about their own needs, and so they mean to get to you next week, and next week drifts on for a year.
A Crucial Overlooked Element
Lenny: What has come up since this has come out that you would want to either add to, or tweak, or help people better understand? I imagine there’s some criticism. I imagine there’s a lot of, “Yes, yes, yes. This really works.”
Ethan Evans: Two things I’d love to clarify. The first is many people ask me, “Why do I have to do this? Shouldn’t my manager notice what I’m doing? Shouldn’t my manager help with my career? Shouldn’t my manager be planning for me?” And what I say about that is what your manager should do and $4 will get you a cup of coffee at Starbucks.
The point of this loop is it’s in your control. It is true that a good manager would do all those things I just mentioned, but not all managers are good and some of them need some help. And the thing I would just say about The Magic Loop is it’s in your control.
And so you can be upset that your manager isn’t perfect, but move on from that and take control of your own situation. That’s the first thing I’d say. The other big extension I would make is look, if you are a manager or a leader of any type, you can initiate The Magic Loop from your side, so you can talk to your employees and say, “Hey, what are your career goals? Would you like to form a partnership where you step up to new challenges and I help you get to your goals?”
I had a lot of success forming this kind of partnership with my employees, where as they saw growth and success, they really leaned in and like, “This system works. You’re actually investing in me now. I’ll work extra hard.” And I’m like, “Yes, and we can grow your team or grow your opportunity,” and it was very win-win.
What If You Don’t Want Promotion
Lenny: To give people a little bit of social proof, you mentioned some of the folks you’ve worked with on this. Can you share some stories, or stats, or anything to help people understand how helpful this ended up being to folks you’ve worked with?
Scope of the Magic Loop
Ethan Evans: Yeah, absolutely. I’ll tell one story from each end of the spectrum. And what I mean there is entry-level people and then high level executive leaders. I had an entry-level person write me back and say, “Look, when I learned about The Magic Loop, I was at a company and not doing very well. I started applying it. They offered me a $30,000 raise and a bigger job. And I turned it down because I got hired at this other company that was offering me even more, and I went there. And they’ve promoted me also,” and he was one of the people who wrote in and said, his exact words were, “A year ago I was made redundant.” So he is in the UK, redundant is their word for laid off. “A year ago I was made redundant. I got this first job and I got an offer for an increased salary, and then I got the second job and I got an increase when I joined that was even bigger.” And he was in that situation of, “Mow I need to sort of slow down and digest all of that.”
On the complete other end, one of my best people I ever worked with joined my team at Amazon as what we would call an SDE II, which in Amazon is a level five employee. He grew with me kind of following this process to a senior engineer. Then he switched to management and ran a small team. Then he became a senior manager and he relocated with my organization. He opened a new office in another city, was eventually promoted to director running his own office of a couple hundred people. And this was over the course of about eight years. He went from a mid-level engineer to an executive with a team of 800 people. Now he was a very hard worker, but over this eight years we just saw all this progress.
And then eventually he moved on. He founded his own startup, sold that, and now works as an executive vice president at one of the major online banks. And so his career in some sense has exceeded mine, but during that eight year span, he just grew so much. And this is the process we followed.
Promotion Challenges for Senior Leaders
Lenny: Wow, those are excellent examples. What levels does this help you with? At what level is this most useful, and then does it kind of taper out it? I don’t know if you get to VP level, do you still try using Magic Loop?
Shifting from Doer to Influencer
Ethan Evans: So I think it works anywhere from the start of your career to pretty far into it. I think at my level, I finished my career as a vice president at Amazon. It does peter out in the sense of the active. And what I mean by that is you’re still doing the same thing, but you don’t have to talk about it. Your managers are expecting you to step up and recognize challenges. They’re expecting you to ask for resources when you need them, and you don’t sort of have this level of explicit conversation around, what can I help you with? They’re expecting you to anticipate what’s needed.
So in the newsletter we did together, I wrote about how over time, you go from asking your manager, “How can I help?” To suggesting to your manager, “These are some things I see that seem like they need to be done. Would you like me to do them?” To just seeing what needs to be done and sort of keeping your leader in the loop and saying, “Hey, I noticed that we have this problem. I fixed it. I noticed we have this opportunity. I’ve started program against it.” I think at the executive level, it’s much more you being proactive and just keeping your leader in the loop.
Lenny: I think in the post, the way you described this step is this is advanced mode. Don’t jump straight to this. Don’t just start suggesting things, because you may get it wrong.
How to Get Selected
Ethan Evans: Yeah, well, it’s all a matter of rapport and trust. A huge part of career success is how much trust you have, mutual respect with your leadership. When they’re confident that you’re going to make the right decisions, they’re confident to let you go. But yeah, when you’re brand new or you’re new to a manager, if you just jump in, you may either not work on the things they value or even find yourself working across purposes, and that isn’t the right place to start.
Lenny: Awesome. Okay. Just to close out this conversation. You touched on this, but why is it that you think this is so important and effective? Why do you think this works so well? People may not recognize, “I see this is the key to this.”
Inventing and Creating Systematically
Ethan Evans: Well, I think it’s two things. First, I mentioned how rare it is for managers to be offered help. If you’re a manager, you’ll recognize this. If not, feel free to talk to any manager, whether your own or somebody else. Ask them how much they worry and how much they feel overwhelmed and wish someone would give them a hand. Management can be a lonely job, because you feel like you’re responsible for everything. So having an ally, it’s just a huge weight off people’s shoulders.
And then I think a lot about social engineering. The social engineering’s here is just the simple, “You help me, I’ll help you.” It doesn’t have to be exploitative, it’s just we help those people who help us, and that’s built into human survival.
And I think this loop works so well because it’s just leaning a little bit into that behavior. So many relationships with managers are oppositional. You tell me what to do, and I’m kind of like a kid in high school who’s trying to figure out how do I skip as many classes as possible and turn in as little homework and still get by with a D? That relationship won’t build your career.
Some people approach their jobs as my goal is to do the least I can and still collect my paycheck. That’s an approach if you’re okay with where you are. It’s not what I coach though. I assume people want to grow.
Optimizing After Invention
Lenny: Okay, so maybe it’s just as a closing question, for people that are listening and want to start putting this into practice slash are stuck in their career and are just like, “Okay, I see. Here’s something I can do.” Could you just again summarize the loop briefly?
Ethan Evans: Sure. Step one, make sure you’re doing your current job well. The way I explain this is when you go to your manager and ask, “What could I do to help?” You don’t want their answer, even if they don’t say it quite so bluntly to be, “Do your F-ing job.” You need to be doing that already. So be doing a good job.
And unfortunately, a good job is in the eyes of your manager in this case. You may think I’m doing great work, but if your manager doesn’t, they’re the ones you need to build as an ally here.
Once you have that, go ask how you can help, do whatever you’re asked, and then go back to your manager and suggest or ask, “I would like to meet this goal. Can I keep helping you? What could I take on that you need that would also help me meet this goal?” And that’s where you start to try to bring your two sets of aims together. What do you need done, how can I get to my goal? And let’s do those things together.
And then you just repeat this loop. You build trust, you build the relationship. And with all good managers, and even a lot of moderate managers, they appreciate the help so much, they really lean into that.
Winning Strategies for Interviews
Lenny: I think there’s two really important elements of this that you haven’t even mentioned necessarily, that I think are part of the reason this works so well. One is this forces you and your manager to identify the gaps that are keeping you from the next level, which it’s often vague, and then you get to a performance review, and then your manager’s like, “Ethan, you’re still not good on this and this and that,” and you’re like, “You never told me that that’s the things you’re looking for for me to get promoted.” So I think there’s this implicit, here’s what you need to work on to get to the next level, which I think is part of step four.
And then you actually did touch on this that it’s important to share your goal to your manager. Here’s what I want. I want to get promoted. A lot of times they don’t know that and you helping them understand, “Here’s what I want, help me get there.” It goes a long way. So there’s a lot-
Leadership Is Influence, Not Workload
Ethan Evans: Managers often fall into the trap. They chose to become managers, so they assume one of two things about you. They either assume that you want to keep doing exactly what you’re doing forever, just maybe make a little more money.
So you’re an artist, you want to keep drawing forever. You’re a lawyer, you want to keep writing contracts forever. Or they assume that, “Hey, I became a manager. I’m very proud of my career. That must be what you want.”
And these assumptions are natural, right? We tend to view by default that our path is great and everyone would want to be us. Now of course, some good managers don’t do that. But if you clarify and express your goals, you remove that ambiguity.
Botching Jeff Bezos’s Product Launch
Lenny: I actually had a period in my career where I specifically did not want to get promoted. I was very happy where I was, and I just wanted to keep doing this awesome IC role. Is that something at all you see where people are just like, “I’m good. I don’t need to get promoted,” and then is this helpful in that in any way or is it not as big a deal?
Fixing the Problem Amid Jeff’s Frustration
Ethan Evans: So first, I reached a point in my career where I was no longer pursuing promotion either, and I wanted to do other things. So I’ve lived that myself and I’ve used the same loop, but I used it to go do what I wanted to say, “This is now what I want, and how do we get there? How do we create a role where I’m adding value appropriate to my level, but I’m doing this other work that’s fun?” I moved into gaming and I really wanted to do that.
Second, I think it is still helpful because there’s something you want probably. Maybe you want to work on different kinds of projects or maybe you want to work with a different higher performance team. Or maybe you want to rebalance your life and say, “Hey, I love what I’m doing, but how can I be a star performer for you but within these boundaries?”
So if you truly have the perfect job just as it is, you may not need The Magic Loop. But I know so few people if you’re like, “Nope, there’s absolutely nothing I could improve about my role.”
Lenny: Yeah, I think that your point about your goal doesn’t have to be promotion. It could be work on a different part of the org, try something totally… Maybe transition to a new function that could be part of your goal. Awesome.
Okay, so along the same lines of career progression, you work with a lot of senior manager types, kind of the level of L7 and one M2-ish, and you share with me that one of the most frustrating parts of their job in that specific portion of their career is they get stuck at that level and they don’t move up, and it becomes really annoying, and they’re not sure how to break out of that. What advice you share with folks like that, that may be listening?
Confronting the Issue Face-to-Face
Ethan Evans: Yeah, so it’s common to get stuck there, and there are a few reasons for it. First, there are a lot of senior managers. If you think of your average director, they may have six to eight reports. How many more directors are needed? So there’s a choke point.
Second, that choke point is worse in the current economy, and in the past maybe a lot of companies, Amazon, Google, apple, etc., were growing very rapidly. And so it wasn’t just you were waiting for some other director to leave. The teams were getting bigger.
I experienced this at Amazon, where over a nine-year period I went from managing six people to 800. And so I went from a senior manager all the way to a vice president, and I described I was, in some sense just riding the elevator. The elevator was going up, and as long as I managed to stay on it, I was going to arrive at vice president.
But the other thing that causes people to get stuck is the difference between a senior manager and a director is how you lead and the work you’re doing. And you can get as far as senior manager by being really strong in your function and being really good at getting things done. As a director, and as a VP beyond that, it becomes much more about influence, coordination with others, and letting go of being in all the details yourself. And so senior managers really have to change some behavior.
I often reference the book by Marshall Goldsmith, What Got You Here Won’t Get You There. Not only because it’s a great book classically on this problem, but because the title tells the story. All the great traits that got you to this one level won’t get you to the next level where you’re more expected to be thinking in strategic terms, thinking longer term.
Getting Promoted Despite Failure
Lenny: So to someone that may be in that role today and they’re not moving up, is there anything they can do? This point about just there’s no roles for you, there’s only so much you can do there, is the advice just wait until an opportunity arrives? Is it run this Magic Loop until something happens? Is there anything you can do?
Ethan Evans: I would be honest with people and say some patience is required. At this level, there is some notion of, do we need a director? Do we need a vice president? Do we have a challenge at that level that needs that person? And so promotions at this level, I often teach have two components. The first component is can I eat and do that job? Am I qualified? Do I have the skills? But the second piece is, do we have such a job that needs that?
However, there is a lot you can do. A lot is in your control. And what is in your control is to start practicing those next level skills. Start working with your leadership on, where can I take on a strategic project? How can I become more of an inventor? I teach some about how to sort of systematically be inventive. It’s not pure magic. Edison said it’s 1% inspiration and 99% perspiration. You can learn the 99%, and the 1% isn’t as hard then. So you start showing those next level traits. And as I describe it most succinctly, how do you make yourself the person who will be chosen out of the eight?
And you can be chosen, there are several ways to move up. Your boss can leave or be let go. They can be promoted to another role. But another way is I coach now, and I have several clients recently. I was just talking to a client yesterday, her two peers were let go. They were all the same level. Her two peers were let go and she was given their teams. And she expressed that her boss had been told, “You have too many senior managers for the size of your organization. We need to do some change in the organization, clean house, and put all your people under the folks who have potential.”
Well, obviously she must be one of those people, because she still has her job and has more people and more to do. And unfortunately, her peers are shopping for new employment. So be that person, and that’s where The Magic Loop comes in. Be that person.
Imposter Syndrome and Fear of Mistakes
Lenny: I was just talking actually to a senior PM leader who pointed out that with this kind of lean environment of a lot of flattening of orgs and a lot of layoffs, that this is becoming increasingly hard. Exactly what you’re describing. There’s just less spots, because companies are running more lean, and so you just kind of have to wait.
I think part of this advice you just shared, which is classic do the job before you have the job makes all the sense in the world. Because once people see that you can do it, obviously they’ll feel a lot more comfortable putting you in that position.
Growing from Reckless to Deliberate
Ethan Evans: And they’ll be looking. I always remind people, as a leader, I want the best people under me I can have. It’s not that I don’t wish to promote you. If you think about my job, this helps people, right? I have selfish motivation to promote you. A lot of people think, “The bosses there holding me down.” Well, maybe some bosses are, but why wouldn’t I want stronger, more capable direct reports? Why wouldn’t I want people under me who can do more of my job? Frankly, that’s the only way I can do less of my job.
Lenny: Plus this pressure you’re always getting from your reports. So like, “Hey, I’m ready to get promoted, because this time”… You mentioned this word inventiveness, and I was just listening to Jeff Bezos on Lex Fridman, and I don’t know if you heard this, but Jeff Bezos described himself most as an inventor more than anything else that he does. Is that something that you think about? Is that influenced by Jeff Bezos any way, that idea of being an inventor as a leader?
Cost of Surprise Launches and Team Care
Ethan Evans: I’ll say a couple things about that. First, I know you talked to my old boss, Bill Carr, who wrote Working Backwards. What I don’t know is if he shared with you that after he published it, he actually realized there was a better title. He wishes that he had called the book The Invention Machine, because what Jeff was trying to do with Amazon was create the most inventive company, the company that would systematically out-invent others. And so while Working Backwards is a great title, Bill and Jeff think they should have called it the Invention Machine.
When I joined Amazon, I did not think of myself as an inventor, but I saw that we had these leadership principles think big and invent and simplify that pushed on that. And I said, “I’m in trouble. I don’t know how to do this.” And I sat down and thought about that. What am I going to do? It seems like that’s required. And I figured out how to become systematically inventive. So I now hold over 70 patents as one benchmark of inventiveness, and they were all created during my 15 years at Amazon.
And the way I did that, inventiveness actually isn’t that hard. I teach about this. And to invent systematically, first you do need to be somewhat of an expert in whatever area you want to invent. So Lenny, if you and I say let’s get together and we’re going to invent cancer drugs, we have the problem that neither of us, as far as I know is a biologist, a doctor. We don’t have the right background, we don’t know what we’re doing. So we would just be fumbling around I guess with a bathtub full of chemicals hoping. It’s probably not going to work out that well. So you have to be something of a knowledgeable expert.
But then the second thing people don’t do is they don’t spend dedicated time actually thinking. They feel like, “Invention is just going to come to me.” When I want to invent, I get away from all my devices. I go in a room with the problem I have, and I force myself to actually concentrate on what do I know and how can I invent? And the most straightforward way to invent is not to somehow come up with something completely new, but instead to put together two things that exist.
And so my example of this, I have a patent I talk about a lot for a drone delivery for Amazon, but the drone doesn’t fly from the warehouse. Instead, a truck with no top drives slowly around the neighborhood, and the drones go back and forth from the truck. As opposed to the driver stopping at every house, you can have four or six drones hitting everything in the neighborhood.
And the way I came up with this idea is one day I was thinking about drones and delivery, but I loved military history. And so I was thinking also about an aircraft carrier and I was thinking, is there a way to have an aircraft carrier for drones? And from that, it was very quick for the light bulb to go on and say, well, what about a truck?
And so I have this patent, and we haven’t seen this become reality yet. I’m waiting for my idea to become part of Amazon’s drone delivery system, but I think ultimately it will.
Amazon Leadership Principles and Drafting Ownership
Lenny: That is badass. I’m imagining returns come back to the truck. We’re using that rope thing that just captures them with that little hook.
Bias for Action
Ethan Evans: Yeah. Well, there’s no reason… Same thing. When you want to return something as opposed to taking it to the UPS Store or whatever, you just put it on your porch, and then on your phone, on your app, maybe you take a picture of it so that the drone can recognize the box or you put it in a designated spot, and you push a button and the drone takes your return away. Yes, there’s no reason.
Lenny: Can’t wait for that. And it takes your dog backs in it sometimes, part of it.
Upward Influence and Refining Principles Word-by-Word
Ethan Evans: My dog’s too heavy, thank you.
The Contrarian Corner
Lenny: My dog’s not. There’s an owl in our backyard that we sometimes worry he is going to come grab our dog on. This idea of invention, this is really interesting. I didn’t plan to talk about this, but for someone like say a PM on a team that wants to get better at invention, innovation, big thinking, is there a practice you find helpful here? Is it block off two hours, get a pen and paper, and just think about the specific two adjacent things working together?
Handshake Business Deals
Ethan Evans: So that’s part of the process, is put in dedicated time. The interesting thing I would say is you don’t need that much time. Two hours is great, but you only need two hours once a month. People think invention takes all this time. The thing is once you have one good idea, it often takes years to express that.
So you had the idea to have a newsletter. I know some of the history of your newsletter. You’ve been working on the expression of that idea for years now. Jeff and Amazon had ideas like, “Let’s have Prime shipping.” Well, Prime is still getting better and still being worked on. It’s a 20 some year old idea. The Kindle a decade’s old idea now still getting better.
So the point here is you don’t need very many good ideas to be seen as tremendously inventive. Like Elon Musk, Tesla, he can kind of dust off his hands and be like, “I am now an Edison-like inventor.” So he keeps doing it, but you don’t need that many inventions.
Lightning Round Q&A
Lenny: This touches on something else Jeff Bezos shared on the podcast that most of his innovation and work is in the optimizing phase. It’s not the here’s the idea, it’s the making it cheaper, and better, and faster. And that’s where most of the good stuff comes from. In this point of Tesla, Elon had this idea, and now the hard work is actually making it scalable and cheap enough for people to use, not just an electric car.
Ethan Evans: With the idea of Jeff saying that invention is really a lot of the incremental and optimization, I completely agree with that. To invent well, you need a base idea, but then there’s so much of the work is making that idea real.
And again, Prime is a great example of this. The Amazon Prime program was a great example of, okay, we want fast free shipping. We want this program. That was a one-time idea that they did build, but now Prime has expanded. First it was two-day in the US, then one-day in the US, now it’s same day in the US. But also they added Prime Video, Prime Music, Prime Gaming. There’s actually something like 25 things you get free with Prime. Most people have no idea, because you get free photo storage and this ongoing list. And all of that is that incremental optimization to make it better, better, better, better. And of course Jeff’s goal, which you probably heard him say, was to make Prime a no-brainer, to where you would be irresponsible really not to be a member.
Favorite Shows, Interview Questions, and Products
Lenny: I know you have an awesome Jeff Bezos story that I want to get to, but before we do that, one more question along this line of career advice and progression. So I read somewhere that you’ve interviewed over 2,500 people over the course of your career. And so kind of going back to the beginning of a career, or at least getting a job, what have you found is most helpful in standing out as a candidate when you’re interviewing, and essentially getting hired? What advice do you have for people that may be going through an interview process right now?
Ethan Evans: There’s a lot of evidence that suggests that the number one and two factors in any interview are appearance and enthusiasm. And it doesn’t mean you have to be beautiful, but show up somewhere looking like you’re interested in the job, not in your pajamas. And most importantly, be enthusiastic. People want to work with people that want to work with them. So if you seem very judgmental of the company and like you have to sell me on it, you’re going to turn them off. I look at every interview of whether or not I really want this job, I might’ve decided I don’t want the job. I still want the offer.
And so I come to any interview I do leaned in and talking about how excited I am to be a part of this opportunity and what I know about the company. Beyond those cosmetics, the biggest thing I see particularly at higher levels is people talk about what they have done but not why it mattered. They don’t talk about the impact.
See, a leader is not hiring someone to just do work. They’re hiring someone because they have a problem or a need. And so if you can show them, “Look, here’s the things I’ve done that have made a difference. Here’s the things I’ve done that have helped my past employers where I’ve had an impact.” So I didn’t just do work. That makes you a worker. Someone who has an impact is more of a leader.
And leader doesn’t need to mean people manager, just a higher level, that I have done something that solve the big problem, and here’s how it changed the company or customer outlook. That’s what I’m looking for in an interview, is are you bringing me an understanding of the business that shows you contributed to the business, or are you just telling me how hard you worked?
Core Life Philosophy
Lenny: Awesome. On that first piece, now that most interviews I imagine over Zoom, in terms of enthusiasm and looking professional, is there anything you’ve found that people may not be thinking about in those two buckets?
Space Dreams and Giving Back
Ethan Evans: Yeah. Show the person full-time dedication. So unless you really don’t have any choice, don’t take an interview from a car, don’t have your camera off. Eye contact is still a real thing. Body language is still a real thing. Gestures like I’m making now with my hands, they’re part of your presentation.
So be fully present and try to project through the camera a little bit of I’m excited to be a part of this and I appreciate the opportunity. I often tell people the best way to prep for an interview might be a good night’s sleep and a pot of coffee, that being fully engaged and energetic is a huge lever.
Closing Thoughts and Contact Info
Lenny: Awesome. And I think basically, the feedback there is don’t over obsess with the content. There’s a lot of value in just how you come across.
Ethan Evans: Yeah, 100%.
Lenny: Let me tell you about a product called Arcade. Arcade is an interactive demo platform that enables teams to create polished on-brand demos in minutes. Telling the story of your product is hard, and customers want you to show them your product, not just talk about it or gate it. That’s why product four teams such as Atlassian, [inaudible 00:39:49], and Retool use Arcade to tell better stories within their homepages, product change logs, emails, and documentation.
But don’t just take my word for it. Quantum Metric, the leading digital analytics platform created an interactive product tour library to drive more prospects. With Arcade, they achieved a 2x higher conversion rate for demos and saw five times more engagement than videos. On top of that, they built the demo 10 times faster than before.
Creating a product demo has never been easier. With browser-based recording, Arcade is the no-code solution for building personalized demos at scale. Arcade offers product customization options, designer approved editing tools, and rich insights about how your viewers engage every step of the way. Ready to tell more engaging product stories that drive results? Head to arcade.software/lenny and get 50% off your first three months. That’s arcade.software/lenny.
Now let’s take a little trip to failure corner. This is something that I do more and more on this podcast, talk about people’s failures in their career and their learnings. And apparently you have a great story of failing the great Jeff Bezos and surviving to tell the tale. Could you share that story?
Ethan Evans: I do. It’s both a highlight and a low light. So I had been at Amazon about six years. I had become a director, and I was responsible for launching Amazon’s app store.
And so we were building an Android-based app store to go on Google phones and eventually on the Kindle tablets. And we got to launch day. And at that time, Jeff used to write a letter introducing new products. He would write a letter that said, “Dear customers, today Amazon’s proud to launch blah blah, blah, and it’s got these great features and I hope you really enjoy it. Thanks Jeff.” And we would take down all the sales stuff on www.amazon.com and that letter would fill the whole screen.
And so he had written a Jeff letter, and this Jeff letter emphasized a particular feature of our product that he really liked. So that something that made it a little different.
And that specific thing was we had a button called test drive that you could click on and it would open the app in a simulator in your web browser, so you could check out the app and interact with it before putting it on your phone. So he thought this was really cool and he was all about it.
Well, my team had built all this technology. We had test drive working. It was kind of a hard piece of technology if you think about simulating any of thousands of arbitrary apps. And we worked all night to launch it, and it wasn’t quite working at 6:00 AM. We were still debugging.
Now you know engineers very well. And I’m sure most of your listeners know about engineers, even if that’s not their discipline. We always think we’re this close to finding the last bug.
So about 6:15 AM, I get a message from Jeff that says, “Hey, I woke up, where’s the letter?” Because it was supposed to go live at 6:00 AM, right after the markets in New York would’ve opened at 9:00 AM Eastern. And he says, “Where’s the letter?” And I write him back and I say, “Well, we’re working on a few problems.” And what I’m thinking in my head is, “Get in the shower, get in the shower. I just need 20 minutes, get in the shower.”
Lenny: For Jeff to get in the shower.
Ethan Evans: Yeah. And 30 seconds later, I have an email back that says, “What problems?” And at this point I have to start explaining, and I end up explaining that we’re having a problem with a database, and we’re debugging this database problem. And he’s like, “Wait, there’s a database in your design? We’re trying to eliminate all Oracle databases and move to AWS. Why do you even have this?” And he is just getting more and more frustrated and angry.
And he starts copying in my boss, and my boss’s boss who’s with Jeff Wilke, the CEO of retail. And they start asking me questions. And it’s just this snowballing, but 7:30 in the morning, Jeff is clearly angry. And there’s this list of other people waking up and feeling like, “Well Jeff is angry, so my job is to be even more angry,” and it’s just raining in on me.
Lenny: Oh man.
Ethan Evans: So what did I do? The interesting thing is what do you do when the future richest man in the world is mad at you? He wasn’t quite richest man in the world yet, but he was headed there.
So the first thing I did was I owned it. I said, “Yes, it’s not working. It’s my fault. I will deal with it.” I took ownership. And the second thing I did was start updating him very proactively and saying, “Here’s where we are.” 8:00 AM, “This is exactly where we are. This is what we’re going to do and the next hour, and this is when you’ll get your next update. I will update you again at 9:00 AM, so here’s our plan.”
And even though Jeff had sort of lost trust in me, like it’s down, and it’s not right, and I’m mad, given that he agreed with the plan, he was willing to give me 60 minutes. And then I would update him again and say, “Okay, this is what we’ve done and this is what we’re going to do, and we’ll update you again at 10:00 AM.” So I was buying life one hour at a time.
Now the other thing I did, and this is a good thing about Amazon, as more and more leaders got copied into this angry thread, they started reaching out in back channel and saying, “We’ve all been under Jeff’s Eye of Sauron, we know it’s miserable. What can we do to help?” And essentially Andy Jassy’s organization, which was AWS at that time, and his CTO, a guy named Werner Vogels said, “You’re having a database problem, let’s get you some principal engineers from the AWS database team.”
And these principal engineers showed up at 9:00 AM roughly, and they looked at our design. We had made some fundamental mistakes in our database usage and they said, “It’s too complicated to fix this. We’re just going to give you 500 AWS machines so that your crappy design will run anyway. That’s the immediate fix.” And I’m like, “Okay, well I guess if you have 500 databases lying around because you’re AWS, it’s a great solution,” and that’s what they did.
So the next step is we fixed the problem. A bunch of us worked together very hard to get the problem all fixed. Now it took all day, and Jeff was still frustrated because the opportunity to sort of control the messaging and the media by having his letter up had passed. People had noticed our launch and the articles had been written, and so Jeff was still very mad.
So we fixed the problem, but Jeff now had no trust in us. The weekend went by. He was using the system looking for bugs because he is like, “This team’s not reliable now. Ethan’s not reliable. I better check it myself.” So you have the CEO checking on you.
And he found a problem and emailed me like Saturday night at 9:00 like, “I was doing this and it broke.” And luckily I was able to tell him exactly what happened by 9:30. Anyway, the next part of the story is that following week, I had a meeting with him on another topic.
So I was part of this small group that was trying to figure out how to build a competing browser. You may not remember, but Amazon had a browser called Silk for a while. And I was invited to this meeting, but I wasn’t a critical participant. So you may know this idea from Scrum where they say some people are pigs and some are chickens, and the chickens are sort of observers. I was a chicken in this meeting, and that turns out to be a great analogy because I was thinking, should I chicken out and not go? I could skip this meeting with the CEO who’s angry at me. But when I had that thought, I realized if I can’t face the CEO, I’d better pack my desk. That’s the end.
So I went to this meeting early, and Jeff always sat in the same chair, so I knew where he would sit when he came in. So I sat down right next to his chair and I thought, “I don’t know, let’s find out.”
And so the meeting goes by, and of course in my mind Jeff is totally ignoring me, not even looking at me. But I think that’s just me projecting, because remember I wasn’t central to the meeting.
So at the end of the meeting, everybody gets up to leave. He turns and looks at me and says, “So how are you doing? I bet it’s been a hard week.” And I thought, “Oh, okay, we’re going to talk.” And I said, “Yeah,” I just sort of answered him with, “Of course it’s been hard, but here’s what we’re doing and here’s what we’re going to do in the future.” And we had a very human conversation. And I didn’t believe Jeff would’ve forgotten that I let him down, but it was clear he had forgiven it.
So I was still going to have to, as it turns out, re-earn his trust. But the thing I did that’s key for people to learn from is it’s really easy to flame. He had been flaming me, writing angry emails. Angry emails are easy. Sitting three feet from someone and being angry with them face-to-face is hard. And when faced with, I can either start ranting at this person who reports to me, or I can say something nice, he chose to say something nice, and that rebuilt our relationship.
So the end of the story is two years later, I was promoted to vice president. So even though I had failed the CEO on this very public launch where he was very definitely mad at me, I re-earned the trust, I showed I had learned the lessons of how to launch more reliably without outages, and I was promoted.
And so I share that story because I think what I want people to understand is if I can get away with publicly failing one of the richest and most famous inventors on earth, and then get promoted and finish my career at Amazon very successfully, you can dig out of any hole. You just have to manage it right.
Lenny: That is an amazing story. So there’s a lot of lessons that I want to pull on here. One is just if you get caught in a situation like this where something completely fails, what I took down as you were talking, one is admit, yes, this is a huge problem, own it. This is like, don’t try to deflect.
Two is the way I describe what you did here, is something I call prioritizing and communicating, where you prioritize, “Here’s what we need to do,” and then communicate. “Here’s our priorities.” And I love that you have this every hour, “Here’s the latest, here’s the latest.” So make people understand you are on it and you’ll continue to keep them updated. I imagine one of the worst fears is I have no idea what’s happening here. I’m going to go in and start micromanaging.
Ethan Evans: You’re exactly right. I’m trying to hold off micromanagement. I’m trying to give them, “Okay, I believe with this and I can wait an hour,” and then I can wait an another hour because that team seems to be on it. So I’m trying to rebuild trust one hour at a time, and avoid having three or four levels of management all come in and start helping.
Lenny: Then I love this other piece of advice of meet them in person, try to take it offline essentially, which I know you did later. But that’s such a good point that it’s hard to be as mad, and angry, and flamey in person. People are just going to be like, “Okay, I get it. Let’s try to figure this out.” Amazing. Is there anything else? Those are the three that I took away. Just like if you’re caught in that situation in the moment, is there anything else that you found to be really helpful?
Ethan Evans: I mean, work hard and fast, right? You do have to fix the problem. My team had been up all night. I had to start sending people home to sleep in shifts. We had to pull in all this help. And so it was a very hard weekend.
When you have a mistake, it’s on you to pull out the stops, even if it’s uncomfortable to recover from it. And again, this is not the time to be like, “Well, it’s the weekend now, and my team, we’ll hit it Monday.” I’d have been out the door so fast, I would’ve had the comic Wile E. Coyote skid marks as I bumped down the street. So I would say that’s important. It’s part of showing ownership.
Lenny: The other part of this is something I went through for a while when I was starting to become a more senior leader is I had a lot of imposter syndrome, and this fear that if I messed up, everything would crumble. People would see that I don’t actually know what I’m doing, and I’m not really ready for this level of seniority. And so there’s this fear of one big mistake, it’s over. Clearly this was an example of a huge mistake and it was not over for you. Is there any lessons there that you take away of you can mess up and still do well, even if it’s this level of mistake?
Ethan Evans: I think a lot of people in my position would’ve quit. They would’ve let the shame… I was just a little bit bullheaded where I’m like, “Yeah, I messed up. But I know I’m still a good person and a good worker. Yes, I made a mistake, but I’m going to move on.” Part of the story I haven’t told that you might enjoy is I mentioned that Jeff Wilke was Jeff’s number two at that point. Jeff Bezos, number two person, and he was my skip level.
Well, during this process, he came physically into our offices and he wanted to talk to me, and my manager who was vice president said, “Hey Jeff, this is my team. I own it. If you have any criticism, say it to me. You don’t mean to talk to my team.” And Jeff Wilke said to my boss, whose name was Paul, “Paul, that’s excellent leadership. I really appreciate what you’re doing. Please step out of the way. I want to talk to Ethan. You’re doing a great job, Paul. Now step aside.” And then he kind of read me the riot act.
And the rest of that funny story is I was so happy with how well my meeting with Jeff Bezos went, I patted myself on the back and like, “I’m going to go face Jeff Wilke now. I’m going to schedule a meeting with him and do the same thing. I’ve got this down.”
So I go to meet with Jeff Wilke, figuring I’m going to run the same playbook. I’m going to look him in the eye and all will be forgiven. And Jeff Wilke looks at me and says, “Ethan, when you launched this, did you know you were gambling with the result? Did you know it might not work?” And I said, “Yes. We had a media commitment to launch on that day, and I thought shooting for the date was more important than perfect certainty.”
And he said, “Well, two things. First, you were wrong. You were wrong to prioritize date over our reputation. You let Amazon down in public and that was a mistake.” He said, “Second though, at least you knew you were gambling. If you hadn’t known you were gambling, we’d be discussing your departure.” And I’m like, “Okay.” Here I thought I was rolling in this meeting like I’m going to run my relationship playbook. And he’s evaluating whether or not to keep me.
The bullheadedness is even after he had told me he had been considering firing me, I’m like, “Well he isn’t. So I’m just going to go forward.” And a lot of that stubbornness of sure I made a mistake, but I’m not going to live in shame about it, I think is what people can take away. I think a lot of people feel they’re more dead in the water than they are.
Because everybody makes mistakes, right? I mean Jeff and Fire Phone, that’ll be an albatross around his neck. Jeff and Fire Phone will be a phrase of anybody who knows Amazon for the rest of his life.
Lenny: Yeah, we talked about it on the Working Backwards podcast, and why didn’t Working Backwards work for the Fire Phone, we talked about it. I love that these quotes and lines are so seared in your brain. You can remember it like word for word exactly what-
Ethan Evans: Well, I’ve relived that moment many times.
Lenny: And then just along the lines of working your way out of the hole, is essentially what you did just succeed for two years and do great, and that was the key there?
Ethan Evans: No, I think I did have to learn. I’ve always been sort of an operational cowboy, meaning I like to go fast and loose. I prioritize speed, and I really had to step back and say, “Okay, Amazon at this level and scale doesn’t like that.” So I’ve taught myself a new phrase which was fear the New York Times headline. Be aware that if Amazon is down, it goes up on every news website immediately. And so if Amazon has some kind of mistake, it’s on Wall Street Journal and CNN.
And so as a leader, I had to think, is what I’m doing going to generate a New York Times headline? Because if it is, I’d better be really careful. And that’s what I taught myself is you can’t be paralyzed, but I taught my whole team, we don’t want to be in the New York Times for the wrong thing. And that was the lesson
Lenny: Along the lines of lessons, last question here, what’s something that you took away from the way you approached it that you should have changed or should have done differently, that you’ve done differently since? Obviously don’t… You mentioned this idea of don’t promise a date that you’re not that certain you’re going to hit. I guess is there anything along those lines?
Ethan Evans: I have two things here. First, Amazon loved in the past, they loved surprise launches. They love the idea of we’re going to be quiet, quiet, quiet. Because basically it was a reaction I think to Microsoft where they felt Microsoft always talked about what was coming and then pushed the dates back. And so there was this whole thing about vaporware. And Amazon wanted to be the other way, which is we won’t say anything and then it will just be there. The problem I came to say is the biggest thing I learned with surprise launches is that you’re surprised by what doesn’t work.
And so I shifted the approach to let’s do a lot of beta testing. We always, even if others don’t agree quite and say, “You’re right, we’re not going to have a surprise launch.” Some of our beta testers, even if they sign NDAs are going to leak. And that’s a better outcome than launching something that doesn’t work. That’s one lesson.
The other lesson is this thing that broke in front of Jeff Bezos, ultimately it was a new college graduate engineer who wrote that code. And he had been left alone to write part of our user interface, but he had written it in such a way that it didn’t scale. Now we didn’t give him any help or oversight. We left him on his own, because we were busy focusing on other pieces of the problem.
And shortly after the disaster, he left the company. And the mistake I made was not reaching out to him and really reassuring him of, “Yes, you wrote the bug, but that’s not on you. The system failed you and we don’t see you. Bugs happen.”
So the thing I regret in this whole thing is not realizing that even though no one in the team ever yelled at him or whatever, he knew it was his bug, and he obviously saw me and others sort of taking a beating. And so he left, and I wish he hadn’t done that. And I wish more than that I had stepped in. I didn’t realize what he was feeling.
Lenny: It’s interesting, the lesson there isn’t catch that person sooner, and notice these links in the chain that may break. But it’s more just be there for that human that have this challenge, that people may not be focusing on.
Ethan Evans: Because we lost a good person, and he probably felt very bad about it. And we all feel bad when we make mistakes. That can’t be prevented. But he felt undue responsibility I think, and that I really regret.
Lenny: This is actually a really good example of ownership. You mentioned this term ownership and that connects to… Amazon has these leadership principles. I think there’s 14 of them. One of them is around ownership. And apparently you helped craft the actual language for that principle, which I think is a huge deal with Amazon. I imagine very few people have a say over how to define, and describe, and say these principles. Could you just talk about this principle that you contributed to, how it came to be that you helped actually write it?
Ethan Evans: Amazon is now kind of on its fourth version in my mind, maybe there’s more. But its fourth major revision of its leadership principles over its 25 plus year history.
And when it was going from version one to version two, Jeff and his leadership team sat down together. And actually in version one, there were three different lists. They were leadership principles and core values, and something else I don’t remember. And they were like, “Three lists is stupid. Let’s make one list.”
Well ownership, the term had been a part of one of those lists, but when they merged everything, they took it out. And this guy Jeff Wilke I mentioned, the number two and the leader of retail, he brought a bunch of us a bunch of his directors. He brought the proposed list to us in a meeting and said, “Hey, this is the proposed new version, do you have any comment?” And we all sat around and talked and said, “Where’s ownership? Ownership is missing.” So we told him, he said, “Look, ownership is missing. We think it should be there.” And he said, “Well, why don’t you propose a draft?”
And so about a half dozen of us sat around and roughed out a draft of how we felt ownership should be written. And I proposed these six words, which are, “An owner never says that’s not my job.” Maybe that’s seven words.
So I propose this specific language as a part of it and we sent off this draft. And months go by, we hear nothing. And then one day the leadership principles are announced and ownership is back in. It’s been modified, but that, “An owner never says that’s not my job,” is a part of the leadership principle, and it’s remained to this debt.
And what I love about that is because Amazon has one and a half million employees who live by these leadership principles, it’s probably the most impactful thing I’ve ever written.
Lenny: Wow. So those seven words are the most impactful thing you’ve ever written. I love that and I totally get that. I’m looking at the principles right now and it comes right at the end of that principle. We’ll link to the 14 leadership principles. Is there another principle that you really love or one or two? I don’t know. It’s probably hard to pick your favorites.
Ethan Evans: I’m a huge proponent of bias for action. Bias for action says speed matters in business and many decisions are reversible. And so it’s important to go faster.
And I think people don’t understand that in a competitive environment, being right is good, but being quick is necessary. Because if there are 10 startups working on an idea, some of them will gamble, and they’ll make bad gambles, and they’ll go out of business. But some of them will gamble and make an early bet and be right. And if you are not moving quickly, you’ll be beaten by the people who maybe got lucky.
And so you’ve got to have a process that values speed, values, what can we do today? What can we commit to today? So I really like bias for action. Now that is what got me in trouble with Jeff, right? I was willing to gamble. So it has to be in balance, but that’s my other favorite.
Lenny: Again, the Jeff Bezos interview with Lex Fridman, he was talking about how with Blue Origin, with the way Amazon, he thought about Amazon is customer obsession. That was the core goal and differentiator of Amazon. With Blue Origin, he wants it to be decisiveness. It’s basically leaning into this bias for action fully, which is really interesting.
Ethan Evans: I saw that part of the interview and I thought, “Wow, that’s exactly right.” Because again, rockets blow up and they have people on them. You’ve got to get it right, but you also have to keep moving, because there’s always one more thing you can safety test. So how do you balance it?
Lenny: Yeah, it’s interesting. With rockets, that’s the one that you pick. It’s pretty bold to be all move forward kind of thing. So this principle, again, going back to ownership, so you basically suggested this phrase, “You didn’t hear anything,” and all of a sudden it becomes part of the whole thing. Did that feel weird that they never told you, or I don’t know if they gave you credit for that, or it’s like, no, it’s great?
Ethan Evans: Yeah, I wouldn’t even claim credit for it, except I kept a copy of the email that says, “Ethan thinks it should say blah.” I have the written proof. Because it’s not about the credit. I’m very happy and proud that those words were kept. But in Amazon, I doubt if Jeff knows I wrote those words. It’s not like I’ve ever told him, “Hey, do you know you kept my words?” That’s not appropriate. It’s just a fun anecdote.
And it does show, I guess something people can learn from that though, you can influence way up in a company if your ideas are good. And also, when we challenged, Jeff Wilke was a strong opinionated leader who didn’t necessarily always love being challenged.
And so when we first told him, “Well, we think you’re missing ownership,” he was like, “You’re staying that the whole S team can’t get its leadership principles right?” I mean it wasn’t exactly that way, but he was very much like, “Well, is this really necessary? Why do you think it’s necessary?” And his challenge to us to write it was kind of framed as, “Well if you’re so sure it’s good, show us.” But again, I’m stubborn and I’m like, “All right, let’s write it.” And we did.
Lenny: That’s funny. That’s not a great example of leadership where he is like, “Hey guys, I need your feedback on this thing. But no, don’t actually tell me anything’s wrong.”
Ethan Evans: Well, yeah. I mean for a bunch of directors to kind of critique the work of people two levels higher, he wanted it, but then he’s sort of naturally resistant to it if we’re kind of poking at his baby.
Lenny: It’s unlikely that there’s something huge missing and it turns out there was.
Ethan Evans: Yeah.
Lenny: And I guess just on these principles, people may not know this, but this is where disagree and commit comes from. It’s actually have backbone, disagree, and commit. We talked about this on the podcast about working backwards. I also love leaders are right a lot. That comes up a lot and I love that, to be successful, you need to be right. You can’t just project confidence. You can’t just be in a bunch of meetings and ship things. You need to be right to be successful.
Ethan Evans: And that one’s been rewritten to carefully say, it’s always interesting what is the history of the edits, which you wish you could see the edit history on these. That one got modified to say something about leaders actively work to disconfirm their beliefs.
And the key there is it was trying to get at the idea that you’ve got to be very open and always be questioning, “Yes, I think I’m right, but what’s the new evidence? What am I learning? What’s changing?” And in fact, it also says they seek diverse perspectives.
And that was a way of getting at what’s called DEI, diversity, equity, and inclusion. That’s a subtle nod towards if everyone in the room is a 50-year-old white man, you may not really be making the right overall decision for Amazon’s customer base. You may be making the one for 50-year-old white suburban Seattleites. And so it’s just some of these, every word in those has been studied as an individual word inside the company.
Lenny: Amazing. Okay. Let’s move on to the final area I wanted to spend a little time on, and this is called contrarian corner. I’m curious if you have any contrarian opinions about things basically that other people believe that you don’t believe, something you see that many people don’t see. Is there anything that comes to mind?
Ethan Evans: Yeah, I think a place where I’m currently very contrarian is the return to office movement. Many leaders at my level appear or publicly favor the need to get back into the office potentially full-time.
And I’m contrarian on this because of innovation. Specifically, I looked it up, you can check my facts on Wikipedia. The first purpose-built office, the first building ever built to be an office was built in 1726 in London. And so we’re about 300 years into learning how to use offices well.
And what that means is offices aren’t going to get much better. What’s the last major thing you can think of that got better in offices? You might say well open offices, but a lot of people would say that’s not even a good idea. These big rows of desks and loud pits.
With working from home, we’ve only been doing that for a few years since the pandemic began and at all since the internet started 20 years ago. Which one is likely to have more opportunity for improvement? There’s so many things we haven’t explored with remote work. And I think the people who say, “Back to the office, it’s because we know it works,” well we know what it is, but I have so much more faith in the opportunity to improve the remote experience. And so I think long-term, it’s going to triumph.
The one other place where I’m a huge contrarian is doing business on a handshake. I understand companies need lawyers, and I have an attorney for certain things. But I coach people. Most of the people I coach, there’s no NDA in place. There’s no contract in place. They pay me through PayPal and I do good coaching for them.
I think too much of the world is contract driven, and we’ve lost the idea of your word being your bond, and you can actually trust me to follow through on my commitments. And I’m a contrarian there.
I realize I will occasionally get burnt. Someone will behave in a way, they’ll let me down. But I think when we’re always suspicious of people, that’s a high cost. And the other place I’m contrarian is just doing business on faith.
Lenny: That reminds me, Sam Altman has a similar philosophy of just trust people and assume it’ll all be okay. Sometimes you’ll get burned, but on balance, it’ll end up being much better for you and for everyone around you.
Ethan Evans: I didn’t know that Sam had said that, but I strongly agree with it.
Lenny: Yeah, although he had some challenges recently. I don’t know if it’s working great, but it ended upgrade for him. So anyway, okay. We’ve actually reached our very exciting lightning round. Before we get there, is there anything else you wanted to touch on, or share, or leave listeners with?
Ethan Evans: No, I’ve really enjoyed this conversation. I could talk about careers forever and I love doing that, but I think we’ve covered a ton today that will really help people. So I’m good. Let’s hit the lightning round.
Lenny: All right. With that, we reached our very exciting lightning round. Are you ready?
Ethan Evans: I’m ready.
Lenny: Ethan, what are two or three books that you’ve recommended most to other people?
Ethan Evans: Two or three books. My number one recommendation is a book called Decisive. It’s by Chip and Dan Heath, and it’s about the science of making better decisions. The reason I recommend it so much is it will make your career better because leaders are decision makers, but also your personal life. So I apply it at least as much in my personal life as I do in my professional life.
My second most recommended book is Leadership and Self Deception, much less known than Decisive, a little bit harder to approach. It’s by a group, a research group called the Arbinger Institute, and it’s about, the self-deception is we cause a lot of our interpersonal problems while blaming them on others. And it walks through how are you part of the problem you’re having with somebody else and what can you do about it?
The third and final book was recently brought to me by someone I work with that you know, Jason [inaudible 01:13:21]. That book is The Almanack Of Naval Ravikant. And Naval Ravikant is an angel investor responsible for AngelList.
But what I love about that book is he has a recipe. He really boils down how to be successful while loving what you do. And he says, “No one can be a better version of you.” Don’t try to copy me and be, “I’m going to be like Ethan, or I’m going to be like Lenny.” Instead, figure out what you uniquely do best that you love, because no one can copy you being you. And that’s your defensible sort of career value. And I really like that mental model.
Lenny: Yeah, Naval has so many insightful messages, and you can read all these on his Twitter. We’ll link to his Twitter, and someone just made a book out of his tweets basically. He’s such an interesting dude.
Ethan Evans: Yes, that’s right.
Lenny: Awesome. What is a favorite recent movie or TV show you’ve really enjoyed?
Ethan Evans: So I grew up on a farm, and so all the Taylor Sheridan, 1923, and Yellowstone, and all of those series, we’ve watched everything he’s put out. We do kind of laugh like, wow. Are you familiar with Yellowstone at all?
Lenny: Absolutely. A lot of death.
Ethan Evans: Yeah. At one point my wife and I were watching it, we would start betting. So the episode is starting, how many people will die in this episode? This ranch in Montana, but yet somehow they’re always killing people. How does this work?
Lenny: That’s what your life was like, is what I’m hearing. Favorite interview question that you like to ask candidates?
Ethan Evans: I think my favorite interview question is, “Tell me about a time where you needed to disagree with your management, where you needed to stand up or fight for a position against higher leadership or people in power.” Because I think that’s really hard to do. I’m normally interviewing leaders, and I think having a bunch of people who just say yes isn’t helpful. You need people to have, as you said, have backbone, disagree and commit. So that’s what I’m normally looking for.
Lenny: Awesome. Is there favorite product you’ve recently discovered that you really love?
Ethan Evans: It’s silly, but my favorite product that I’ve discovered recently is the Chuckit!, which you use to whip a ball for your dog a quarter mile. It basically extends your arm. And it’s just fun to send a ball soaring way further than you could ever throw it. And you feel like, “Wow, look at me. I’m a major league pitcher.” Because I have this three foot lever arm and I understand physics. If we look at tech products, there’s so many I love. It’s too easy to say ChatGPT and stuff, so I won’t go there.
Lenny: Awesome. My dog does not love chasing balls, so I haven’t had a reason to buy that, but I’ve never thought about just the joy of flicking a ball really far. Do you have a favorite life motto that you often come back to, share with folks, find useful in work or in life?
Ethan Evans: I happen to be a Christian, and the motto that I think about the most is, “To whom much has been given, from him much will be required.” And so I think a lot about what is my social responsibility.
I’ve been very lucky. I grew up on a farm in Ohio now. I wasn’t a farm boy, my father was a chemist. But I grew up in upper middle class settings, and I’ve ended up being extremely successful, able to retire from my job at 50 to kind of coach and teach. What do I owe to pay forward? So those words are obviously ancient spiritual texts, but they’re the ones I take away and think the most about. What’s my responsibility?
Lenny: As an example of someone that to whom much has been given, but because he’s worked so hard, Jeff Bezos is starting a space business as you know. If you had the chance to go to space, would you go?
Ethan Evans: Well, I of course saw his interview where he talked about how he thought about the safety and the conversation he had to have with his mother. I would like to go to space. I’m not willing to pay what I think the current tickets are, but I would take the risk. So what’s the risk of that ride? One in a hundred, one in 50, even more that you won’t come back. I would probably take the gamble.
Lenny: So you’d be an early adopter? Where along that curve would you be, an early adopter, laggard?
Ethan Evans: Well, I’m old enough that I remember when the Challenger space shuttle exploded, and I said I would get on the next one and I said, “They’re never going to be more careful than the next one, so I’ll get on the next one.”
So I think I would get on any one I was offered because of the chance. Unlike Jeff who claims he wasn’t scared, I would probably be really terrified, at least at liftoff. While you’re up there, it’s great. Everything either goes wrong going up or coming down. It’s not the middle.
Lenny: Ethan, I think we’re going to help a lot of people with their career. I think we’re going to help them work through failure, become better owners. Thank you so much for being here. Two final questions. Where can folks find you online if they want to reach out? Also, just share what you do now in case people could use that help. And then how can listeners useful to you?
Ethan Evans: So the best place to find me online, I do all my writing on LinkedIn. It’s where the professional community is. So Ethan Evans on LinkedIn. My actual handle there is Ethan Evans VP for my history as a vice president. That’s the best place to find me. I do have a Substack newsletter. I do teach through the Maven platform, but all of those are linked off LinkedIn.
And really, how readers help me, they comment on what I write, because I miss things. I am one person’s perspective. And so I actually have a process where I take in all the comments people write, all the different perspectives, all the different exceptions, or special cases, or examples, and that’s how I improve my own thinking is I read every comment and think, “Okay, what did I miss? What could I have said better? How can I incorporate this if I ever talk about this again?”
Lenny: Just to give you another opportunity to plug the stuff you do now, what do you help people with in case people could value could you use the stuff that you offer? You said you coach, you have a course. What sort of stuff?
Ethan Evans: I focus on two topics, career development. So how do you row in your career, the whole Magic Loop, and how do you attain promotion or attain a new role raise if that’s your goal? And then leadership specifically. I teach a course that’s been very popular called Stuck at Senior Manager - Breaking Through To Executive, which is how to get out of that sort of stuck, “I’m working really hard, I’m pretty good. I’m managing 25 or 50 people, but how do I get to the big chair? How do I get to the division level leadership and what do I need to change?” It’s that whole what got you here won’t get you there. And I love to see people succeed at that. People write me back and say, “I did get a job. I did get promoted, I did get a raise,” and that’s my fulfillment.
Lenny: Amazing. Ethan, thank you so much for being here.
Ethan Evans: Thank you, Lenny. And I got to say, you are very good at this. You’re so smooth and you just do a great job interviewing. It’s been really been a pleasure.
Lenny: I really appreciate that, and so are you. Thank you. Bye everyone.
Ethan Evans: Bye everyone.
Lenny: Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.
Glossary
| English | 中文 |
|---|---|
| Andy Jassy | Andy Jassy |
| AngelList | AngelList |
| app store | 应用商店 |
| Arbinger Institute | Arbinger Institute |
| beta testing | beta 测试 |
| Bias for Action | Bias for Action(崇尚行动,Amazon 领导力原则之一) |
| Bill Carr | Bill Carr |
| Challenger | 挑战者号(航天飞机) |
| ChatGPT | ChatGPT |
| Chip and Dan Heath | Chip 和 Dan Heath |
| Chuckit! | Chuckit! |
| Contrarian Corner | 异见角(Contrarian Corner) |
| Customer Obsession | Customer Obsession(客户至上,Amazon 领导力原则之一) |
| Decisive | 《Decisive》(决断力) |
| DEI (Diversity, Equity, and Inclusion) | DEI(多元、平等与包容) |
| executive coach | 高管教练 |
| Fire Phone | Fire Phone |
| Have Backbone, Disagree, and Commit | Have Backbone, Disagree, and Commit(敢于直言、敢于异议并全力以赴,Amazon 领导力原则之一) |
| IC (Individual Contributor) | IC(个人贡献者) |
| imposter syndrome | 冒充者综合征 |
| Invent and Simplify | Invent and Simplify(发明与简化,Amazon 领导力原则之一) |
| Jeff Bezos | Jeff Bezos |
| Jeff Wilke | Jeff Wilke |
| Leaders Are Right a Lot | Leaders Are Right a Lot(领导者在很多时候是对的,Amazon 领导力原则之一) |
| Leadership and Self Deception | 《Leadership and Self Deception》 |
| leadership principles | 领导力原则 |
| Lex Fridman | Lex Fridman |
| Marshall Goldsmith | Marshall Goldsmith |
| Maven | Maven(在线教学平台) |
| Naval Ravikant | Naval Ravikant |
| NDA | NDA(保密协议) |
| New York Times | 纽约时报 |
| newsletter | newsletter(通讯/邮件订阅) |
| Oracle | Oracle |
| Owner | Owner(Owner,Amazon 文化中的”主人翁”概念) |
| PM | PM(产品经理) |
| Prime Gaming | Prime Gaming |
| Prime Music | Prime Music |
| Prime Video | Prime Video |
| Principal Engineer | Principal Engineer(首席工程师) |
| rapport | 默契 |
| S Team | S Team(高级管理团队) |
| Sam Altman | Sam Altman |
| Scrum | Scrum |
| SDE (Software Development Engineer) | SDE(软件开发工程师) |
| Silk | Silk(Amazon 浏览器) |
| skip level | 越级上级(skip level) |
| social engineering | 社会工程学 |
| Stuck at Senior Manager - Breaking Through To Executive | Stuck at Senior Manager – Breaking Through To Executive(卡在高级管理者——突破到高管层) |
| Taylor Sheridan | Taylor Sheridan |
| Test Drive | Test Drive(试驾,应用试玩功能) |
| The Almanack of Naval Ravikant | 《The Almanack of Naval Ravikant》 |
| The Invention Machine | 《The Invention Machine》(发明机器) |
| The Magic Loop | 魔法循环(The Magic Loop) |
| Think Big | Think Big( Think Big,Amazon 领导力原则之一) |
| UPS Store | UPS Store |
| vaporware | vaporware(雾件) |
| Wall Street Journal | 华尔街日报 |
| Werner Vogels | Werner Vogels |
| What Got You Here Won’t Get You There | 《What Got You Here Won’t Get You There》 |
| Working Backwards | 《Working Backwards》(逆向工作法) |
| Yellowstone | 《Yellowstone》 |
Reformatted by reformat_english.py
掌控你的职业发展 | Ethan Evans(Amazon)
掌控你的职业发展 | Ethan Evans(Amazon)
精彩内容预告
Ethan Evans: 人们以为发明创造需要花费大量时间,但其实你只需要每月抽出两小时就够了。关键在于,一旦你有了一个好点子,往往需要数年时间去将它实现。
你当初有了做 newsletter 的想法。我知道你 newsletter 的一些历史。你花了数年时间在打磨这个想法的表达。Jeff 和 Amazon 也有过类似的想法,比如”我们来做 Prime 配送”。Prime 至今仍在不断优化、持续迭代。这是一个有着二十多年历史的想法。Kindle 同样如此——一个诞生了几十年的想法,至今仍在不断改进。这里的要点是:你并不需要很多好点子,就能被视为极具创造力的人。
Lenny: 今天的嘉宾是 Ethan Evans。Ethan 曾任 Amazon 副总裁,现任高管教练和课程讲师,专注于帮助领导者成长为高管。Ethan 在 Amazon 工作了 15 年,参与发明并运营了 Prime Video、Amazon Appstore、Prime Gaming 和 Twitch Commerce——其中仅 Twitch Commerce 一项就是 Amazon 十亿美元级别的业务。他领导过超过 800 人的全球团队,参与起草了 Amazon 14 条核心领导力原则之一,拥有超过 70 项专利。目前他将时间用于高管教练辅导和开设课程,帮助人们在职业发展中晋升、培养领导技能,并在高层岗位上取得成功。
在我们的对话中,Ethan 分享了他为一个重要项目在 Jeff Bezos 面前失败的经历,以及他从中学到了什么。我们花了一些时间讨论一个叫做”The Magic Loop”(魔法循环)的方法,这是一个非常简单的理念,我保证它会帮助你在职业中获得晋升和发展。我们还聊到了许多其他职业建议,主要面向资深 IC(个人贡献者)和各级管理者。我们谈到了在面试中脱颖而出的建议,还有 Amazon 最重要、最有影响力的几条领导力原则,以及更多内容。我从 Ethan 身上学到了很多,很高兴能把这期节目带给大家。接下来,请听 Ethan Evans。
(广告段落已跳过)
The Magic Loop(魔法循环)
Lenny: Ethan,非常感谢你的到来,欢迎来到播客。
Ethan Evans: Lenny,非常感谢你的邀请。我非常期待今天讨论我们准备好的那些话题,希望能帮到大家。
Lenny: 我想聊的第一个话题是 The Magic Loop。你今年早些时候为我的 newsletter 写了一篇客座文章。你可能不知道,它目前是我 newsletter 上 300 多篇文章中历史上第六受欢迎的帖子。你预期过这个建议会引起如此强烈的共鸣吗?你觉得它为什么能引起这么大的反响?
Ethan Evans: 我好胜的那一面其实很想分析一下第一到第五名,看看它们是不是占了不公平的优势——比如它们有更多的时间积累?但我确实非常希望这些建议能引起这样的共鸣,因为我在简化和提炼上下了很大功夫,让它变得真正容易理解和践行。所以我对它的表现非常满意,但我确实也期待它能取得这么好的成绩。
Lenny: 我想说,有时候文章的热度还会继续攀升,所以这未必是这篇帖子的最终排名。
Ethan Evans: 最终排名,对。
Lenny: 好的。对于还没有读过那篇文章的人,或者读过但想温习一下的人,我们来多花点时间聊聊。你能简要描述一下你写的这个”The Magic Loop”的理念吗?
Ethan Evans: 当然可以。The Magic Loop 是一个几乎在任何情况下都能促进职业发展的方法,即使你的上司有些难对付也适用。它的前提是你确实在某个环境中工作——通常是自己创业或者有一位上司。The Magic Loop 的核心理念分为五个步骤,非常简单。
第一步,你必须把当前的工作做好。如果你的表现连”合格”都算不上,那职业发展就无从谈起。这并不是说此时你必须成为团队里的明星,但你不能让你的上司对你的表现不满意,比如”Ethan 做得不太好”这种。你需要主动与你的上司沟通,了解自己的表现,并解决存在的问题。所以第一步是:做好你当前的工作。
第二步是主动询问你的上司你能如何帮忙。站在管理者的角度来说——我与数百位管理者交流过——很少有人会主动去问自己的上司:“我能帮你做些什么?你需要什么?“仅仅是开口询问就能让你脱颖而出,同时它也开始建立起一种关系:我们在同一支队伍里,我作为你组织中的一员,是为了让你成功,而不仅仅是为了自己。
第三步是:无论他们说什么,照做。假设你挖了一个大坑——你说”我能帮你做什么?“对方说”我们确实需要有人每天把托盘清理一下”,你心想”我不是这个意思,我想要的是有挑战性的工作,我不想做这种维护性的杂活”。但不管怎样,照他们说的去做,即使那不是你最喜欢的工作。
第四步:让魔法发生
Ethan Evans: 完成了前三步,并且可能重复几次之后,第四步就是魔法所在。你回到你的上司那里说:“嘿,我很喜欢和你一起工作。我在想,有没有什么方式能帮到你,同时也能帮我实现我的目标?“不管这个目标是转岗、加薪还是晋升,你可以说:“我的目标是我很想学这个新技能。你有没有什么需求,恰好也能帮我学到这个新技能?“这个方法之所以奏效,是因为管理者会帮助那些帮助自己的人。这是人之常情,我们都会这样做。
通常,管理者非常乐意各退一步来迁就你,他们会说:“当然,我需要这个。我们可以调整一下安排,逐步找到满足你目标的办法。“不过,要让第四步奏效,你必须清楚自己的目标是什么,也就是说,你要明确自己想要什么。这部分就取决于你自己了。
第五步:循环往复
然后第五步是所有步骤中最简单的——就是重复。就像洗头时的”涂抹、冲洗、重复”一样。第五步就是,当你和你的上司一起朝着你的目标努力、讨论你的方向、互相帮助的时候,魔法循环的奥秘就是不断地循环往复。
Lenny: 我正想问你,为什么你叫它魔法循环(The Magic Loop)?另外,我们虽然直接深入了内容,但这个方法的目的是什么?我想到了现在大家可能已经比较清楚了——它能帮助你在职业上前进,但你有什么想补充的吗?
Ethan Evans: 好的,很公平。我之所以叫它魔法循环,是因为几年前我向我的受众推广了这个方法。效果实在太好了,人们纷纷写信回来说:“我怎么才能让它停下来?我现在已经力不从心了。我的上司给了我这么多很酷的事情做,我觉得自己跟不上节奏了,而且我已经被晋升过一次了,需要时间来消化。“它就像施了魔法一样奏效,几乎在任何情况下都管用。
当然也有例外,比如你遇到了非常剥削型的管理者,他们会说:“哦,太好了,你工作更努力了,继续保持吧”,却不会为你做任何事情。但这种情况很少见。至于目的,是的,就是为了帮助你在职业生涯中获得满足感。很多人对自己的工作不满意,很多人想提升一个层级或者涨薪。不是所有人都是如此——有些人想换一种工作内容,他们觉得无聊了。魔法循环是通往所有这些目标的路径,因为它在与你的领导建立一种合作关系:“你看,我愿意帮你,但我也需要你帮我。“而大多数优秀的管理者对此非常乐于接受。
为什么需要这样做
Lenny: 我们在讨论这个方法的时候,我提出过一个反馈——我觉得我可以直接告诉我的上司:“嘿,我想发展我的职业生涯。我们可以一起做些什么来帮我达到目标?“而你的回应是,大多数管理者并没有那么优秀,也没有那么用心地关注员工的职业发展。你能谈谈这一点吗?听到这些内容的人可能会想:“为什么我需要做这些?这看起来工作量很大。”
Ethan Evans: 如果你有一位很好的管理者,你可能不需要这么多的正式步骤。他们可能已经给了你很好的反馈,所以你不需要再去主动询问。他们可能已经主动给你提供了更上一层楼的机会,你接受了一些,也许拒绝了一些。那很棒。我设计魔法循环,是给那些要么不知道该怎么做、要么管理者不够优秀或者只是太忙的人。
记住,很多管理者有很好的意愿去帮助自己的员工,但他们忙于自己的生活、自己的工作、自己专注的各种事情,甚至也包括自己的职业发展。管理者往往忙于考虑自己的需求,所以他们本打算下周来关注你,然后”下周”一拖就是一年。
Lenny: 自从这个方法发布以来,有什么你想补充、调整,或者帮助大家更好理解的地方吗?我猜会有一些批评的声音,也会有很多人说”对对对,这真的很管用”。
Ethan Evans: 有两点我想澄清。第一,很多人问我:“为什么我需要这样做?我的上司不应该注意到我在做什么吗?我的上司不应该帮我规划职业吗?我的上司不应该替我做计划吗?“对此我说的是,你的上司”应该”做什么,和你花四美元在星巴克买杯咖啡一样——“应该”本身值不了几个钱。
这个循环的核心在于,它是你可以掌控的。确实,一个优秀的管理者会做到我刚才说的那些事情,但并不是所有管理者都优秀,有些管理者需要一些帮助。关于魔法循环,我只想说——它掌握在你自己手中。
所以,你可以对你上司的不完美感到不满,但放下这个念头,掌控你自己的处境。这是我想说的第一点。另一个重要的延伸是,如果你是一位管理者或任何类型的领导者,你可以从你这一侧主动发起魔法循环。你可以和你的员工说:“嘿,你的职业目标是什么?你愿意建立一种合作关系吗——你承担新的挑战,我帮你实现你的目标?”
我和自己的员工建立这种合作关系取得了很大的成功。当他们看到成长和成功时,他们会更加投入,觉得”这个体系是有效的,你真的在投资我,我会加倍努力”。而我则回应:“是的,我们可以扩大你的团队、拓展你的机会”,这是非常双赢的局面。
真实案例
Lenny: 为了给大家一些实证,你提到过一些和你一起用过这个方法的人。你能分享一些故事、数据或者任何内容,帮助大家了解这个方法对那些人到底有多大帮助吗?
Ethan Evans: 当然可以。我讲两个极端的例子——也就是入门级员工和高层管理者各一个。有一个入门级员工写信告诉我:“我了解到魔法循环的时候,在一家公司干得不太好。我开始应用这个方法,公司给我加薪三万美元,还给了更大的职责。但我拒绝了,因为我被另一家公司录用了,给的待遇更高,我就去了那里。到了那边他们又给我晋升了。“他是那些写信给我的人之一,原话是:“一年前我被裁了。“他在英国,“redundant”是他们对”被裁”的说法。“一年前我被裁了,我得到了第一份工作,拿到了更高的薪水,然后我又得到了第二份工作,入职时的涨幅更大。“他当时的情况是:“现在我需要放慢脚步,消化这一切。”
另一个极端的例子——我曾经共事过的最优秀的人之一,加入我的亚马逊团队时是我们所说的 SDE II,在亚马逊是第五级员工。他跟随我,基本按照这个流程成长为高级工程师。然后他转为管理岗,带了一个小团队。之后他成为高级经理,随我的组织搬到了另一个城市。他开设了一个新办公室,最终被提升为总监,管理自己办公室的几百人。这一切大约用了八年时间。他从一个中级工程师成长为管理八百人团队的高管。当然他本身也非常努力,但在这八年里我们确实见证了他的所有进步。
后来他离开了。他创立了自己的创业公司,将其出售,现在在一家大型网络银行担任执行副总裁。从某种意义上说,他的职业生涯已经超越了我。但在那八年间,他就是成长了那么多。而这就是我们遵循的过程。
Lenny: 哇,这两个例子太好了。这个方法适用于哪些职级?在什么级别最有用,然后效果是不是会逐渐减弱?我不确定,如果你已经是 VP 级别了,还会继续用魔法循环吗?
Ethan Evans: 我觉得它从职业生涯初期一直到相当后面的阶段都适用。在我那个级别——我在亚马逊以副总裁的身份结束了职业生涯——它确实会在某种意义上逐渐淡化。我的意思是,你仍然在做同样的事情,但不需要再谈论它了。你的管理者期望你主动站出来、发现挑战。他们期望你在需要资源时主动去争取,不再需要那种明确的对话——“我能帮你做什么?“他们期望你预判需求。
在我们合作的那篇 newsletter 里,我写过,随着时间推移,你会从问管理者”我能怎么帮忙?“过渡到向管理者建议”我看到了一些需要做的事,你希望我来做吗?“再到主动看到需要做的事,让领导知情——“嘿,我注意到我们有这个问题,我已经解决了。我注意到我们有机会,我已经着手推进了。“我觉得在高管层面,更多是你主动出击,同时让领导了解情况。
Lenny: 我记得在那篇文章里,你描述这一步的方式是——这是高级模式。不要直接跳到这一步。不要上来就开始提建议,因为你可能会判断失误。
Ethan Evans: 对,这完全取决于默契和信任。职业成功很大一部分取决于你拥有多少信任、与领导层之间的相互尊重。当他们相信你会做出正确的决定时,他们才会放手让你去做。但确实,当你刚入职或刚换了一个管理者时,如果你直接跳进去,你可能会去做他们不看重的事情,甚至可能发现自己的方向与他们背道而驰。这不是正确的起点。
为什么魔法循环如此有效
Lenny: 太好了。好,我们来收尾这段对话。你刚才提到过一点,但你为什么认为这个方法如此重要、如此有效?为什么你觉得它这么管用?人们可能没有意识到——“我明白了,这是关键所在。”
Ethan Evans: 我觉得有两个原因。第一,我之前提到过,管理者被主动提供帮助是多么罕见。如果你是管理者,你会认同这一点。如果你不是,尽管去问任何一个管理者,不管是你的还是别人的。问问他们有多焦虑、有多感到不堪重负、有多希望有人能搭把手。管理可以是一份孤独的工作,因为你会觉得自己对所有事情都负有责任。所以拥有一个盟友,对他们来说是如释重负。
第二,我经常思考社会工程学。这里的社会工程学很简单,就是”你帮我,我帮你”。它不一定是功利性的,只是我们倾向于帮助那些帮助过我们的人,这是刻在人类生存本能里的。
我认为这个循环之所以如此有效,就是因为它稍稍借助了这种行为倾向。很多与管理者的关系是对立性的——你告诉我做什么,我就像高中生一样,琢磨怎么能尽可能少上课、尽可能少交作业,还能勉强混个及格。这种关系不会帮你构建职业生涯。
有些人对待工作的态度是:我的目标是用最少的付出换取薪水。如果你对现状满意,这也是一种活法。但这不是我所教授的。我默认人们想要成长。
简要回顾魔法循环
Lenny: 好,那也许作为收尾问题,对于正在听节目、想要开始实践这个方法的人,或者在职业生涯中感到停滞的人——“好的,我明白了,这是我可以做的事”——你能再简要总结一下这个循环吗?
Ethan Evans: 当然。第一步,确保你当前的工作做得很好。我的解释方式是:当你去找管理者问”我能怎么帮忙?“的时候,你不会希望他们的回答——即使他们不会说得那么直白——是”先把你自己的活干好”。你需要先把本职工作做好。
而不幸的是,“做好”的标准在你管理者的眼中说了算。你可能觉得自己做得很好,但如果你的管理者不这么认为,他们才是你需要争取为盟友的人。
做到这一点之后,去问你能怎么帮忙,按要求去做,然后再回到管理者那里建议或询问:“我想达成这个目标。我能继续帮你吗?有什么你需要的、同时也能帮我达成目标的事情可以交给我?“这就是你开始把双方的诉求汇合到一起的地方——你需要什么,我怎么达到我的目标,我们一起来做这些事。
然后你不断重复这个循环。你建立信任,建立关系。所有优秀的管理者,甚至很多一般的管理者,都非常感激这种帮助,会真正投入其中。
被忽视的关键要素
Lenny: 我觉得这里面有两个非常重要的要素,你甚至没有特别提到,但它们也是这个方法如此有效的原因。第一,这迫使你和你的管理者一起找出阻碍你晋升到下一级的差距——这些差距往往是模糊的,然后到了绩效评估的时候,管理者会说:“Ethan,你在这方面、那方面、还有那个方面还不够好。“你会想:“你从来没告诉过我这些是你期望我做到的。“所以我觉得这里隐含了——“这是你需要提升的,才能晋升到下一级”——我认为这也是第四步的一部分。
第二,你确实提到过这一点,就是要向管理者分享你的目标。“这是我想要的,我想要晋升。“很多时候他们并不知道这一点。你帮助他们理解”这是我想要的,帮我达到那个目标”,这会产生很大的效果。所以这里面有很多——
Ethan Evans: 管理者经常会陷入一个陷阱。他们自己选择了成为管理者,所以他们会对你做两种假设之一。他们要么假设你想一直做现在做的事情,只是可能想多赚一点钱。
所以你是设计师,你就想一直画图。你是律师,你就想一直写合同。要么他们假设:“嘿,我成了管理者,我为自己的职业生涯感到自豪。那一定也是你想要的。”
这些假设是很自然的,对吧?我们倾向于默认认为自己的道路很好,每个人都想成为我们这样。当然,一些优秀的管理者不会这样做。但如果你主动澄清并表达你的目标,你就消除了这种模糊性。
不想晋升怎么办
Lenny: 我在职业生涯中确实经历过一个阶段,我明确不想晋升。我对当时的状况很满意,就想继续做那个很棒的 IC 角色。这种情况你见过吗?有人就是觉得”我挺好的,不需要晋升”,那这个方法对这种情况有帮助吗,还是说就不那么重要了?
Ethan Evans: 首先,我在职业生涯中也到了一个不再追求晋升的阶段,我想要做其他事情。我自己经历过这个,我也用了同样的循环,但我用它来做我想做的事——我说”这是我现在想要的,我们怎么达成?我们怎么创造一个角色,让我在这个级别上创造相应的价值,同时做这些我觉得有趣的其他工作?“我转入了游戏领域,我当时确实非常想去做那件事。
魔法循环的适用范围
Ethan Evans: 其次,我觉得它仍然有帮助,因为你大概总会有些想要的东西。也许你想做不同类型的项目,或者想和一个绩效更高的团队合作。又或者你想重新平衡生活——“我喜欢我现在做的事情,但怎么才能在你设定的这些边界内成为明星员工?”
所以,如果你真的拥有完美无缺的工作,你可能不需要魔法循环(The Magic Loop)。但我认识的人中,几乎没有谁会说:“不,我的角色完全没有任何可以改进的地方。”
Lenny: 对,我觉得你说的这点很好——目标不一定是晋升。可以是去组织中的其他部门工作,尝试完全不同的事情……也许是转型到一个新的职能领域,这也可以成为你的目标的一部分。很好。
高级管理者的晋升困境
Lenny: 好,继续聊职业发展这个话题。你接触过很多高级管理者,大概是 L7 和 M2 这个层级,你跟我分享过,他们职业生涯中这个阶段最令人沮丧的一点就是:他们卡在这个层级上无法上升,变得越来越烦躁,又不知道怎么突破。对于可能正在收听这个节目的这类人,你会给出什么建议?
Ethan Evans: 确实,在这个层级卡住是很常见的,原因有几个。首先,高级管理者数量很多。你想想一个典型的总监,他下面可能有六到八个直接下属。那还需要多少个总监?所以这里存在一个瓶颈。
其次,在当前的经济环境下,这个瓶颈更加严重。过去,很多公司——Amazon、Google、Apple 等等——都在快速增长。所以你不仅仅是在等另一个总监离开,团队本身也在不断扩大。
我在 Amazon 亲历了这一点。在九年时间里,我从管理六个人发展到管理八百人,从高级经理一路做到了副总裁。某种意义上,我只是在乘坐一部向上的电梯——电梯在往上升,只要我能留在上面,我就会到达副总裁这个位置。
从执行者到影响者的转变
Ethan Evans: 但导致人们卡住的另一个原因是,高级经理和总监之间的区别在于你如何领导以及你做的工作性质。凭借在自身职能领域的强大能力和出色的执行力,你可以一路升到高级经理。但到了总监,以及更高层的副总裁,工作重心就很大程度上转向影响力、与他人协调,以及放手不再事必躬亲。所以高级经理确实需要改变一些行为模式。
我经常引用 Marshall Goldsmith 的书《What Got You Here Won’t Get You There》(把你带到这里的不会把你带到那里)。不仅因为这本书确实是关于这个问题的经典之作,更因为书名本身就说明了一切——那些让你达到当前层级的优秀特质,不会把你带到下一个层级。在更高的层级上,人们更期望你以战略思维思考,着眼更长远的未来。
Lenny: 那对于现在正处在这个角色中、无法往上走的人,他们能做什么呢?你刚才说的——没有合适的岗位,这确实有很大一部分你无法控制——建议就是等机会出现吗?是继续运行魔法循环(The Magic Loop)直到有事情发生吗?还是有什么别的办法?
Ethan Evans: 我会坦诚地告诉人们,确实需要一些耐心。在这个层级,存在一个现实问题:我们需不需要一个总监?需不需要一个副总裁?我们有没有那个层面需要人来解决的挑战?所以这个层级的晋升,我经常教大家,包含两个组成部分。第一个是:我能不能胜任那个工作?我够不够格?我有没有相应的能力?但第二部分是:我们有没有这样一个需要人来做的岗位?
如何成为被选中的人
Ethan Evans: 不过,你确实有很多可以做且在你的掌控范围内的事情。你能做的,就是开始练习下一层级所需的技能。开始和你的领导层探讨:我可以在哪里承担一个战略性项目?我怎样才能成为更具创造力的人?我教过一些关于如何系统性地进行创新的方法——它不纯粹是魔法。Edison 说过,百分之一的灵感加上百分之九十九的汗水。那百分之九十九是可以学习的,而一旦你学会了,百分之一的灵感就没那么难了。所以你要开始展现下一层级的特质。用我最简洁的话来说就是:怎么让自己成为八个人中会被选中的那一个?
你是可以被选中的。晋升有好几种路径。你的上级可能离开或被解雇,也可能被晋升到其他岗位。但还有另一种情况——我现在做教练,最近有几个客户。昨天我刚和一个客户聊过,她的两个同级被解雇了。他们原来都是同一层级,她的两个同级被解雇了,然后把他们的团队都交给了她。她说她的上级被告知:“你的组织中高级经理太多了,相对于组织规模而言。我们需要做一些组织调整,清理一下,把人员都放到那些有潜力的人下面。”
显然,她就是那些有潜力的人之一,因为她保住了工作,还管了更多的人和更多的事。而不幸的是,她的同级们正在找新工作。所以要成为那样的人——这就是魔法循环(The Magic Loop)发挥作用的地方。成为那个人。
Lenny: 我最近恰好跟一位高级 PM 领导聊过,他提到在当前这种精简的环境下——大量组织扁平化、大量裁员——这种情况变得越来越困难。正好就是你描述的这种现象。职位就是更少了,因为公司在更精简地运转,所以你只能等待。
我觉得你刚才分享的建议中有一部分,就是经典的”先做那个岗位的工作,再得到那个岗位”,这完全说得通。因为一旦人们看到你能做到,他们自然会更有信心把你放到那个位置上。
Ethan Evans: 而且他们也在寻找这样的人。我总是提醒大家,作为领导者,我希望下面有最优秀的人。不是我不想提拔你。你想想我的工作性质就明白了——这对我也有好处,对吧?我有自己的私心去想提拔你。很多人觉得”老板在压着我”,好吧,也许有些老板确实如此,但为什么我不想有更强、更有能力的直接下属呢?为什么我不想手下有能做更多我现在工作的人呢?坦白说,那是我唯一能让自己少做些工作的办法。
Lenny: 再加上你下面的人也会不断给你施压。“嘿,我已经准备好晋升了,这次行了吧”……你刚才提到了”创造力”这个词,我正好在听 Jeff Bezos 在 Lex Fridman 的播客,不知道你听没听过,Jeff Bezos 最认同自己的身份是发明家,超过他所做的其他任何事情。你会想到这个吗?成为发明家作为领导者的理念,有没有受到 Jeff Bezos 的影响?
Ethan Evans: 关于这点我可以说几点。首先,我知道你采访过我的前老板 Bill Carr,他写了《Working Backwards》(逆向工作法)。我不知道他有没有跟你分享过,那本书出版之后,他实际上意识到有一个更好的书名。他希望当时把书叫做《The Invention Machine》(发明机器),因为 Jeff 在 Amazon 想做的事情就是创建最具创造力的公司——一家能系统性地在发明上超越其他公司的企业。所以虽然《Working Backwards》是一个很好的书名,但 Bill 和 Jeff 觉得应该叫它《The Invention Machine》。
系统性地发明创造
Ethan Evans: 我加入 Amazon 的时候,并不认为自己是发明家,但我看到我们有这些领导力原则——Think Big 和 Invent and Simplify——在不断推动这一点。我当时就想,“我有麻烦了,我不知道该怎么做。“于是坐下来认真思考这个问题:我该怎么办?这似乎是必需的能力。最终我找到了系统性地发明创造的方法。以一个衡量标准来说,我现在拥有超过 70 项专利,它们全部是在 Amazon 的 15 年间创造的。
要做到这一点,其实发明创造并没有那么难。我也教过这方面的内容。要系统性地发明,首先你需要对你想发明的领域有一定的专业素养。Lenny,如果咱俩说,来,我们一起发明抗癌药物,问题是据我所知,咱俩都不是生物学家或医生。我们没有合适的背景,不知道自己在做什么。所以大概只能对着一浴缸的化学品瞎碰运气,结果多半不会太好。所以你必须是一个有一定知识储备的专家。
但第二件人们不做的事情是,他们不会花专门的时间真正去思考。他们觉得,“灵感自己会找上门来。“而我想发明的时候,会远离所有电子设备,带着我要解决的问题走进一个房间,强迫自己真正集中注意力思考:我知道什么?我能怎么发明?最直接的发明方式,不是凭空想出某个全新的东西,而是把两个已有的东西组合在一起。
我经常举的一个例子是,我有一项为 Amazon 设计的无人机配送专利。但无人机不是从仓库起飞的——而是一辆没有车顶的卡车在社区里缓慢行驶,无人机在卡车和各户之间来回穿梭。相比司机在每家每户门前停车,你可以让四到六架无人机覆盖整个社区的所有住户。
我想到这个主意的过程是这样的:有一天我在思考无人机和配送的问题,同时我酷爱军事历史,所以也在想航空母舰。我就想,有没有办法做一个无人机的航空母舰?顺着这个思路,很快灵光一现——卡车不就行吗?
于是我有了这项专利。我们还没有看到它成为现实,我在等我的想法成为 Amazon 无人机配送系统的一部分,但我相信最终会的。
Lenny: 太酷了。我在想退货也可以送回卡车上——用那个绳索装置,上面有个小钩子把无人机捕获回来。
Ethan Evans: 没错。同样的道理。你想退货的时候,不用再拿到 UPS Store 之类的地去,直接放在门廊上,然后在手机的 app 里操作一下——也许拍张照片让无人机识别包裹,或者放在指定位置——按一下按钮,无人机就把你的退货带走了。完全没问题。
Lenny: 迫不及待了。有时候还能顺便把你的狗送出去兜一圈。
Ethan Evans: 我的狗太重了,谢天谢地。
Lenny: 我的可不重。我们家后院有只猫头鹰,我们有时候担心它会把我们的狗抓走。“发明”这个话题真的很有意思。我本来没打算聊这个,但对于比如一个团队里的 PM,想要在发明、创新、宏大思考方面变得更强,你有没有觉得什么做法特别有用?是比如说留出两个小时,拿上纸笔,去想两个相邻的东西怎么组合?
Ethan Evans: 留出专门的时间确实是这个过程的一部分。但有趣的是你其实不需要那么多时间。两个小时很好,但你只需要每个月拿出两个小时一次就够了。人们以为发明需要花大量时间。关键在于,一旦你有了一个好点子,表达和实现它往往要花好几年。
你当初有了做 newsletter 的想法。我了解你 newsletter 的一些历史,你已经为这个想法的表达和实现努力了好几年了。Jeff 和 Amazon 有过这样的想法,“我们做 Prime 配送吧。“而 Prime 至今还在不断完善、持续迭代——这是一个二十多年的老想法。Kindle 也已经是一个十年前就有的想法了,至今仍在不断改进。
所以这里的要点是,你不需要很多好点子就能被认为是极具创造力的发明家。比如 Elon Musk,Tesla——他基本上可以拍拍手说,“我现在是一个爱迪生式的发明家了。“他还在继续发明,但你并不需要那么多发明。
发明之后的优化
Lenny: 这让我想到 Jeff Bezos 在播客里提到的另一点——他的大部分创新和工作其实都在优化阶段。不是”我有个点子”那一刻,而是让它更便宜、更好、更快。大部分好的成果都来自这个阶段。拿 Tesla 来说,Elon 有了这个想法,之后真正困难的工作是让它可规模化、让大众用得起,而不只是一辆电动汽车。
Ethan Evans: Jeff 说发明实际上很大一部分是渐进式改进和优化,我完全同意这个观点。要做好发明,你需要一个基础想法,但大量工作是让那个想法变成现实。
Prime 就是一个很好的例子。Amazon Prime 项目很好地说明了这一点:好,我们想要快速免费配送,我们想要这个会员计划——那是一次性的想法,他们确实把它建出来了。但之后 Prime 不断扩大——最初是美国两日达,然后美国一日达,现在美国当日达。但他们还加入了 Prime Video、Prime Music、Prime Gaming。实际上你免费获得的 Prime 权益大约有 25 项,大多数人根本不知道——比如免费的照片存储,这个列表还在不断增加。所有这些都是渐进式的优化,让它变得更好、更好、更好、更好。当然 Jeff 的目标——你可能听他说过——是让 Prime 变成一个不用犹豫的选择,让你觉得不加入会员简直是不负责任。
面试中的制胜之道
Lenny: 我知道你有一个特别精彩的 Jeff Bezos 的故事,我很想聊到那部分,但在那之前,顺着职业建议和职业发展这条线,再问一个问题。我在某处读到过,你职业生涯中面试过超过 2500 人。那么回到职业的起点,至少在找工作这个环节,你发现什么最能帮助候选人在面试中脱颖而出、最终拿到 offer?对于那些正在经历面试过程的人,你有什么建议?
Ethan Evans: 有很多证据表明,任何面试中排名第一和第二的因素是外表和热情。这不是说你必须长得好看,而是你要表现出对这个职位有兴趣,别穿着睡衣去面试。最重要的是,要有热情。人们想和那些想跟他们共事的人一起工作。所以如果你表现得对公司充满审视和评判,好像在说”你得说服我”,你就会让他们反感。我对待每一场面试的态度是:不管我是不是真的想要这份工作,即使我已经决定不要了,我仍然想要拿到 offer。
所以我参加任何面试,都会投入地表达我有多兴奋能参与这个机会,以及我对这家公司的了解。超越这些表面因素之外,我看到最大的问题——尤其在更高级别——是人们谈论自己做了什么,却不谈为什么这件事重要。他们不谈影响力。
领导力是影响力,不是工作量
Ethan Evans: 你看,领导者招人不是为了让人干活。他们招人是因为自己有问题或需求需要解决。所以如果你能展示说:“看,这些是我做过的事,它们产生了实质性的影响。这些是我为前雇主做的、真正带来改变的事情。“——这就不是”我做了工作”,那只是工人。有影响力的人才更像领导者。
“领导者”不一定意味着带团队的管理者,而是一种更高的层级——我做了某件解决重大问题的事,而且能说清楚它如何改变了公司或客户的局面。我在面试中寻找的就是这一点:你能否让我看到你对业务的理解、对业务的贡献,还是只是在告诉我你有多努力?
Lenny: 很好。关于你说的第一点——热情和专业形象,现在大多数面试应该都在 Zoom 上进行了——在这两方面,你有没有发现一些人们可能没想到的要点?
Ethan Evans: 有的。要向对方展示你全程全神贯注。所以除非真的别无选择,不要在车里参加面试,不要关掉摄像头。眼神交流仍然很重要,肢体语言仍然很重要。像我现在的手势——这些都是你表达的一部分。
要完全投入,试着透过镜头传递出”我很高兴参与这件事,我珍惜这个机会”的感觉。我经常告诉别人,面试最好的准备方式也许是一晚好觉加一壶咖啡——保持全神贯注和精力充沛是一个巨大的杠杆。
Lenny: 很好。我想这里的核心反馈就是:不要过度纠结内容。你呈现自己的状态本身就有很大价值。
Ethan Evans: 对,百分之一百。
搞砸了 Jeff Bezos 的发布
Lenny: 现在我们来走一趟”失败角”。这是我在播客上越来越多做的一个环节——聊聊人们职业生涯中的失败和收获。据说你有一个精彩的故事:搞砸了伟大的 Jeff Bezos,然后活下来讲了这段经历。能分享一下吗?
Ethan Evans: 当然。这既是我职业生涯的高光时刻,也是低谷时刻。那时我在 Amazon 大约六年了,已经升到总监,负责上线 Amazon 的应用商店。
我们当时在做一个基于 Android 的应用商店,要上 Google 手机,最终也要上 Kindle 平板。我们到了发布当天。那时候,Jeff 习惯为每个新产品写一封公开信。他会写一封”亲爱的顾客们,今天 Amazon 很荣幸地推出某某产品,它有这些出色的功能,希望你们喜欢。谢谢,Jeff”的信。我们会撤下 www.amazon.com 上所有的促销内容,那封信会占满整个屏幕。
他已经写好了一封 Jeff 信,而这封信重点推荐了我们产品中一个他特别喜欢的功能——一个让我们的产品有点与众不同的东西。
具体来说,我们有一个叫”Test Drive”的按钮,点击之后会在浏览器的模拟器中打开应用,这样你可以先体验、交互一下,再决定是否装到手机上。他觉得这非常酷,对此非常兴奋。
我的团队搭建了所有技术。Test Drive 是可以跑的。想想看——模拟成千上万个不同的应用——这在技术上是有难度的。我们通宵工作来准备发布,但到了早上六点还是不太行,我们还在调试。
你很了解工程师。我猜你的大多数听众也了解工程师,即使这不是他们的专业领域。我们总是觉得自己离找到最后一个 bug 就差一点点。
大约早上六点十五分,我收到了 Jeff 的消息:“嘿,我醒了,信呢?“因为信本该在六点上线——正好是纽约股市东部时间九点开盘之后。他说:“信呢?“我回复说:“嗯,我们还在处理几个问题。“而我脑子里想的是:“去洗澡吧,去洗澡吧。我只需要二十分钟,去洗澡吧。”
Lenny: 让 Jeff 去洗澡。
Ethan Evans: 对。三十秒后我就收到了回信:“什么问题?“到这个时候我不得不开始解释。我解释说我们在数据库方面遇到了问题,正在调试这个数据库问题。他说:“等等,你们的设计里有数据库?我们正在努力淘汰所有 Oracle 数据库,迁移到 AWS。你们为什么会有这个?“他越来越沮丧、越来越生气。
他开始抄送我的老板,还有我老板的老板——Jeff Wilke,零售业务的 CEO。他们也开始问我问题。就这样雪球越滚越大。到了早上七点半,Jeff 明显很愤怒。其他的人也陆续醒来,觉得”Jeff 生气了,所以我的任务就是比他更生气”——就这样一股脑地砸向我。
Lenny: 天哪。
Ethan Evans: 那么我做了什么呢?有意思的是——当未来的世界首富生你气的时候,你该怎么办?他当时还不是世界首富,但正在朝那个方向走。
我做的第一件事是承担责任。我说:“是的,系统没有正常运行。这是我的责任。我来处理。“我主动承担了所有权。第二件事是开始非常主动地向他更新进展:“现在的情况是这样的。“八点整:“目前确切的状态是这样,接下来一小时我们准备这样做,您下次收到更新的时间是这个点。我会在九点再次更新您。这是我们的计划。”
虽然 Jeff 已经对我有些失去信任——系统挂了,不对劲,他很生气——但既然他认可了这个计划,他还是愿意给我六十分钟。然后我会再次更新:“好的,这是我们做了的,这是我们接下来要做的,我们会在十点再次更新。“就这样一小时一小时地争取时间。
Ethan Evans: 我做的另一件事——这也是 Amazon 好的一面——随着越来越多的领导被抄送进这条愤怒的邮件链,他们开始通过私下渠道联系我,说:“我们都经历过 Jeff 的’索伦之眼’,知道那有多难受。我们能帮什么忙?“基本上是 Andy Jassy 的团队,也就是当时的 AWS,以及他的 CTO,一位叫 Werner Vogels 的人,说:“你们遇到了数据库问题,我们派 AWS 数据库团队的几位 Principal Engineer 过去帮忙。”
这些 Principal Engineer 大概上午九点到了,看了我们的设计。我们在数据库使用上犯了一些根本性的错误,他们说:“修复太复杂了。我们直接给你 500 台 AWS 机器,这样你那个糟糕的设计也能跑起来。这是临时解决方案。“我心想:“好吧,如果你是 AWS,手头恰好有 500 台数据库服务器闲着,这确实是个好方案。“他们就真这么干了。
修复问题与 Jeff 的持续不满
下一步就是修复问题。我们一群人非常努力地协作,把问题全部解决。这花了整整一天时间,而 Jeff 仍然很沮丧,因为通过发布他的公开信来控制舆论和媒体叙事的时机已经错过了。人们已经注意到了我们的上线,相关报道也发了出去,所以 Jeff 依然非常生气。
我们修复了问题,但 Jeff 对我们已经失去了信任。周末过去了。他在使用系统,找 bug,因为他觉得:“这个团队现在不可靠。Ethan 不可靠。我最好自己检查。“于是你面对的是 CEO 在亲自检查你的工作。
他发现了一个问题,大概周六晚上九点给我发邮件说:“我在做这个操作,结果出错了。“幸运的是,我到九点半就能确切告诉他发生了什么。接下来的故事是,那一周之后,我因为另一个议题和他有一个会议。
当面面对
我当时是一个小组的成员,正在研究如何构建一个竞品浏览器。你可能不记得了,但 Amazon 曾经有一个叫 Silk 的浏览器。我被邀请参加这个会议,但我不是关键参与者。你可能知道 Scrum 中的一个说法,有些人叫”猪”,有些人叫”鸡”,“鸡”基本上是观察者。我在这个会议里就是一只”鸡”,而这个比喻恰巧很贴切,因为当时我在想:我要不要”鸡”一下——不去了?我可以跳过这个和对我生气的 CEO 一起参加的会议。但当我产生这个念头时,我意识到:如果我连面对 CEO 都做不到,那我最好收拾东西走人。到此为止了。
于是我提前到了会议室。Jeff 总是坐在同一把椅子上,所以我知道他进来会坐哪里。我就坐在他椅子的旁边,心想:“不知道会怎样,走着瞧吧。”
会议进行中,当然,在我心里 Jeff 完全在无视我,连看都不看我一眼。但我想那可能只是我自己的投射,因为要记住,我本来就不是会议的核心人物。
会议结束时,大家都起身准备离开。他转过头来看着我说:“你最近怎么样?我猜这周挺难熬的吧。“我心想:“哦,好吧,我们要聊聊了。“我说:“是的,“我就那样回答他:“当然很难,但这是我们正在做的,这是我们将来要做的。“我们进行了一次非常人性化的对话。我不认为 Jeff 会忘记我让他失望了这件事,但很明显他已经原谅了。
所以我仍然需要——后来也确实如此——重新赢得他的信任。但我做的那个关键举动,值得人们学习的是:发火很容易。他一直在对我发火,写愤怒的邮件。愤怒的邮件很容易。坐在离某人三英尺远的地方,当面对他生气,这很难。当他面对选择——要么对这个向他汇报的人开始咆哮,要么说句友善的话——他选择了说句友善的话,而那重建了我们的关系。
从失败中被提拔
这个故事的结局是:两年后,我被提拔为副总裁。所以,即使我在这个非常公开的上线中让 CEO 失望了,他确实对我非常生气,我重新赢得了信任,证明我学会了如何更可靠地发布、避免宕机的教训,然后我得到了晋升。
我分享这个故事,是因为我想让人们理解:如果我都能在公开场合辜负地球上最富有、最著名的发明家之一,然后还能被提拔,在 Amazon 以非常成功的方式结束我的职业生涯——那你从任何坑里都能爬出来。你只需要处理得当。
Lenny: 这是一个非常精彩的故事。这里面有很多我想提炼的教训。第一个就是,如果你陷入类似的处境,某个东西彻底失败了,我在你讲的时候记下的要点——第一,承认问题:是的,这是一个严重的问题,承担责任。也就是说,不要试图推卸。
第二,我对你做法的描述是我所说的”排定优先级并沟通”——你排定优先级:“这是我们需要做的,“然后沟通:“这是我们的优先事项。“我很喜欢你每小时更新的方式:“这是最新情况,这是最新情况。“让相关人员明白你在处理这件事,并且你会持续更新他们。我想象中最令人恐惧的情况之一是:我完全不知道现在是什么状况。那我就要直接介入开始微观管理了。
Ethan Evans: 你说得完全正确。我在试图阻止微观管理的介入。我在试图给他们一种感觉:“好吧,我相信这个计划,我可以再等一小时。“然后我可以再等一小时,因为那个团队看起来确实在认真推进。我在试图一小时一小时地重建信任,同时避免三四层管理层全部涌入开始”帮忙”。
Lenny: 然后我很喜欢你提到的另一个建议——当面见面,基本上就是尝试把事情转到线下处理,我知道你后来就是这么做的。但这一点真的很好:人很难在面对面的时候保持那种愤怒、暴躁和攻击性。人们会变得更像:“好吧,我明白了。我们一起来想办法解决。“太棒了。还有别的吗?这就是我总结的三个要点。就是如果你在现场遇到了那种情况,还有什么你觉得特别有帮助的吗?
Ethan Evans: 我的意思是,要快速努力地工作,对吧?你必须修复问题。我的团队通宵没睡。我不得不开始安排人员轮班回家睡觉。我们不得不调动所有这些支援。所以那是一个非常艰难的周末。
当你犯了错误,就得不遗余力地去修复,即使过程令人不适。再次强调,这不是说”现在是周末了,我的团队周一再干”的时候。如果那样的话,我早就被踢出门了,走的时候身后会留下漫画里 Wile E. Coyote 那种刹车印。所以我想说这很重要。这也是展现主人翁精神的一部分。
冒充者综合征与犯错的恐惧
Lenny: 这件事的另一个方面,是我在成长为更高级别管理者时经历了一段时间的东西——我有很严重的冒充者综合征,害怕一旦搞砸了,一切就会崩塌。人们会发现我其实并不知道自己在做什么,我并没有真正准备好承担这个级别的职责。所以有一种恐惧:犯一个大错,就完了。显然,你的经历就是一个巨大错误的例子,但对你来说并没有”完”。关于”你可以搞砸但仍然做得很好,即使错误到了这种程度”,你有什么体会可以分享吗?
Ethan Evans: 我觉得很多处于我这个位置的人可能就辞职了。他们会任由羞耻感……我只是有点犟脾气,心想:“没错,我搞砸了。但我知道我仍然是个好人,是个好员工。是的,我犯了错,但我会继续前进。“这个故事还有一个我没讲的部分,你可能会感兴趣——我提到过 Jeff Wilke 当时是 Jeff 的二号人物。Jeff Bezos 的二号人物,他也是我的越级上级。
在此期间,他亲自来到我们办公室,想跟我谈话。我的经理,一位副总裁,说:“Jeff,这是我的团队,我来负责。如果你有什么批评,对我说。你不应该直接找我的团队。“Jeff Wilke 对我老板说——他叫 Paul——“Paul,这是出色的领导力表现。我非常欣赏你这么做。请让开一下,我要跟 Ethan 谈谈。你做得很好,Paul。现在让开。“然后他把我严厉训斥了一顿。
这件事中还有个有趣的后续——当时我跟 Jeff Bezos 的会面进行得非常顺利,我十分得意,心想:“我接下来要去面对 Jeff Wilke 了。我要跟他约个会面,如法炮制。我已经摸清门道了。”
于是我去见 Jeff Wilke,打算故技重施。我要直视他的眼睛,一切就会被原谅。Jeff Wilke 看着我说:“Ethan,你上线的时候,知不知道自己在赌结果?知不知道可能会失败?“我说:“知道。我们有媒体的上线档期承诺,我认为瞄准日期比确保万无一失更重要。”
他说:“好,有两点。第一,你错了。你把日期置于声誉之上是错误的。你让 Amazon 在公众面前丢脸了,这是一个错误。“他说:“第二,至少你知道自己在赌。如果你连自己在赌都不知道,我们现在讨论的就是让你走人了。“我心想:“好吧。“我本来以为我是胸有成竹地走进这个会议,准备运行我的人际关系剧本。结果他在评估要不要留我。
那种犟劲儿体现在,即使他已经告诉我他曾考虑开除我,我的反应是:“但他最终没有。所以我就继续往前走。“这种固执——“没错我犯了错,但我不会活在羞耻中”——我想这是大家可以从我的经历中带走的。很多人觉得自己比实际状况更无可救药。
毕竟每个人都会犯错,对吧?Jeff 和 Fire Phone,那会成为他终身的一个污名。“Jeff 和 Fire Phone”将成为认识 Amazon 的人余生都会挂在嘴边的一句话。
Lenny: 对,我们在《Working Backwards》播客上讨论过这个话题,讨论为什么逆向工作法在 Fire Phone 上行不通,我们专门聊过。我喜欢这些话语在你的脑海中刻得如此之深,你能一字不差地回忆起来——
Ethan Evans: 嗯,那个时刻我在脑海中重演了很多次。
Lenny: 说到从坑里爬出来,你本质上是不是就是连续两年做出好成绩,那就是关键所在?
从莽撞到审慎
Ethan Evans: 不,我觉得我确实需要学习。我一直有点像个莽撞的操作者,意思是喜欢快节奏、大刀阔斧。我优先追求速度,而我确实需要退一步说:“好,Amazon 在这个层级和规模上不喜欢这种做法。“所以我给自己学了一句新话:敬畏纽约时报的头条。要意识到如果 Amazon 宕机了,它会立刻出现在所有新闻网站上。如果 Amazon 出了什么差错,华尔街日报和 CNN 都会报道。
所以作为领导者,我必须思考:我正在做的事情会不会成为纽约时报的头条?如果是的话,我最好格外谨慎。这就是我学到的——你不能被恐惧麻痹,但我教会了整个团队:我们不想因为错误的事情登上纽约时报。那就是教训。
Lenny: 说到教训,最后一个问题——你从当时的处理方式中有什么事后的反思?有什么你本应该改变、后来确实改变了的做法?显然不是……你提到了这个观点,不要承诺一个你没有把握的日期。我想问的是在这个方向上还有其他的吗?
惊喜发布的代价与对团队成员的关怀
Ethan Evans: 我有两点。第一,Amazon 过去非常喜欢惊喜发布。他们喜欢这个理念:我们安安静静、安安静静、安安静静。因为我认为这在某种程度上是对 Microsoft 的反应——他们觉得 Microsoft 总是预告即将推出的产品,然后一再推迟日期。所以就有了”雾件”这个概念。Amazon 想走另一条路:我们什么都不说,然后产品就在那里了。但我后来认识到,惊喜发布最大的问题是——被”惊喜”的是你自己,你不知道什么会出问题。
所以我转变了策略,开始做大量 beta 测试。即使其他人不完全同意,我也会说:“你们说得对,我们不做惊喜发布了。“我们的一些 beta 测试者,即使签了 NDA,也可能会泄露。但这比上线一个不能用的东西要好得多。这是第一个教训。
第二个教训是,在 Jeff Bezos 面前出故障的那个东西,最终追溯到一个刚毕业的工程师写的代码。他被单独留下来编写我们用户界面的一部分,但他的写法不具备可扩展性。而我们没有给他任何帮助或监督,让他独自工作,因为我们都忙于关注问题的其他部分。
灾难发生后不久,他离开了公司。我犯的错误是没有主动找到他,真正地安抚他:“没错,是你写的 bug,但这不是你的错。是体系让你失望了,我们不怪你。Bug 是会发生的。”
所以整个事情中我遗憾的是,没有意识到——即使团队里没有人对他吼叫或怎样——他知道那是他的 bug,而且他显然看到我和其他人挨了训。所以他离开了,我希望他没有那样做。我更希望我当时主动介入。我没有体会到他的感受。
Lenny: 有意思的是,这个教训不是”更早地发现那个人,注意链条中可能断裂的环节”,而更多是”在那个面临困境、可能被忽视的人身边,给予支持”。
Ethan Evans: 因为我们失去了一个优秀的人,而他可能为此感到非常难受。我们犯错时都会感到难受,这是无法避免的。但他承担了不该由他承担的责任,这一点我真的非常遗憾。
Amazon 领导力原则与 Ownership 的起草
Lenny: 这其实是一个关于主人翁精神的绝佳例子。你提到了 ownership 这个词,而这正好关联到……Amazon 有一套领导力原则,我想大概有 14 条。其中一条就是关于 ownership 的。据说你参与了这条原则具体措辞的制定,我觉得这在 Amazon 是一件非常重要的事。我想很少有人有机会参与定义、描述和表述这些原则。你能谈谈你贡献的这条原则,以及你是如何参与撰写的吗?
Ethan Evans: 在我看来,Amazon 现在大概已经进入了第四个版本——也许更多——但在其超过 25 年的历史中,领导力原则经历了第四次重大修订。
Ethan Evans: 当从第一版过渡到第二版时,Jeff 和他的领导团队坐在一起商讨。实际上在第一版中,有三个不同的列表——领导力原则、核心价值观,还有一个我不记得是什么了。他们觉得,“三个列表太蠢了,合成一个吧。”
Ownership 这个词原本是其中一个列表的一部分,但当合并所有内容时,它被拿掉了。我之前提到的那位 Jeff Wilke,公司的二号人物、零售业务负责人,把他手下的一批总监召集起来,在一次会议上拿出了拟定的新列表,说:“这是新版的拟定稿,你们有什么意见吗?“我们围坐在一起讨论,说:“Ownership 呢?Ownership 不见了。“于是我们跟他说,“你看,Ownership 不见了,我们认为它应该在。“他说:“那你们拟一个草案吧。”
于是我们大约六个人坐在一起,粗略地起草了一份我们认为 Ownership 应该怎么写的文案。我提出了那六个词——“An owner never says that’s not my job.”也许这是七个词。
我把这段具体的措辞作为草案的一部分提了出来,然后我们发了出去。几个月过去了,没有任何消息。然后有一天,领导力原则正式公布了,Ownership 重新回来了。内容经过了修改,但”An owner never says that’s not my job”这句话保留在了领导力原则中,并且一直延续至今。
而我最喜欢这一点的地方在于,Amazon 有一百五十万员工以这些领导力原则为准则,这可能是我写过的最有影响力的文字了。
Lenny: 哇,所以这七个词是你写过的最有影响力的文字。我很喜欢,完全能理解。我正在看这些原则,这句话正好出现在那条原则的末尾。我们会在节目备注中附上这 14 条领导力原则的链接。还有没有其他你特别喜欢的原则?一两条?可能很难挑出最喜欢的。
Bias for Action(崇尚行动)
Ethan Evans: 我是 Bias for Action(崇尚行动,Amazon 领导力原则之一)的坚定支持者。Bias for Action 说的是速度在商业中很重要,而且很多决策是可逆的,因此加快行动很重要。
我认为人们不理解的是,在竞争环境中,做对了是好事,但速度快才是必要条件。因为如果有十个创业团队在做同一个想法,其中一些会赌一把,赌错了就倒闭。但也有一些会赌一把,早早下注并且赌对了。如果你不快速行动,就会被那些可能只是运气好的人打败。
所以你必须建立一套重视速度的流程,重视”今天能做什么?今天能承诺什么?“所以我非常喜欢 Bias for Action。当然,这也正是我给 Jeff 惹麻烦的原因,对吧?我愿意冒险。所以它需要平衡,但这是我的另一个最爱。
Lenny: 说起来,Jeff Bezos 接受 Lex Fridman 采访时谈到过,他对 Blue Origin 的思考方式不同于 Amazon——Amazon 的核心目标和差异化在于 Customer Obsession(客户至上)。而对于 Blue Origin,他希望核心是果断(decisiveness),基本上就是全面倾向于这种 Bias for Action,这确实很有意思。
Ethan Evans: 我看了那段采访,心想,“说得完全正确。“因为话说回来,火箭会爆炸,上面还有人。你必须把事情做对,但你也必须持续前进,因为总是还有更多的安全测试可做。你怎么平衡?
Lenny: 是的,很有意思。在火箭领域选择这条原则——全面往前推进的那种——确实很大胆。回到 Ownership 这条原则,你基本上建议了这句话,然后”什么也没听到”,突然间它就成了整个体系的一部分。他们从来没跟你说过,或者我不确定他们有没有给你署名,还是说,不,觉得挺好的?
向上影响与原则的逐字推敲
Ethan Evans: 是的,我甚至不会主动邀功,只是我保留了一封邮件的副本,上面写着”Ethan 认为应该写某某”。我有书面证据。因为这不是为了功劳,那些话被保留下来,我非常高兴和自豪。但在 Amazon,我怀疑 Jeff 是否知道那些话是我写的。我从来没去跟他说过,“嘿,你知道吗,你保留了我的话。“那不合适。这只是个有趣的轶事。
不过这确实说明了——我想人们可以从中学到一些东西——如果你的想法足够好,你可以在公司里向上产生很大的影响力。而且,当我们提出质疑的时候,Jeff Wilke 是一个有强烈主见的领导者,不一定总是喜欢被挑战。
所以当我们最初告诉他”我们认为你漏掉了 Ownership”时,他的反应类似于,“你是说整个 S Team(高级管理团队)连领导力原则都写不对?“不完全是原话,但他的态度很明确,“这真的有必要吗?你们为什么觉得有必要?“他让我们自己写,某种程度上是在说,“如果你们这么确信它好,那就证明给我们看。“但同样,我很固执,我说,“好,我们来写。“然后我们真的写了。
Lenny: 这挺逗的。先说”大家对这事提提意见”,然后你真提了意见他又不乐意——这不是一个很好的领导力示范。
Ethan Evans: 嗯,是的。毕竟一群总监去点评比自己高两级的领导的工作,他确实想要我们的意见,但当我们真的指出问题时,他又本能地抵触,因为那毕竟是他自己的”孩子”。
Lenny: 本来不太可能有什么重大遗漏,结果还真有一个。
Ethan Evans: 是的。
Lenny: 关于这些原则,可能很多人不知道,Disagree and Commit 其实就来源于此,准确说是 Have Backbone, Disagree, and Commit(敢于直言、敢于异议并全力以赴,Amazon 领导力原则之一)。我们在播客中讨论《Working Backwards》(逆向工作法)时也谈过这个。我还很喜欢 Leaders Are Right a Lot(领导者在很多时候是对的)这条,它经常被提到。我很喜欢这个理念——要想成功,你需要真正做对。你不能只是展现自信,不能只是参加一堆会议、发布一堆东西,你需要真正做对才能成功。
Ethan Evans: 那条原则后来被修改了,措辞很讲究——你总想知道这些修改的历史,真希望能看到这些原则的编辑记录。那条被改成了关于”领导者积极努力去证伪自己的信念”的表述。
关键在于,它想要传达的理念是,你必须保持非常开放的心态,不断追问:“是的,我认为自己是对的,但有什么新的证据?我学到了什么?发生了什么变化?“事实上,它还说要寻求多元视角(seek diverse perspectives)。
这是对 DEI(多元、平等与包容)的一种微妙呼应——如果房间里的每个人都是五十岁的白人男性,你可能并没有真正为 Amazon 的客户群体做出正确的整体决策,你做的决策可能只适合住在西雅图郊区的五十岁白人男性。所以这些原则中的每一个词,在公司内部都经过了逐字推敲。
异见角(Contrarian Corner)
Lenny: 太棒了。好,让我们进入最后想花点时间聊的区域,叫做异见角(Contrarian Corner)。我很好奇,你有没有什么反主流的观点——基本上就是别人相信但你不太相信的东西,或者是你看到了很多人没看到的东西。有什么想说的吗?
Ethan Evans: 有的。我认为我目前最反主流的一点是关于重返办公室的浪潮。我这个层级的很多领导者公开表态支持需要回到办公室,甚至可能是全职回到办公室。
Ethan Evans: 我在这个问题上持反主流观点,原因在于创新。具体来说,我查过——你可以在维基百科上核实——历史上第一栋专门建造的办公楼,于 1726 年建于伦敦。也就是说,我们在学习如何善用办公室这件事上,已经有大约 300 年的历史了。
这意味着办公室不会再有太大的改善空间了。你能想到的办公室领域最近一次重大改进是什么?你可能会说开放式办公,但很多人认为那甚至算不上一个好主意——那些大排的工位和嘈杂的开放式区域。
而远程办公呢,我们只是从疫情开始才真正大规模实践了几年,充其量从互联网诞生算起也不过 20 年。哪一个更有改进空间?远程工作中有太多东西我们还没有探索过。那些说”回到办公室吧,因为我们知道它有效”的人——我们确实知道办公室是什么样的,但我对远程体验的改进潜力抱有远得多的信心。所以我认为,长远来看,远程办公终将胜出。
握手经商
另一个我非常反主流的地方是握手做生意。我理解公司需要律师,我自己在某些事务上也有律师。但我做教练——我辅导的大多数人之间没有任何 NDA(保密协议),没有任何合同。他们通过 PayPal 付款,我给他们做好辅导。
我认为这个世界上太多事情被合同驱动了,我们丢掉了”一诺千金”的理念——你其实可以信任我会履行承诺。在这点上我是反主流的。
我知道我偶尔会被辜负,有人会做出让我失望的事。但我觉得当我们总是提防别人的时候,那也是一种高昂的代价。另一个我持反主流观点的地方就是凭信任做生意。
Lenny: 这让我想到,Sam Altman 也有类似的哲学——信任别人,假设一切都会没问题。有时候你可能会吃亏,但总体而言,这对你和身边的人都要好得多。
Ethan Evans: 我不知道 Sam 说过这个,但我非常认同。
Lenny: 对,虽然他最近也遇到了一些挑战。我不知道这个策略对他来说效果如何,但最终结果对他还不错。不管怎样——我们终于到了令人期待的闪电问答环节。在此之前,你还有什么想补充、想分享,或者想留给听众的吗?
Ethan Evans: 没有了,我真的很享受这次对话。我可以永远聊职业发展这个话题,我很喜欢聊这些,但我觉得我们今天已经涵盖了大量能真正帮助到人们的内容。我这边没什么了,来吧,进入闪电问答。
闪电问答
Lenny: 好。那我们正式进入令人期待的闪电问答。准备好了吗?
Ethan Evans: 准备好了。
Lenny: Ethan,你向别人推荐最多的两三本书是什么?
Ethan Evans: 两三本书。我排第一的推荐是一本叫《Decisive》的书,作者是 Chip 和 Dan Heath,讲的是做出更好决策的科学。我之所以如此推荐它,是因为它不仅能让你的职业更好——因为领导者就是做决策的人——还能改善你的个人生活。实际上我在个人生活中应用它的频率至少和在职业生活中一样多。
我第二常推荐的书是《Leadership and Self Deception》,知名度远不如《Decisive》,读起来也稍微难入门一些。它由一个叫 Arbinger Institute 的研究小组写的,讲的是自我欺骗——我们自己造成了很多人际问题,却把责任推给别人。书里逐步分析你如何成为了你与他人问题的参与者,以及你能做些什么。
第三本,也是最后一本,是最近和我一起工作、你也认识的 Jason 推荐给我的。那本书是《The Almanack of Naval Ravikant》。Naval Ravikant 是一位天使投资人,也是 AngelList 的创建者。
我喜欢这本书的地方在于他有一套方法。他真正把”如何在热爱你所做的事情的同时获得成功”提炼了出来。他说,“没有人能成为比你更好的你。“不要试图模仿我——“我要像 Ethan 那样”或者”我要像 Lenny 那样”。相反,找到你独特地最擅长、最热爱的事情,因为没有人能复制”你做自己”。这就是你职业生涯中具有防御性的价值。我非常喜欢这个思维模型。
Lenny: 对,Naval 有很多深刻的见解,你可以在他的 Twitter 上看到这些内容。我们会附上他的 Twitter 链接,有人基本上把他的推论编成了一本书。他真是个有趣的人。
Ethan Evans: 没错。
喜爱的影视、面试题与产品
Lenny: 好。你最近最喜欢的电影或电视剧是什么?
Ethan Evans: 我在农场长大,所以 Taylor Sheridan 的所有作品——《1923》、《Yellowstone》以及他出的所有剧集——我们全都看了。不过我们也会笑,觉得——你了解《Yellowstone》吗?
Lenny: 当然。死了很多人。
Ethan Evans: 对。有一次我和我妻子在看的时候开始打赌——这一集开始,这集会死多少人?一个蒙大拿州的牧场,但不知怎的他们总是在杀人。这怎么搞的?
Lenny: 我听得出来,你的生活就是这样的。你最喜欢问候选人的面试问题是什么?
Ethan Evans: 我最喜欢的面试问题是:“讲一个你需要与你的管理层意见不一致的例子——一个你需要站出来对抗更高层领导或掌权者、为一个立场据理力争的时候。“因为我觉得这真的很难做到。我面试的通常是领导者,我觉得身边全都是只会说”是”的人并不有益。你需要有人——正如你所说的——Have Backbone, Disagree, and Commit(敢于直言、敢于异议并全力以赴)。所以那正是我通常在寻找的东西。
Lenny: 好。你最近发现的最喜欢的产品是什么?
Ethan Evans: 说来有点傻,但我最近发现的最喜欢的产品是 Chuckit!——就是那种帮你把球甩出四分之一英里给狗捡的工具。它基本上延长了你的手臂。把球送到比你所能投掷的距离远得多的地方,真的很好玩。你会觉得自己很厉害——“哇,看看我,我是大联盟投手。“因为我有了这个三英尺长的杠杆臂,而且我懂物理。至于科技产品的话,我喜欢的太多了。说 ChatGPT 之类的太容易了,所以我就不往那个方向说了。
人生信条
Lenny: 好的。我的狗不喜欢追球,所以我没有理由买那个东西,但我从没想过单纯享受把球甩得很远的快感。你有没有一个经常回来的人生座右铭——常常分享给别人,在工作或生活中觉得有用的?
Ethan Evans: 我碰巧是一名基督徒,我思考最多的一句座右铭是:“多给的,向他多要。“所以我经常思考我的社会责任是什么。
我一直非常幸运。我在俄亥俄州的一个农场长大——不过我不是农场男孩,我父亲是化学家。我在中上阶层的环境中长大,最终获得了极大的成功,能够在 50 岁退休去做教练和教学。我亏欠什么,需要怎么回馈?所以这些话虽然出自古老的灵性文本,但它们是我最常铭记在心、反复思考的——我的责任是什么?
Lenny: 作为一个”被给予了很多”的人的例子——而且因为如此努力工作——Jeff Bezos 正在创办太空公司,你知道的。如果有机会去太空,你会去吗?
太空梦与回馈
Ethan Evans: 我当然看过他的采访,他谈到了对安全问题的思考,以及他不得不和母亲进行的那次谈话。我想去太空。但我觉得目前的票价太高了,不愿意支付那个价钱。不过我愿意承担风险。那次飞行的风险有多大?百分之一、五十分之一,甚至更高的概率回不来。我大概会赌一把。
Lenny: 所以你会是一个早期接受者?在那条曲线上你会处于什么位置——早期接受者,还是落后者?
Ethan Evans: 我年纪够大,还记得挑战者号航天飞机爆炸的时候。当时我说过我会坐下一班,我说,“他们绝对不会比下一班更小心了,所以我坐下一班。”
所以我觉得只要有机会我就会上去,因为那个机遇太珍贵了。不像 Jeff 声称他不害怕,我大概会非常恐惧,至少在发射的时候会。等你到了上面,就很棒了。出问题要么是在上升阶段,要么是在下降阶段,不会在中间。
结语与联系方式
Lenny: Ethan,我觉得我们这期节目会帮助很多人在职业发展上取得进步。我觉得会帮助他们走出失败的阴影,成为更好的 Owner。非常感谢你来参加节目。最后两个问题。想联系你的人在网上哪里可以找到你?顺便分享一下你现在做的事情,也许有人需要你的帮助。然后,听众怎样才能对你有帮助?
Ethan Evans: 在网上找到我的最佳地点是 LinkedIn,我所有的文章都发在那里,那里是专业社区的所在地。在 LinkedIn 上搜索 Ethan Evans 就行。我的账号名是 Ethan Evans VP,因为我做过副总裁。这是找到我的最佳途径。我确实有一个 Substack newsletter,也通过 Maven 平台授课,但所有这些链接都在我的 LinkedIn 上可以找到。
至于读者如何帮助我——他们给我写的内容留下评论,因为我总会遗漏一些东西。我只是一个人的视角。所以我实际上有一个流程:我收集人们写的所有评论、所有不同的视角、所有不同的例外或特殊情况或案例,这就是我提升自己思考的方式——我阅读每一条评论,然后思考,“好吧,我遗漏了什么?哪些地方我可以说得更好?如果我再次谈到这个话题,如何把这些融入进去?”
Lenny: 再给你一个机会推荐一下你现在做的事情——你帮助人们解决什么问题,也许有人觉得有价值?你说过你做教练,也有课程,具体是什么样的?
Ethan Evans: 我专注于两个主题。一是职业发展——如何在职业中划桨前行,整个魔法循环(The Magic Loop),以及如何获得晋升或获得新角色、加薪,如果那是你的目标的话。二是领导力。我教授一门非常受欢迎的课程,叫”Stuck at Senior Manager – Breaking Through To Executive”(卡在高级管理者——突破到高管层),讲的就是如何摆脱那种困住的感觉——“我工作非常努力,我做得还不错,我管理着 25 或 50 个人,但我怎么才能坐上那把大椅子?我怎么才能进入事业部级别的领导层?我需要改变什么?“这就是那个”把你带到这里的不会把你带到那里”(what got you here won’t get you there)的问题。而我最喜欢看到的就是人们在这方面取得成功。人们写信回来说,“我确实拿到了那个职位,我确实获得了晋升,我确实得到了加薪,“这就是我的满足感。
Lenny: 太棒了。Ethan,非常感谢你来参加节目。
Ethan Evans: 谢谢你,Lenny。我得说,你非常擅长做这个。你非常流畅,采访做得非常好。真的很荣幸。
Lenny: 非常感谢你的称赞,你也是。谢谢大家。再见。
Ethan Evans: 再见。
Lenny: 非常感谢收听。如果你觉得这期节目有价值,可以在 Apple Podcasts、Spotify 或你最喜欢的播客应用上订阅。也请考虑给我们评分或留下评论,因为这真的能帮助其他听众找到这个播客。你可以在 lennyspodcast.com 找到所有往期节目或了解更多关于这个节目的信息。下期再见。
术语表
| 原文 | 中文 |
|---|---|
| Andy Jassy | Andy Jassy |
| AngelList | AngelList |
| app store | 应用商店 |
| Arbinger Institute | Arbinger Institute |
| beta testing | beta 测试 |
| Bias for Action | Bias for Action(崇尚行动,Amazon 领导力原则之一) |
| Bill Carr | Bill Carr |
| Challenger | 挑战者号(航天飞机) |
| ChatGPT | ChatGPT |
| Chip and Dan Heath | Chip 和 Dan Heath |
| Chuckit! | Chuckit! |
| Contrarian Corner | 异见角(Contrarian Corner) |
| Customer Obsession | Customer Obsession(客户至上,Amazon 领导力原则之一) |
| Decisive | 《Decisive》(决断力) |
| DEI (Diversity, Equity, and Inclusion) | DEI(多元、平等与包容) |
| executive coach | 高管教练 |
| Fire Phone | Fire Phone |
| Have Backbone, Disagree, and Commit | Have Backbone, Disagree, and Commit(敢于直言、敢于异议并全力以赴,Amazon 领导力原则之一) |
| IC (Individual Contributor) | IC(个人贡献者) |
| imposter syndrome | 冒充者综合征 |
| Invent and Simplify | Invent and Simplify(发明与简化,Amazon 领导力原则之一) |
| Jeff Bezos | Jeff Bezos |
| Jeff Wilke | Jeff Wilke |
| Leaders Are Right a Lot | Leaders Are Right a Lot(领导者在很多时候是对的,Amazon 领导力原则之一) |
| Leadership and Self Deception | 《Leadership and Self Deception》 |
| leadership principles | 领导力原则 |
| Lex Fridman | Lex Fridman |
| Marshall Goldsmith | Marshall Goldsmith |
| Maven | Maven(在线教学平台) |
| Naval Ravikant | Naval Ravikant |
| NDA | NDA(保密协议) |
| New York Times | 纽约时报 |
| newsletter | newsletter(通讯/邮件订阅) |
| Oracle | Oracle |
| Owner | Owner(Owner,Amazon 文化中的”主人翁”概念) |
| PM | PM(产品经理) |
| Prime Gaming | Prime Gaming |
| Prime Music | Prime Music |
| Prime Video | Prime Video |
| Principal Engineer | Principal Engineer(首席工程师) |
| rapport | 默契 |
| S Team | S Team(高级管理团队) |
| Sam Altman | Sam Altman |
| Scrum | Scrum |
| SDE (Software Development Engineer) | SDE(软件开发工程师) |
| Silk | Silk(Amazon 浏览器) |
| skip level | 越级上级(skip level) |
| social engineering | 社会工程学 |
| Stuck at Senior Manager - Breaking Through To Executive | Stuck at Senior Manager – Breaking Through To Executive(卡在高级管理者——突破到高管层) |
| Taylor Sheridan | Taylor Sheridan |
| Test Drive | Test Drive(试驾,应用试玩功能) |
| The Almanack of Naval Ravikant | 《The Almanack of Naval Ravikant》 |
| The Invention Machine | 《The Invention Machine》(发明机器) |
| The Magic Loop | 魔法循环(The Magic Loop) |
| Think Big | Think Big( Think Big,Amazon 领导力原则之一) |
| UPS Store | UPS Store |
| vaporware | vaporware(雾件) |
| Wall Street Journal | 华尔街日报 |
| Werner Vogels | Werner Vogels |
| What Got You Here Won’t Get You There | 《What Got You Here Won’t Get You There》 |
| Working Backwards | 《Working Backwards》(逆向工作法) |
| Yellowstone | 《Yellowstone》 |
此文档由 AI 分片翻译(translate_long_document)