Amazon VP: Questions On Corporate Politics But They Get Increasingly Darker | Ethan Evans

Amazon VP: Questions On Corporate Politics But They Get Increasingly Darker | Ethan Evans — Ryan Peterman

Ryan Peterman

AI-assisted summary of Amazon VP: Questions On Corporate Politics But They Get Increasingly Darker | Ethan Evans — original source. Check the original for full context.

Source published:

Detailed notes

## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=0s) Introduction and The Darkening Arc of Corporate Politics

The episode opens with a chilling teaser quote from Ethan Evans, former Amazon Vice President: "I'll find another way to come around HR and make your life miserable." Ryan Peterman welcomes Ethan back for a third appearance on the show, framing the discussion around common workplace scenarios that grow increasingly morally gray and adversarial. When Ryan presses Ethan on whether he ever had to burn someone to get ahead, Ethan is unapologetic about the reality of top-tier corporate life: "It is still a mind game and a competition. I'm allowed to win." From Jeff Bezos tearing into Ethan during an annual review for empire-building to the ethical dilemma of whether lying is optimal in high-stakes environments, the conversation does not pull punches. As Ethan remarks before diving in: "This hole has no bottom. Let's go."

Ryan lays out the broader thesis that inspired this line of questioning: rapid advancements in AI models mean that technical tasks are increasingly automated. If AI handles the direct technical execution, the relative weight of non-technical skills—communication, maneuvering, and soft skills—expands dramatically. Furthermore, if automation leads to fewer tech roles overall, the same number of ambitious professionals will be fighting over a shrinking pool of positions, inevitably intensifying corporate politics. Ethan fully embraces the challenge: "Sometimes life is dark, so let's go for it."

[02:16](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=136s) Securing Credit in Collaborative Environments

Ryan introduces the first dark scenario: when working collaboratively on a high-stakes project and multiple peers are jockeying for visibility, how do you make sure you actually get credit for your contributions? Ethan points out a counter-intuitive reality of corporate life: it is far easier to claim credit after the fact than in the immediate, heat-of-the-moment aftermath. In real time, everyone is hypersensitive about ownership. By contrast, looking back years later, claims become cemented in narrative. Ethan illustrates this using his own career: he often states that he helped start Amazon Prime Video or was the first engineer on Prime Video. While others were certainly in the room that day, they are not present to dispute it now, and at most, someone might leave a comment on a YouTube video saying, "Hey, I was there, too."

To capture credit when a milestone happens, Ethan emphasizes that the single most effective tactic is to be the first person to speak up and broadcast the milestone. Speaking first does not mean lying or erasing teammates; one can deliberately use the word "we" and name collaborators:

```mermaid flowchart TD accTitle: Communication Dynamics for Claiming Credit accDescr: Contrast between speaking first versus reacting, showing how credit is captured.

subgraph FirstMover["First to Speak (The Announcer)"] A["Announce Launch: 'We shipped this!'"] --> B["Acknowledge Team: Ryan, Fred, Sarah, Rajeev"] B --> C["Result: Speaker captures the lion's share of recognition"] end

subgraph FastFollower["Second to Speak (The Color Guy)"] D["Peer already sent the announcement"] --> E["Reply-All with Technical Context"] E --> F["Claim Specific Piece: 'I had fun building the algorithm that doubled sales'"] F --> G["Result: Secures individual contribution without conflict"] end ```

The speaker naturally captures the lion's share of executive attention, even when graciously sharing it in the text. If someone else beats you to the announcement, silence is fatal. You must chime in as a fast follower to stake a claim on your exact contribution—for example, responding with enthusiasm about how much fun it was to build the specific algorithm that doubled sales. "What doesn't work is be silent and hope your part will be noticed. That's what never works."

[04:40](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=280s) Managing Upward Reporting and Playing the "Color Guy"

Ryan points out that engineering hierarchies often create structural visibility deficits: individual engineers do the heavy lifting, but product managers (PMs) or engineering managers (EMs) are the ones interfacing with executive leadership and delivering upward updates. Ethan offers a concrete tactical playbook for this dynamic: 1. **Coach and prompt your leaders directly:** Managers often fail to give credit not out of malice, but out of tunnel vision. When Prime Video was first launching and Ethan was a senior manager, he walked into his VP's office and explicitly instructed him: "Today's the day now you write the congratulations message to everyone." Ten minutes later, the VP sent out the praise email. Individual contributors can make the exact same ask of their PMs prior to executive reporting: "This is a big accomplishment for the team and a big moment for me. When you report up, please mention what we specifically built." 2. **Follow up with technical color:** If the PM or EM fails to mention you, bypass them gently by sending a complementary technical follow-up note to leadership. Ethan suggests framing it as: *"Following onto the product manager's note, I thought leadership might be curious about some of the technical underpinnings of how we pulled this off."* Leadership cannot rebuke this without looking anti-intellectual or dismissive. 3. **Adopt the sports broadcast framework:** In sports broadcasting, there are two distinct roles: the play-by-play announcer (who calls what happened) and the color commentator (the ex-player who explains *why* the play was difficult and how it worked). Let the PM be the play-by-play announcer; step up and be the "color guy" who explains the complexity.

[07:58](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=478s) Visibility Theater vs. Honest Value

Ryan challenges the broader organizational health of this dynamic. In many companies, engineers register for leadership reviews under the guise of asking for "steering" or headcount, when their true hidden motive is simply to flash their face and project in front of executives right before promo committee. If everyone follows this advice, orgs devolve into hollow visibility contests where people talk endlessly without creating impact.

Ethan acknowledges that pure visibility-seeking creates a toxic, overly political environment, but counters with several hard realities: - **Most people simply never act:** Despite good intentions, roughly half the people listening will take zero initiative tomorrow. Being in the half that speaks up already differentiates you. - **You can intentionally attach real substance to visibility:** When providing technical follow-ups to executives, deliver actionable insight. Tell them whether the system was architected for long-term scale, or warn them honestly that while the system is launch-ready, immediate success will require a secondary scaling investment. - **Opting out is just self-inflicted martyrdom:** Engineers who refuse to speak up out of moral disgust with corporate politics usually end up stuck in their cubicles contemplating "quiet quitting" or rage-quitting because their careers stall. Ethan delivers a blunt critique to those who refuse to engage with the system: > "You're telling yourself you're this bold martyr for honesty, and all you are is a martyr. Don't do that. Instead, take it as a challenge and say, 'Okay, I'm going to talk, but what I say is going to be worth hearing.'"

[10:49](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=649s) Stretching the Truth vs. Simplifying the Message

Ethan challenges engineers who stay silent out of resentment toward loud colleagues who are "just flapping their faces." Refusing to speak up just because you do not want to be put in the same bucket as blowhards is a mistake; instead, you should raise the bar on yourself and create a new, better bucket. He delivers a blunt reality check to those who quietly stew over their own brilliance: "If you're as good as you think, if you're sitting there about how hot you are, then you got to be able to find something useful to say. And if you can't construct something worth hearing, then go back and revisit that 'but I'm so hot,' right?"

When Ryan asks if the best strategy is generally to be as loud and outspoken as possible, Ethan says no—phrased that way, you will just be seen as a blowhard making false claims. However, if you reframe the goal to claiming everything you legitimately can, and stretching "legitimate" right up against the limits to keep the message simple, then the answer is yes. Because human brains cannot hold onto complex caveats, you have to boil your achievements down to short, punchy marketing messages without crossing into outright falsehoods.

To illustrate how he personally "balloons up" a claim for simplicity, Ethan shares how he always introduces himself as "the first engineer on Prime Video." In reality, when he worked on Amazon's first video product, it had not been named Prime yet. One engineer—the person who was actually first to work on it *after* it was officially christened Prime—once came back and challenged Ethan on this, feeling Ethan was claiming too much. Ethan's take is that saying "I was the first engineer to work on what became Prime Video" is just a lot of extra, confusing words. The challenger knows what Ethan actually built and simply dislikes the label, which Ethan can live with; it is only if someone could accuse you of never being on the team at all that you would be in real trouble.

[13:42](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=822s) Getting Comfortable in the Gray Area of Soft Skills

Ryan pushes back on the ambiguity of this approach, asking how to find the right spot in that "gray area." Ethan points out that while engineers are trained in binary—loving the black-and-white certainty of zeros and ones—all soft skills are inherently gray and context-dependent. You must never cross into the "black" of lying, where you cannot back up your claims and risk damaging your reputation, nor should you trap yourself in the "pure white" of indisputable facts that not a single person on a team project would argue with.

As a second personal example of navigating the gray, Ethan brings up his patent portfolio. On many of his patents, multiple inventors are listed: sometimes Ethan was the true inventor and others were added for social reasons, and sometimes someone else was the true inventor and Ethan's name got tacked on. Rather than tedious caveating—"I have 70 patents, 25 of which I feel like I was the inventor"—he simply states that he holds 70 (or 75) patents. The key to operating in the gray area is to "read the room" and tailor the framing of your true accomplishments to what your specific audience values:

- "I was the first person working on Prime Video." - "I was the first person working on Amazon Video." - "I was the first manager and I hired a team and they built it."

Every single one of those statements is true, just viewed through a different lens.

[16:08](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=968s) The College Exam Analogy and the Tragedy of "Alfred"

Noticing Ryan wants to press him further, Ethan laughs and invites him to push. Ryan asks where on the spectrum—from 100% indisputable truth to outright lie—someone should place themselves on average for the fastest career growth. Ethan immediately answers, "More is better," right up until the point where you cannot back it up and it hurts your reputation. He pushes people toward claiming more because the vast majority of engineers say and claim far too little, blinded by a misplaced faith in "cosmic fairness." Conditioned by university, where every test question is objectively graded, engineers sit around waiting for a manager to count their git check-ins or read all their code to determine who did the real work.

```mermaid flowchart LR accTitle: How Corporate Performance Is Actually Graded subgraph Myth["The University Myth"] M1["Write code & check-ins"] --> M2["Manager audits every line"] M2 --> M3["Objective, fair grade"] end subgraph Reality["The Corporate Reality (6 Months Later)"] R1["Tell your story ("Ryan")"] --> R2["Manager recalls a '97'"] R3["Stay silent ("Alfred")"] --> R4["Manager forgets -> 'F'"] end ```

In the real world, Ethan explains, corporate evaluations work as if you took a college exam, and six months later the professor sits in a room with a stack of ungraded tests and assigns a score based purely on memory and impression. The manager will not reread the exam; they will just think, *"I know Ryan. He's about a 75."* Your job is to have managed that relationship and surfaced your work over those six months so the manager instead thinks, *"I know Ryan. He's definitely a 97."*

Ethan acknowledges that this reality makes people's skin crawl: "They're like, 'It's so wrong. This guy, I hate him because he's telling me these things that just shouldn't be.' And I'm with you. But I'm telling you the real world." The dark side of this social, short-memory world is what happens to the quiet engineer—whom Ethan names "Alfred." Even if Alfred did 75-level work, six months later the manager says, *"Oh yeah, Alfred, I don't remember much about him,"* and gives him an F, leaving Alfred sitting in his cubicle contemplating rage-quitting because the fair grading he waited for never came.

[19:18](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1158s) The Silent Engineer's Publicity Method: The Matt Round Tool (MRT)

Ryan asks how people who are naturally quiet can gain this kind of visibility when loud self-promotion does not come naturally to them. While acknowledging that the world has favored extroverts for at least the last hundred years, Ethan lays out several concrete ways introverts can let their work speak for itself—just not in a vacuum or in isolation:

- **Write about your work:** If you hate speaking up in meetings, publicize what you are doing via email or Slack. - **Let others publicize it or create sharable artifacts:** Put your work where it will get reviewed, package code into a sharable component for other engineers, or turn your work into a white paper or a brown-bag talk. - **Build something everyone uses (and name it after yourself):** If you build an indispensable tool, people will eventually come looking for the creator.

To cap off this "silent engineer's publicity method," Ethan shares a fun piece of Amazon lore about a long-gone engineer named Matt Round. Ethan never met him in person, yet he knows who Matt Round is because Matt built Amazon's internal interview-tracking system, which everyone at the company used for over a decade. Matt named it the "Matt Round Tool," or **MRT**. By building something ubiquitous and stamping his initials on it, Matt Round became famous across Amazon "without ever saying a word—or I guess you had to say three letters, right? You had to call it MRT." Ryan then begins to transition to the next topic: how to handle competitions over project scope when you spot an impactful career opportunity.

[21:51](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1311s) Securing Scope: Earning Trust and Demanding Your Own Project

When an engineer conceives a high-impact idea before pitching it, the critical challenge is ensuring they are the one granted the scope to execute it rather than watching it handed to someone else. From a manager’s perspective, two fundamental criteria must be met before greenlighting an initiative: trust in capability and availability of time. The manager does not necessarily need the person to be the single best engineer in the company, but they must trust that the individual is not a liability or a delivery risk. Simultaneously, the engineer must demonstrate that their calendar can absorb the effort. That requires actively creating bandwidth—whether through comprehensive documentation, automation, or setting up clean handoffs for existing operational burdens—so the manager can easily justify freeing them up.

```mermaid flowchart LR accTitle: Securing Project Scope accDescr: Process of converting a new idea into assigned scope with a manager.

subgraph Pitch["Idea & Capacity"] A["Pitch New Idea"] --> B["Clear Bandwidth<br/>(Automate / Handoff)"] end

subgraph Framing["Manager Dynamics"] B --> C["Explicit Ownership Claim<br/>('I am excited to build it')"] C --> D{"Manager Decision"} end

subgraph Outcomes["Outcome"] D -->|"Give away"| E["Encounter Pushback<br/>(Thorny engineer)"] D -->|"Assign"| F["Own the Scope"] end ```

The originator naturally holds the initial advantage because they understand the nuances of the idea better than anyone else. However, keeping that advantage requires intentional phrasing. When pitching to leadership, never leave ownership ambiguous. Instead of neutrally presenting a suggestion, frame it with clear intent: *"I have this really valuable idea. I think it's going to change our business or change our team, and I am excited to make it happen."* This psychological anchoring forces the manager to consciously decide to disappoint you if they consider delegating it elsewhere—a confrontation most people inherently avoid. If you stay passive, the manager will casually hand your idea to someone else without a second thought.

[24:18](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1458s) The "Thorny" Principle: Why Nice People Get Passed Over

To survive and advance in corporate environments, top performers must maintain an edge of friction: "Disappointing them comes with pain." Being thorny does not mean behaving like a toxic jerk; it means refusing to roll over when wronged. If a manager strips away your initiative and hands it to a peer, responding with passive acceptance signals that your ideas can be appropriated for free. A strong contributor pushes back immediately and establishes consequences, signaling that if this is how ideas are treated, they will take their contributions elsewhere.

Managers perform an ongoing triage driven by human self-preservation rather than cosmic justice. The contrast between two archetypal employees highlights this dynamic: - **The Thorny, Pushy Engineer:** Demands high-visibility work and makes it clear that being denied resources will lead to friction or their eventual departure. - **The "Alfred" (The Easygoing Rock):** Silently absorbs slights, stays in his cubicle being mad, and accepts movie tickets or lunch vouchers instead of high-stakes scope.

Because managers are pressed for bandwidth and want to keep their overall team intact, practical triage incentivizes taking from the quiet, compliant team member to appease the demanding one. Managers rarely admit this out loud, comforting themselves with the lie that they will "make it up" to the nice engineer later. In practice, the pushy engineer returns for more, and the polite team player remains permanently stranded in the "leftover bucket."

[27:44](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1664s) Team Composition: Unreasonable Agitators vs. Cannibal Superstars

When building a high-performing organization, filling every seat with ambitious, aggressive superstars sounds appealing on paper but frequently collapses into internal conflict. Unless an organization is experiencing hypergrowth where high-impact projects land in laps constantly, a team of pure alpha drivers becomes cannibalistic. They fight for limited scope, undermine one another, and clash with leadership.

Conversely, a team composed entirely of agreeable role players produces a peaceful, stagnant culture where zero meaningful progress occurs. Citing the classic maxim—reasonable people conform to their environment, while all progress depends on unreasonable people—effective organizations rely on friction-oriented individuals who relentlessly question why workflows require three clicks, why revenue goals are capped, or why legacy constraints exist. Managers need a calibrated ratio: enough unreasonable agitators to drive breakthrough change, balanced by steady contributors to avoid total organizational chaos.

[29:52](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1792s) Defending Your Projects from Opportunistic Peers

A pervasive fear among technical staff is not just management reallocating their work, but opportunistic peers circling a compelling project and trying to carve out pieces for themselves. Handled correctly, peer interest can be converted into political leverage. By structuring the initiative into a massive endeavor where you control the core architecture, you become the "kingmaker holding the cookie jar," distributing work streams to others while keeping primary ownership.

When direct defense is necessary to protect an initiative from being co-opted, three tactical countermoves preserve ownership: - **Build Under the Radar:** Maintain operational secrecy and avoid unveiling prototypes until execution is underway and leadership has formally assigned ownership. - **Provide Alternative Bait:** Leverage your idea pipeline to redirect interested peers toward alternate projects, pitching other compelling proposals to leadership so colleagues direct their energy elsewhere. - **Outrun the Field:** Accelerate your execution velocity by pushing working prototypes and business cases far ahead of anyone else's ability to catch up. - **Offload Undesirable Work (The Darker Route):** Use your new initiative as justification to unburden yourself of legacy operational debt. Propose to your manager that your focus must shift entirely to the high-value project, simultaneously recommending that your opportunistic peers are perfectly suited to take over your tedious maintenance tasks.

[32:35](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=1955s) Rejecting Scarcity Mentality and Playing the "Weekend Project" Game

Continuing his thought on sharing credit ("Sarah, I got it," or "Ethan and Sarah"), Ethan emphasizes that he prefers to keep things above board and wants to challenge the underlying scarcity mentality in Ryan's questions. While people often assume there is only so much good work, promotion, and visibility to go around, Ethan points out that there is actually plenty of good work available—and even when it comes to promotions and visibility, "if a company wants to bad enough, they can promote whoever they want." Because of this, he tries not to treat workplace dynamics as a zero-sum game or a prisoner's dilemma, starting instead by looking for a win-win: figuring out how to expand the scope of a project so it's bigger for everyone.

If someone tries to muscle in on a cool project, Ethan suggests welcoming them in on the condition that they make it better and finish it in half the time—or playfully testing their commitment by giving them a hard time. He'll tell a peer, "Well, okay, but you know, this is a cool project and it's better than what you're working on. So, like, show me you're serious. What are you going to build this weekend to move it forward?" If the colleague balks and says they have weekend plans, Ethan replies with a smile, "Well, then sorry. Like, this is a weekends project, right?... I thought you were committed." You can get away with a lot if you frame it as a friendly challenge to step up because you are already putting in that effort yourself.

He likens this dynamic to the classic human tendency to goad each other into crazy stunts—the kinds of stories that start with "watch this, hold my beer," where someone gets talked into jumping off a bridge and doing a backflip. That is simply how human nature works, which leads into what Ethan calls a tough message about soft skills: "Human skills are about dealing with humans' weird, broken minds that are not rational. They are emotional." Emotions aren't inherently bad—they provide energy and excitement—but navigating them requires understanding human psychology.

[34:48](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2088s) The Poker Table Analogy: Ethical Card Sharks vs. Manipulation

Drawing an analogy that resonates with many engineers, Ethan brings up the old poker adage: "If you can't tell who the mark is at the poker table, it's you." In the corporate game of reading people's minds, motivations, and soft skills, "if you're not in charge, then you're the mark." This psychological game plays out consciously and unconsciously in every single meeting. If you aren't paying attention to colleagues' motivations, satisfactions, and fears—not to manipulate them, but simply to understand the room and play your cards right—then you aren't even in the game.

- **Playing to win vs. manipulation:** Poker is a mind game and a competition where you are allowed to win without manipulating the other person ("I can't make you play cards a certain way... I'm not putting you down by beating you. I'm just beating you. You had a fair chance. You held your cards. I was better and I won and I get the money"). - **What crosses the line into cheating:** True manipulation is the equivalent of having someone stand over an opponent's shoulder or planting a hidden camera to see their cards. Being an ethical "card shark" simply means becoming exceptionally good at understanding how people's minds work and playing your own hand well.

[36:13](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2173s) How to Reject Bad Projects: Playing Offense and the Porcupine Defense

Ryan shifts the conversation to the flip side of taking on great projects: offloading undesirable work onto others, and more importantly, how to protect yourself when someone tries to dump unwanted scope onto you. Ethan immediately notes that if a bad project has already been pointed at you and you are forced to refuse it, "you've already lost round one." While you can still recover, the best defense is a good offense. You should constantly be proposing ideas to your team, boss, or company so that everyone perceives you as too busy driving high-value initiatives to take on grunt work ("Ryan's full of ideas and he's doing all this stuff. We couldn't possibly give him anything"). That way, if someone approaches you, you can genuinely say you'd love to help, but you're already locked into projects A, B, and C.

```mermaid flowchart TD accTitle: Strategies for Defending Against Unwanted Work accDescr: Flowchart showing Ethan Evans's offensive and defensive tactics when peers or managers try to assign undesirable scope.

subgraph Offense["Round 1: Play Offense (Best Defense)"] O1["Proactively propose ideas & initiatives"] --> O2["Appear visibly busy with Projects A, B, C"] O2 --> O3["Preemptively volunteer for a time-boxed maintenance sprint"] end

subgraph PeerDef["Round 2: Defense Against Peers"] P1["Push back: 'If it's so easy, you automate it'"] P2["Porcupine defense: Be thorny so they target a 'squirrel'"] end

subgraph MgrDef["Round 2: Defense Against Managers"] M1["Make a deal: Trade current grunt work for the next great project"] M2["Subtle quills: Accept the task but set a hook for a better challenge next"] end

Offense -->|"If caught looking idle"| PeerDef Offense -->|"If assigned by boss"| MgrDef ```

If you screwed up by looking idle without any ideas cooking and someone tries to shove bad work onto you, Ethan outlines two primary defensive tactics:

1. **Challenge them to solve their own problem:** Tell them the task is too big to take on. When they inevitably minimize it ("Oh, it's easy, it's just this"), push right back: "Great, you automate it. Go ahead." 2. **The Porcupine (or Hedgehog) Defense:** Remember that you are not the only person on the team, and Ethan guarantees there is someone else who won't resist. If you act "thorny" enough—pushing back with "I'm not taking on your work. Who do you think you are?"—the person offloading the work will move on to an easier target who says, "Oh yeah, I can help with that." As Ethan vividly puts it: "Can the tiger or the dog eat the porcupine? They can, but it's not worth it. I'll go find a nice mushy squirrel. And so, when they come to you, you get those porcupine thorns out. And they're like, 'Ouch, I'll go find the squirrel.' And then, you know, there's bunny guts all over the lawn somewhere else. And that's your peer, but it's not you."

[38:51](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2331s) Bargaining with Your Manager and Turning Grunt Work into a Virtue

Ryan points out the obvious risk of using the porcupine defense against your own manager: they control your performance reviews and whether you get fired. Ethan agrees that if you constantly say no to your boss without bringing enough proactive value to the table, "then you're just not helpful. Goodbye." Beyond playing offense, if a manager brings you unappetizing work, the next best move is to look them in the eye and make a deal. Ask them candidly, "Look, we both know this is not very appetizing work. Can we just agree that's true?" Whether the manager admits it just needs to get done or insists it's great work (at which point you can give a knowing eye-roll that says "Come on"), you pivot straight to a bargain: "I'm going to crank through this, but the deal is I get this next thing." Because most managers have their own plates full, don't want a fight, and need their team pulling with them, they will usually take the deal.

Even better, if you see a pattern and know a wave of maintenance or grunt work is inevitable, you can play offense by volunteering for it up front and turning the hit into a virtue. You can approach your manager and say: - "I've really enjoyed getting to work on X, Y, and Z. You've given me some good projects." - "I know our team has some maintenance work and I know you're always hunting for people to do it. I'm going to spend the next two weeks doing whatever maintenance you want because I want you to know I'm on your side." - "I'm going to do my own bug bash this weekend, tomorrow night, next week, fill in whatever, my next on-call. Tell me what is most important to you because I want to get to where... we're both free for me to work on this thing that you need, this better thing."

What never works, Ethan warns, is sitting quietly in your cubicle or home office hoping you won't be noticed. While staying quiet usually makes you invisible for rewards, the exact opposite happens when a manager is handing out bad work. Speaking from his own experience as a manager looking for someone to take a thankless task, Ethan describes scanning the team roster: "Who haven't I seen in a while? Oh, it's Alfred the grumpy guy. Here we go. He's already grumpy. Why not give him this?" Ironically, Alfred is grumpy because his previous work went unnoticed and he "got an F on the test"—meaning the manager actually made him grumpy in the first place—but since Alfred still goes along with things, he gets stuck with the bad work.

Finally, Ethan explains the subtle art of being a porcupine with your boss without coming across as a jerk ("Hey, man. I didn't stab you. These are just my quills"). It comes down to showing small signs that you aren't thrilled with the assignment without actually refusing to do it. When handed "extra crap work," you can say, "All right, I will get this done, but we got to do better. Like, I'm looking for better next time." That small verbal challenge sets a psychological hook, putting the manager on notice that as soon as this task is finished, you expect a better challenge.

[43:00](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2580s) Stopping the Cycle of Bad Projects: From Bunny Guts to Bear

Continuing his advice on how to push back when a manager tries to dump undesirable work on you, Ethan explains the power of setting a psychological hook. If a manager comes back with another subpar task after you have already asked for something "juicier," you can hold the line: "I told you juicy, we both know this isn't that. I'm going to give you one more pass." According to Ethan, most managers—and most humans—simply cannot stomach going up against that firm expectation repeatedly, even if they never explicitly agreed to your terms. Rather than enduring pushback every time they hand you an assignment, the manager will conclude it isn't worth the friction and move on to an easier target—someone else who is "going to turn into bunny guts when I eat him."

Ethan acknowledges that many listeners will feel this dynamic is deeply unfair and are "so sick of being bunny guts spread on the lawn when the wolf got me." His prescription is blunt: change. You have to evolve from a rabbit into a porcupine, and eventually into a bear. He reassures the audience that this is a normal learning curve and that everyone was "bunny guts" at some point in their career simply because they didn't know any better. At this point, Ryan loses his composure, bursting into laughter at the graphic mental image of a "slaughtered field of rabbits," prompting Ethan to laughingly promise he will find a new analogy for the next topic.

[44:10](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2650s) How to Be First in Line for a Scarce Promotion

Ryan introduces the next, slightly darker scenario: wanting a promotion when there is only a single slot available—whether due to a strict promo quota or because only one manager role exists—and needing to ensure you are first in line. Ethan begins with a dose of realism: if there are already several more senior, qualified people on the team who have clearly expressed interest in that spot, the right move is to "get out of line" and go somewhere with better opportunity. He jokes that he always makes fun of the post office because he can't fathom how anyone moves up there—"either you deliver the mail or you don't, and then there's postmaster and there's one of those and they stay there until they retire." If you are metaphorically working at the post office, leave for an organization that is actually growing.

Assuming the organization is growing and spots will open up, Ethan outlines how to get to the front of the queue. Because managers aren't mind readers, you first have to state clearly that you want the role. Next, ask what it would take to become their top choice, even framing it with playful absurdity: "Hey, Ryan, against all odds, what would cause you to bump me to the front of line and put me first? Like, what would that have to look like?" Framing the question this way works because any manager can answer a hypothetical, which then gives you concrete criteria you can negotiate and execute against.

Beyond asking, the true secret to jumping the line is becoming indispensable—the person the manager knows will "ride to my rescue when there's a problem." Plenty of people do their regular day-to-day jobs well, so to stand out, you have to jump on crises and fires. When a system goes down or a customer is furious over an outage, the person who steps up with technical brilliance and leadership gets noticed. At promotion time, a leader's primary question is: "Are they going to be the person I can count on no matter what? Are they going to keep me out of trouble?" Because crises rarely happen conveniently between nine and five—usually striking on weekends or holidays—demonstrating this trait requires real sacrifice.

- **The "Worst Problem" Rule:** Ethan shares a tactic from someone he recently spoke with who would ask their manager, "What are your three biggest problems?" Since every manager always has problems, they can easily name three. The employee would then follow up: "Great. Which one's worst?... I want to work on your worst problem. How do we make that happen?" - **The Hard Truth:** Ethan clarifies that while he has answered how to win the spot, many people secretly want to know how to get the promotion *without* putting themselves out too much—and short of bribery, there is simply no answer for that.

[48:17](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=2897s) Boiling the Water Slowly: Building a "Work Marriage" with Your Manager

Ryan pushes back with a nuance on the "worst problem" tactic: if a direct report came up to him overly eager to get promoted, obviously kissing up by asking for his worst problem right out of the gate, it might feel weird and off-putting. Ethan agrees that personalities vary and that throwing a manager straight into the hot water—"Hey, I want to be promoted. How can I do anything you need so that you want to promote me?"—will strike most people as creepy. Instead, like the classic "frog in a pan" metaphor, you have to boil the water slowly by gradually escalating a win-win relationship, much like how Ryan is gradually escalating the darkness of his interview questions.

```mermaid flowchart LR accTitle: Gradual Escalation to Becoming a Manager's Go-To accDescr: A four-stage progression showing how to build trust with a manager over time rather than asking for a promotion cold. subgraph Foundation["1. Build the Base"] A["Deliver solid, then exceptional daily work"] --> B["Proactively help & take initiative on small ideas"] end subgraph Partnership["2. Deepen the Partnership"] C["Ask for growth tips & special challenges"] --> D["Propose a win-win: become the go-to crisis right hand"] end B --> C ```

Ethan emphasizes that this gradual progression isn't manipulation; it is standard relationship building. Just as in dating—where you express interest, ask someone out, and go to dinner before getting serious—you are essentially "dating your manager" to form a temporary "work marriage" that eventually grants you a privileged position on the team.

[51:34](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3094s) Why Smart Leaders Want an Expensive, Promoted Team

Ethan then pivots to a related question that employees often used to bring him: "Why do you treat so-and-so so well, why do they get all the benefits, or why didn't you promote me?" Whenever someone asked why he hadn't promoted them, Ethan would flip the question back on them: "Why didn't you earn it? Why didn't you promote yourself?... Show me something." If an employee complained about a favored peer, Ethan was happy to list every single way that high performer was contributing, promising the complainer that if they delivered the same output for the same amount of time, they would get the exact same spot—especially since the high-performing "climber" would inevitably move up or move out anyway, leaving an opening behind.

He concludes with a piece of management logic that he notes some bosses aren't smart enough to figure out: a leader should want the most senior, most promoted team possible. Rather than hoarding junior talent, Ethan always wanted his reports to rise to new levels so he could pay them more and benefit from senior-level execution. While that meant dealing with budget constraints and fighting uphill battles with upper management, he never hesitated to defend his payroll to his bosses: "Look, yes, I have an expensive team. Why are they expensive? Because my team is damn good and you know it." By pointing to the track record of stars he had developed and exported to become leaders across other teams in the company, he could look executives dead in the eye and argue that building a "star organization" costs money, "but it's good for you."

[53:10](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3190s) Paying for Performance and the Myth of Fast Promotions

Ethan Evans shares an example from his current advisory work coaching a company's chief product and technology officer (CPTO). He was blunt with the executive: *"I can make your team higher performing, but it's gonna cost you salary when they step up. They're gonna want to be rewarded. Are you ready to pay for performance?"* If leadership wants higher output, they must be prepared to hand out more stock options and compensation. Evans operated this way internally throughout his career at Amazon because high expectations require matching rewards.

When employees approached him complaining, *"Why didn't you promote me?"* his immediate retort was always, *"Why didn't you promote yourself?"* Promotions require mutual, explicit agreements where an individual steps up, takes on a stretch project, looks the manager in the eye, and meets an agreed-upon bar. Employees who simply whine without taking initiative were fundamentally uninteresting to him.

Evans admits to a painful early-career mistake from twenty years ago when he was new to Amazon. An engineer struck a deal with him, did the work, but Evans did not understand the corporate promotion cycle and missed the nomination window. The engineer rage-quit. Evans acknowledges the engineer was completely justified: *"I blew it. But that was like user error, not intent."* He vowed never to repeat that error. He notes that across corporate life, virtually no one ever feels they were promoted too quickly or given unexpected early recognition; almost everyone believes the process takes far too long because human nature leads everyone to imagine themselves as top performers.

[55:35](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3335s) Handling Managers Who Avoid Career Growth Conversations

Ryan Peterman observes that while Evans is exceptionally direct about promotion criteria, many managers avoid explicit conversations about levels and career progression. Evans’s initial instinct is to advise people to find a more ambitious manager who can relate to wanting upward mobility. However, when working under an evasive manager is unavoidable, employees must decode the manager’s indirect language by analyzing who they actually reward.

Rather than trying to force an uncomfortable conversation, observe the individuals who have been promoted under that manager. Look for patterns in their achievements, behaviors, and working styles. Evans recommends reaching out directly to those promoted peers to ask how it happened: whether they stated it in an annual review, what specific projects they tackled, or how their conversations were structured. If an investigation reveals that the manager has promoted virtually no one or acts completely randomly, there is no viable system to work within—meaning you either accept delayed timelines or transfer out.

```mermaid flowchart TD accTitle: Navigating a Manager Evasive About Promotions accDescr: Decision flow for decoding and handling a manager who avoids career growth conversations.

Start["Manager avoids promotion talk"] --> Audit["Audit manager's track record"]

subgraph Analysis["Analyze History"] Audit --> CheckPromos{"Have they promoted others?"} CheckPromos -->|"Yes"| Interview["Interview promoted peers<br/>& decode reward patterns"] CheckPromos -->|"No / Rare"| DeadEnd["Unworkable system"] end

subgraph Action["Actionable Path"] Interview --> Adapt["Conform to proven pattern<br/>& adopt manager's language"] DeadEnd --> Choice{"Decide career move"} Choice -->|"Stay"| Accept["Accept slow, random timelines"] Choice -->|"Leave"| Transfer["Find an ambitious, supportive manager"] end ```

[58:25](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3505s) Using AI to Decode Communication and Manage Up

Evans proposes a modern tactical hack for dealing with indirect managers: leveraging AI for personality typing and communication strategy. Employees can gather samples of their manager’s writing—such as emails, internal documents, or public posts—and feed them into an LLM.

- **Prompting Strategy:** Input the text and instruct the AI: *"Analyze this person's communication pattern. I have this goal, which is I want to ask for a promotion. I'm very direct. They don't seem to be. How do I approach this person?"* - **Bridging the Gap:** The model can break down personality nuances and suggest the exact vocabulary, phrasing, and framing needed to resonate with that specific manager. - **Future Dynamics:** Evans notes that while using AI to bridge communication differences is a healthy tactic today, it will soon evolve into a battle of influence and manipulation, eventually requiring people to use personal AI countermeasures to protect their own boundaries against tailored outreach.

[01:00:13](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3613s) Navigating the Vague "Carrot-Dangling" Manager

Peterman raises a common corporate trap: managers who keep direct reports in a gray area, dangling the promise of a promotion with vague reassurances like *"You need to do more work, I want that for you,"* while evading concrete timelines or actionable checklists.

Evans explains that managers resist being pinned down for both legitimate and bad reasons:

* **System Constraints (Legitimate):** Managers rarely have unilateral authority over promotions. At companies like Google and Amazon, packets must pass through committees, calibration panels, and skip-level approvals. A manager cannot guarantee an outcome governed by a third-party panel. * **Loss of Flexibility:** Managers fear direct reports treating a discussion as a rigid contract. If a manager names four criteria, an employee might complete them mechanically, demand immediate promotion, and push back if the quality is subpar or if an unpredicted fifth requirement emerges. * **Bad Faith:** Some managers simply want to keep dangling the carrot to extract endless discretionary effort without any genuine intention to promote.

To disentangle systemic barriers from bad faith, Evans advises shifting the conversation away from an impossible guarantee. Explicitly acknowledge the promotion panel: *"I know you face a panel. I know you need our skip's approval... I'm not asking for you to guarantee me that we're going to get through the panel. I want to know what it's going to take for you to be ready to be enthusiastic to go make my case."* By asking what it takes to turn the manager into an active champion rather than asking them to guarantee a panel's vote, you remove their defensive hesitation and force clarity on their expectations.

[01:03:06](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3786s) Pinning Down Vague Managers and Chris Voss Negotiation Tactics

When Ethan was working toward his own promotion to Vice President at Amazon, his VP had an honest conversation about the boundaries of what he could control: "Ethan, on this cycle, I'm going to do everything I can. I'm going to put you up and I'm going to put my reputation out there, and we're going to see if we can make it happen." At that time, Jeff Bezos personally approved every VP promotion in the company; a manager could fight aggressively and line up all the support, but nobody could guarantee what Bezos would ultimately decide. For employees struggling with managers who dodge commitments and seek endless wiggle room, the key is not attacking them, but drawing them into your emotional reality: "Look, I understand that answering me or telling me what you're willing to do is still dependent on me delivering and that new things could come up. But understand, I need help with the fact I have no clarity... I feel like it's a moving target. Can you help me with that?"

To disarm evasive managers, Ethan points directly to Chris Voss's negotiation book *Never Split the Difference*, which focuses on getting counterparts to adopt your perspective through tactical empathy and calibrated questions. When a manager dismissively instructs someone to "just keep working toward it," Ethan suggests responding with Voss's signature question: "How can I do that?" Asking "How can I feel good about working towards such an unknown destination?" shifts the burden back onto the manager, forcing them to solve your uncertainty rather than brushing it aside.

Ultimately, an employee must determine whether a manager is negotiating in good faith or simply stringing people along. The litmus test is objective observation across the team: look around and see what the manager has actually delivered for others. If peers are earning promotions, compensation bumps, and high-visibility opportunities, the manager is credible, and the responsibility lies on the individual to figure out what criteria they have not yet met. If, on the other hand, everyone on the team is perpetually led down an indefinite path with zero advancements, the only real solution is to get out from under that manager.

[01:06:30](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=3990s) When Your Manager Is the Bottleneck to Your Promotion

Ryan shifts the conversation to organizational bottlenecks where promotion slots are structurally limited because the manager above you is not moving up. When a manager is parked in their role, the entire reporting line below them becomes compressed. Ethan breaks this dilemma into two distinct archetypes: the ambitious manager who is struggling to break through, and the content or stagnant manager who has stopped pushing altogether.

For the ambitious manager, Ethan advocates forming an explicit upward alliance: "Hey, I want to move up. You want to move up. If we can do this thing together, we'll both move up." Ethan utilized this exact dynamic during his career at Amazon, enlisting high-performing reports to help him deliver outsized impact so he could earn a promotion and immediately pull them up behind him. If a manager is uncomfortable having direct conversations about advancement, an employee can frame the mutual alliance around broader team impact: "What's rewarded in this company, and how can I help our group be more rewarded?"

```mermaid flowchart TD accTitle: Navigating a Blocked Manager accDescr: Flowchart showing decision paths when an employee's promotion is blocked by their manager's career status.

Start["Manager Is Blocking Your Promo Path"] --> Check{"Is your manager ambitious?"}

subgraph Alliance["Case A: Ambitious Manager"] Check -->|"Yes, wants to rise"| TeamUp["Form upward alliance:<br/>'If we win together, we both move up'"] end

subgraph Divergence["Case B: Stagnant / Parked Manager"] Check -->|"No, content or given up"| StagnantCheck{"Are they supportive or hoarding?"} StagnantCheck -->|"Supportive & people-focused"| SponsorOut["Ask for sponsorship to transfer:<br/>'Let me be your ambassador elsewhere'"] StagnantCheck -->|"Hoarding you out of self-preservation"| CreateLeverage["Polite ultimatum & urgency narrative:<br/>'My career is important; I must grow'"] end ```

[01:08:21](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=4101s) Polite Ultimatums, Urgency Narratives, and Tactical Leverage

When dealing with a manager who is ambivalent, tired, or has given up on climbing higher, staying in place often means accepting career stagnation. Ethan suggests two primary approaches depending on whether the manager is benevolent or possessive:

- **The External Ambassador Approach:** Less aggressive, downward-focused managers often pride themselves on mentoring and taking care of their people. In these cases, you can ask for their blessing to transfer: "If we can't create that opportunity in this team, will you help me find it in another org? I could be a great ambassador for your leadership and our team elsewhere." - **The Polite Ultimatum (Dealing with Hoarders):** If a manager insists on hoarding you because losing you destroys their own standing, you must assert firm personal leverage using the unarguable anchor: *"My career is very important to me."* You express a clear preference to stay, paired with an unmistakable willingness to leave: "I'm going to move up. I would love to do it with you here, but I'm gonna have to do it."

To make that boundary palatable without threatening the manager, Ethan recommends wrapping it in an honest "season of life" narrative that introduces external urgency. A professional might explain that they have a strict two-to-three-year window before starting a family, or an impending need to relocate to care for aging parents, which demands aggressive career growth right now: "I have to do everything I can to have a fast career while I have this moment... If it can't be here, I'm gonna have to figure something out."

When Ryan questions whether framing a timeline around future life plans enters an ethical gray area, Ethan emphasizes that in real-world negotiations, managers are reacting to the immediate human reality rather than dissecting hypothetical motives. More importantly, framing your career through subjective personal feelings and family priorities makes your position unassailable: while a boss can debate business metrics, they cannot debate what you feel or believe about your own life.

[01:12:56](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=4376s) The Family Guardrail and Reality Checks on Ambition

Ethan explains why bringing up family obligations acts as an unassailable boundary or conversational trap when managing career expectations. A manager cannot dispute personal, moral imperatives: "There are certain things you can't say to people... you can't tell me not to care for my aging parents. You can't tell me to not to plan to take care of my family." If a boss were callous enough to reply with, "Wow, your family's really your problem," that serves as an immediate signal to walk away: "Door, please. Check, please."

Conversely, clever managers immediately recognize what is occurring: - They recognize the subtle negotiation taking place beneath the surface. - They realize the report understands the rules of corporate politics ("Okay, he's listened to Ethan and Ryan's podcast. He knows the game"). - They flip the dynamic back around to transactional performance: "What do I want from you? And what's it going to take? What do I want you to deliver?"

Ethan notes that Ryan’s recurring line of questioning boils down to dealing with managers who dislike ambition. He distinguishes between healthy drive and delusional overreach: - **Pushing too hard:** New graduates fresh out of college asking, "I'd like to be a VP in two years. How do I do that?" Ethan's standard reality check was: "Is your last name Bezos and I didn't notice?" If they refuse to recalibrate, they are shown the door. - **Normal ambition vs. Zen culture:** Some managers view ambition as a "dirty word," romanticizing work as pure and insisting success will arrive purely in due time. Ethan states bluntly that people subscribing to that view are not the audience for this podcast. Ambitious people need to find hard-charging managers who share their hunger, while maintaining guardrails against being worked to death.

[01:15:43](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=4543s) Handling Political Reports, Dishonesty, and Growing Careers

Ryan asks Ethan whether his direct reports at Amazon ever ran these political tactics on him—cloaking hidden demands in polite messaging. Ethan reflects that only one or two people were exceptionally smooth at it. Because he was known for direct transparency, most people simply asked him plainly, "This is what I want and how can I get it," allowing him to lay out the bill of what they had to deliver.

However, Ethan encountered other categories of reports: - **Outright dishonesty:** A few people attempted to manipulate him through verifiable falsehoods. Ethan fired them without hesitation once dishonest behavior crossed the line. - **Hyper-ambitious talent outgrowing available roles:** Ethan led high performers whose ambitions outpaced the company's internal trajectory. In one instance, a report wanted a rapid promotion that would take at least six months at Amazon; the employee noted, "Samsung will make me a VP tomorrow." Ethan encouraged him to take the opportunity, and the person went on to have a wildly successful career. - **Passive-aggressive or stagnant performers:** The workers Ethan disliked managing were those who were "asleep," bitter, or passive-aggressive about an issue without being direct. He preferred putting problems on the table to determine whether an issue could be fixed, accepted, or resolved by parting ways. - **Content maintainers:** Those in seasons of life where they merely want to do their baseline job and be left alone serve an operational purpose: "Those are the people that the top performers get to pass all their mediocre work to."

Ryan quotes a viral tweet observing that top performers rarely complain about their managers because high performers naturally possess optionality and simply depart for greener pastures.

[01:19:04](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=4744s) The Dark Realities of Firing: How Managers Drive Out Reports

Addressing Ryan's question about the difficulty of gathering evidence to terminate someone, Ethan details the darker side of management leverage. Proving a lie outright can warrant termination for dishonesty, but even without ironclad documentation, an established manager holds overwhelming power: "A manager in good standing at any level can get rid of any one employee and there's like 50 ways to do it."

```mermaid flowchart TD accTitle: Managerial Tactics to Drive Out an Employee accDescr: Flowchart illustrating the progressive levers a manager uses to force an employee out. subgraph DirectDisincentives["Direct Soft Disincentives"] A["Assign unglamorous, low-impact tasks"] B["Crush promotion timelines (e.g. 3–7 year reset)"] end subgraph FormalPressure["Formal & Administrative Pressure"] C["Telegraph below-average performance reviews"] D["Compile lists of unmet subjective expectations"] end subgraph OperationalSqueeze["Operational Squeeze"] E["Micromanage attendance and start times"] F["Assign brutal on-call shifts & bug-backlog tickets"] end DirectDisincentives --> FormalPressure FormalPressure --> OperationalSqueeze OperationalSqueeze --> G["Voluntary resignation or papered termination"] ```

Ethan breaks down the exact levers a manager uses to make someone leave: - **Dumping bad work:** Shifting the report onto the worst assignments. - **Extending the horizon:** Bluntly resetting their promotion expectations to three to seven years, practically ensuring they look elsewhere. - **Pre-framing performance reviews:** Telling the report upfront that they are tracking below average, while preemptively building a dossier of obscure missed expectations to counter any achievements. - **HR institutional bias:** HR functions primarily to protect the company and support managers in good standing. An employee complaining to HR that their manager is suddenly unfair or assigning bad tickets will find HR nodding politely while backing the manager, provided no illegal actions occurred. - **Operational misery and micromanagement:** Strict enforcement of minor rules (such as arriving at 10:05 AM when the day starts at 10:00 AM), assigning heavy on-call shifts, and pulling 20 of the worst bugs out of a 500-ticket backlog to demand they be fixed as performance metrics. If the manager lacks technical context, they simply ask a senior peer to identify the nastiest unresolved bugs.

Ethan emphasizes that good managers do not execute these tactics on high performers because driving out valuable contributors is "pathological." However, against dishonest, toxic, or cancerous employees, managers have an extensive toolkit to force an exit.

[01:22:44](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=4964s) Engineering an Exit: Squeezing Out Unwanted Reports

Continuing his hypothetical walkthrough of how an executive can run circles around Human Resources, Ethan Evans details how easily a manager can weaponize mundane tasks to force an employee out. A manager can casually ask a lead engineer like "Fred" for a list of a hundred useless backlog tickets that ought to be closed. Armed with that list, the manager approaches the targeted report and assigns twenty specific tickets from that batch, demanding they all be completed within a week to assess their total business value. If the employee later pushes back and complains about being assigned trash tasks, the manager maintains complete cover by claiming they were merely validating Fred's judgment. Once the report grinds through the miserable assignment, the manager simply closes the remaining eighty with no resolution, having successfully shoved twenty lousy tasks down the employee's throat with total bureaucratic deniability.

```mermaid flowchart TD accTitle: The Manager's Leveraged Exit Strategy accDescr: Flowchart illustrating how a manager applies administrative pressure and resets expectations to force an employee out.

subgraph Pressure ["Task Pressure"] A["Request 100 useless tickets from lead"] --> B["Assign 20 to targeted report"] B --> C["Establish bulletproof business justification"] end

subgraph Psychological ["Psychological Reset"] D["Signal bleak future: 'reset promotion timeline'"] --> E["Apply steady, defensible punishment"] end

subgraph Outcome ["The Inevitable Exit ('Evaporation')"] F["Quits or transfers voluntarily"] G["Loses temper / commits outrageous fireable offense"] end

C --> D E --> F E --> G ```

Ethan explains that when a leader truly wants rid of someone, the playbook is straightforward: make it unmistakably clear that their future at the company is finished. A manager delivers a chillingly calm, veiled message:

> "I just want to level with you. After recent events, I gotta be honest. I'm seeing this as a challenging year. And I know you've asked me about promotion. I think you might want to reset your timeline."

Once that tone is set and the punishment steadily rolls in, the manager only has to wait. The report will inevitably "evaporate"—either by reading the writing on the wall and voluntarily quitting, or by becoming so furious that they commit an outrageous misstep that hands the manager instant cause for termination. Ethan emphasizes that sane managers do not treat good people this way, but it remains an effective corporate weapon because of how flawed human dynamics operate.

---

[01:25:03](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5103s) Personality Mismatches and the Corporate Breakup

When Ryan notes that such tactics could be used unfairly against someone a manager simply dislikes, Ethan acknowledges the vast gray area in workplace relationships and outlines the constructive alternative for handling reports who simply do not click. If a manager genuinely attempts to accommodate an employee—for instance, asking a pessimist to adopt a more upbeat mindset for the team's culture—and the employee still cannot adapt, the professional approach is an amicable split. The manager sits down with the report and frames it directly:

> "Ryan, look. We've talked before about compatibility. You and I just—we're not that compatible. I would like to help you find a place where you're going to thrive. Would you be open to that?"

In this gentle scenario, the manager offers to make internal or external introductions to help the individual land on their feet. However, if the employee refuses the olive branch and digs in, insisting the manager is unjust, the manager will inevitably revert to political strategies to push them out.

Ethan defends this reality of corporate hierarchy without sugarcoating it. If an employee drains too much managerial energy and disrupts the team's zen, the org chart dictates who wins:

> "The corporate hierarchy has determined that I'm the important one. That's why I'm the boss... And I deal with the same thing above me. Either I make Bezos or whoever happy or I'm expendable. That's our system of life."

Ethan likens the cooperative exit to a classic breakup line—"it's not you, it's me, but you still need to pack your stuff and move out." A manager can often recognize that an employee who grates on their nerves might thrive under a different leader whose quirks and operating style actually align with the employee's personality.

---

[01:28:53](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5333s) How an Engineer Can Take Down a Bad Manager

Ryan pivots to the inverse dynamic: whether an individual contributor can ever successfully team up with HR to take down a bad manager. Ethan reveals that the outcome hinges heavily on timing: over 50% of the battle is decided by whoever approaches HR first, because the first party gets to establish the framing. When managing down, a savvy leader will proactively drop a note to HR stating they are addressing specific performance issues with a report, ensuring any subsequent complaint by the engineer is viewed through the lens of a disgruntled underperformer.

For an employee trying to fight an uphill battle against a toxic manager, Ethan outlines four critical prerequisites to have any chance of success:

- **Frame the issue around business impact, not personal grievance:** Never open a conversation with HR by declaring that the manager is awful and needs to be fired. Instead, anchor the complaint strictly in verifiable facts and explain how specific managerial behaviors are obstructing your ability—and the team's ability—to deliver results for the company. - **Secure peer corroboration:** A solo complaint looks like personal friction. You need at least one other peer to step forward and independently verify the pattern of behavior. - **Leverage high performance and reputation:** Joe Average or an underperformer will get zero traction; HR and leadership will not go out on a limb for them. Standing out as a top-rated superstar, having your name recognized on key tools, or having an existing relationship with your skip-level manager dramatically tilts HR's receptivity in your favor. - **Produce an objective "smoking gun":** Merely being a mediocre or unpleasant manager is rarely enough to get someone fired if they have a decent relationship with their own boss. To force an exit, there typically must be evidence of illegal, blatantly unethical, or flagrantly unacceptable misconduct.

Ethan reflects that during his career as an executive, he occasionally terminated managers based on reports bubbling up from below, but it only happened when multiple people came forward over time and presented clear facts revealing unethical conduct or extreme incompetence that Ethan could verify himself. While many employees harbor fantasies of swift justice, unseating an entrenched manager requires significant evidence and leverage.

[01:32:36](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5556s) Why Organizations Tolerate Bad Managers: The 18-Month Coaching Trap

Ethan points out that while movies make it seem like an employee can heroically expose and unseat a bad boss, that happens "one in a million" in real life. Usually, three or four people simply resign before upper leadership ever notices. To illustrate this inertia, Ethan shares a story about one of his executive coaching clients. The client admitted having a serious dilemma: he had a manager reporting to him who was well-liked personally, yet team members kept quitting one after another, all citing that specific manager in their exit feedback. The client had been attempting to coach the manager to change, but nothing had improved.

When Ethan asked how long this coaching had been going on, the client replied, "18 months." Ethan was flabbergasted: employees had been leaving the organization for a year and a half, yet leadership refused to act because the manager was "nice" and the leader "had hope for them." When Ethan challenged him with, "If I had told you this story, what would you tell me to do?", the executive conceded instantly: "I'd tell you, fire that manager." Yet he hesitated because of personal affinity and fear: the company had a hiring freeze, and he worried he could not get an approved backfill. Ethan’s blunt verdict was that the manager was a cancer actively killing the team, and that you have to learn to live without them rather than let good people bleed out. Ironically, the upper leader viewed the problematic manager as "great" simply because "they do whatever I want."

```mermaid flowchart TD accTitle: The Cycle of Managerial Inertia accDescr: Flowchart illustrating why upper management delays firing toxic or ineffective managers despite high team turnover. subgraph Reality["The Ground Reality"] A["Bad Manager Mistreats Team"] --> B["High-Performing ICs Quit"] B --> C["Exit Feedback Cites Manager"] end subgraph Inertia["Executive Rationalization"] C --> D["Upper Leader Likes Manager"] D --> E["18 Months of Ineffective Coaching"] E --> F["Fear of Losing Headcount / No Backfill"] F -.->|"Inaction Enables"| A end ```

[01:35:16](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5716s) Likability vs. Performance: The "Bob with the Donuts" Paradox

Responding to the story, Ryan observes that personal leverage in these situations boils down to two axes: how high-performing someone is, and how well-liked they are. Ethan agrees, breaking down who is actually difficult to terminate:

- **Disliked and low performer:** The easiest to fire. They do bad work, nobody likes them, and no one objects when they are let go. - **Disliked but high performer / thorny:** Also relatively easy to remove if they are broadly despised across the organization. Leaders grow exhausted by the friction. - **Mediocre and universally liked ("Bob"):** By far the hardest person to fire. They are slightly below average and work is late or subpar, but there is no obvious "smoking gun" catastrophe to justify termination. Because "everybody loves Bob"—he brings donuts, hosts the annual team barbecue, and enthusiastically volunteers for tasks—any manager trying to hold him accountable looks like the villain.

Ethan explains that you can navigate this by combining likability with "thorniness." The goal is to remain warm, friendly, and pleasant all the time, reserving resistance exclusively for when someone attempts to push unfair or misaligned tasks onto your plate.

[01:37:15](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5835s) The "Shitwork Tokens" Framing

To push back effectively without burning bridges, Ethan recommends wrapping boundaries in lighthearted humor. He introduces the script of public work allowances:

> "All right, but you're using up one of your crap work tokens. You know, I only give so many of those a month. So, is this where you want to spend one? We'll do it. It's only three a month."

Even though the manager never officially agreed to any rule granting employees a monthly limit on grunt work, humans naturally conform to clear conversational frames. If an employee says, "Hey boss, I only give out three shitwork tokens a month... we are burning a token. Is this it?", the manager subconsciously accepts the limit.

Doing this in front of witnesses makes it even more potent: the manager cannot snap back with "I'm the boss and you have unlimited tokens" without looking petty and authoritarian to the entire room. The manager accepts the victory of getting a "yes" today, but the anchor is set in their mind that the employee's tolerance for low-value tasks is strictly metered.

[01:39:25](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=5965s) The True Driver of Job Security

When Ryan asks whether likability matters more than performance for surviving layoffs and organizational cuts, Ethan confirms that likability carries immense, often hidden weight. Decisions frequently hinge on subjective, non-performance criteria; Ethan recalls an instance from a past company where a leader openly argued to spare an employee from layoffs because "that guy's married and has a family to support" while another was single—a consideration that, while technically illegal, happened in closed rooms nonetheless.

Likability can easily be reframed into an operational necessity: - **Reframing likability as resilience:** When cutting staff, leadership often looks for culture anchors. An executive can defend a mediocre performer by arguing, "Ryan isn't always our top performer, but this new room has to pull together. Who do we want in that room? Who's going to light up the room and keep everybody's morale up after we go through this grim event?" - **The danger of the irreplaceable jerk:** Relying on the Cal Newport philosophy of being "so good they can't ignore you" has a dark side. A brilliant engineer named Robert who is abrasive and uniquely understands an arcane legacy system will be kept only out of necessity. Behind the scenes, leadership is actively strategizing how to cross-train others so they can unload him: "No one likes to feel trapped and depending on someone who's unpleasant."

Ethan clarifies that you do not need to be a "super lovable teddy bear" to reap the benefits of likability. It simply requires basic decency: do not be rude, avoid talking down to colleagues, and beware of triggering the fragile egos of technical managers who are already secretly battling imposter syndrome about whether their skills are becoming obsolete.

[01:42:31](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6151s) Why Managers Mark People for Death and the Human Rationalization Machine

Continuing his breakdown of how fragile managerial dynamics can become, Ethan explains what happens when a subordinate repeatedly shows up their boss in front of the rest of the team. Doing that immediately marks you "for death" in the manager's eyes for two distinct reasons: first, the manager simply dislikes you; second, the manager cannot tolerate you destabilizing their control. If the boss cannot win you over, their hand is forced to shut you up in order to keep the rest of the team aligned and protect their authority.

Ethan emphasizes that people do this without ever feeling like villains because "humans are incredible rationalization machines." When night falls, an insecure or cutthroat manager's mind naturally conjures a self-serving justification: "Nobody wakes up in the morning and like, 'I'm a super villain.' This doesn't happen." Instead, real-world villains believe they are tragic, misunderstood figures serving a greater good, protecting their families, or merely doing what must be done because "this is just the way the world is and some people got to die." Our minds are literally engineered to rationalize nasty behavior away.

[01:43:41](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6221s) Defending Against Undermining Peers: Going First and Priming Management

Ryan pivots to an even darker scenario: what happens when peers are competing for the exact same limited promotion spot and actively undermine your credibility to leadership? Ethan stresses that speed is everything—"going first really matters." If you witness a peer taking shots at someone else even once, you must assume they will inevitably turn that weapon on you. Rather than waiting to be attacked, you need to proactively get in front of your manager.

Ethan outlines the exact script to inoculate your manager without sounding like an accuser: - Go to leadership early and note: *"Hey, I don't know if you've noticed, but there is some undermining in this team."* - Acknowledge the competitive environment while establishing your own moral ground: *"Some people will take shots at each other. I'm never going to do that, but that means I'm counting on you to recognize it because I'm not going to play that game."* - Ask them to anchor their opinion strictly on real output: *"Please judge my performance by what I actually do, not by what anyone else says."* - Close with a humble request: *"If you ever have any question about what I've actually done, grant me 10 minutes to show you. Cuz if I can't back it up, that's great... that's fair. But if I can, judge me by what I've done."*

This proactive move plants a seed in the manager's mind. When the rival peer inevitably comes to chirp and run you down, the manager immediately recognizes the behavior: "Oh, that's what Ryan was talking about." Consequently, the manager discounts the smear against you and knocks the undermining peer down a peg for bad behavior.

```mermaid flowchart TD accTitle: Inoculating Management Against Peer Undermining accDescr: Flowchart illustrating the proactive strategy to neutralize rival attacks before they happen.

subgraph Proactive["1. Preemptive Inoculation"] A["Notice peer's undermining behavior"] --> B["Meet with manager early"] B --> C["Acknowledge team competition & refuse to play dirty"] C --> D["Ask to be judged solely on tangible work"] end

subgraph RivalAction["2. The Inevitable Attack"] D --> E["Rival peer talks trash to manager"] end

subgraph Outcome["3. Manager's Reaction"] E --> F["Manager recalls prior conversation"] F --> G["Discounts smear against you"] F --> H["Penalizes rival for toxic behavior"] end ```

[01:46:32](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6392s) Handling Late Attacks with Mirroring and Subtly Exposing Bad Actors

If a peer beats you to the punch and the manager questions your contributions, Ethan warns against reacting defensively. Instead, he recommends leaning on Chris Voss's tactical mirroring technique from *Never Split the Difference*: - Repeat the last few words the manager says with a question inflection (e.g., Manager: *"Well, you didn't contribute that much."* You: *"Contribute that much?"*). - Let awkward pauses force the manager to elaborate until they inadvertently expose their source (e.g., *"Well, so-and-so said..."*). - Express calm disappointment while challenging the factual gap: *"I'm really disappointed by what you're sharing. I think if you're willing to examine it, my work speaks strongly for itself... What's the best way for me to just showcase what I've contributed to you so that you're fully informed?"* - Framing it around making the boss "fully informed" delivers a subtle dig that they currently lack the facts, without directly offending them.

Outside of managing up, Ethan warns that counterattacking peers in the dirt only drags you into the gutter. Instead, set traps or awaken the team's neutral observers: - When a toxic colleague talks behind someone else's back, quietly validate the victim: *"Hey, I heard Ethan say that you didn't contribute that much. I just want to let you know I thought you contributed a lot. I'm not sure where that came from."* - To a third party, casually raise curiosity: *"You know, I noticed today Ethan was saying bad things about Fred's work. Why do you think that was? What caused him to bring that up? It's so strange."* - Dropping subtle seeds of doubt makes others realize the person operates with double meaning, stripping away the underminer's social cover. Ultimately, Ethan reiterates: if a team is genuinely full of snakes, your best move is simply finding your way out.

[01:50:24](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6624s) When Everyone Plays Politics: The Prisoner's Dilemma

Ryan asks what happens if politics is treated like an adversarial game where every single player applies these tactics optimally—does that shift the winning strategy? Ethan clarifies that while politics in toxic organizations often turns into zero-sum manipulation, that dynamic is never ideal. In healthy organizations, managers track credit accurately, peers communicate transparently, and the company focuses on "rising tides that lift all boats." Higher business performance drives up company value, equity expands, and everyone wins together.

However, when an environment degenerates into a classic game-theory Prisoner's Dilemma, mutual betrayal dominates. If everyone is maneuvering in politically optimal, adversarial ways, they all stab each other constantly, canceling out any individual edge and returning the entire team to neutral where nobody makes progress. Ethan begins to explain how an individual should respond once they recognize that everyone around them is locked in that exact stalemate.

[01:52:04](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6724s) Finding the Softer Poker Table and the Intersection of Skills

When facing an environment where everyone around the table is exceptionally politically astute, Ethan Evans views it through a gambling analogy: if you find yourself sitting with a table full of world-class poker players, you might be able to hold your own, but the strategically superior move is to find a table full of suckers and clean them out. Rather than grinding against equal or superior operators in a brutal game, it is far more lucrative to move to an arena where your specific profile makes you the obvious star.

Ethan illustrates this dynamic using his own career shift into online coaching and teaching. He evaluated his capabilities and recognized that he possessed three core strengths: he was a solid public speaker, he possessed deep knowledge about career mechanics, and he understood social media dynamics from his tenure at Twitch as both an executive and an active streamer. Taken individually, he was nowhere near the top: - He was far from the best Twitch streamer in the world. - He was likely nowhere near the single best public speaker. - He might not have even held the absolute deepest theoretical knowledge on careers.

However, at the precise intersection of those three distinct skills, he had virtually zero direct competition. He had located a poker table where he could completely dominate. He contrasts this with people who obsess over remaining in the most punishing environment just to say they competed at the highest level. Comparing it to professional athletics, Ethan points out that fighting for a benchwarmer slot on a World Cup championship team requires massive effort, whereas being the undisputed franchise star on a sixth-place team often yields a substantially larger paycheck. Both paths are legitimate, but professionals must be honest about whether they value the vanity of the elite team badge or the financial and career leverage of being the star player.

---

[01:54:13](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6853s) How the Political Game Changes When Everyone Plays Optimally

Ryan Peterman asks how behavior shifts when you are forced to remain at that high-level table where every participant is playing the game optimally. Ethan explains that the dynamics change fundamentally because all simple moves, cheap tricks, and surface-level traps become completely obsolete. When you are dealing with less experienced peers, simple bluffs, baiting tactics, or minor political posturing can easily tilt the board in your favor.

Once every peer at the table is an all-star, however, play becomes intensely conservative. Everyone understands the mechanics of leverage, influence, and organizational strategy. As a result: - No one falls for obvious bluffs or basic traps. - There are no easy shortcuts available to exploit. - Any tactical or strategic mistake is instantly identified, seized upon, and ruthlessly punished by the other players.

In an all-star environment, a single miscalculated step can immediately take you out of the running, forcing everyone into an ultra-cautious, defensive posture.

---

[01:55:11](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=6911s) How Jeff Bezos Burned Ethan for Empire Building

Ryan pivots to an explicitly darker hypothetical: empire building. Given Ethan's immense rise to the VP level at Amazon, Ryan asks candidly whether Ethan ever engaged in the practice himself. Ethan readily admits that in hindsight he certainly did, noting that the human mind has a boundless capacity for self-rationalization. Leaders rarely tell themselves they are empire building for sheer status; instead, they frame it through backlog ambition: "Imagine what we could achieve with 375 more people, and since it isn't coming directly out of my personal wallet, why not ask for it?"

This habit came to an abrupt, brutal halt during an annual review meeting with Jeff Bezos shortly after launching the Amazon Appstore. Ethan's team walked in with a massive headcount proposal. Because they had initially built the organization as an extremely lean engineering unit, they had zero dedicated marketing staff. Convinced they needed a full-fledged marketing division, they submitted an arbitrary request for 25 marketers, rationalizing that operating in five countries justified five PR specialists per country.

```mermaid flowchart TD accTitle: Bezos Line-by-Line Headcount Interrogation accDescr: Ethan's massive headcount request is dismantled by Jeff Bezos down to line-by-line red pen approvals.

subgraph Ask["The Empire Ask"] A["Appstore Team submits massive request<br/>(e.g., 25 marketers, 5 PR)"] end

subgraph Interrogation["The Executive Test"] A --> B["Bezos Question 1:<br/>'What are these people actually going to do?'"] B -->|"Crappy surface answer"| C["Bezos Question 2:<br/>Follow-up probe"] C -->|"Second vague answer"| D["Credibility Collapses:<br/>'I don't believe any of your numbers.'"] end

subgraph Correction["The Mandate"] D --> E["Mandate: Buckets capped at 2-3 heads max"] E --> F["Line-by-line red pen review in front of S-team leaders"] end ```

The review immediately unraveled under Bezos's interrogation: - Bezos pressed them on the concrete responsibilities of the requested hires: "What are they *actually* going to do?" - The team offered superficial answers along the lines of "They'll do marketing—that's why they're marketing people." - Bezos asked a sharp follow-up question, received another flimsy response, and shut the review down completely. - Bezos declared flatly that because their first two answers were complete nonsense, he refused to believe any remaining numbers on the proposal. - He ordered the team to return with an itemized spreadsheet where no single bucket exceeded two or three people, explicitly tied to precise deliverables.

When Ethan and his team returned with the revised sheet, Bezos sat in front of all his senior direct reports with a red pen, taking them over the coals line by line—approving two heads for PR, striking another bucket down to zero, and approving three elsewhere only with rigorous caveats. Ethan acknowledges Bezos was completely right: the team had let project launch euphoria morph into lazy daydreaming rather than disciplined operational thinking.

---

[01:59:11](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=7151s) Empire Building the Right Way: Tranching and Merch by Amazon

Following that burn, Ethan refined his approach to acquiring resources. Instead of asking for bloat that stripped resources from other deserving corporate priorities, he focused on building credible, high-return business proposals and mastering execution mechanics. Whenever senior executives pushed back on large headcount proposals by claiming the team could never hire that fast, Ethan would propose a performance-based tranche model: - The executive holds an allocation of 100 headcount. - Roles are released in tranches of 20 at a time. - If Ethan's organization failed to successfully fill the first 20 heads with high-caliber talent, they forfeited the right to the next 20.

Ethan also learned that legitimate empire building stems from generating novel revenue that executive leadership actively wants to fund. A prime example occurred during his time leading the Amazon Appstore. Tasked with competing against Google and Apple—behemoths that fully owned their respective mobile operating systems—Ethan's team searched for an asymmetrical advantage. Recognizing that neither Apple nor Google possessed Amazon's physical logistics backbone, they pitched mobile game developers on handling their physical merchandise and game swag.

To support this, they spun up an internal initiative called Merch by Amazon, kicking it off with on-demand t-shirt printing. When senior leadership questioned why an Appstore software team was diverting headcount into printing t-shirts, Ethan defended the hypothesis. While the project ultimately did not move the needle on mobile app distribution, the underlying printing and fulfillment infrastructure took off in an unexpected market: printing custom party shirts, political statements, and viral slogans.

Recognizing the surge, Ethan immediately pivoted the business model away from mobile games to focus purely on high-volume print-on-demand consumer apparel. That venture eventually scaled into a business generating over $1 billion a year before being spun out of his organization into its own corporate division, proving that sustainable empire building relies on rapidly converting resources into measurable revenue and pivoting when commercial realities dictate.

[02:01:59](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=7319s) Shifting Resources and Pivoting Failed Projects

Ethan reflects on the necessity of staying flexible when business hypotheses crash and burn. He recalls his original thesis for printing t-shirts: the goal had been to convince mobile game developers to prioritize submitting their apps to the Amazon Appstore. In reality, game makers did not care in the slightest because merchandise represented such a trivial slice of their revenue. Instead of admitting defeat and surrendering the assets, Ethan's team discovered alternative ways to monetize the operation, kept the cash flowing, and preserved the initiative. He applies that same logic directly to headcount: whenever he secured staffing for a project that subsequently tanked, he never went back to leadership offering to return the headcount. Instead, he would preemptively announce that the failed project was shut down, but frame it as great news because he had already redeployed those engineers onto a winning initiative that was now moving twice as fast.

Ethan concedes that some of his former peers listening to his stories might view him as "an empire builder" or describe his maneuvers as "really slippery." While he dislikes the idea that people might view him that way, his ultimate rationalization is that he consistently produced hard results and cold cash for the company:

> "The only defense I have is I made it pay off for the company to the goals the company wanted and/or in hard cold cash... Some of my old peers will be like, 'Ethan, you were just really slippery.' I hate that idea that they might think that. I would say, 'Well, I did deliver a lot of value, right? At least I made a lot of money and you can't deny that.'"

[02:03:28](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=7408s) Retaining Headcount and Playing Offense in Resource Competition

When asked whether leadership ever attempted to claw back his headcount, Ethan explains that Amazon rarely shrank during his tenure, meaning pure headcount clawbacks were uncommon. However, avoiding cuts required relentlessly playing offense. By the time senior leadership realized a project was faltering, Ethan had already reassigned his personnel to other high-value initiatives. For leadership to take them away, they would have had to actively pull people off an acknowledged top priority. Furthermore, Ethan made it an ironclad rule never to leave open requisitions at year-end, which was leadership's favorite target for clawbacks. When Amazon created competitive hiring pools—for example, authorizing 1,500 open roles across the company against a total budget of only 1,000, with a mandate that the gate would drop once 1,000 hires were made—Ethan poured immense effort into hiring fast so all his spots were filled before other teams even realized what happened.

```mermaid flowchart TD accTitle: Ethan's Preemptive Headcount Defense Loop accDescr: Flowchart illustrating how Ethan retained headcount by hiring fast and redeploying resources before leadership could intervene.

subgraph Allocation["1. Aggressive Hiring"] A["Company opens overbooked headcounts"] --> B["Ethan fills roles fast before gates shut"] B --> C["Slower teams leave reqs unfilled"] C --> D["Ethan petitions to 'borrow' their open reqs"] end

subgraph Defense["2. Redeployment & Execution"] D --> E{"Does project succeed?"} E -- "Yes" --> F["Deliver massive value & cash"] E -- "No" --> G["Preemptively redeploy team to working initiative"] G --> H["Ship raw, visible iterations ('warts and all')"] H --> F end ```

Ethan's empire-building tactics extended to actively seizing headcount from struggling peer teams. He taught internal courses on rapid hiring and would openly lobby leadership to reassign unused requisitions from slower teams to his own org before the year ended. His underlying justification was speed and visible execution: while his releases were sometimes hacked together and admittedly shipped with "warts," having working software in production always defeated the perfectionists who spent two years polishing deliverables that never saw daylight.

- **Hiring as a competitive race:** Amazon's overbooking strategy rewarded managers who filled seats aggressively; teams that waited until November found the gate closed and their headcount revoked. - **The ship leaving the dock analogy:** Once resources were hired and deployed to the open sea of a new project, pulling them back became far too difficult for leadership to justify. - **Biased toward shipping:** Ethan preferred shipping raw, imperfect solutions that proved tangible progress over getting bogged down waiting for a flawless launch that might never materialize.

[02:07:33](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=7653s) Navigating Tech Careers and Value Creation in the Age of AI

Turning to the modern tech environment, Ryan asks how professionals should navigate career planning amid the boom-and-bust uncertainty created by artificial intelligence. Ethan notes that while he lacks a Wall Street crystal ball, AI will inevitably generate distinct winners and losers, eliminating certain routine positions while creating roles not yet understood. In response, Ethan strongly advocates developing breadth and flexibility over narrow technical depth. He emphasizes doubling down on interpersonal soft skills specifically because AI targets rule-governed disciplines—such as syntax-heavy coding, legal analysis, and mathematics—whereas human politics, empathy, and messy gray areas remain virtually impossible for a disembodied AI model to replicate.

At the same time, Ethan warns against both extremes: neither ignoring AI tools out of denial nor making the mistake of obsessing over them entirely. Dedicating every waking moment solely to AI tool mastery can turn into a pyrrhic victory—what Ethan calls "winning the race off the cliff":

> "You will be the best person at using the tools, but as those tools chip away at what you do or obsolete what you do, you'll be the last one kept around to operate them until they don't need you either."

Reflecting on history, Ethan points out two contrasting possibilities: just as spreadsheets increased the demand for financial analysts and automated teller machines did not wipe out bank tellers, AI-assisted tools and "vibe coding" might expand software demand by exposing non-technical people to what code can do until they hit limits where real engineers become necessary. Regardless of how the balance shakes out, keyboard-pounding manual coding will change forever. Moving forward, the true value shifts toward high-level judgment: deciding what actually needs to be built, prioritizing releases, and articulating the value proposition to customers when engineers can easily produce ten times more software than before.

[02:11:41](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=7901s) Taste, Judgment, and Why Org Flattening Is Cyclical

Addressing the rapid rise of AI coding and automation, Ethan points out that organizations rarely need ten times as many features; in reality, they often need fewer, better, or distinctly different features. The critical question becomes who decides what actually gets built. That decision requires human taste and discernment: "I'd rather be in the judgment seat than in the running the tools seat." High-level judgment will remain exceptionally prized regardless of how powerful developer tools become.

Ryan brings up the recent industry-wide trend of delayering organizations and eliminating middle management layers, asking whether this flattening is merely a temporary fluctuation or a permanent shift. Ethan argues firmly that delayering is a cyclical phenomenon tied to economic pressures and headcount freezes. When companies shift from aggressive expansion to rationalization and belt-tightening, executives habitually target middle managers under the misguided assumption that they produce nothing of direct value.

To illustrate why management layers are deeply embedded in human nature, Ethan points to historical precedent: around 600 BC in ancient China, early dynasties introduced testing for civil servants, which evolved into formal written examinations by 200 BC. Because administrators and managers have existed for millennia, Ethan remains skeptical that software tools can suddenly alter fundamental organizational dynamics: - **Historical permanence**: Human organizations have required administrative and coordination layers for thousands of years to centralize, organize, and represent collective work. - **The management workload paradox**: While AI might allow managers to lead larger spans of control through automation, the surge in individual output creates a corresponding surge in required decisions, judgment calls, and cross-team communication, which can actually increase the necessity for managerial coordination. - **The Jensen Huang outlier**: High-profile examples like Nvidia CEO Jensen Huang managing 60 direct reports cannot be generalized. Those 60 individuals are elite, battle-tested executives. Expecting an average first-line manager to scale from ten direct reports to a hundred while maintaining quality is unrealistic.

---

[02:15:11](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=8111s) Navigating Layoffs: Controlling Optics and Staying Off the Chopping Block

Ryan asks how professionals can safeguard themselves against potential downsizes and how to manage the optical fallout if they are caught in a layoff. Addressing optics first, Ethan emphasizes that the historical stigma around being laid off has largely vanished. With massive downsizing rounds across Meta, Amazon, Google, and other major tech firms, being impacted is understood as an organizational reality rather than an indictment of personal competence.

The secret to framing a layoff during interviews is acknowledging it cleanly as a simple fact and immediately pivoting toward the future:

```mermaid flowchart LR accTitle: Layoff narrative pivot framework accDescr: Three-step framework moving from stating facts, to reframing learnings, to pivoting to future value. A["State the Fact<br/>'Org was eliminated'"] --> B["Reframe Experience<br/>'Brings big-tech scale'"] B --> C["Pivot to the Future<br/>'Excited to apply it here'"] ```

Candidates should explain matter-of-factly, "Yeah, unfortunately my organization at Meta was eliminated," and then leverage that background into a compelling value proposition: - Frame the exit as an opening to bring world-class architectural insights, operational philosophies, or scaling experience to a new organization. - Avoid dwelling on grievance or disappointment; keep the past concise and steer the conversation directly toward what you can build next.

When it comes to surviving a corporate workforce reduction in the first place, Ethan notes that individual direct managers rarely make the final call; decisions typically occur two or three levels higher at the skip-level or executive tier. Top managers facing mandate-driven organizational shutdowns will actively lobby their peers to place their high performers elsewhere. To ensure you make that internal transfer list: - **High performance ratings**: Secure top-tier ratings in advance, as leadership reviews workforce spreadsheets by performance tier first. - **Recognized contributions**: Build visible tools or foundational platforms that bear your name (revisiting the example of Matt Round's internally famous tool). - **Sole-source knowledge**: Maintain critical domain knowledge—much like the indispensable, curmudgeonly senior engineer—so leadership cannot safely eliminate your post without breaking core operations. - **The winning formula**: Survival relies equally on technical excellence and social visibility: "Be good and be likable. Both are additive, maybe even multiplicative."

---

[02:18:39](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=8319s) Demystifying Executive Presence: Gravitas, Influence, and the Danger of Overconfidence

Shifting from political defense to constructive soft skills, Ryan asks Ethan to define "executive presence" and explain how an aspiring leader can cultivate it. Ethan explains that executive presence is inherently determined by the perception of others. He outlines two distinct lenses for understanding it:

| Model | Core Concept | Key Breakdown / Indicator | |:--- |:--- |:--- | | **Academic Framework** | Compositional Attributes | • 60% Gravitas (weight of accomplishments)<br/>• 30% Communication skills<br/>• 10% Appearance | | **Behavioral Framework** | External Deference | Colleagues actively seek out your perspective and backing on initiatives outside your direct scope. |

At its core, executive presence comes down to whether an individual commands the room. High presence is revealed when people instinctively listen, watch your body language, or take cues from your reactions. Ethan notes wryly that in highly political corporate settings, if an executive picks up their phone while someone else is speaking, the entire room may mentally dismiss the speaker simply because of that gesture.

Ryan observes that quiet technical veterans sometimes earn this presence purely through deep historical competence, while others carry it through posture, tone, and boundary-setting. Ethan illustrates both the power and the hazard of natural presence with a personal anecdote about his own speaking style. Because he naturally speaks with deep conviction—sounding like "the voice of God" handing down tablets from a mountain—people assume he has absolute certainty. His wife once gave him a candid reality check: > "Ethan, I've learned that you sound like you know. And so sometimes when I think something different, I don't say anything because you sound so sure. And then it turns out you're wrong. And I'm like, 'Why didn't I say anything? I knew we needed to turn right at the last corner, but you said, "No, it's straight."' And you sounded like you knew and I bought it."

This represents executive presence tipping into a liability: projecting absolute conviction when offering an unverified hypothesis, leading others to abandon their own correct judgment simply because of how authoritative you sound.

[02:22:13](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=8533s) The Anatomy of Executive Presence

Ethan Evans explains that the primary foundational drivers of executive presence are confidence and decisiveness. When someone wavers and undermines themselves by saying, "Well, I think maybe it's straight," listeners are immediately invited to challenge them. In contrast, stating something clearly and decisively—"It's straight. We don't turn. It's two lights, then a right"—prompts immediate buy-in because of its specificity.

To illustrate how persuasion works, Evans shares an exercise from the executive presence class he teaches: he tells participants that statistics containing numbers are 62% more believable than claims without them. In reality, he completely invented that figure on the spot, but because it sounded exact and was delivered with sheer conviction, almost everyone buys it unquestioningly. Evans points out that whether someone likes it or not, physical and vocal markers historically dictate perception: being tall, being white, and having a deep voice carry profound, unearned advantages across political and corporate history. He jokes that when actors voice God, they always speak in a deep baritone because "you never see a squeaky God."

Beyond physical traits, presence is cultivated through vocal modulation, controlled pacing, deliberate pauses, purposeful gestures, and unflappable emotional regulation. Evans describes the ideal archetype as the "trustworthy uncle"—a capable, calm relative who runs a successful business, owns two cars, has a lovely family, and seems entirely comfortable in every room. When such leaders express anger, it is never an out-of-control, spit-spraying tantrum; rather, it is a chilling, controlled lean-in: "How dare you, little one." Evans characterizes these behaviors as human adaptations of primate dominance displays: the behavioral cues that determine which ape commands the tribe and gets the bananas.

- **Vocal Delivery:** Speaking slowly, lowering the pitch, and introducing deliberate pauses project authority far more effectively than rapid speech. - **Controlled Emotion:** True executive command relies on never appearing flustered; even negative emotions like anger are expressed with deliberate composure rather than wild outbursts. - **Primate Dominance Cues:** Many interpersonal presence techniques mirror mammalian dominance behaviors, signaling high status through posture, space ownership, and unhurried reactions.

---

[02:25:00](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=8700s) Vocal Manipulation and Archetypes: From Thatcher to Musk

Ryan Peterman brings up Elizabeth Holmes as a well-known example of an executive who artificially deepened her voice to project leadership authority, noting that leaked recordings reveal her natural speaking register was substantially higher. Evans confirms this pattern and cites Margaret Thatcher, the UK's first female prime minister, who early in her political career was attacked in the media for sounding high-pitched and "screeching." In response, Thatcher deliberately trained herself to speak lower and slower, adopting masculine vocal markers to compete in a male-dominated political arena. While people can rightfully debate the fairness of having to adopt such tactics, Evans emphasizes pragmatism: it worked for Thatcher and Holmes alike.

```mermaid flowchart TD accTitle: Executive Presence Paths accDescr: Two distinct routes to commanding authority in business: deep technical mastery versus theatrical showmanship and conviction. subgraph ExpertisePath["Expertise & Substance"] A["Unimpeachable Track Record"] --> B["Quiet Authority"] B --> C["Warren Buffett Model"] end subgraph ShowmanshipPath["Showmanship & Conviction"] D["Theatrical Stage Presence"] --> E["Audacious Projections"] E --> F["Jobs / Musk Model"] end ```

Evans emphasizes that an executive does not need every single trait to succeed, provided they leverage alternative strengths. He contrasts two major archetypes: 1. **The Expert Architect (Warren Buffett):** Buffett is never described as a dramatic showman, yet he commands immense executive presence and universal deference strictly through his track record and unmatched investing acumen. 2. **The Charismatic Showman (Steve Jobs and Elon Musk):** Jobs relied on meticulous, highly polished stagecraft. Musk, while lacking polished oratory, commands audiences through pure, unwavering conviction in outrageous claims.

Peterman notes that while Jobs was exceptionally rehearsed, Musk’s public speaking often appears unpolished. Evans explains that Musk’s particular showmanship lies in delivering seemingly impossible concepts—such as building manufacturing factories in outer space—with absolute, unflinching certainty. Musk frames his vision around an undeniable narrative of past triumphs: critics said electric vehicles and private space exploration were impossible, yet he delivered both. His presence hinges on daring the audience to doubt him again, converting utter conviction into corporate reality.

---

[02:29:25](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=8965s) How to Network Naturally by Giving Away Value

Addressing how professionals should build authentic relationships at work, Evans rejects the dreaded cocktail party model—awkwardly standing around a room with a drink in hand trying to schmooze strangers. Instead, he outlines an organic, generous framework: identify something you genuinely love doing, that you are skilled at, and that comes easily to you, and package it to give away to others at zero cost.

```mermaid flowchart LR accTitle: Generosity-Based Networking Model accDescr: Flowchart showing how identifying personal passions and sharing them creates broad organizational influence. A["Identify Personal Passion / Skill"] --> B["Package into Resource or Service"] B --> C["Give Away to Peers Freely"] C --> D["Broad Internal Goodwill & Recall"] D --> E["Effortless High-Leverage Network"] ```

Evans illustrates this approach with two personal and observational examples: - **Hiring Workshops:** Early in his Amazon tenure, Evans realized he excelled at rapid, high-quality hiring. He packaged his system into an internal training class for other managers, eventually expanding to broader executive teaching and public Twitch streaming. Because he loved doing it, helping others never felt like a burdensome chore. - **The Ski Ticket Facilitator:** Evans recalls an engineer at Amazon who loved skiing and negotiated bulk discounts directly with local mountain resorts. He handled the distribution of discounted lift tickets internally purely out of his passion for skiing and getting cheaper passes for himself. In doing so, he forged hundreds of personal relationships across diverse business units. Whenever he needed a favor, a cross-functional resource, or an engineering review, colleagues instantly recognized him—"Oh, you're the ski ticket guy!"—and eagerly helped him out.

Evans stresses that networking value does not need to be deeply technical or work-related. As long as a person shares something they enjoy that makes life easier or better for others, they build deep, resilient professional capital without awkwardness or superficiality.

[02:32:29](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9149s) Organic Networking and the Dark Principles of Power

Ethan explains why traditional forced networking feels so excruciating. Walking up to a stranger and awkwardly saying, "Hi, I'm Ethan. Why are you here? Let's find something in common so you give a shit," is an introvert's ultimate nightmare. Without a genuine shared interest, building a real relationship from scratch is nearly impossible. By contrast, organic connection works effortlessly when centered around a concrete hobby or utility—like a group ski ticket initiative where everyone involved already shares excitement about the weekend weather and snow conditions. For software engineers, this common ground usually lies in domain expertise: every engineer knows a specific technology deeper than the average peer. Sharing that knowledge on forums, on Reddit, or in internal recordings creates immediate organic value without forced schmoozing.

Ryan pivots to the darker, Machiavellian side of corporate networking, citing a viral post outlining the basic rules of workplace politics: 1. Identify who holds power and who does not. 2. Help those powerful people as best as you can. 3. Ensure they are fully aware that you are the one helping them.

Ryan asks how someone targeting a promotion can apply this calculus to get the decision-making VP on their side without coming across as blatant or transactional.

[02:34:17](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9257s) Getting on an Executive's Radar and the Refugee Aid Sledgehammer

Ethan lays out practical tactics for catching a senior executive's attention. One direct method is demonstrating broad organizational reach. An employee can reach out mentioning an internal tool, interview utility, or community project they created, casually noting that hundreds of people across the VP's organization are actively using it. Even if the executive does not personally need the tool, powerful people are acutely vigilant about anyone who commands influence over their headcount. Noticing that a single person has the ear of a third of their team forces the leader to pay attention—either out of strategic wariness or to harness that influence for their own objectives.

Another proven path is working through intermediaries. Instead of cold-pitching a distant VP, an employee should approach one of the VP's direct reports within their existing network and ask for an introduction, a recommendation, or a skip-level meeting. People are naturally inclined to grant favors that cost them very little, because being helpful provides a tremendous emotional payoff and makes the giver feel generous and influential.

```mermaid flowchart TD accTitle: Paths to Executive Visibility accDescr: Two distinct routes to get on a senior executive's radar: demonstrating broad bottom-up influence or using network intermediaries.

subgraph Direct["Direct Leverage"] A["Build High-Utility Tool / Community"] --> B["Attract Critical Mass of Org"] B --> C["Drop In: '300+ of your people use this'"] C --> D["Executive Takes Notice / Wants Influence"] end

subgraph Intermediary["Intermediary Path"] E["Helpful Peer / Direct Report in Network"] --> F["Request Intro / Skip-Level Recommendation"] F --> G["Peer Grants Low-Cost Favor to Feel Good"] G --> H["Warm Introduction to Executive"] end ```

To illustrate the sheer power of network intermediaries, Ethan shares an extreme example from his personal life: - **The Challenge:** Early in the Russia-Ukraine war, Ethan was doing humanitarian charity work for Ukrainian refugees in Poland and needed to transport 10 suitcases packed with medical supplies and gear overseas for free on a United Airlines flight. - **The Ask:** Rather than hunting down airline reps himself, he posted a simple request to his professional network asking if anyone knew someone at United who could authorize the baggage waiver. - **The Escalation:** A connection responded that he personally knew the Chairman of the Board of United Airlines and introduced Ethan directly via email. - **The Interaction:** Ethan candidly told the Chairman, "Dude, this is such a waste of your time. Just delegate me to someone. Here's what I need." The Chairman graciously replied, "It's cool. I like to help people." - **The Outcome:** The bags flew entirely free, and when the courier arrived at the airport, the local United ground crew met him with a custom gift basket.

Ethan notes that while this was "using a sledgehammer to kill an ant," it underscores how asking for reasonable favors gives people in a network an easy opportunity to feel like benevolent benefactors at virtually zero personal cost.

[02:39:33](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9573s) The "One Meeting" Rule for Mentorship Requests

When asked how he responded to lower-level employees who approached him with obvious career-advancement motives while he was an Amazon VP, Ethan admits he was unapologetically direct. Engineers three or four tiers below him in the hierarchy would routinely ask for monthly one-on-one mentorship sessions. His standard response set hard operational terms upfront:

> "I have absolutely no time for this. I have no time to put you on my calendar, but here's the deal. I'm going to give you one meeting. You're going to bring me something really interesting I don't know, and you're going to bring me value in that meeting. And if you do, we'll have another one. That's your shot. Go do it."

Ethan explained to them that senior executive work is largely monotonous—dominated by back-to-back reviews and pushing organizational paperwork around. If an engineer could deliver fresh technical insights, unique operational intelligence, or genuine business value, Ethan was thrilled to keep meeting. But the moment the conversations became boring or generic, the meetings stopped. Some engineers stepped up and thrived under the condition, while others never scheduled the first conversation, which suited Ethan just fine.

[02:41:01](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9661s) Triangulating Hidden Incentives

Ryan points out that most corporate leaders do not state their terms with Ethan’s level of bluntness, making it difficult for junior employees to decipher what leaders actually care about. Ethan emphasizes that uncovering a leader's true priorities and hidden incentives requires intentional investigation across multiple vectors:

- **Direct Inquiries:** Simply asking leaders about their priorities when a sufficient foundation of trust exists. - **Observational Listening:** Paying close attention during broad communication forums like org-wide all-hands meetings and leadership staff reviews, tracking specifically which problems they repeatedly highlight and which metrics they celebrate. - **Triangulation via the Network:** Speaking to the leader’s direct reports, chiefs of staff, or long-tenured colleagues to cross-reference what keeps the executive up at night before pitching a solution.

[02:42:06](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9726s) Four Ways to Discover What Leaders Value

To uncover what a senior leader truly cares about, Ethan Evans breaks down a concrete four-part framework: ask, listen, triangulate, and observe. Triangulating involves cross-referencing what a leader tells different individuals—piecing together fragments, rumors, and inferences from across their circle. Observing actions provides the clearest signal of all, because actions speak louder than words. A leader's true priorities are revealed by where they invest capital, where they allocate headcount, what meetings dominate their calendar, and where they dedicate their time. Once those priorities are clear, an employee can align their work to those specific focus areas and ensure their contributions surface through hallway conversations, status reports, or mutual colleagues.

```mermaid flowchart TD accTitle: Four Ways to Discover Leader Priorities accDescr: A flowchart illustrating the four methods to determine what leaders value and align work accordingly.

subgraph Discovery ["1. Discover Hidden Priorities"] A["Ask Directly"] B["Listen to Nuance"] C["Triangulate with Peers"] D["Observe Resource Allocation"] end

subgraph Alignment ["2. Align & Deliver Value"] E["Match Projects to Priorities"] F["Showcase Work via Reports & Networks"] end

Discovery --> Alignment ```

Evans contrasts this subtle approach with his own direct, transactional philosophy: "Let's make a deal." In his view, offering to deliver specific, high-value outcomes in exchange for career advancement is not inherently bad; it is simply the explicit corporate compact—bring more value, get paid more, and move up. However, many leaders are uncomfortable being openly transactional and operate implicitly. Working under these leaders requires tolerating ambiguity:

> "You're going to have to weather more ambiguity. I have found that if you build a relationship with people... they may never be willing to be transactional or explicit with everyone, but they will do it with you inside the confines of that built personal relationship."

---

[02:44:43](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=9883s) Sudden Disappearances and What Happens Behind the Scenes in HR

Ryan Peterman shares an experience from his time as an engineer at Meta: while poor performance typically leads to a visible, gradual process of being managed out, there were instances where a coworker was present on Friday and vanished by Monday with zero explanation. Evans explains that when an employee abruptly disappears, it is almost never standard performance management; it occurs because the individual engaged in behavior that exposed the company to severe legal, financial, or reputational liability—such as theft, embezzlement, racism, or sexual harassment.

Leaks to the press are a frequent driver of immediate dismissals. Evans recalls an employee with strong personal political beliefs who objected to a corporate initiative, leaked an internal memo to a reporter, and failed to realize how extensively internal IT tracking monitors document access and data movement. Once the story broke, security traced the paper trail directly to them, resulting in immediate termination.

Other dismissals stem from astonishing lapses in judgment rather than outright malice: - **The Gun Collection in the Game Studio:** While Evans was running a video game development team producing violent shooters, an artist brought his extensive collection of real firearms into the office, spreading them across his desk in an open California workplace. When questioned, the artist innocently explained that he was designing weapon assets and wanted the real guns on hand as visual reference models. While leadership recognized he was purely thoughtless rather than dangerous and sent him home with a strict warning never to repeat it, Evans notes that an immediate termination would have surprised no one. - **The Stalker Janitor Incident:** Returning from a business trip, Evans was met at the door by his female executive assistant and a female team leader. The leader had arrived at work to discover what appeared to be dog mess under her desk—a plausible scenario under the office dog-friendly pet policy. However, the cleaning staff determined it was human feces. An investigation by corporate security quickly connected the act to a building janitor who had exhibited inappropriate fixation on the female leader, claiming this bizarre act was an expression of romantic interest. The individual was immediately fired and served with a restraining order banning him from approaching the building or the employee.

---

[02:50:13](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10213s) Burning People to Get Ahead and Early Amazon Choices

Responding to Peterman's question about whether he ever had to deliberately "burn" someone to advance his own career, Evans pauses, cautioning against the human tendency toward retrospective rationalization. He acknowledges that he fiercely competed with peers and actively worked to ensure his achievements appeared superior. However, he maintains that he never targeted an individual to intentionally destroy them or sabotage their position.

Instead, the situations he feels most conflicted about stem from competitive forks in the road where advancing his own ambitions inevitably affected someone else's trajectory. Evans recalls his first week at Amazon, having accepted an offer for a confidential project without knowing what role he would occupy. Upon arrival, his new manager presented him with two distinct paths: 1. Leading the development of Amazon's very first customer-facing video product. 2. Building the underlying backend digital ingestion infrastructure intended to support video, music, and the digital books initiative that eventually became the Kindle.

Driven by a preference for consumer-facing technology rather than core infrastructure, Evans immediately opted for the video product, setting off a chain of events that dictated career outcomes for the leaders around him.

[02:52:16](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10336s) The Cost of Fighting for Projects: Screwing Over a Peer Unintentionally

Ethan Evans reflects on the single clearest moment in his career where his aggressive pursuit of a project directly hurt another colleague. Earlier in his tenure, he had pitched leadership on building a new video product. His leader immediately agreed: "Great, done." Evans had no idea at the time, but another manager was scheduled to join the company the very next Monday. Leadership had apparently promised this new hire that he would be the one building the video product. Because Evans had staked his claim and won it just days prior, the newcomer was unexpectedly reassigned to an infrastructure project instead—effectively taking a role he did not want for two whole years.

Evans admits that even if he had known another candidate existed, he still would have fought aggressively for the role. He had domain history, felt he was exceptionally qualified, and wanted to build what he cared about. His intention was never to sabotage the other manager, but the structural reality remained zero-sum: Evans got what he wanted, and someone else suffered the fallout.

- **Unintended side effects of ambition**: Even when you are not actively trying to harm someone, pursuing prime opportunities means someone else loses out. - **Two-year fallout**: The incoming manager was stuck leading an infrastructure project rather than the product vision he had negotiated when signing his offer. - **No regrets on advocating for oneself**: Evans acknowledges that he would have made the same push regardless: "I would have still pushed for it, sure, because I want to do what I want to do, just like everybody else."

---

[02:53:24](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10404s) Responding to Critics Who Hate Corporate Politics

Ryan Peterman brings up the polarizing nature of discussing corporate politics. Many viewers appreciate the candid breakdown of "how the game works," but another substantial group finds the premise morally distasteful, asking how anyone can endorse such manipulative dynamics. Evans explains that a close personal friend holds that exact viewpoint, arguing that the system is fundamentally toxic and that discussing tactics validates the "evil side."

Evans respects the desire for a fair world where people are judged strictly on intentions, capability, and merit, but points out that corporations operate on scarcity, competition, and flawed human psychology. Idealistic reforms take decades or centuries, just like the historical fights against slavery, oppression, and gender inequality. He mentors women navigating corporate bias not because he endorses discrimination, but because waiting for systemic perfection does not help someone's career this year.

To illustrate his view on harsh moral choices, Evans shares a deeply personal story regarding the war in Ukraine, where he runs a charitable foundation aiding refugees in Poland:

```mermaid flowchart TD accTitle: Pragmatic Moral Tradeoff accDescr: Visualizing the moral calculation between real-world constraints and theoretical ideals.

subgraph RealWorldCrisis ["Real-World Moral Dilemma"] A["Ukrainian friend's husband completes 2-year volunteer army term"] B["Military refuses discharge; facing near-certain death at the front"] C["Evans & friend provide $1,000 to bribe him out of service"] D["Husband spared; likely replaced by an unknown soldier"] A --> B --> C --> D end

subgraph EthicalTakeaway ["Corporate Politics Parallel"] E["Critics judge by theoretical ideals"] F["Pragmatists act within flawed reality"] E -.->|"VS"| F D --> F end ```

By providing $1,000 alongside a friend to bribe the man out of service, they saved his life, knowing full well that an unknown replacement likely took his place on the front line. Evans notes that critics can find 50 ways to call that decision evil, but in a messy world of immediate stakes, he prioritized helping the person in front of him. In his view, navigating corporate politics follows the exact same logic: dealing with how the world operates today rather than refusing to engage because conditions are imperfect.

---

[02:59:03](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10743s) Top Book Recommendations on Power Dynamics and Influence

Peterman asks for Evans's definitive reading recommendations for understanding power, influence, and corporate psychology. Evans names three foundational texts:

1. ***Leadership and Self-Deception* by the Arbinger Institute**: Evans’s all-time favorite book on relationships. It examines the mistake of treating people as "objects" or "APIs"—pushing buttons simply to elicit an automated response. When leaders dehumanize peers or subordinates into roadblocks, people sense the manipulation and push back. Approaching others with genuine empathy and transparency creates reciprocal respect. 2. ***Never Split the Difference* by Chris Voss**: A tactical masterclass in negotiation by a former FBI hostage negotiator. Evans emphasizes that understanding negotiation is really about understanding underlying human motivation and psychology. 3. ***The 48 Laws of Power* by Robert Greene**: Although Evans admits he dislikes endorsing the "dark side," he considers Greene's work a vital, comprehensive catalog of psychological manipulation. Whether one chooses to deploy those tactics or not, studying them is essential for recognizing when they are being used against you.

---

[03:00:45](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10845s) Speedrunning to VP: What to Do Today

Peterman asks how Evans would "speedrun" his way to a VP position if he were starting fresh today at Amazon. Evans—drawing on his background as a former VP at Twitch—immediately clarifies the meta-strategy: he would **not** attempt to speedrun to VP inside modern Amazon. When Evans joined, Amazon was compounding at an extraordinary rate and grew a hundredfold, creating endless greenfield leadership openings. Today, mature tech giants no longer offer that organic velocity.

Instead, Evans outlines a pragmatic multi-step roadmap:

* **Suck out skills within 18–24 months**: Treat the initial big-tech role as an intensive apprenticeship to absorb processes, technical architecture, and execution standards. * **Master an externally valuable domain**: Specialize deeply in an infrastructure or platform competency—such as AWS services—that other companies are desperate to adopt. * **Jump externally to a high-growth scale-up**: Leverage specialized expertise to skip levels externally, pitching emerging high-growth firms on his ability to help them implement and scale those critical cloud technologies rapidly.

[03:02:17](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=10937s) Swinging for Home Runs and Hopping Companies

Continuing his strategy on how to speedrun a career to Vice President, Ethan explains that once you deliver value cheaply at a new company, you immediately use that leverage to push for advancement and leadership. However, to actually become a VP, you need real management skills that you are not naturally trained in, meaning you must actively study psychology, organizational dynamics, risk-taking, and decision-making.

Crucially, Ethan advises ambitious engineers to "favor gambling" and taking big risks. You will move up much faster by shooting for massive wins and missing a few than by playing it safe, because—as he notes with a touch of dark humor—"unfortunately, fortunately, you can always leave behind the smoking ruins of your disaster at one company and try again somewhere else." Drawing an analogy from the baseball book *Moneyball*, he contrasts batting for a safe on-base percentage with swinging hard and wild for a home run. While swinging for the fences means striking out more often, "nobody cares that you got on base; they like to see the ball fly over the wall." Taking enough big swings eventually lands the home run that makes you famous.

Putting it all together, Ethan's blueprint is to take your expertise and the Amazon brand name on your resume, move to a high-growth company, deliver value, ask for advancement, and take big risks. If the gamble succeeds, you move up; if it fails, you hop to another company and try again. Once you hit a high-growth company where your bets pay off and you are moving up—which might take until your third or fourth company—you ride that wave to the end of your speedrun.

```mermaid flowchart LR accTitle: Ethan's Career Speedrun Loop accDescr: Leaving Big Tech with brand leverage to take big swings at high-growth companies, hopping if a risk fails, and riding the wave once a bet succeeds. subgraph Prep["1. Foundation"] A["Build expertise & resume at Amazon (L4 to L5/L6)"] B["Study psychology, orgs & decision-making"] end subgraph Execution["2. High-Growth Swings"] C["Join high-growth company"] D["Deliver value & take big risks"] end subgraph Outcome["3. Result"] E["Ride the wave to VP"] F["Leave 'smoking ruins' & hop"] end A --> B B --> C C --> D D -->|"Home run (Success)"| E D -->|"Strike out (Disaster)"| F F -->|"Try again (3rd or 4th company)"| C ```

[03:04:08](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=11048s) Why Staying in Big Tech Today Is a "Slug Run"

While Ethan personally knows many people who started at entry-level at Amazon and are VPs today, he doesn't believe that path is repeatable anymore without taking 35 years. Trying to climb from the bottom to VP inside modern Big Tech is no longer a speedrun; it is a "slug run"—like a video game completionist playthrough where you are forced to slowly grind through every single side quest.

The reason this internal path has dried up comes down to raw headcount growth. When Ethan joined Amazon, the company had 14,000 employees; by the time he left, it had grown to 1.4 million, where it has more or less plateaued. The explosive growth that created endless leadership vacuums is simply gone. He points to Ryan's former employer, Meta, as an identical example: Meta used to grow like crazy and made many careers, whereas now it is shrinking. When Ethan asks Ryan if his own rapid career success at Meta would be repeatable today, Ryan agrees that while you might still move quickly through the early engineering levels, it is no longer repeatable at the higher levels where the business case matters much more.

Because of this stagnation at the top, Ethan recommends staying at Amazon only long enough to progress from L4 (entry-level) to L5, or maybe L6, and then getting out. Inside Amazon, there are roughly 30,000 to 50,000 L4s and 50,000 L5s, which means "you're just a number." However, if you leave for an external company where you are the *only* AWS-native engineer, you instantly transform being one of 50,000 L5s into massive leverage. This dynamic drives Amazon crazy: they cannot afford to pay all 50,000 L5s what each engineer is individually worth on the open market, so external companies constantly poach them to cut down their AWS bills and implementation times.

- **Amazon's growth plateau:** Grew from 14,000 employees when Ethan joined to 1.4 million when he left, and remains around 1.4 million today. - **Internal headcount scale:** Amazon has roughly 30,000–50,000 L4 engineers and 50,000 L5 engineers. - **External compensation arbitrage:** An external company might value an L5's AWS expertise at $300,000 because of the money saved on cloud bills and implementation speed, whereas Amazon is only paying them $200,000, making it easy for outsiders to buy them out.

[03:06:31](https://www.youtube.com/watch?v=KhjhRRz3VJw&t=11191s) Outro and Ryan's Ergonomic Keyboard Project

Ryan wraps up the interview by thanking Ethan for his time and transparency and asking where listeners can find his work. Ethan directs people to his website, `ethanevans.com` (which links out to all his platforms), and to LinkedIn under Ethan Evans. Thanking Ryan, Ethan jokes that he knows Ryan has an endless list of questions, so they will have to continue the conversation someday.

Addressing the audience directly, Ryan asks viewers to leave a like or comment to help the show grow, and invites recommendations for future guests—noting that past guests like Barbara Liskov, Mike Stonebraker, and Marc Brooker were all brought on the podcast specifically because viewers suggested them in the comments.

Finally, Ryan shares an update on a side project he has been building outside of the podcast: an ergonomic split keyboard that he wished existed, holding up a two-piece prototype to the camera (without its final case). They recently launched the keyboard on Kickstarter and hit their funding goal within eight hours. While the team is now embarking on the long journey of building the manufacturing tooling, Ryan notes that late pledges are still open on Kickstarter via the link in the description for anyone who wants to pick one up.

## Video description In this episode, I asked Ethan Evans (ex-Amazon VP) questions about common situations in corporate politics but they get increasingly darker.

• My ergonomic keyboard project I mentioned, you can follow along here: https://read.compose.llc/ • The Kickstarter page for it: https://www.kickstarter.com/projects/ryanlpeterman/compose-simple-ergonomics-beautifully-done

𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀:

• Spotify: https://open.spotify.com/episode/12o4mzyWFA5EPqkXDMw5UH • Apple: https://podcasts.apple.com/us/podcast/the-peterman-pod/id1777363835 • Transcript: https://www.developing.dev/p/e068-ethan-evans

𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝘁𝗼 𝘁𝗵𝗶𝘀 𝗲𝗽𝗶𝘀𝗼𝗱𝗲'𝘀 𝘀𝗽𝗼𝗻𝘀𝗼𝗿 𝗳𝗼𝗿 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 𝗺𝘆 𝘄𝗼𝗿𝗸:

• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://workos.com/

𝗧𝗶𝗺𝗲𝘀𝘁𝗮𝗺𝗽𝘀:

00:00 Intro 00:42 How to receive credit for your work 19:18 Ways for quiet people to get visibility 21:32 How to be trusted for top projects 29:52 How to defend from others taking your project 36:13 How to reject bad projects 44:10 How to be first for promo 55:35 How to handle managers that dislike career growth talk 01:06:30 What if your manager is in the way 01:15:43 Did he ever have overly political reports 01:28:06 How to fire a bad manager 01:35:16 What gives you leverage 01:43:41 How to defend against peers undermining you 01:50:24 What if everyone is good at politics 01:55:11 How Jeff Bezos burned him for empire building 02:03:27 How to retain your headcount 02:07:31 Career recommendations for the current landscape 02:15:11 How to avoid negative layoff optics 02:18:39 How to develop executive presence 02:29:25 How to network in a natural way 02:33:30 How to network with powerful people 02:41:01 How to learn hidden incentives 02:44:43 What happens behind the scenes with HR 02:50:13 Did he burn people to get ahead 02:53:24 What he says to people who hate politics 02:59:03 Top book recommendations on power dynamics 03:00:45 How he would speedrun career growth today 03:06:56 Outro

𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗘𝘁𝗵𝗮𝗻:

• Personal website: https://www.ethanevans.com/ • Newsletter: https://levelupwithethanevans.substack.com/ • LinkedIn: https://www.linkedin.com/in/ethanevansvp/ • YouTube: https://www.youtube.com/@EthanEvansVP • X/Twitter: https://x.com/EthanEvansVP • Facebook: https://www.facebook.com/ethanevansvp

𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗥𝘆𝗮𝗻:

• Newsletter: https://www.developing.dev/ • X/Twitter: https://x.com/ryanlpeterman • LinkedIn: https://www.linkedin.com/in/ryanlpeterman/ • Threads: https://www.threads.com/@ryanlpeterman • Instagram: https://www.instagram.com/ryanlpeterman • TikTok: https://www.tiktok.com/@ryanlpeterman

𝗥𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝗱 𝗶𝗻 𝘁𝗵𝗶𝘀 𝗲𝗽𝗶𝘀𝗼𝗱𝗲:

• Never Split the Difference: https://www.blackswanltd.com/never-split-the-difference • Leadership and Self-Deception: https://arbinger.com/bookstore/leadership-and-self-deception • The 48 Laws of Power: https://www.penguinrandomhouse.com/books/330912/the-48-laws-of-power-by-robert-greene/

[Source](https://www.youtube.com/watch?v=KhjhRRz3VJw)

中文简报

前亚马逊副总裁 Ethan Evans:步步深入剖析职场政治与生存法则 在前亚马逊副总裁 Ethan Evans 与 Ryan Peterman 的对话中,双方探讨了随着人工智能逐渐承接更多技术任务、技术岗位竞争加剧,职场政治与软技能为何变得前所未有地重要。Evans 指出,企业并非按照高校考卷那样客观公正地评估成果,被动等待赏识的“诚实殉道者”往往会被忽视。他阐述了在灰色地带确立成果归属、主导高价值项目范围的技巧,并建议职场人在面对同僚抢夺或低价值琐事分摊时,应主动出击、适当展示“带刺”的锋芒,或通过与主管直接置换利益来保护自身发展空间。 抢占工作功劳与曝光度:率先公开发布成果能占据主要认知份额,技术人员应学会充当补充关键背景的“解说员”,避免因坚守绝对被动与沉默而在长周期考评中沦为被遗忘者。 确立核心项目主导权并展现“带刺”锋芒:高绩效者在争取业务范围时会主动绑定执行意愿,让管理者意识到剥夺其权益会付出摩擦成本,避免陷入因好脾气而持续被边缘化的陷阱。 防御低价值杂活的转嫁:最有效的防御是通过主动推进高价值提案让自己保持忙碌;若不得不接手繁重琐事,应将其转化为功劳并直接与主管谈判,以换取下一个优质项目的优先权。

Reading summary

Former Amazon Vice President Ethan Evans argues that as technical execution becomes commoditized, organizational leverage, calculated visibility, and political assertiveness determine career trajectories in competitive corporate hierarchies. Cultivating Visibility and Navigating the Gray Area (4:40) Evans contends that individual contributors frequently face structural visibility deficits because engineering and product managers typically present technical updates to executive leadership. To counter this imbalance, Evans advises coaching managers directly to share credit or stepping in as the "color guy" with technical follow-up notes that deliver meaningful architecture insights without appearing overtly self-promotional. For introverted engineers who avoid verbal self-promotion, he recommends codifying work into reusable artifacts, tools, or written white papers, citing engineer Matt Round, who achieved broad company recognition by creating and naming Amazon's internal interview tool "MRT." Operating effectively requires becoming comfortable in the gray area of soft skills, which Evans distinguishes from outright dishonesty. Rather than over-qualifying accomplishments or restricting statements solely to indisputable, uncontested facts, professionals must frame their genuine work around what specific stakeholders value. Evans illustrates this through his portfolio of 70 to 75 patents and the launch of Prime Video, arguing that framing identical milestones through multiple truthful perspectives is a necessary skill for standing out. The 'Thorny' Principle and Defending Workload (24:18) According to Evans, agreeable employees are routinely passed over because managers triage limited administrative bandwidth by appeasing aggressive team members and taking from compliant contributors. Surviving this corporate triage requires being "thorny"—maintaining an edge of friction and establishing that being stripped of projects carries consequences. While likability offers substantial survival value during layoffs—exemplified by the "Bob with the Donuts" archetype, where broadly liked employees prove exceptionally difficult to dismiss—unmitigated pleasantness without pushback invites managerial exploitation. To deflect unwanted grunt work, Evans stresses playing offense by proactively proposing valuable initiatives so that leadership already perceives your bandwidth as completely saturated. If forced to negotiate over undesirable tasks, he recommends striking an explicit bargain: candidly acknowledging the low-appetite nature of the work and agreeing to complete it on the condition of securing a prime project next, or preemptively volunteering for a time-boxed maintenance sprint to convert an inevitable burden into visible team goodwill. Decoding Evasive Managers and Peer Competition (63:06) When dealing with managers who avoid explicit promotion discussions, Evans recommends analyzing the manager's historical promotion record or using large language models to decode their writing style and draft aligned asks. Drawing on negotiation principles from Chris Voss's Never Split the Difference, Evans advises using calibrated questions—such as "How can I do that?"—to draw evasive managers into the employee's reality and extract concrete criteria for advancement. In politically adversarial environments where peers actively undermine one another, Evans argues that speed is essential. Rather than reacting defensively, professionals should approach leadership proactively, establishing that they will not engage in mudslinging while requesting to be evaluated strictly on verifiable output through brief evidentiary reviews. When organizational relationships deteriorate completely, Evans notes that corporate hierarchies inherently favor the manager, who possesses dozens of operational levers to force an exit, making calculated lateral transfers far more practical than attempting to unseat a entrenched boss. Resource Competition and Career Acceleration Strategies (180:45) Evans describes resource competition and headcount allocation as an inevitable part of executive leadership. Reflecting on an annual review where Jeff Bezos rigorously dismantled his 25-person marketing request for the Amazon Appstore, Evans notes that leaders often rationalize empire building under the guise of ambitious backlogs. To protect staffing when initiatives failed, Evans routinely redeployed personnel to winning projects before leadership could execute clawbacks, while aggressively filling requisitions before company hiring pools closed. For professionals aspiring to speedrun a trajectory to Vice President today, Evans advises against attempting to climb internally within mature tech giants due to slowing organizational growth. Instead, he outlines an external roadmap: treat early big-tech roles as an intensive 18-to-24-month apprenticeship to master high-demand infrastructure like AWS, jump to high-growth scale-ups where that knowledge commands a premium, and embrace high-risk bets. Drawing on baseball's Moneyball philosophy, Evans asserts that executive advancement rewards swinging for high-visibility home runs over maintaining safe, low-impact reliability. Evans acknowledges that treating corporate dynamics as a zero-sum game can devolve into a destructive Prisoner's Dilemma that neutralizes individual advantages. While critics view organizational politics as toxic, Evans maintains that professionals must pragmatically master the human realities of scarcity, leverage, and perception as they exist today rather than waiting for structural ideals to emerge.

Original transcript

[0:00] I'll find another way to come around HR [0:03] and make your life miserable. This is [0:05] Ethan Evans, former Amazon VP, and I [0:07] brought him on for a third time to [0:09] [music] ask him questions about [0:10] corporate politics, but the questions [0:12] get increasingly darker. I see you want [0:15] to push me. You were there ever cases [0:17] where you had to burn someone to get [0:20] ahead? It is still a mind game and a [0:22] competition. I'm allowed to win. [0:25] >> You had so much success as a VP. Did you [0:28] do empire building? We had our annual [0:30] meeting with Bezos. Well, Jeff tore into [0:32] it. Is lying optimal in high stakes [0:36] situations? [0:38] >> This hole has no bottom. Let's go. [0:41] Here's the full episode. [0:46] I don't know what's going to happen in [0:48] the future, but with all the latest [0:50] advancements, it seems like these models [0:53] are able to do the technical work of [0:56] tech workers. And in that case, it feels [1:01] like the non-technical work may become [1:04] more important in the future. And at the [1:06] same time, this is a theory that a lot [1:08] of people have, which I hope isn't true, [1:09] but it's reasonable, which is if these [1:13] models can do the work of tech workers, [1:15] maybe there will be fewer roles in tech. [1:19] And in that case, I could also see [1:21] politics becoming more important because [1:23] there's the same number of people [1:26] competing for uh fewer roles. And so [1:29] what I want to do in conversation today [1:31] is ask you everything uh in terms of [1:34] soft skills, corporate politics to try [1:37] and help people in this these potential [1:40] future scenarios. And to start us off, I [1:44] put together a set of questions about [1:45] corporate politics which uh are dark and [1:50] get darker as they go on, but they're [1:52] also common scenarios that people [1:54] experience. And I'm hoping you can [1:56] answer transparently about how people [1:58] should handle these and your experiences [2:01] uh in these scenarios. [2:03] >> Yeah, absolutely. I don't know what you [2:05] have in mind, but I'm always game for [2:08] hard questions. I like questions that [2:10] push my thinking and if they're dark, [2:13] well, sometimes life is dark, so let's [2:15] go for it. [2:16] First question, you know, how do you [2:18] make sure that you get credit for your [2:20] work when there's a collaboration and [2:22] people are competing for visibility? [2:25] Yeah. So, I think recognition, [2:28] particularly in a collaborative sense, [2:30] is tricky. One of the good things is [2:33] it's easier to claim more recognition a [2:35] little later. At the moment, people are [2:37] very sensitive to it. Like I say, I [2:40] helped start Prime Video or I was the [2:42] first engineer on Prime Video. Well, now [2:45] that's like long ago. There are some [2:47] other people who would be like, "Well, I [2:49] was part of that team too on that day, [2:51] but they're not here right now." So, and [2:54] they probably even if they see this, [2:56] what are they going to do? They're going [2:57] to be like, "Hey, I was there, too." [2:59] Maybe there's a comment. If you scroll [3:00] down in this video years later, maybe [3:02] there's a comment says, "Hey, I was [3:04] there, too." It's not really a problem. [3:06] So, to get your credit, number one, [3:08] realize credit is easier to take a [3:10] little bit after. You want to get credit [3:12] in the moment, but there's also later [3:14] and it's easier. Second, that the way to [3:17] get credit is to be the first to speak [3:19] if you can. It doesn't mean you have to [3:22] say things that aren't true, but those [3:24] who speak first or those who speak up [3:26] first, if you say, "Hey, we shipped [3:29] this. I want to I want I'm excited to [3:32] share. We just released this feature." [3:35] whether you're sending that internally [3:36] or externally to a boss to a product [3:38] manager you can include the Wii and say [3:40] oh I did it with Ryan and Fred and Sarah [3:43] and Rajie [3:45] but if you're the one saying it you're [3:48] the one who gets the lion share of the [3:50] credit even if it looks like and you are [3:53] sharing that credit because the speaker [3:55] gets it. Now, if someone else speaks [3:57] first, what you need to do at that point [4:01] is figure out a way to add on about what [4:04] you did. [4:06] So, if you speak first and Ryan sends [4:08] out this message that says, "Well, we [4:09] did this project, whatever." I can at [4:11] least chime in and say, "Yeah, this was [4:14] a great project. I really had fun [4:17] solving blah blah blah or, you know, and [4:20] claiming your piece. I really had fun [4:22] coming up with the algorithm that [4:25] doubled our sales and you find a way at [4:28] least to say your part. What doesn't [4:32] work is be silent and hope your part [4:34] will be noticed. That's that's what [4:37] never works. Yeah. And I think a a very [4:40] common pattern of this and this is just [4:43] the way the teams are laid out is your [4:46] group of engineers and then there's a [4:48] product manager and the product manager [4:50] is often doing the upward reporting or [4:53] maybe it's an engineering manager that's [4:54] doing the upward reporting and so the [4:57] people who actually do the work may not [5:00] be as visible. [5:02] >> What would you say in that case? [5:04] >> Yeah. So one thing you can do is you can [5:06] talk to your manager, product manager [5:09] about remember to share the credit with [5:11] the team. Remember to highlight some [5:13] people. I'll give you an example. Um [5:17] when my team finally launched that first [5:20] v version of Prime Video, I was a senior [5:22] manager. I had a vice president and I [5:25] went to that vice president and I said, [5:27] "Today the day now you write the [5:29] congratulations message to everyone." So [5:32] I prompted him like he wasn't the sort [5:34] to give out a lot of praise. So I [5:36] prompted him like today's the day you [5:38] should write the message saying good job [5:40] team. And once I sent that to him he's [5:43] like I don't think he'd have done it but [5:45] like 10 minutes later out comes this [5:47] like great job team blah blah blah [5:49] message. So you can actually somewhat [5:51] direct people because a lot of people [5:55] intend to give credit but they're not [5:56] thinking about it. So like that product [5:58] manager, they're thinking about I need [6:00] to report the news. They're not thinking [6:03] it's important to note what Ryan did. So [6:07] just giving them that prompt of hey this [6:10] is a big accomplishment for the team. [6:12] It's a big moment for me. Can you make [6:14] sure when you report this up to like [6:17] mention what we did or mention us, not [6:19] just what happened? And usually they're [6:22] willing to do it. If they don't or they [6:24] won't uh and you've tried that, [6:28] find a way to share the news yourself. I [6:31] it may not be in the announcement to [6:33] leadership, but [6:35] share a like technical note and say [6:38] follow on to the product manager's note [6:40] and say, I don't know if all of you in [6:43] leadership are curious, but I thought [6:45] you might want to know some of the [6:47] technical underpinnings of how we did [6:49] this. And then you can talk about [6:50] whatever you want. No one is going to [6:52] come back to you and say like we don't [6:54] care about how any of it works because [6:55] that makes them look bad. So you're [6:59] you're finding a way to talk about [7:02] things in a way that's hard for people [7:04] to not like uh or to at least shut down. [7:08] And so let the product manager share the [7:10] fact it happened, but then you share the [7:13] color. Think of it uh if you watch any [7:16] sports of any type, they always have two [7:18] people in the booth. They have the [7:20] play-by-play announcer who's like, "So [7:22] and so hit the ball or kicked the ball [7:24] or caught the ball." But then they have [7:26] the color guy and the color guy is there [7:30] saying like, "Yeah, and he's the great [7:33] receiver out of this university in his [7:35] fourth year and like that's a really [7:38] tough play. When I was a player, it was [7:41] really tough to run that pattern or [7:43] whatever." You can be your own color [7:45] guy. If the PM is the announcer, [7:50] you give the color. And those are two [7:52] jobs and everyone welcomes the color [7:54] guy. Do that. [7:58] There's often these forums for [8:00] leadership reviews where you put [8:01] yourself down and you say, "I'm trying [8:03] to get uh steering on this or I'm trying [8:06] to get some headcount or something." And [8:08] I noticed that actually the real outcome [8:12] they wanted was to put the project in [8:15] front of leadership. So when that [8:16] person's promo is coming along, then [8:18] it's visible and that person's aware of [8:21] their work. And so if everyone takes [8:24] this advice, everyone's competing to to [8:28] speak but not have impact. you know, it [8:31] feels like that's uh not healthy for an [8:33] org if everyone's clamoring for [8:35] visibility with no value. What would you [8:38] say to that? [8:40] So, first I'd say you're right. If [8:42] everyone's clamoring for visibility with [8:44] no value, you've got a very political [8:46] organization. Uh but here's some truths [8:49] that will set you free. Number one, most [8:51] people uh never say anything. If uh like [8:56] most people take no action, including by [8:58] the way, half the people I'm speaking to [9:00] right now who are watching me, they're [9:02] like, I'm going to do something [9:04] different. And the fact is tomorrow [9:05] they're going to do nothing different. [9:07] So, I'm challenging you like be in the [9:08] half that does something. Um second, uh [9:13] you can choose to add value. I was [9:15] describing how to share news or share [9:17] detail. But when I said like share some [9:20] of the technical detail, you can do that [9:22] with a purpose. You can be like what [9:24] should I tell leadership about what [9:26] happened or about how this built this is [9:28] built so that they know I can tell them [9:32] it either is built for scaling and it's [9:35] ready to go and you can trust it or I [9:37] can tell them you know it's important [9:39] for you to know this is launch ready but [9:42] if we have a lot of success we're going [9:44] to need to invest in scaling you can [9:46] make it somewhat useful [9:49] I understand the worry and there are [9:52] some orgs where like too many people are [9:54] talking just to get visibility. [9:58] You don't want that. But I would say if [10:01] you have to have a problem, first be one [10:04] of the people who's talking, then figure [10:07] out how to add value. Because so many [10:10] people listening to this are like, I'm I [10:12] don't care what Ethan says. I don't I [10:14] can't stand the idea of I'm talking for [10:16] no reason, so I'm not going to do that. [10:19] And that's the person who's sitting in [10:21] their cube contemplating either quiet [10:23] quitting or rage quitting because they [10:25] can't get ahead because they've decided [10:27] to opt out of the system. And I get it. [10:31] I get what you're feeling. But you're [10:33] you you're telling yourself you're this [10:36] bold martyr for honesty and all you are [10:38] is a martyr. And so, you know, don't do [10:42] that. In instead, take it as a challenge [10:44] and say, "Okay, I'm going to talk, but [10:47] what I say is going to be worth hearing. [10:49] I'm just going to raise the bar on [10:51] myself as opposed to I'm going to get [10:53] mad at all these other people I see just [10:56] flapping their faces and I'm not going [10:59] to say anything because to talk puts me [11:02] in the same bucket as them." Don't do [11:04] that. Don't get in a bucket with them. [11:06] Make yourself a new bucket that's [11:08] better. And if you're as good as you [11:10] think, if you're sitting there about how [11:11] hot you are, then you got to be [11:13] able to find something useful to say. [11:15] And if you can't construct something [11:17] worth hearing, then go back and revisit [11:21] that. But I'm so hot Right? That's [11:24] the challenge I have to you. [11:25] >> Is the best thing to do generally be as [11:30] loud and outspoken as you can. [11:33] >> First, I don't think there's ever like a [11:35] perfect best thing. And second, I would [11:37] answer that no because the way you [11:39] phrased it, you're going to be seen as a [11:41] blowhard, right? You're going to be seen [11:43] as claiming falsely. If you rephrase [11:46] what you said slightly to make sure you [11:48] claim everything you legitimately can [11:50] and stretch legitimate a little bit [11:53] against the limits, then yes. Example, I [11:58] always say I was the first engineer on [12:00] Prime Video. Now, the truth is, and I've [12:03] had one guy come back and challenge me [12:06] on this, when I worked on that product, [12:09] it was Amazon's first video product, but [12:11] we hadn't named it Prime yet. So, when I [12:15] worked on it, it was never called Prime. [12:17] It became that. So, I could explain I [12:20] was the first engineer to work on what [12:21] became Prime Video. That's just a lot of [12:24] extra confusing words. [12:27] So, I'm ballooning up my claim. It's not [12:29] false, but it is how you look at it. And [12:32] I'm simplifying my messaging and I'm the [12:35] first person who worked on that. The guy [12:37] who's the first guy who worked on it [12:39] when it was called Prime, he thinks I'm [12:41] claiming too much. Well, fine. You push [12:44] those boundaries a little bit because [12:46] people's brains can't hold that much. [12:48] You've got to make your message simple. [12:50] So, claim as much as you reasonably can. [12:54] Don't get caught out. Like, luckily that [12:56] guy isn't like, "You never worked on [12:57] Prime Video." He knows what I did. He [13:00] just doesn't like how I label it. I can [13:02] live with that. If he was like, "Hey, [13:03] that's You were never on the [13:04] team." Like, you know, "Show me the [13:07] proof you're ever on the team or you [13:08] ever did anything." Then I'd be in [13:09] trouble. So, [13:12] you want to push those limits, but not [13:15] to being false, more to just being [13:17] really simple because it's a lot easier [13:19] to believe like remember Ethan started [13:22] Prime Video than this more complex story [13:24] and it's close enough to write. Now, [13:27] some people are like, "Well, that's not [13:28] really close enough to write. You're [13:29] embellishing." Well, [13:32] I don't know what to tell you. It's [13:33] simpler and simple works. Simple [13:36] messages work. It's like, you know, it's [13:39] all marketing messages are very short. [13:42] >> And I I hear what you're saying, but it [13:44] seems like there's a gray area there. [13:46] How do you find the right place in the [13:49] gray area? [13:50] >> Yeah. Well, okay. So, you want to talk [13:52] about soft skills today. One thing [13:54] you're going to have to accept on all [13:55] soft skills is they're gray, right? Like [13:59] there, you've asked me a couple times [14:00] stated like the best is this, the best [14:02] at that. That's a good challenge for me. [14:04] But best is almost always context [14:07] dependent. Who are you talking to? What [14:10] do they care about? So you have to move [14:13] in that gray area. And what I would say [14:16] is get comfortable in the gray as [14:19] opposed to we as engineers were trained [14:23] in binary. It's zero or it's one. We [14:25] love black and white. Soft skills and [14:28] these kinds of things are gray. Never [14:31] verge into the black where you're lying. [14:34] But also don't feel like you have to [14:36] limit yourself to the pure white of [14:40] facts not a single person would argue [14:42] with because on a team project who had [14:45] the contribution and who had the idea. [14:48] Let's take another example. I hold many [14:50] patents. A lot of those patents have [14:53] other inventors on them. Sometimes I [14:57] feel that I'm the inventor and some [15:00] other people's names got added because [15:02] of social circumstances and sometimes to [15:05] be honest someone else was the inventor [15:07] and my name kind of got added. [15:10] Those situations I just say I have 70 [15:13] patents. I could try and divide it into [15:15] like I have 70 patents 25 of which I [15:17] feel like I was the inventor or I could [15:20] just say 75 patents. So, answering your [15:24] question about gray areas, [15:27] my advice is [15:29] read the room. And what does read the [15:32] room mean? It means understand your [15:33] audience and figure out how to explain [15:36] what you did in a way that the audience [15:38] is like, "Okay, you did that and it was [15:40] good." You have to adjust. I can tell [15:43] most of my [15:45] resume accomplishment stories many [15:48] different ways, right? I say I was the [15:51] first person working on Prime Video. I [15:53] can also say I was the first person [15:54] working on Amazon video. I can also say [15:56] I was the first manager and I hired a [15:58] team and they built it. It's all they're [16:01] all true. And that's the gray area is [16:03] every one of those is true, but they're [16:05] a different way of looking at it. Push [16:08] me. I see you want to push me [laughter] [16:11] >> because I'm thinking so there's a [16:13] spectrum here of complete no one will [16:17] will push back on it 100% truth and then [16:20] there's outright lie [16:24] if you had to say where on the spectrum [16:27] you should place yourself on average for [16:30] for the fastest career growth where [16:33] would you [16:33] >> More is better more is better until you [16:36] be until it starts to damage your [16:38] reputation. You can't back it up. More. [16:42] Why I say more is better? Because most [16:44] people say too little and claim too [16:46] little and they have this faith which is [16:49] misplaced. The key is what I'm fighting [16:51] against is not on the table in your [16:53] equation. What I'm fighting against is [16:56] all the people who are hoping to be [16:58] noticed. They're waiting for someone to [17:03] go look at the check-ins and count [17:05] checkins or go look at all the code and [17:09] decide who had the real and that's never [17:11] going to happen. They're looking for [17:13] this deep evaluation that will create [17:15] this cosmic fairness. [17:17] That's [17:19] natural because we we came through [17:22] university where you took a test and it [17:24] got graded and every question got a [17:26] score. And we're trained to think that's [17:28] going to happen in life and it's not. So [17:30] what I'm pushing back is imagine you [17:32] took an exam and you were back in [17:34] college. But the score that was going to [17:36] be written down was what you could [17:37] convince the professor your effort was [17:40] worth because that's how your work is [17:42] actually scored at a job. You fill out [17:46] the same exam. Theoretically, it could [17:48] be graded and give you a point score, [17:51] but it's really going to be [17:53] six months later, the manager, the [17:56] professor is going to sit down in a room [17:58] with all these exams and think, "What do [18:00] I think about Ryan? I feel like he [18:02] probably got about a 75 on this exam." [18:05] They're not going to reread it or grade [18:06] the questions. They're gonna be like, "I [18:08] know Ryan. He's about a 75." You want to [18:10] have told a story where it's like, "I [18:12] know Ryan. He's definitely a 97." I get [18:16] why some people's skin is literally [18:18] crawling right now. They're like, "It's [18:20] so wrong. This guy, I hate him because [18:23] he's telling me these things that just [18:25] shouldn't be." [18:27] And I'm with you. But I'm telling you [18:30] the real world. And it's how well you [18:33] manage that relationship and describe [18:36] your work and surface it. They're like, [18:38] "Man, Ryan is my 97." [18:41] And [18:42] that does mean, by the way, the dark [18:44] side is that means someone else who was [18:47] a 75 is like, "Oh yeah, Alfred, I don't [18:52] remember much about him." That's an F. [18:53] Alfred's the guy who's sitting and [18:55] hoping for the fair grading. And now [18:58] he's in his cube contemplating rage [19:00] quitting because he got an F. This is [19:03] the world. The world is a social world [19:05] with short memory. And you've got to [19:09] claim what you really did. And why I [19:12] tell people to claim more is so many [19:14] people are Alfred sitting quietly [19:16] expecting a fair grade. [19:18] >> These behaviors come more naturally to [19:20] some people who are louder. Um but what [19:23] about some people who are, you know, [19:25] more quiet by nature? Do you have any [19:27] ideas on how they can get this [19:29] visibility? [19:30] >> Yeah, absolutely. There's a few ways. [19:33] Um, look, the world favors extroverts. [19:36] It's done that for at least a hundred [19:38] years. There's some evidence it was [19:40] different in the past. But getting your [19:42] point, um, what someone who's quieter [19:45] should do is number one, can you write [19:47] about it? If you're not the sort of [19:49] person who wants to talk about it or [19:51] speak in a meeting, can you write about [19:53] what you're doing somewhere? Can you [19:55] email it? Can you put it in Slack? Can [19:56] you [19:58] publicize it somehow? [20:00] Second, if you can't do that, can you [20:02] get someone else to publicize it? So, [20:05] can you put it somewhere where it's [20:07] going to get reviews? Can you let your [20:10] work speak, but not in a vacuum? Can you [20:12] share it out if you only want to like if [20:15] you only want to talk to other [20:16] engineers? Can you turn something you [20:18] did into a sharable component? Can you [20:21] turn it into a a talk for whatever, a [20:24] white paper, a brown bag? What are the [20:27] ways you can let your work truly speak [20:32] for itself but not in isolation? The way [20:34] to succeed totally quietly is build [20:38] something everyone else uses. If that [20:41] happens, they will eventually they will [20:43] truly come looking for you like who [20:45] built this? A story here that's fun is [20:49] there's a longgone Amazon engineer. His [20:52] name was Matt Round. I never met him, [20:55] but he built something called the Matt [20:58] Round Tool or MRT, which was our [21:02] interview tracking system for over a [21:04] decade. Everyone used MRT. Well, it was [21:08] the Matt Round tool. So, I never met [21:10] this guy, but I can tell you a little [21:11] bit about him because his tool became [21:14] used by everybody and it was named after [21:17] him. That's a way to be famous without [21:21] ever saying a word or I guess you had to [21:23] say three letters, right? You had to [21:24] call it MRT. [21:26] So that's the silent engineers publicity [21:30] method. [21:32] >> One situation that I've I've heard [21:34] people talk about or my friends have [21:36] I've encountered this is um competitions [21:39] over scope. So, let's say you find a [21:44] incredible opportunity and you know it's [21:48] going to be impactful. It's going to be [21:49] great for your career. This is before [21:51] you tell anyone about it. How do you [21:54] make sure that you get that scope? [21:57] >> There's a few things. Uh number one, for [22:00] me to give you a project as a manager, I [22:02] have to believe a couple of things about [22:04] you. First, I have to believe your [22:06] work's good enough. Like if you have a [22:07] good idea, I have to believe, okay, [22:10] you've had a good idea, but are you the [22:13] one who can carry it out? And you don't [22:15] have to be the best person, but I at [22:16] least have to believe you're not the [22:17] worst person or someone who's a risk. [22:19] So, it's a trust in your ability. You [22:22] have to establish that. The second thing [22:24] is I have to believe you can make the [22:27] free time or you have the time or I can [22:30] free your time. I'm going to be able to [22:32] let you do it. And that means if you [22:34] have other work, being able to hand it [22:36] off, having it well documented, [22:39] automating it, whatever it is you need [22:41] to do in order to get that work to a [22:45] point where you have the time to do this [22:48] project. So, what you want to do is [22:50] think through how am I going to make the [22:52] case to my manager that this is or to [22:54] whoever that this is a valuable addition [22:57] and that I'm the right person both [23:00] ability and time to take it on. The key [23:04] is you do start with an advantage. If it [23:07] was your idea, then you're the one who [23:08] understands it best. You're the one [23:10] who's thought about it most. So, you [23:13] should be in a leading position [23:16] for that role as long as you don't screw [23:19] it up, as long as you don't have a bad [23:22] track record or have a bad relationship [23:24] or have something else going on that's [23:26] super critical. The other thing is be [23:29] clear to ask for it. Say, "I have this [23:31] great new idea." You don't have to say, [23:33] "And I want to make sure you put me on [23:35] it." You phrase it as, "I have this I [23:37] have this really valuable idea. I think [23:39] it's going to change our business or [23:40] change our team. [23:42] and I am excited to bring it, you know, [23:45] to to build it. I'm excited to make it [23:48] happen. Uh that messaging sets in [23:52] people's minds that you're the person [23:54] and that they have to choose to [23:56] disappoint you if they're going to give [23:57] it to somebody else, which most people [24:00] will shy away. If you don't say [24:02] anything, it's like, "Oh, it's a good [24:03] idea. I'll give it to Fred." But if [24:06] you've said and I want to do it, um, [24:10] then they have to decide, oh, well, if I [24:12] give it to Fred, I'm gonna have to tell [24:13] Ryan that and get him just to think [24:16] like, is that worth it? This is another [24:18] rule I tell people. You do need to be a [24:21] little thorny. Um, [24:24] one of the traits I think great leaders [24:26] have, and this includes great engineers, [24:28] is disappointing them comes with pain. [24:31] Not that they're jerks, but they're not [24:33] just going to be, "Oh, that's fine. Oh, [24:36] yeah. No, don't worry about it." You got [24:38] to be like, "What? What did you do?" No, [24:43] my idea. If this is how it's going to [24:45] be, I just won't bring any more ideas. [24:47] Like, what the hell? And then, you know, [24:49] you got to put that little push back in [24:51] there of like this is not okay. And uh [24:56] again, if you're good, the threat is I [24:58] will take my good ideas somewhere else. [25:01] And this is important [25:04] again. Remember poor Alfred? He's [25:06] sitting there with his F and he's mad. [25:08] He has a good idea. If I can take away [25:10] his idea and he's just going to sit [25:12] there in his cube and be mad again. Like [25:14] Alfred gets abused. Why? He gets abused [25:18] because it's free to me as a manager. I [25:21] have to make a trade-off between Ryan [25:23] who's pushing me for stuff and Alfred [25:26] who's always like just willing to suck [25:28] it up. Well, maybe I actually think [25:30] you're a little bit too pushy and I'd [25:32] like to help Alfred out, but I do have [25:34] an ugly triage to do, which is, well, if [25:38] I don't cater to Ryan, he's out of here. [25:42] Whereas, if I don't cater to Alfred, [25:44] that guy is solid as a rock. He'll be [25:46] here two years from now. I'll give him [25:48] like some free lunch coupons and movie [25:51] passes and he'll be so grateful. Don't [25:54] be Alfred. You've got to be [25:58] a little thorny. And again, those same [26:00] people are like, "Why do I have to do [26:01] that? Why should I Why?" They love the [26:03] word should. Why should I have to do [26:06] that? Well, okay. In cosmic justice land [26:09] where the god of your choice is making [26:11] everything just. You shouldn't. But we [26:14] don't live in that land. We live in [26:16] reality land where managers have a [26:18] choice. They have some pushy people that [26:20] are still good and they want to keep on [26:22] their team. and they have some pretty [26:24] like easygoing people that are kind of [26:28] gonna go with the flow. The fact is the [26:31] right decision for me as a manager, not [26:33] the just decision, but the practical one [26:37] is take a little from the people who are [26:39] going to be all right about it and give [26:42] it to the ones that aren't because [26:45] that's how I keep my whole team. And [26:47] yes, for all of you who don't like it, I [26:49] have just said a little bit screw the [26:52] nice people for the bad people, [26:54] but I have a job to do. And so, of [26:58] course, I also never tell myself how I [27:00] just said it to you. Like, as a manager, [27:02] I never say like, "Oh, I'm going to [27:03] screw all my nice people to help these [27:05] two jerks." But subconsciously, I'm [27:08] making this tradeoff. And what I'm [27:10] telling myself is, I will get back to [27:11] them and take care of them. The problem [27:14] is you're back around asking me for more [27:16] stuff and I never quite get back to them [27:18] and I meant to and I had a good heart [27:20] about it and it just didn't happen [27:24] and nonetheless you got everything you [27:26] wanted and they lived with what was left [27:28] over. And if you're in this leftover [27:30] bucket, it's not that I meant bad things [27:32] for you. It's I had, you know, there was [27:35] this person always talking to me and I [27:37] needed to get them out of my office. So, [27:39] I gave them what they wanted cuz I'm [27:41] human. When I was a manager, I used to [27:44] think about, you know, what's the [27:46] optimal team composition in terms of [27:49] like the personalities of the people? [27:50] And I'm curious to hear your thoughts. [27:53] Would you rather have a team that's full [27:56] of these super ambitious, pushy, you [27:59] know, superstars or would you rather [28:02] have pure role players? [28:04] >> Yeah. So, I'd love to tell you I'd like [28:07] all like pushy superstars, but you can't [28:09] keep that many people happy unless [28:12] unless your business circumstance is [28:14] just dropping [28:17] choice projects in your lap. That can [28:20] happen in a high growth scenario where [28:22] like everyone is against their growth [28:24] limits. [28:25] But absent that and particularly now [28:27] when there's a lot more like flat [28:28] headcount scenarios, those people just [28:31] eat each other. They turn cannibal and [28:33] they turn [28:35] cannibal towards you and each other and [28:36] it's very ugly. So a few of them though [28:39] the reason you don't want all role [28:42] players or all people who are very [28:44] easygoing [28:46] is you need those spark of change of [28:50] ambition of you need people who are [28:54] agitating for changes and ideas [28:58] I think because in this world of uh [29:03] very easygoing people the team may be [29:07] calm, but [29:10] no one is pushing. And so it's peaceful, [29:15] but it's not high impact. There's a [29:17] quote I love or a saying I love, which [29:19] is um reasonable people conform to their [29:23] environment. Therefore, all progress is [29:26] due to unreasonable people. People are [29:28] like, "But why? But why? Why does it [29:30] have to be that way? Why does it take [29:32] three clicks? Why why can't why won't [29:34] the customer pay a million dollars? Why [29:37] can't we all have hovercraft? Like those [29:40] are the people who push things. [29:43] You need some of them. Too many though [29:46] and uh you just have chaos because [29:50] everybody's pushing different [29:51] directions. In the situation where you [29:53] have a project and you haven't unveiled [29:56] it yet and you really want to work on [29:57] it, I actually think a lot of engineers, [30:01] they don't worry about the manager [30:02] giving it away. They worry about other [30:05] engineers getting excited about their, [30:07] you know, thing that they're excited [30:09] about. So in that case, how would you [30:13] defend against other engineers coming in [30:15] saying, "Oh, I want a piece of that. Oh, [30:17] that looks fun. Oh, that looks [30:19] impactful." Well, number one, that might [30:21] be a good thing. Like the first question [30:23] I would ask myself is if my fellow [30:25] engineers are excited about what I'm [30:27] doing, how do I make like great, how do [30:30] I make it big enough or tricky enough or [30:32] hand pieces out so I'm kind of the [30:34] kingmaker, right? So I'm like I'm like [30:36] the person holding the cookie jar [30:38] handing out cookies. That's a great role [30:40] to be in or could be. Now if you're [30:43] really worried about defending, one [30:45] thing, of course, is don't tell them [30:46] until it's too late, right? Work on it. [30:48] Keep it to yourself. uh or until it's [30:50] assigned to you. The other uh thing is [30:54] if you had one good idea, you're [30:56] probably smart enough to come up with [30:58] multiple good ideas. So, can you like go [31:00] to your manager and be like, I have this [31:02] great idea. I'm going to work on this [31:04] thing, but by the way, there's these two [31:06] other ideas, and I think people on the [31:08] team would be excited about it. Whether [31:10] they are or not, you've you've given [31:12] some like um I don't know uh other bait [31:16] trail, right? And it doesn't mean that's [31:19] illegitimate, just you've given people [31:22] other interesting things to work on. But [31:25] from a pure defensiveness, I guess if [31:27] you're thinking about how do I keep my [31:29] good work to myself, I would say outrun [31:32] the competition. [31:34] uh be a little ahead of them, be further [31:37] down the prototype avenue or further [31:40] down talking about it or [31:43] uh to where [31:45] they're not um [31:48] up to speed. They can't keep up. The [31:51] other thing that's a little bit darker, [31:52] you like dark, you probably have work to [31:55] get off your plate. Think about what you [31:57] have on your plate. You could get stuck [31:59] on their plate so they have something to [32:00] do like I want to get rid of this. You [32:02] talk to your boss and you're like, "I [32:04] have this great new idea. It's going to [32:05] make us a bunch of money or get us a [32:06] bunch of customers, but I have to get [32:08] rid of Product Fu, but you know what? [32:10] Both Ethan and Sarah would be great to [32:13] take over Project Fu. They're up to [32:16] speed on it." Um, now they may hate you. [32:20] You got to be careful. You'll make [32:21] enemies. You got to figure out a way to [32:23] like um say, "We'd have to figure out [32:27] how to manage product project fu. [32:30] There's a couple other people working on [32:31] it. Maybe we can move it around and then [32:33] get the boss to say, "Oh yeah, Fred and [32:35] Sarah, I got it." Or Ethan and Sarah. [32:36] Right. That's [32:38] um that, you know, I like to do things [32:42] above board. I think one of the things I [32:45] want to challenge about some of your [32:46] mentality in these questions, there's [32:49] scarcity mentality. There's only so much [32:51] good work. It is true. There's only so [32:53] much promotion, so much visibility. But [32:56] when it comes to good work, there's a [32:58] lot of it. Even with promotions and [33:00] visibility, if a company wants to bad [33:03] enough, they can promote whoever they [33:05] want. So, I try first to solve these not [33:09] as a zero someum game or a prisoner's [33:11] dilemma. I try to figure out how can I [33:13] actually make them winwin. It isn't [33:16] always possible, but at least start [33:18] there of how can I find a way to make [33:20] this project bigger? How can I find a [33:23] way to if somebody else wants in on it, [33:26] say to them, great. how can we make it [33:28] better and do it in half the time, [33:30] right? Or, you know, I even give them a [33:33] hard time. I'll say something like, [33:35] "Well, okay, but you know, this is a [33:37] cool project and it's better than what [33:38] you're working on. So, like, show me [33:40] your serious. What are you going to [33:41] build this weekend to move it forward?" [33:43] And they're like, "Oh, this weekend I [33:45] have plans." Well, then sorry. Like, [33:48] this is a weekend's project, right? I [33:51] mean, you know, you can do you you can [33:53] say it with a smile like, "I thought you [33:55] were committed. You can get away with a [33:57] lot if you can play it off as hey like [34:01] step up. Come on, I'm doing it, you [34:04] know, and there there's just a game to [34:06] that because humans humans push each [34:09] other, right? Like how do all those [34:11] stories that end with like watch this, [34:12] hold my beer, and then some guy doing [34:14] something crazy. It's usually he got [34:17] pushed into it. Like, oh, you should [34:18] jump off the bridge. Maybe you should [34:20] jump off the bridge. Well, I if I did [34:21] it, I'd do a backflip. Oh, you and they [34:24] it's this that's how humans are. Another [34:28] tough message about soft skills. Human [34:31] skills are about dealing with humans [34:34] weird broken minds that [34:38] are not rational. They are emotional and [34:42] that can be good. Emotions give us [34:44] energy. They give us excitement. [34:46] But you have to understand human [34:48] psychology. And I would say to anyone [34:50] listening, you're either uh many of you [34:54] like a lot of engineers understand poker [34:56] and that story about if you can't tell [34:58] who the mark is at the poker table, it's [35:00] you. Well, in the game of understanding [35:03] each other's minds and understanding [35:06] each other's motivations and soft [35:08] skills, if you're not in charge, then [35:11] you're the mark, right? Because that [35:13] game is happening in every meeting [35:15] consciously and unconsciously. And if [35:18] you're not thinking about people's [35:20] motivations and their satisfaction and [35:23] their fears, not to manipulate them, but [35:26] just to understand and be able to play [35:27] your cards, right? You're not in the [35:30] game. [35:31] And remember, poker isn't a game where [35:33] you manipulate each other. I can't make [35:36] you play cards a certain way, but it is [35:40] still a mind game and a competition. I'm [35:42] allowed to win. And so that's where I [35:44] feel like you can be ethical and be a [35:45] card shark and be really good at playing [35:48] your hand. I'm not putting you down by [35:51] beating you. I'm just beating you. You [35:53] had a fair chance. You held your cards. [35:55] I was better and I won and I get the [35:58] money. That's what I'm telling people to [36:00] do. Like the other way to do it is like, [36:02] "Oh, I have someone standing over your [36:03] shoulder or a planted camera." That's [36:05] cheating. That's manipulation. [36:08] Just be really good at understanding [36:11] people's minds. [36:13] when you want to take on that project, [36:15] maybe you offboard some of the stuff [36:16] that you don't want to do to other [36:18] people. And I think a lot of people have [36:20] experienced receiving that. So, [36:22] someone's trying to give them scope that [36:24] they don't want. What's the typical ways [36:27] to, you know, protect against that and [36:30] say, "Oh, I don't want to take on this [36:31] work. Thank you." Though, [36:33] >> if you're in the situation where it's [36:35] been pointed to you and you have to [36:36] refuse it, you're already you've already [36:38] lost round one. like there may be [36:39] recovery but the the way to avoid that [36:42] is to be the one proposing something uh [36:45] to the to the team the boss the company [36:48] whatever be playing offense once you're [36:51] playing defense you're already losing so [36:52] I will answer how to defend but the [36:55] first defense right the the you know in [36:58] this case the best defense a good [37:00] offense is be the one putting forward [37:04] ideas and talking about what could [37:06] happen so that everyone's Like Ryan's [37:09] full of ideas and he's doing all this [37:10] stuff. We couldn't possibly give him [37:12] anything. And then if I come to you, [37:14] you're like, "Man, I'd love to, but I'm [37:18] on projects A, B, and C or I have these [37:20] new initiatives to do this stuff and I [37:23] can't possibly do that." Now, if you [37:26] screwed up and you looked idle and you [37:28] didn't have some ideas cooking and [37:31] somebody's trying to shove stuff on you, [37:34] um there are a couple defenses. Uh, [37:38] number one is, hey, if this is so e, you [37:40] know, I can't take this on. It's too [37:42] big. It's too much. They're like, oh, [37:44] it's easier. It's just this. It's that [37:46] great, you automate it. Go ahead. Uh, so [37:49] push back like, why aren't you solving [37:52] your own problem? Remember I said be a [37:54] little thorny. The next defense is [37:57] you're not the only person on the team. [38:00] So I guarantee you there's somebody on [38:04] the team who's not going to resist. [38:07] And so just be thorny enough that they [38:09] go to that other person instead of you. [38:12] Be the person when they come like I'm [38:13] not taking on your work. Who do you [38:16] think you are? And then they'll go to [38:18] the person who's like, "Oh yeah, I can [38:20] help with that." That person is out [38:22] there. So it's the way you defend [38:24] yourself is to be not worth it, right? [38:27] It's like a hedgehog defense or [38:28] porcupine. Like, yes, can the can the [38:32] tiger or the dog eat the porcupine? They [38:34] can, but it's not worth it. I'll go find [38:36] a nice mushy squirrel. And so, when they [38:40] come to you, you get those porcupine [38:42] thorns out. And they're like, "Ouch, [38:44] I'll go find the squirrel." And then, [38:46] you know, there's bunny guts all over [38:48] the lawn somewhere else. And that's your [38:50] peer, but it's not you. to say no, to [38:54] give porcupine, you know, quills to your [38:58] manager. [38:59] They control if you get fired or not. [39:02] They control your performance and all [39:03] that. So, if you're constantly saying [39:05] no. Yeah. If you're constantly saying [39:08] no, then you're just not helpful. [39:10] Goodbye. But that's my point about play [39:15] offense, right? is you've got to be [39:17] doing something that brings enough value [39:19] so the manager isn't always bringing you [39:21] things. The other thing I would say is [39:25] if that doesn't work, try making a deal. [39:28] Just look the manager in the eye and [39:29] say, "Look, we both know this is not [39:31] very appetizing work. Can we just agree [39:33] that's true?" The manager will either be [39:35] like, "Yeah, but it needs to be done." [39:38] Or they'll be like, "No, it's great." [39:40] And you can just roll your eyes in a way [39:42] that's like, "Come on." So then you just [39:44] move on either way and you're like, I'm [39:46] going to do this, but I want to do this [39:48] other thing. So I'm going to crank [39:50] through this, but the deal is I get this [39:53] next thing. And again, most managers, [39:59] they don't want to fight. They got other [40:01] things to do. They need their team [40:02] pulling with them and they know they're [40:04] asking you to do some unappetizing work [40:08] and so they will make a deal. So there [40:12] is a role to be a team player and to [40:14] take on some of the stuff that needs to [40:16] be done. There's also a way actually to [40:20] get credit. [40:22] Let's say your peer wants to hand stuff [40:23] off or your manager wants to hand stuff [40:25] off. Go to them and say, "Hey, you know, [40:28] it's been I've I've really enjoyed [40:31] getting to work on X, Y, and Z. You've [40:33] given me some good projects. I know our [40:36] team has some maintenance work and I [40:39] know you're always hunting for people to [40:41] do it. I'm gonna spend the next two [40:43] weeks doing whatever maintenance you [40:45] want because I want you to know I'm on [40:47] your side and give me anything you want. [40:51] I'm going to crank through it and then I [40:52] want to do this or then I want to do [40:54] that. But you you just if you're going [40:56] to have to take the hit anyway, turn it [40:58] into a virtue. If you think the hit is [41:01] coming or you've seen a pattern, go [41:03] volunteer for it and bargain up front [41:06] like, "Hey, I know we're buried in [41:08] backlog or buried in bugs. I want to get [41:10] us through that. I'm going to do my own [41:11] bug bash this weekend, tomorrow night, [41:14] next week, fill in whatever my next on [41:16] call. Tell me what is most important to [41:19] you because I want to get to where then [41:21] I'm free to we're both free for me to [41:24] work on this thing that you need, this [41:26] better thing." And so it's about all of [41:30] these are strategies though to play [41:31] offense. [41:33] What doesn't work is to sit in your cube [41:36] or sit in your home office or wherever [41:38] it is you're sitting and hope you like [41:40] this is the one case where hope you [41:42] don't get noticed doesn't work. Normally [41:43] it's normally you won't get noticed if [41:46] you do nothing. But when I'm handing out [41:47] work, I go look around my team like [41:49] who haven't I seen in a while. Oh, it's [41:51] Alfred the grumpy guy. Here we go. He's [41:53] already grumpy. Why not give him this? [41:57] Well, why is he grumpy? Because he got [41:58] an F on the test. Because his work [41:59] didn't get noticed. I actually made him [42:01] grumpy. But I don't know that. I just [42:02] know he's kind of grumpy, but he still [42:04] goes along with stuff. So, I'll give it [42:06] to him. As a manager, I go looking for [42:08] who can I give this to. Human skills are [42:11] an art. They're not a pure science. [42:12] There's an art to being the thorny [42:14] person without being seen as a jerk. You [42:18] can be the porcupine without being a [42:21] jerk. It's like, "Hey, man. I didn't [42:24] stab you. These are just my quills. [42:26] Like, so how do you do that? What does [42:28] that mean? It means [42:31] the little signs that you're not quite [42:34] happy [42:36] without actually opposing stuff. Let's [42:38] say the boss brings you some extra crap [42:40] work. You can be like, [42:44] "All right, this is I will get this [42:46] done, but we got to do better." Like, [42:48] I'm looking for better next time. And [42:50] just that little challenge, you're just [42:53] setting that little hook of I'm looking [42:55] for a better challenge tomorrow or soon [42:58] as this is done, I want something [43:00] juicier. And you're just setting that [43:01] little hook because if they come back [43:03] and like here's another thing you need [43:04] to do. And I'm like, I told you juicy, [43:07] we both know this isn't that. I'm going [43:09] to give you one more pass. [43:12] Most managers can't take that because [43:15] most humans can't. Even though they [43:17] never agreed, they can't take going up [43:20] against that expectation over and over [43:21] of like, I'm gonna take him something [43:23] else and he's going to give me [43:25] again. It just it's not worth it because [43:29] there again, there's somebody else who's [43:30] going to turn into bunny guts when I eat [43:32] him. And [43:35] I also know there's people listening who [43:37] are like, "This is so unfair and I'm so [43:40] sick of being bunny guts spread on the [43:41] lawn when the wolf got me." [43:44] Yeah. Change. become the porcupine, then [43:47] become the bear, [43:50] and it's okay. It's It's like a learning [43:52] process. Everybody was bunny guts at [43:54] some point in their career because they [43:56] didn't know better. [43:57] >> I want to [laughter] He's losing it. [44:01] He's got this vision of a slaughtered [44:03] field of rabbits. [44:05] >> Oh my god. Okay, [laughter] [44:06] >> we're going to come back. I'll get a new [44:07] analogy. I'll save you for my analogy. [44:10] Okay, the next situation um a little bit [44:13] darker as as I mentioned but also [44:16] realistic is imagine you know you you [44:19] want to get promoted but there's only [44:22] one available slot. Maybe there's a [44:24] promo quota or maybe it's one of those [44:27] roles where you know there's there's [44:29] only one manager role and you kind of [44:30] want it. How do you make sure that [44:32] you're the the first in line to get [44:34] that? [44:35] >> So first honesty sometimes is not [44:37] possible. sometimes like I'm not going [44:39] to promise people things that are [44:41] impossible. If you have several more [44:42] senior people in your team who are [44:44] qualified and have done a good job [44:45] expressing their interest, the right [44:47] thing to do is get out of line. Go [44:49] somewhere else. Go somewhere where [44:51] there's more opportunity. Uh and I I [44:54] mention that only because some people I [44:57] always make fun of the post office [44:58] because I can't imagine how you move up [45:00] in the post office. Like either you [45:01] deliver the mail or you don't and then [45:03] there's postmaster and there's one of [45:04] those and they stay there until they [45:06] retire. I don't know what the hell you [45:08] do at the post office. So, if you're at [45:09] the post office, metaphorically, get [45:11] out. Go somewhere that's growing. Now, [45:14] if it is growing and there's going to be [45:16] spots, you have to be sure. [45:20] Managers aren't mind readers. They don't [45:22] know [45:24] what you want. So, you've got to make [45:25] sure they know you want the role. The [45:27] second thing is you can ask them like, [45:29] "How can I be your first choice for this [45:31] role?" Or, "What would it take?" A great [45:34] way to phrase that is under what [45:36] circumstances, like what would lead you [45:38] to choose me, even if you have to be [45:41] kind of absurd, like, "Hey, Ryan, [45:42] against all odds, what would cause you [45:44] to bump me to the front of line and put [45:46] me first?" Like, what would that have to [45:47] look like? Why do you ask it that way? [45:50] Everyone can answer that. Everyone can [45:52] say, "Well, this is what it would take." [45:54] And then at least, you know, and you can [45:56] negotiate those criteria and say, "What [45:58] about this? What about that?" [45:59] The second thing though is [46:02] who gets promoted is who's [46:04] indispensable, who I can count on, who I [46:07] know is going to ride to my rescue when [46:09] there's a problem. So, what I would do [46:11] is I'd say if I want to jump the line, [46:13] if I want to make sure I get there, I [46:14] have to jump on crisis. When there's a [46:17] fire, I have to jump on it. Why? [46:20] um [46:22] doing your regular job well. There's a [46:24] lot of people doing that in a crisis [46:28] when a system is down, when a customer [46:31] is angry because they have an outage. [46:34] Who steps up to handle that and who is [46:38] technically brilliant and maybe a [46:39] leader, they get noticed. And [46:44] the question I'm asking myself at promo [46:46] time is this person I'm about to put on [46:49] my team, are they going to be the person [46:52] I can count on no matter what? Are they [46:55] going to keep me out of trouble? So you [46:56] have to show that trait. [46:59] Now what that usually means crises [47:01] unfortunately rarely happen conveniently [47:03] between 9 and five. They're always on a [47:05] weekend or a holiday. So you're going to [47:07] have to make some sacrifices to do that. [47:10] But to show you want to have a [47:12] discussion with your leader. [47:15] What's keeping you up at night? What do [47:16] you need most? I'm gonna work on those. [47:21] Um I just spoke to someone. They had a [47:24] great rule. They went to their manager [47:26] and they would have a chat with their [47:27] manager and say, "What are your three [47:29] biggest problems?" And their manager [47:30] would always can all managers always [47:32] have problems. They can always say, "You [47:33] know, I have these three problems." They [47:34] would say, "Great. Which one's worst?" [47:36] And they say, "Oh, this one." Say, [47:38] "Great. I want to work on your worst [47:40] problem. How do I like I want to go [47:42] solve your worst problem. How do we make [47:44] that happen? Well, of course, [47:47] somebody who's shown me repeatedly they [47:49] want to solve my worst problem. Who else [47:51] do I want on my team? That's how you get [47:55] there. It is hard. Okay, you've asked a [47:58] question. I want to be clear. [48:01] I've answered how do you get the spot? [48:03] What a bunch of people actually wanted [48:05] to know is how do I get that spot [48:07] without putting myself out too much that [48:09] I can't answer for you. There isn't, you [48:12] know, I don't know, bribery. Like there [48:14] isn't an answer for that one. [48:17] >> In that last bit there, you mentioned [48:21] someone he asked what are your worst [48:22] problems. I wonder if there might be [48:25] some unexpected opposite effect or what [48:28] I mean is if I was a leader and someone [48:32] was coming up to me and overly obviously [48:35] eager to try to get promoted almost, you [48:38] know, kissing up to me and saying, "Hey, [48:40] what's your worst problem? Okay, I'm [48:41] going to go solve that." It might make [48:44] that leader feel weird. It could I mean [48:47] again this is about all personalities [48:49] are different and you have to figure out [48:50] how to approach each personality. The [48:53] the question is the same which is what [48:56] are they going to value enough to invest [48:59] in me and enough to really get out on a [49:02] limb to try and help me. How do I How do [49:06] I set up a win-win deal where I'm [49:08] helping them and they want to help me [49:12] and we can keep pushing that to be more [49:14] and more extreme that uh just like [49:17] you're pushing me with darker and darker [49:19] questions, you don't normally jump [49:21] straight to the end. You build up. So, [49:24] you start by [49:26] doing good work, just being solid, [49:29] really solid. Then you get really good. [49:31] Then you start asking your manager, [49:32] "What can I help you with? What is it [49:34] you need done? I had this idea, so I [49:36] just did it and I thought it would help [49:37] you." You just build and then you start [49:41] asking like, "Hey, I want to grow and it [49:45] seems like we have a great working [49:46] relationship. [49:48] Could you give me some tips on how to [49:49] grow? Could you give me some things that [49:51] you think are challenges I need to work [49:52] on? Is there something special you need [49:54] done?" And then after you do that, you [49:57] deepen it again and you're like, "Hey, [50:00] I would really for both of us could is [50:03] there a role where like you need a [50:05] right-hand person who's your go-to in a [50:08] crisis?" Because I love hard problems. I [50:12] love being challenged with crisis, [50:15] and I'm sure you have some. Is there a [50:18] win-win where I jump on those? It's good [50:20] for me to like have that chance. And [50:23] it's good for you. you know, there's [50:24] somebody who's always going to step up [50:25] when you need it and you you've built [50:28] your way into it. So, this is a little [50:29] bit you're kind of asking the classic [50:32] frog in a pan thing. If you take your [50:35] manager and throw them in the hot water [50:36] of like, hey, I want to be promoted. How [50:38] can I do anything you need so that you [50:40] want to promote me? A lot of people are [50:41] going to be like creepy. Okay, you got [50:45] to boil that water a little slowly. [50:48] And this is not manipulation, [50:51] it's relationship, right? If you're [50:54] dating, [50:56] you like send someone a note or express [50:59] interest, you ask them out, you go to [51:01] dinner, you know, there's a process of [51:03] getting to know someone. [51:05] There are a lot of analogies between [51:10] different types of relationships and [51:12] there are some there's a process and [51:15] you're dating your manager in a way to [51:17] build a relationship. It's not because [51:19] you're going to get married but you are [51:22] it is a work marriage in a way for a [51:26] while anyway and that's okay. You build [51:29] that relationship and then you hold a [51:32] privileged position. [51:34] This is something you haven't asked. You [51:36] can't ask this question. People would [51:39] come to me and say like why do you treat [51:41] so and so so well or why do they get all [51:43] the benefits? Or they would also say why [51:46] don't why didn't you promote me? And I [51:48] always when I say why didn't you promote [51:49] me I say why didn't you earn it? Why [51:52] didn't you promote yourself? Like I want [51:55] to move you up. [51:57] show me something. And if you're asking [52:00] about this person, oh, I'm happy to list [52:02] all the ways they are contributing. And [52:05] if you want to do the same for the same [52:07] period of time, I'll put you where they [52:08] are, right? Like, because they'll be [52:10] gone, by the way. They're a climber. [52:12] They're going to either move up in our [52:13] company or move out. There will be a [52:14] hole. Get moving. So, I was a different [52:17] boss, I guess. But I was always tell [52:19] people like, you want a promotion? [52:22] Here's a piece of logic for you. Some [52:24] bosses aren't smart enough to figure [52:25] this out. I want the most senior, most [52:28] promoted team I can have. Why? Why on [52:31] earth would I not want the best people [52:32] on my team? So, if you can rise to be at [52:35] a new level, I want to pay you that and [52:37] have that because I'd rather have a [52:39] senior person than a junior person. Now, [52:41] I have a budget and whatever and I have [52:44] to fight uphill, but I have no problem [52:46] fighting up to my management saying, [52:48] "Look, yes, I have an expensive team." [52:51] Why are they expensive? Because my team [52:53] is damn good and you know it. and I've [52:56] moved people out of my team to other [52:58] teams and now they're leaders on those [53:00] other teams and you know there's stars [53:01] there. We have a star organization. We [53:04] build stars that costs money but it's [53:07] good for you and I can tell that with a [53:09] completely straight face and look the [53:10] financial officer whoever in the eye [53:14] story I'm coaching a company right now [53:17] on this method and I wrote the leader [53:19] there uh he's the chief product and [53:22] technical officer. I wrote him and I [53:24] said,"I can make your team higher [53:26] performing, but it's gonna cost you [53:28] salary when they step up. They're gonna [53:30] want to be rewarded. Are you ready to [53:32] pay for performance?" So, this is just [53:34] somebody I'm coaching and I'm telling [53:35] him like, I can raise your team's [53:37] performance, but it is going to like [53:40] you're going to have to hand out more [53:41] stock options. Are you ready? I did that [53:44] internally all the time. That's how you [53:47] make it work. [53:48] >> When someone would say, "Why didn't you [53:51] promote me?" You would you would say [53:53] directly back to them, why didn't you [53:55] promote yourself? [53:56] >> Absolutely. Those [laughter] words, [53:58] >> right? Why didn't you promote me? Why [54:00] didn't you promote yourself? Like, where [54:02] where is where's the work? Where's you [54:05] know, you didn't come to me. You didn't [54:07] get a special project from me. We didn't [54:09] make a deal and look each other in the [54:10] eyes. You do this, this, and this, and [54:12] deliver, and that's the bar. [54:16] There is one engineer, I've written [54:18] about this. I made a mistake early in my [54:20] career. [54:22] I still regret this. 20 years ago, an [54:24] engineer came to me, he made a deal and [54:27] I I failed to deliver. It was not [54:30] intentional. I was new to Amazon. I [54:33] didn't understand the system. And by the [54:35] time I went to get him promoted, I was [54:37] too late and had missed the window. And [54:38] I didn't even know there was a window. [54:40] And he rage quit. And he should have [54:43] unfortunately cuz I blew it. But that [54:46] was like user error, not intent. And I [54:50] never made that mistake again. Anyone I [54:53] promised I would help them move up. [54:54] Sometimes it was when I said sometimes, [54:56] unfortunately, it took longer. I always [54:58] got it done. But the people who just wh [55:02] they're uninteresting to me. And I [55:05] always tried to be clear to people the [55:07] door was open. The other thing about [55:09] promotion for everyone, no one ever in [55:11] life said, uh, you might be one of the [55:14] few exceptions. I know you had a [55:15] remarkable career. Very few people, [55:17] maybe even not you, ever said, "Oh yeah, [55:19] I got I got promoted way too early. They [55:22] gave me a bunch of stuff I wasn't even [55:24] expecting." Almost everyone in life is [55:25] like, "This took too long." That's going [55:28] to be true. Everyone hates the timeline [55:30] because who imagines oursel to be best? [55:33] It's always us. So you mentioned that [55:36] relationship building with the manager. [55:38] There's this game. We're talking about [55:39] this game, you know, how how you get [55:41] promoted and the system. Some people [55:45] don't like the game to the point where [55:47] you wouldn't want to talk about it [55:48] directly and others are fine with being [55:51] very transparent. Sounds like you're, [55:53] you know, the type of manager I could go [55:55] to you and say, "Hey, [55:57] >> I'm this level. I want to be this level. [56:00] What does it take?" And you would just [56:02] answer. [56:02] >> I would. I could imagine there's some [56:05] managers though that kind of push it off [56:07] or maybe it's an uncomfortable [56:08] conversation. What would you say to [56:10] someone that's under a manager that [56:12] doesn't want to talk explicitly about [56:15] promos? Part of me wants to say find a [56:18] better manager. Find someone who's [56:21] motivated because [56:23] sometimes those managers [56:25] aren't ambitious themselves and so [56:27] they're going to have trouble relating [56:29] to someone who wants to move up. But if [56:31] that's your situation and you have to [56:33] work with someone like that, I think [56:35] then what you have to do is look at who [56:38] they're rewarding. Uh look at who have [56:41] they promoted uh and why. And you might [56:45] think, oh well, how do I know why? Well, [56:47] one one example may not show you, but if [56:50] you see several people who got moved up [56:52] under them, you can find a pattern. Who [56:54] are they moving up? And then what I [56:56] would say is if they can't talk about [56:58] it, number one, you might be able to [56:59] talk to some of those people and say [57:01] like, I see that Ethan promoted you. How [57:04] did that work out? How did that come to [57:05] be? Or I see you got to senior manager [57:07] or senior engineer. What happened? [57:09] Figure out what they're rewarding and go [57:12] be that. And that's a slower process. It [57:15] may not be as comforting, but figure out [57:19] their language. Everyone has a language [57:21] to express this. [57:24] You have to figure out how how do they [57:27] have that conversation? Again, I would [57:29] go talk to the people that did get [57:30] promoted and say, "Did you have any kind [57:32] of conversation? [57:34] Did they ask something? Did you write it [57:36] down in your annual review that it was a [57:38] goal?" Like, how I try and find out how [57:42] did the manager make that decision? And [57:45] then I would go conform to that pattern [57:48] as best I could because that's what's [57:50] going to work without being as direct as [57:52] I am. That said, if you go do all this [57:55] investigation and find out they [57:56] basically didn't promote anyone or there [57:58] is no pattern, then you're back to my [58:01] like [58:03] there is no system to work in there. [58:05] You're you have to get to a place where [58:07] there is a workable system that if the [58:10] manager hasn't promoted anyone or [58:12] they've promoted very few people and [58:14] very late [58:16] then either you accept that that it's [58:19] going to be a little bit random and it's [58:21] going to be when they get around to it [58:22] or you get out. Here's a trick. AI has [58:26] made this super possible. It used to be [58:28] harder. [58:29] That manager communicates with people. [58:31] They write, they speak, they whatever. [58:33] grab a bunch of their communication, [58:35] throw it all into an AI and say, [58:37] "Analyze this person's communication [58:39] pattern. I have this goal, which is I [58:41] want to ask for a promotion. I'm very [58:44] direct. They don't seem to be. How do I [58:45] approach this person?" AI is amazing at [58:50] personality typing them and telling you [58:52] the words and methods to work with their [58:55] ability. Um, this, by the way, is like a [58:58] hack for anything at this point. Anyone [59:01] that you have some email chains with or [59:03] some of their public writing, grab it. [59:06] Tell AI, "This is a bunch of [59:08] communication from Ryan or from Ethan. I [59:10] want this thing, whatever it is. How do [59:13] I approach them in order to get it?" And [59:15] it will answer it for you. And that's [59:17] like, now if you're on the far side of [59:20] that, right? Like, uh, I've just told a [59:22] bunch of people how to approach me. [59:26] If there's a clever person listening, [59:28] they're like, "Ethan has lots of blog [59:29] posts and I want this from him. So, I'm [59:31] gonna get these emails now in the future [59:33] where people won't say, "Oh, I saw you [59:36] on Ryan. Here's my like secret scripted [59:39] email, but I'm going to get that. How do [59:41] I defend myself against it?" Well, one, [59:43] you have to know who you are and still [59:45] what your boundaries are. Two, though, I [59:47] think there will come a point where we [59:51] will have to have like our own AI [59:52] counter measures. So that's a little f [59:54] futuristic, but the ability of AI to [59:57] help me manipulate you is going to get [59:59] really strong. [60:00] So right now, I'm not saying manipulate. [60:04] I'm just saying use it to be educated [60:06] how to approach that person who has a [60:08] different personality than yours. But [60:10] the manipulation is coming. [60:13] This is a common situation I've heard [60:16] and seen people experience, which is [60:19] they talk to their manager about that [60:22] promo they want and the manager doesn't [60:26] say no, you're so far and here's what [60:28] you need to do and they don't [60:30] necessarily say yes either. There's this [60:32] gray area in the middle where they it's [60:35] they dangle this carrot but they don't [60:37] exactly give you the full story. So, [60:39] they might say, "Oh, [60:41] >> yes, you want to get promoted. That [60:43] sounds like a good thing. Um, you're [60:46] going to need to do more more work and [60:48] you know, I want that for you and we're [60:50] going to do it." And then if you ask a [60:52] hard question, when will it happen or [60:54] how do what are the concrete steps? They [60:56] go, "Okay, let me, you know, get back to [60:58] you or what do you do in that case where [61:00] it's this gray area, carrot dangling, [61:02] but it's very unclear if the promo is [61:06] concrete or not?" [61:07] >> Yeah. So managers don't like to be [61:10] pinned down. There's both good and bad [61:12] reasons for that. What do I mean good [61:13] and bad? Uh good reason is managers [61:17] don't have final control over [61:19] promotions. So part of what they're [61:20] thinking is I don't want to promise Ryan [61:22] something that I have to get through a [61:24] committee. I have to get through a [61:26] panel. Let's say Google for example. uh [61:29] Google at least in the process they add [61:30] at one point like there's a promotion [61:32] packet and it goes to all these other [61:33] people and the manager isn't really [61:35] there and it's this panel that decides [61:38] so I may truly want to help you get [61:41] promoted but I don't want to I can't [61:43] answer for you like when is the panel [61:45] going to say yes so that can be one [61:47] reason managers are legitimately fuzzy. [61:51] The other reasons they're fuzzy are [61:54] they're not sure when you're going to be [61:57] ready. They don't want to be cornered. [62:00] They don't want you to think they made a [62:02] promise and and uh one of the things [62:05] that's a problem is I if I say there are [62:06] these four things, I don't want you [62:09] coming back to me like I did exactly [62:10] those four. I want this today because [62:12] what if I came up with a fifth or what [62:14] if I think one of the four sucks and [62:16] wasn't very good. So I want to preserve [62:18] some room. The bad reason of course [62:21] everybody fears is I just don't ever [62:23] really intend to do it. I just want to [62:25] keep moving that carrot and keep you [62:26] working and working and working. So how [62:29] do you disentangle these? Well, first if [62:32] it's a system problem, the way to [62:34] disentangle it is to say, look, I know [62:37] you face a panel. I know that you know [62:40] you need our skip's approval. You need [62:42] this panel's approval. [62:44] I'm not asking for you to guarantee me [62:47] that we're going to get through the [62:48] panel. [62:49] I want to know what it's going to take [62:50] for you to be ready to be enthusiastic [62:53] to go make my case. So you try and back [62:57] the question off to something they can [62:58] say yes to because if I face some panel [63:01] I can't guarantee you a result. What I [63:03] can do is guarantee you that I will try. [63:06] So for example when I was ready when I [63:09] was hoping to become a vice president [63:10] and I had had these discussions with my [63:12] vice president he came to me and said [63:14] Ethan on this cycle I'm going to do [63:17] everything I can. I'm going to put you [63:19] up and I'm going to put my reputation [63:20] out there and we're going to see if we [63:22] can make it happen. He was real clear [63:24] though, like Jeff Bezos approved at that [63:27] point all the VP promotions. He could go [63:30] fight for it. He could line it all up, [63:33] but he couldn't guarantee me that Jeff [63:35] would say yes. So, that's how that got [63:37] handled. That's one way. Then [63:41] for these cases of trying to pin them [63:45] down where they want wiggle room, [63:49] you have to say, "Look, I understand [63:52] that answering me or telling me what [63:55] you're willing to do is still dependent [63:58] on me delivering and that new things [64:00] could come up. But understand, [64:04] I need help with the fact I have no [64:06] clarity. I don't have any date [64:08] expectations from you. I feel like it's [64:10] a moving target. Can you help me with [64:13] that as long like what can you do for [64:16] me? What you try and draw them into your [64:19] emotions? [64:21] Imagine what it's like to sit here to [64:24] hear that I'm a good performer [64:26] to want to work hard to achieve a goal [64:29] and to kind of have an amorphous target [64:32] I can't see where you're saying, "Well, [64:34] it's the right direction. [64:36] can you help me out? And you can even [64:39] say,"I know that you're probably not [64:41] trying to leave me in the dark, but what [64:44] can you do to shed some light on that?" [64:46] These are all uh variations. [64:49] Um I would recommend people read the [64:51] book uh Never Split the Difference by [64:54] Chris Voss on negotiation because it's [64:56] all about the psychology of how to get [64:58] other people into your framing. Um, and [65:02] so you get them talking about [65:05] you you find ways to draw them out. You [65:08] ask them questions like, "So, tell me [65:10] who else has succeeded or or tell me [65:12] what success would look like or tell me [65:16] uh how I can measure myself." [65:19] You can also ask them, this is totally [65:20] for the people who've read Chris Foss, [65:22] they'll recognize this. You can say when [65:25] they say, "Well, you should just keep [65:26] working towards it or whatever." You [65:28] say, "How can I do that?" like [65:32] I I and that makes it their problem to [65:34] explain to you how you can feel you know [65:36] how can I feel good about working [65:37] towards such an unknown goal an unknown [65:39] destination [65:41] that makes them puts them on the [65:43] defensive to solve your problem so last [65:47] thing it's a manager who just keeps [65:48] stringing people along well you're going [65:52] to have to get out from under that [65:53] manager or find a way to get a lot of [65:55] leverage over them [65:57] but the way you figure that out is you [65:59] look at what they've done for other [66:00] people? Are they actually promoting [66:02] people or are they leading everyone down [66:04] a path? And if you ever wonder like, am [66:08] I just suspicious or whatever, again, [66:10] it's look around, talk around. What are [66:12] they doing with others? [66:15] You alone [66:18] may feel misused. But if the evidence is [66:21] no, people in this or are getting moved [66:22] up and they are getting raises and [66:24] opportunities, then you have to figure [66:25] out how to earn it. And if nobody's [66:26] getting anything except strung along, [66:28] you have to get out. [66:30] >> So, we were talking about, you know, [66:32] limited number of spots, quota, or, you [66:34] know, promo. And the assumption is [66:37] there's these other peers that you're [66:38] competing with. [66:39] >> Sure. [66:39] >> But there's also a form of that where [66:42] you're not necessarily competing with [66:44] your manager, but there's a limited spot [66:48] because your manager needs to move up so [66:50] they can bring others along with them. [66:52] And so maybe the leaders in your org, [66:55] they're not moving up. Maybe they're not [66:56] ambitious or some other reason. What [67:00] would you do in that case where you you [67:01] want to be in line for a promo and your [67:04] manager is actually the one that's in [67:05] the way? [67:07] >> You know, there's always cases. One case [67:09] is the manager once is ambitious but [67:11] can't get there for whatever reason. [67:13] First question there is, can you help [67:14] them? One of the deals that definitely [67:17] worked for me that I made with some of [67:18] my stars is like, hey, I want to move [67:20] up. you want to move up. If if we can do [67:23] this thing together, we'll both move up. [67:26] And I enlisted multiple people in [67:29] helping me get promoted so that I could [67:32] promote them or vice versa. They got [67:34] promoted and then I could. Either way, [67:37] it was a two-sided equation. So, one [67:41] question I would ask is, is there [67:44] something you can help your ma manager [67:46] with? You can just talk to them about, [67:47] hey, I've shared my career goals. I've [67:49] been wondering. It seems like maybe [67:51] you're looking, you'd love to move up, [67:53] too. Is that true? And is there any way [67:56] I can help you? And that will make you a [67:58] super ally. Unless they're those ones [68:01] who are uncomfortable not talking about [68:02] it. Again, that's tricky. then you could [68:06] just go to like weird language of well [68:12] what's rewarded in this company and how [68:14] can I help our group be more rewarded or [68:17] something a little more oblique. Uh now [68:21] the second problem is your manager [68:23] doesn't really there are some people who [68:25] don't want to move up or they're just [68:27] not willing to push for it or they don't [68:28] think it'll happen. they've either given [68:30] up or they're ambivalent or they they're [68:32] one of those people who figures it'll [68:33] come when it comes and you're more [68:35] impatient than that. That may be a case [68:38] where you have to get out from under [68:40] them to to a different situation or you [68:43] ask them you have a different discussion [68:45] with them and say, "Hey, I'd like to [68:47] move up. [68:49] If we can't create that opportunity in [68:52] this team, will you help me find it in [68:55] another org? I could be a great [68:57] ambassador for your leadership and our [69:00] team elsewhere. Are you willing to help [69:04] me rise or to find a spot? And one of [69:08] the things that can work to your [69:09] advantage is a lot of the managers who [69:11] are a little less aggressive [69:15] are more into taking care of their [69:17] teams. [69:18] they're more into, well, the reason I'm [69:21] not so aggressive is I'm at peace [69:24] helping others or I really believe and [69:26] so they're more downward focused. So, [69:28] some of them are willing to actually [69:30] help you elsewhere. Now, there are ones [69:32] who are like, "No, I need you here and [69:35] if I lose you, my chance of moving up is [69:37] even worse than it already is." That's [69:40] tough. That however is your leverage [69:43] where you can say like look if that [69:45] seems to be the case you can say hey [69:48] here's the honest truth my career my [69:50] favorite words are my career is very [69:52] important to me no one can argue with [69:54] that right my career is very important [69:57] to me and so I'm going to move up I [70:02] would love to do it with you here but [70:06] I'm gonna have to do it and that's just [70:08] like a way there's there's like [70:11] you've expressed your first preference, [70:14] but you've also expressed a willingness [70:16] to make changes. And that's just a way [70:18] that that's essentially the polite way [70:20] of saying either you get it done or I'm [70:23] going to someone who can, but you say it [70:25] in a way that they can't like don't [70:28] threaten me. You just say, look, my [70:29] career is really important to me and I [70:32] have to I have I'm going to grow my [70:33] career somewhere. I'm in a season I'm [70:35] going to tell this story like a younger [70:38] employee. I'm in a season of my life [70:40] where I have this window. My wife and I, [70:43] my husband and I, my partner and I are [70:45] gonna start a family and I only have a [70:48] few years to really focus on work. So, [70:51] I've got to move up now. I've got to do [70:53] everything I can to have a fast career [70:55] while I have this moment. And I really [70:57] want to do that here in this org. If we [71:00] can make a path for that, that's where I [71:02] want to do it. But I wanted to talk to [71:05] you about it honestly because I do have [71:06] to do it. And so if it can't be here, [71:09] I'm gonna have to figure something out. [71:11] And you put on your puppy dog eyes like [71:13] that's a terrible outcome. And then you [71:15] shut up and you let him speak. And the [71:18] way I told that, no one can be mad at [71:20] you. Like you just told me you're [71:22] willing to work really hard for a few [71:24] years. You've got this nebulous we're [71:26] going to have a family thing. I don't [71:27] know, maybe you are, maybe you aren't. [71:29] No lying. But if you haven't totally [71:30] ruled out you're ever going to have [71:32] kids, that's like the easiest excuse in [71:34] the world. Or whatever. I have these few [71:37] years before I have to move home to [71:39] country X to take care of my aging [71:40] parents. There's a million variations of [71:42] it. This story about why you feel [71:45] urgency now and you really want to do [71:46] it. We've got a great relationship. I [71:49] really I enjoy this work. I'd so love to [71:52] contribute more in this organization, [71:55] [sighs] [71:56] but I I do have to advance my career. [71:59] And then you just wait and see what they [72:00] say. [72:02] Yeah, this seems like another one of [72:04] those gray areas because in the other [72:06] case the gray area was selling yourself. [72:08] In this case, it's I guess in a [72:10] negotiation because I could see someone [72:13] who looks at that and goes, "Oh, that's [72:15] not fully accurate or you don't know if [72:18] you're going to have kids or what. [72:20] You're using that as a tool to Yeah. I [72:23] don't think most people are like sitting [72:25] here in a podcast chair, you're thinking [72:27] about what people might be thinking [72:29] about in the moment." they're mostly [72:30] like taking in like, okay, what am I [72:32] being told? And I've got all these other [72:34] worries. But even if they're thinking [72:36] that, like the message is still clear. [72:39] If if you were to come back to me and [72:40] say like, well, you don't really know [72:42] your future, you know, like the future [72:46] is unclear, I can always go back to [72:51] this is how I feel. You can't argue with [72:54] what I feel or what I believe, right? [72:56] You can't tell me like nobody's going to [72:58] get in like well you don't know if [72:59] you're going to have kids. [73:01] No one's going to tell you that. So [73:04] that's what makes this you can call it a [73:06] trap but that's what makes this trap. [73:08] There are certain things you can't say [73:09] to people and and [73:13] you can't tell me not to care for my [73:14] aging parents. You can't tell me to not [73:17] to plan to take care of my family. These [73:18] are like totally off, you know. And by [73:22] the way, if they do say that, you know [73:23] you've got someone you got to get away [73:25] from. like, "Wow, your family's really [73:27] your problem." Okay, noted. Thank you so [73:31] much. Door, please. Check, please. Good [73:34] managers, clever managers will be like, [73:36] "All right, I see what's going on. I see [73:38] the negotiation we're having. I I see [73:40] like I'm on to your game, but I also see [73:43] like that puts them back in my camp." [73:46] We're like, "Okay, I see your game. You [73:48] know, what do I want from you?" I'm [73:50] thinking now like, "Okay, he's listened [73:52] to Ethan and Ryan's podcast. He's he [73:55] like knows the game. Well, as a manager, [73:57] I know the game, too. Like, what do I [73:59] want from you? And what's it going to [74:01] take? What what do I what what do I want [74:04] you to deliver? So, yeah, [74:08] what you keep asking is effectively, [74:11] what do I do with people that don't like [74:14] ambition? [74:15] Remember, there's proper ambition and [74:17] there is pushing too hard. I have had [74:19] people come to me, they're like brand [74:21] new out of college, and they're like, [74:22] I'd like to be a VP in two years. How do [74:24] I do that? Okay, that's a reality check [74:27] problem. Like, um, I don't know, you [74:31] know, is your last name Bezos and I [74:33] didn't notice. Otherwise, unfortunately, [74:35] that's probably not going to happen. [74:38] Let's talk about what could happen. And [74:40] then if they're like, no, no, no, VP. [74:42] I'm like, okay, I see. Like, door, you [74:45] know, you're alone. I don't need it. But [74:49] for normal ambition, there are people [74:51] who like find ambition a dirty word. [74:54] Like why should you worry about this and [74:56] the work is pure and you know just work [75:00] and it'll be yours eventually. And I I [75:03] guess those people, I'm going to be [75:05] really blunt, they're probably not [75:06] listening to this podcast because the [75:08] people you and I attract want more. And [75:11] if you have a boss or a manager who is [75:15] busy being very zen about like, "Oh, [75:17] it'll all come in due time." You're in [75:19] the wrong place. Go start your own [75:21] thing. Go come work for me or one of my [75:23] friends. Like find find a place because [75:27] there's so many hard charging people. [75:30] Go find them. Now, some of those people [75:32] will try and work you to death and [75:34] that's a different set of guard rails. [75:37] But go find someone who's shares your [75:39] basic desire to get somewhere in life. [75:43] >> So when you were a VP at Amazon and I [75:47] mean you're very cognizant of this this [75:49] game did you ever have reports coming to [75:52] you [75:53] employing these tactics something where [75:56] you thought okay this is uh polite [75:59] messaging on top of a hidden message [76:02] which is I want something from you. I [76:05] had one or two people who were really [76:07] good at it, but honestly most people [76:10] maybe because I was very transparent, [76:12] people weren't they were just honest [76:14] with me like this is what I want and how [76:16] can I get it and I'd be like here's the [76:17] bill. But I did have some people who [76:20] were very smooth. I also had a couple [76:23] people I mean I definitely caught some [76:25] people [76:26] lying right like just trying to run a [76:29] game on me and I fired them. When I say [76:32] running a game, they were dishonest. [76:35] They were they were actually claiming [76:38] things that weren't true. Those people [76:41] got gone. The last class of people I [76:44] want to talk about, honestly, [76:46] I had some very ambitious people in one [76:49] team I can think of that I couldn't give [76:51] opportunity to fast enough for their [76:53] desires. We can argue about whether or [76:56] not they were quite qualified, but they [76:58] went to other companies that saw more [77:01] value in them and they had they have had [77:03] or they had wildly successful careers. [77:07] So sometimes even a boss like me runs [77:09] out of opportunity because I attract [77:11] these hard charging people and I [77:13] encourage them. It's okay if they leave. [77:16] Meaning sometimes those people would [77:18] come to me and ask for something and I'd [77:20] be like, "It's going to take six [77:22] months." And I'm thinking like one guy [77:24] is like, "Samsung will make me a VP [77:26] tomorrow." And I'd be like, "You should [77:28] do that." And it was okay. Like this one [77:33] guy went and he went to to Samsung. He [77:35] got a huge role. It was a better job for [77:38] him. That's okay. But your question, did [77:41] I see people using these tactics? Not as [77:44] much as I'd like. I'd rather more people [77:46] were trying to figure out how to grow [77:49] their careers because I want to grow [77:50] people's careers. The ones I hate are [77:52] the ones who I feel are asleep. They [77:55] don't want to work that hard or they've [77:58] got some issue that they're angry about, [78:01] but they're passive aggressive and they [78:03] won't put it out there so that I can [78:05] address it or not. So, I can tell them [78:08] like, "Okay, I hear your issue. That's [78:11] not going to change. So now it's accept [78:13] it or leave and that's okay. Either [78:15] accept it or leave. They're both fine. [78:17] Or yeah, I can fix that. Here's how [78:19] we'll fix it. [78:21] I feel like even in a lot of high [78:24] performing workplaces, a lot of people [78:26] are kind of stumbling around blind with [78:27] no real plan. Some of those people are [78:30] happy that way. So what I try and [78:32] remember is like some people are in a [78:34] season of their life where they just [78:35] kind of want to do their job and be left [78:36] alone. Those are the people that the top [78:40] performers get to pass all their [78:41] mediocre work to. [78:43] >> Yeah. I remember there was this this [78:45] tweet that went really viral. It was [78:47] just an open-ended statement saying [78:49] something like, "Why is it that you [78:51] never hear the highest performers [78:53] complaining about their manager and [78:56] implicit in that is that they leave that [78:59] high performers have optionality and [79:01] they just go and find a better [79:03] situation." [79:04] You mentioned that if someone lied to [79:07] you, you'd fire them. But when you fire [79:11] people, you have to collect all this [79:12] evidence of underperformance and kind of [79:15] chase them down for, you know, some time [79:18] and then [laughter] [79:20] >> like how do you fire someone for lying? [79:22] >> Um, well, number one, if you could [79:24] really prove the lie, you probably could [79:25] terminate for dishonesty. You know, if [79:28] you had like ironclad proof of that was [79:30] a lie. But sometimes you know something [79:31] is a lie and you don't have it. I've [79:33] I've written before that a manager in [79:37] good standing at any level can get rid [79:39] of any one employee and there's like 50 [79:40] ways to do it. So you like dark. First [79:43] thing I can do is just start giving you [79:44] crappy assignments. The second thing I [79:46] can do is just say you know uh Ryan I [79:48] know we've talked about promotion. I got [79:50] to be honest with you. I don't really [79:52] see that coming. Uh you know it would [79:55] take a lot of change and I think you [79:57] better reset your timeline to three to [79:59] seven years. So you're probably going to [80:02] quit. Um, the third thing I can do is [80:04] rate you crappy. Uh, you know, [80:07] communicate like I'm seeing this is pick [80:10] your system, but like this is right now [80:12] I'm seeing you tracking below average [80:13] for the year and I just wanted to tell [80:15] you upfront I I see a low performance [80:17] review coming and you're like, wait, I [80:19] delivered this, this, and this. I'm [80:20] like, yeah, but here's my list of seven [80:22] other things you didn't do. Um, [80:25] I can always drive somebody out. And if [80:26] you go to HR and you're like, he's [80:28] turned on me. He's got all these [80:29] unrealistic things. [80:31] The fact is [80:34] I'm known as a good manager and you're [80:36] somebody below me. Like their HR's job [80:39] is to side with me unless I've done [80:41] something illegal. So they're going to [80:43] say, "Uh-huh. Uh-huh." It's going to be [80:45] very tough. Um, [80:49] and again, people hate this idea. This [80:52] is a flaw of our human society, which is [80:54] that a manager in good standing, if they [80:56] do get it in for one particular person, [80:58] they're going to win that. And like [81:00] theoretically at least an innocent [81:02] person can be totally screwed over. [81:05] What normally prevents that is good [81:07] managers don't want to screw over good [81:10] people. Like that's pathological. Why [81:13] would I want to get rid of a good [81:14] person? But if someone's really [81:17] cancerous in my organization or [81:19] dishonest, I have so many tools. Now I [81:21] can also start gathering all this [81:23] evidence if I want to and that's not a [81:24] bad idea [81:26] just in case I need it. But there's so [81:30] many ways to communicate to you that [81:32] your life here is over and it's only [81:34] going to be crappy work from here on. [81:36] And I can also ride you like, hey, our [81:40] workday starts at 10. You know, it's [81:42] 10:05 this morning. And just like I can [81:45] be on you for everything and like the [81:48] worst on calls and the, you know, the [81:51] most tickets. And it's very easy to make [81:54] your life miserable and it's very hard [81:57] to prove like, oh, Ethan, what are you [81:58] going to do? who go to HR who doesn't [82:00] know from in this context and [82:03] be like Ethan's giving me the worst [82:06] tickets [82:07] what you know like but how hard like let [82:12] me just ask you how hard this would be [82:14] okay we've got a 500 bug backlog and I [82:18] go through it and find 20 really crappy [82:20] things to work on and say I think for [82:22] your next on call these should be your [82:23] priorities by the way I'll be measuring [82:25] you to them hint hint if you don't do it [82:27] it's goes in my evidence file to fire [82:29] you and they're just nasty. And let's [82:33] assume I'm technically incompetent and I [82:34] can't do that. It's still a way to do [82:36] it. I go to Fred and I say, "Fred, I was [82:40] wondering in our bug database like what [82:42] are 100 tickets you think are pretty [82:44] useless and we should just close them." [82:47] Innocent request. Now, I take this [82:49] hundred and I come to you and say, "You [82:51] know, I've been thinking about some of [82:52] these tickets and I need some data on [82:54] these 20. I want you to prioritize [82:58] working on these 20 picked from that [82:59] hundred and get them all done this week [83:03] and tell me what was the total value of [83:05] them. And if you ever come back like [83:08] those were terrible tickets. How could [83:09] you do that to me here? I even know you [83:11] asked Fred what were a bunch of useless [83:12] tickets. Like yeah I was double-checking [83:15] Fred's judgment. You still had to close [83:17] all the tickets. I have a defensible [83:19] thing. What I'm going to do now, thank [83:21] you so much Ryan for plowing through [83:22] those. I'm going to close the other 80 [83:24] with no resolution because you've shown [83:26] that Fred was right, you know, but I've [83:29] still jammed 20 lousy tickets picked by [83:32] Fred down your throat without knowing [83:33] anything about what's going on. I can do [83:36] this all day. You throw me scenarios, [83:38] I'll find another way to come around HR [83:41] and make your life miserable. So, what I [83:43] do to summarize, if I really want rid of [83:46] somebody, I let them know it's over, [83:48] right? with words like, you know, I just [83:52] want to level with you. I see after [83:54] recent events, an illusion to me [83:56] catching you lying, even though you [83:57] don't admit it. After recent events, I [83:59] gotta be honest. I'm seeing this as a [84:02] challenging year. And I know you've [84:04] asked me about, you know, promotion. I [84:07] think you might want to reset your [84:09] timeline. It's all I have to say on [84:10] that. And then I start like making clear [84:13] that the punishment's going to keep [84:14] coming. You will evaporate. [84:17] I just have to wait a little bit. And [84:21] you'll either evaporate by quitting or [84:22] getting another job or you'll evaporate [84:25] by getting pissed at me and doing [84:26] something else outrageous that I have [84:28] instant cause. Luck again though, I want [84:31] to emphasize like sane bosses don't do [84:33] this to good people, but it's a tool. [84:37] And [84:39] that's the way our world of fallen evil [84:40] humans works. [84:43] >> Yeah. And this is another one of those [84:44] gray areas though because uh in the case [84:47] where you're pursuing someone that [84:48] obviously lied. You are kind of just and [84:53] you're outing someone that's bad. I [84:55] guess it would it would be very [84:56] unfortunate if you just didn't like [84:59] someone or there was something that [85:01] didn't quite click with you with [85:03] someone. [85:03] >> Well, there's a there's another way to [85:05] handle that. Okay. So, let's assume you [85:07] and I don't click. It is again [85:10] everything is a gray area in human [85:11] relationships. Let's assume you and I [85:13] don't click and let's even assume I'm a [85:16] good person and I've tried to figure out [85:17] how to work around it. I may have even [85:19] talked to you and say like you know your [85:20] style is [85:23] you tend to whatever some personality [85:26] trait like you tend to look at the [85:27] downside for the upside and I really [85:29] want to run a positive upside team and I [85:31] need you to be more upbeat. You think [85:32] you can do that and you're like yes I'll [85:34] try but the truth is you can't. Um, [85:38] I can just come back to you. The nice [85:41] way to do it is say, "Ryan, look. We've [85:44] talked before about compatibility. [85:46] You and I just [85:48] we're like, you know, not that [85:50] compatible. [85:53] I would like to help you find a place [85:56] where you're going to thrive. Would you [85:59] be open to that?" And and like the [86:01] invit, [86:03] it can be external. I will make [86:05] introductions. [86:06] I will help you. If you take me up on [86:09] that, I just help you find a new place [86:10] with a new fit. If you don't take me up [86:14] on that, you're like, "No, I really want [86:15] to be here and I think you're unjust. [86:17] You need to be my way." Blah blah blah. [86:19] Then I'm like, "Well, I tried. Now I [86:21] just go back to my million strategies to [86:22] get you to decide you want to take the [86:24] offer to move along." Why is that [86:27] potentially justified? [86:29] Uh, I'm not going to claim it's totally [86:31] justified, but the fact is we all have [86:32] to work together. And in the if you're [86:36] too much of a pain in the ass to work [86:37] with, too much of a disturbance to my [86:39] zen, [86:41] frankly, the corporate hierarchy has [86:43] determined that I'm the important one. [86:44] That's why I'm the boss. And like again, [86:47] there's people screaming like, "How can [86:49] you possibly say that?" Well, that's why [86:51] it's an org chart and it goes up at the [86:53] top. Okay? And I deal with the same [86:55] thing above me. Either I make Bezos or [86:57] whoever happy or I'm expendable. [87:00] That's our system of life. And [87:05] we don't live in perfect world. I wish [87:07] we did. We lived, you know, some perfect [87:09] world where that wasn't true. [87:12] But I have a whole team to run and if [87:14] you're sucking up too much of my energy, [87:16] I I have to get rid of that. Now, I can [87:20] think of some people who annoyed me [87:21] enough I encouraged them like maybe we [87:23] need to find you. you know, maybe let's [87:25] work together to find another place [87:27] that's like a more natural fit. And I [87:30] think that's fair because probably if [87:32] we're that different, you're not loving [87:33] it. Like, it's not great for you either. [87:38] And so, you know, this is a little bit [87:39] the breakup line of like, oh, it's not [87:41] you, it's me, but you still need to go. [87:43] Like, still pack your and move out. [87:46] That's the gentle way though that [87:48] somebody doesn't end up fired. And I can [87:50] totally find, look, I probably have an [87:52] opinion of some manager I think who's [87:54] just like you. I probably don't care for [87:55] them that much. I probably think like, [87:58] wow, they operate in this weird way I [87:59] can't stand. But those two are going to [88:02] be perfect together. [88:04] You know, maybe they will. Open [snorts] [88:07] AAI, Enthropic, Cursor, and Versel all [88:11] use this product to make their lives [88:12] better. And the problem it solves is [88:15] when you're building SAS or an AI [88:17] product and you want to sell to other [88:18] companies, there's all these [88:20] requirements you need to meet. There's [88:22] SSO, there's skim, there's arbback, [88:25] there's audit logs. These are all things [88:27] that take time to integrate but aren't [88:29] the main focus of your app. Work OS is [88:31] an API layer that lets you meet all of [88:33] these requirements in just a few lines [88:35] of code. So let's say you have a new SAS [88:38] product and you want to sell to other [88:39] companies. WorkOS will solve all of [88:42] these critical feature gaps for you. You [88:44] can check them out at workos.com to [88:47] learn more and get started. And I [88:49] appreciate them for supporting my work [88:51] and sponsoring this podcast. [88:53] >> As you said, a manager can fire any one [88:56] employee that they wanted. [88:58] >> Yeah. [88:58] >> And you know, HR is going to side with [89:01] the manager. Is there any edge case or [89:04] any weird situation where the opposite [89:08] could be true which is the indeed the [89:12] engineer is in the right and they're [89:14] trying to get rid of an unjust manager [89:17] and they're working with HR. Yeah. So [89:20] over 50% of this is gonna be who goes to [89:22] HR first because you get to set the [89:26] framing. You get to make the complaint. [89:28] So, one of the things I would totally do [89:30] if I'm the manager is before I started [89:33] saying stuff to you, I would send a [89:35] little note to HR that says, "Hey, I [89:37] just want to let you know I'm I've [89:39] noticed some challenges in Ryan's [89:41] performance. I'm going to start working [89:42] on them." You know, ABC, whatever. I [89:45] just set the framing. And that way, when [89:46] you come to them to complain, you're [89:48] running into this wall that I've already [89:49] framed you as a non-performer. Going the [89:52] other way, if you're the employee, [89:55] you want to be the first one to HR about [89:57] the situation [89:59] and you want to frame it as [90:04] not I have a terrible manager, [90:06] but you want to frame it as [90:09] I'm really [90:11] trying to do great work for this company [90:14] and I'm really struggling because of [90:15] fact [90:17] citing behaviors of mine. So, you never [90:20] actually at least open the conversation [90:22] by saying like, "Ethan's terrible and [90:24] you need to fire him." Instead, it's how [90:27] these factual situations, [90:30] again, facts can be viewed many ways. [90:32] You view them your way and get them out [90:34] there. [90:35] These factual situations are limiting [90:38] your ability to produce and that of your [90:41] peers. The second thing is, if you want [90:43] to win one of these uphill battles, [90:45] you're probably going to need at least [90:46] one other person to verify what you're [90:48] doing. like verify the problem. The [90:51] third thing is it sure helps if you're a [90:53] superstar, right? Because if you're Joe [90:56] average or below average, no one's gonna [90:59] go out on a limb. [91:01] You really need to be standing out [91:03] enough that that maybe HR already knows [91:06] you or you're top rated and they're [91:08] like, "Oh, a top rated employee or one [91:10] of the people, you know, or maybe your [91:12] skip already knows you or your name is [91:14] on this tool, right? Those kinds of [91:17] things can influence HR. The last thing [91:21] of course that you hope for is bad [91:25] manager is a huge category. Is there a [91:28] smoking gun where I've done something [91:33] illegal, patently unethical, somehow [91:36] unacceptable to you or someone else that [91:38] can be documented [91:41] um or not? If the manager [91:46] is generally viewed as well performing [91:49] or has a good relationship with their [91:51] boss, it's going to be very, very hard [91:53] to get rid of them. So, I've had stuff [91:56] come to me from employees that have led [91:59] me as a skip level to terminate a [92:01] manager, but it's because [92:04] it was several people over time and the [92:07] facts added up to show my manager was [92:10] actually [92:12] doing things they shouldn't. And when I [92:14] say shouldn't, not just low performing, [92:16] but like unethical [92:18] or just really not like super [92:22] untalented, but that was usually my [92:24] observation as well. Then everyone has [92:27] this fantasy of justice is going to be [92:30] served. And you've asked like, does it [92:33] ever happen? Sure, it happens in the [92:36] movies and it happens one in a million. [92:38] But in real life, [92:41] it's just so much easier to leave. And [92:44] what will actually happen is you'll [92:45] leave and three other people will leave [92:47] and then finally the management will be [92:49] like, "Oh, I'll tell you a story. I'll [92:52] exemplify this for you. One of the [92:53] people I coach, can't say where, he was [92:57] telling me, I have this real problem. I [92:59] have this manager I like, [93:02] but I've been they keep losing [93:06] employees. people keep quitting their [93:08] team and saying it's about the manager [93:10] and I've been trying to coach them to [93:12] change and they haven't been changing. [93:14] What should I do? And I asked this [93:16] manager said, "Well, how long you been [93:18] coaching this person?" And he said, "18 [93:22] months." [93:23] And I said, "Hold on. You've had [93:27] employees in your organization quitting [93:30] and pointing to this manager for 18 [93:33] months and you've been trying to coach [93:36] them to change and they haven't changed [93:39] and you haven't done anything. They're [93:41] like, "Yeah, I like them. I I I I want [93:43] to see them succeed. I I I have this [93:46] hope for them and they're nice." Okay. [93:50] What about your employees who quit? And [93:53] by the way, if this person didn't work [93:55] for you, but you were like, if I had [93:58] told you the story, what would you tell [93:59] me to do? Like, oh, I'd tell you, fire [94:01] that manager. I'm like, right. Well, why [94:04] aren't you doing that? Well, like I [94:06] said, I like them and I don't have a [94:08] problem with them. This is why it [94:10] doesn't work. This is a real case of a [94:13] real client of mine who's got employee [94:16] after employee quitting out from under a [94:18] manager that they see as like I'm going [94:21] to make them better. I like them and I'm [94:24] going to bring them through this. And [94:26] what they're not seeing is like one [94:28] person after another like you is like, [94:30] "Oh my god, I got to get out of here." [94:33] It's not even the message isn't reaching [94:35] the manager. He knows what's happening, [94:36] but he's like, "Oh, I'm gonna work with [94:38] him." [94:40] This is what I'm trying to tell you. [94:41] Like it just, [94:43] you know, and if that person, if that [94:45] client of mine is listening, like, "Yes, [94:47] I am telling your story without your [94:48] names because you need to fire that [94:50] person [94:51] for your own sake and for them." And [94:54] he's like, "Oh, but we're not hiring. [94:56] What if I can't get a back fill?" And [94:57] I'm like, "It doesn't matter." Okay? You [95:00] have a you have a cancer who's killing [95:01] your team. Live without him. Right? But [95:05] or or do something about that. But like, [95:07] but I'm just showing you how the inertia [95:09] works because that manager that you [95:12] think is bad, I think is great because [95:14] they do whatever I want. [95:16] >> It sounds like there's there's two [95:17] things here that give you leverage in [95:19] these conversations. There's your how [95:22] high performing you are and how liked [95:24] you are. If you're high on both of [95:26] those, it gives you power. [95:28] >> Absolutely. So, I often say the hardest [95:31] person to fire is kind of like this [95:34] manager I was just talking about. If [95:36] you're looking as a boss, it's very easy [95:39] to fire people who are disliked and low [95:42] performers. Like they're not that good [95:44] and nobody really cares. Everybody can [95:46] see like easy. [95:48] It's also actually if someone is [95:50] disliked [95:52] but either a high performer or not. If [95:54] most people don't like them, nobody's [95:56] going to care and they're thorny, like [95:58] too thorny in a bad way. Uh that's also [96:02] easy. And thorny there means they've [96:04] made themselves disliked with others, [96:05] not just with me. Like they're generally [96:07] disliked. The hardest one to get rid of [96:10] is the person who's mediocre. They're [96:13] not obviously terrible, but they're not [96:16] very good. They're like below average, [96:18] but everybody likes them. And why is [96:20] that hard? Well, number one, there's no [96:22] smoking gun. They've never screwed [96:23] anything up bad enough that you can just [96:25] be like, "That's terrible. You're out." [96:28] And if you go after them, everybody's [96:31] going to look at you and say, "But [96:33] everybody loves Bob. Why are you down on [96:35] Bob? Like Bob brings donuts. He's [96:37] friendly. He throws a barbecue at his [96:39] house every year. Like he's always [96:42] picking up work. Yeah, the work he does [96:45] kind of sucks and is often late, but [96:47] he's always volunteering [96:50] really hard." So yeah, be likable. Now [96:53] I've said be thorny. How can I be saying [96:56] be thorny and be likable? You can do [96:58] both. Okay? You're likable all the time. [97:02] Meaning like you're friendly, you're [97:04] outgoing, you're pleasant, you're talk, [97:06] you're talkative, [97:08] except when people are trying to do [97:12] something you don't like. And then [97:15] it's just that little push back and that [97:19] little push of come on, just that much. [97:21] Come on, really? This is our priority. [97:24] like, "Is this what you're telling me [97:25] you want me to do?" Just that little [97:27] face. It doesn't take much. The other [97:29] thing is if that's too much, you can [97:31] push back. As I said, with humor be [97:34] like, "All right, but you're using up [97:37] one of your crap work tokens. You know, [97:40] I only give so many of those a month. [97:42] So, is this where you want to spend one? [97:43] We'll do it. It's only three a month." [97:48] Nobody can really get mad at you for [97:49] being like, "Hey, boss, I only give out [97:51] three work tokens a month. If this [97:54] is one you need to spend, I got it for [97:56] you. But like we are burning a token. Is [97:58] this it? And you know people will accept [98:01] this framing. This is the weird thing [98:03] about humans. I can push on you the fact [98:05] that you get three shitwork tokens a [98:07] month. You never agreed to that. You're [98:09] like, I'm the boss. If I want to give [98:11] you 73 shitwork tokens, you're going to [98:13] spend them all and say, "May I have [98:14] another?" But that isn't what we do. [98:16] We're like, oh, three shitwork tokens. [98:19] Okay. [98:21] because you set the frame. So that's a [98:24] way to be thorny and still be liked [98:26] because if other people see you do that, [98:28] they're like, "Hey, that's pretty [98:29] clever." Like Ryan's pretty smooth. [98:32] They're not mad at you, but you just [98:34] like brushed the boss back in front of [98:36] everybody. Even the boss is like, "All [98:37] right, I see." [98:39] Because what are they thinking? They're [98:40] thinking like, "Well, you said yes [98:42] today. That's good. You gave me two [98:43] more. That's fine. I'll deal with it if [98:45] I get to token three." [98:47] But subconsciously, you set the anchor. [98:50] They're like, "Three's the lie." And [98:51] they're going to know that. [98:54] And even worse, if you did it with [98:55] witnesses, [98:57] then they're like, "I kind of agreed to [98:59] it in public." Like, even though I never [99:01] agreed, I let it stand. [99:04] And you've got them cornered because [99:06] they can't be like, "No, Ryan, I I'm the [99:10] one who tells you how much work and [99:12] it's unlimited tokens." That makes them [99:15] look horrible, right? And so, nobody's [99:17] going to do that. And this is this is [99:20] how you be still very likable and funny [99:23] but like lines [99:25] >> for job security. It sounds like [99:28] likability is more important than [99:32] performance. [99:33] >> I mean [99:35] it depends on the context. Being liked [99:38] never hurt anybody. And look, I've seen [99:40] like another decision I saw made [99:42] technically totally illegal. We were [99:45] deciding on a layoff in a company I was [99:47] in and we had to cut some people and one [99:50] of the other leaders said, "Well, that [99:51] guy's married and has a family to sport [99:53] and this other guy doesn't." There's no [99:55] legality in that. You can't bring [99:56] people's family situation, but that was [99:58] what happened. So, decisions get made on [100:02] criteria that aren't performance and [100:06] that's a very real thing. So, likability [100:10] is one of them. and like, hey, a [100:13] question. If I, let's say I wanted to [100:15] save you and you were likable but lower [100:17] performing, hypothetically, [100:19] uh, and there were a bunch of people [100:21] making the decision, what I would say is [100:23] like, yeah, Ryan isn't always our top [100:26] performer, but this new room has to pull [100:30] together. Who do we want in that room? [100:32] Who's going to light up the room and [100:34] keep everybody's morale up after we go [100:38] through this grim event? I think we need [100:41] Ryan at that table. And I've just turned [100:43] your likability into a performance [100:45] asset. And that kind of thing also [100:47] happens because who do I want to work [100:49] with? I want to work with [100:51] I do want to work with really smart [100:53] people, [100:55] but I also want to work with people I [100:56] enjoy who can pull together. And that's [100:59] the likability piece. High performance. [101:02] There are cases where you will say like, [101:04] "Yeah, [101:05] you know, Robert is the only one who [101:07] knows that old arcane system, and even [101:10] though he's really tough to deal with, [101:14] we're going to need him." That also [101:16] happens. That's the Cal Newport so good [101:19] they can't ignore you path. [101:22] But like, what's going on in my mind is [101:24] how can we crossrain someone on what [101:26] Robert knows so that we're not in this [101:28] situation? Because the truth is, I'd [101:31] rather unload him. Nobody ever wants to [101:34] get rid of the likable guy if he's at [101:36] all good. But the high performance guy [101:39] who nobody likes, we're looking for how [101:41] do we get out of this situation? How do [101:43] we get out of our dependence? Because no [101:45] one likes to feel trapped and depending [101:47] on someone who's unpleasant. And that's [101:50] why that's dangerous. [101:54] I also want to make clear, you don't [101:55] have to be like this super lovable teddy [101:58] bear. Just be a decent person. Don't be [102:02] rude or judgmental. Don't be that person [102:04] who's like always talking down. [102:08] Super like engineers hate this. Again, [102:11] this is my list of like stuff. Engineers [102:13] hate managers have fragile egos. They [102:16] have uh impostor syndrome. They're [102:18] always wondering even if they're [102:19] technical managers. Part of their mind [102:21] is like, "Am I technical enough to keep [102:23] up with the team?" Well, there's that [102:25] one engineer who wants to show the [102:26] manager like, "Ah, you're really out of [102:28] touch, old man." [102:31] I don't like that. And so, if you keep [102:35] showing me up in front of the team, [102:37] you become marked for death for two [102:40] reasons. Okay? One, I don't like you. [102:43] And two, I can't have you doing that. [102:45] So, if I can't win you over, then I have [102:47] to shut you up because I got to keep the [102:50] rest of the team with me, and you're [102:52] undermining my authority. And [102:56] humans are incredible rationalization [102:58] machines. I will always my mind will at [103:01] night come up with some reason why [103:03] that's justified. It always does. Like [103:05] that's what human minds do. That's why [103:07] there's so much nasty behavior in the [103:09] world. People don't tell themselves. [103:12] Nobody wakes up in the morning and like [103:15] I'm a super villain. This doesn't [103:17] happen. The super villains wake up and [103:20] they're misunderstood. Nobody [103:21] understands the greater good I'm doing. [103:24] Nobody understands that I'm just getting [103:26] by taking care of my family. Nobody [103:28] understands this is just the way the [103:29] world is and some people got to die. [103:31] They always have some nobody understands [103:33] and it's okay because just and we all [103:37] like were built to do that. Literally [103:40] built to last question on this dark [103:43] topic and we'll go to the the darker [103:45] one. [103:45] >> Darker. All right. [laughter] [103:48] >> This hole has no bottom. Let's go. [103:51] Um, so we've been talking about promos [103:54] and how there's uh maybe limited spots [103:57] in some cases and not that you would [104:01] recommend anyone do this, but let's say [104:05] your peers are going for that spot as [104:07] well and they know that you're one of [104:09] the people that wants it too and so they [104:12] undermine you. So they're attacking you. [104:15] How do you defend against being [104:17] undermined by your peers where they're [104:20] saying, "Oh, he's not, you know, the [104:23] best candidate for that position." [104:25] >> Yeah. So, speed matters. Uh, again, [104:27] going first really matters. If you have [104:31] seen this once, you can predict it will [104:33] happen again. So, if you get bitten once [104:35] or see someone bite someone else once, [104:38] you can predict that person did it once, [104:39] they're going to do it again, they're [104:40] going to do it to me. So then what you [104:43] have to do is get in front of it with [104:44] your management and say, "Hey, I don't [104:47] know if you've noticed, [104:50] but there is some undermining in this [104:53] team." Like, we have a competitive team. [104:56] Some people will take shots at each [104:57] other. I'm never going to do that, but [105:00] that means I'm counting on you to [105:01] recognize it because I'm not going to [105:03] play that game, but I'm counting on you [105:05] to see it. and just please judge my [105:09] performance by what I actually do, not [105:11] by what anyone else says. And then [105:13] you've planted the seed in their mind [105:15] without accusing anybody of when someone [105:17] comes and chirps, they're like, "Oh, [105:20] that's what Ryan was talking about." And [105:22] now you're up too because like I'm going [105:23] to disregard what they said and not [105:26] knock you down a peg. Meanwhile, I'm [105:28] going to look at the other person and [105:29] say, "That's interesting." and knock [105:31] them down for undermining. You really [105:33] want to set that like the if if this is [105:36] a problem you've seen, you want to talk [105:38] to your management and just be like, [105:39] "Hey, I've seen some people in the team [105:41] maybe while you're not there talking [105:42] about each other." And it really [105:44] disturbs me. I'm worried that if they're [105:46] talking about each other or other [105:48] people around me, they're also talking [105:50] about me to you. And I'm not going [105:54] to play that. And I'm I'm not accusing [105:57] anybody, but just please [106:00] judge me by what I actually do. And if [106:02] you ever have any question about what [106:03] I've actually done, grant me 10 minutes [106:06] to show you. Cuz if I can't back it up, [106:09] that's great. Like that's fair. But if I [106:11] can judge me by what I've done and that [106:14] humble pie act of like judge me by what [106:17] I've done and give me a chance to show [106:20] it. Again, who can object to that, [106:24] right? But you've set that anchor so [106:25] that then if somebody comes and like [106:27] well Ryan blah blah blah or [106:30] then they look they're playing into it. [106:32] Now let's assume I know you're going to [106:34] ask me well what have they beaten you to [106:35] it and you find out they've been doing [106:37] this and your boss is like wow really [106:40] how much did you have to do with that [106:41] project? First, you may have to just be [106:43] like, "Okay, once bitten, twice shy. Now [106:45] I've learned." But you can without being [106:49] defensive, you can just say, "Haven't [106:51] done that much, huh?" [106:53] And that's the Chris Voss trick of like [106:55] mirror back to them where they're like, [106:56] "Well, you didn't contribute that much." [106:58] And you say, "Contribute that much." And [107:00] let them like keep talking. Well, so and [107:02] so said, "Oh, interesting. So and so [107:04] said." And you just, this is a trick [107:07] from the the book, but it's very [107:08] powerful called mirroring. you just say, [107:11] repeat the last few words they ended [107:13] with and they will keep talking and [107:15] they'll talk themselves into trouble. [107:17] But eventually you just say, "Well, I'm [107:19] really disappointed by what you're [107:21] sharing. I think if you're willing to [107:24] examine it, my work speaks strongly for [107:26] itself, but I certainly want to make [107:29] sure I'm judged rightly in the future." [107:32] Uh, so that we're both on the same page [107:34] about what I contribute. What's the best [107:36] way for me to just showcase what I've [107:38] contributed to you so that you're fully [107:41] informed? Because that's another little [107:43] dig, very subtle. Maybe you're not fully [107:46] informed right now, but how can I make [107:48] you fully informed in the future? But I [107:50] I haven't said, "Oh, you're not fully [107:52] informed." Just said, "So you can be." [107:54] So I've set this anchor that like you're [107:56] not fully informed, [107:58] but I'll make sure you are in the [108:00] future. These are just all little [108:02] techniques. [108:04] Lastly, I know I say this a lot. If [108:06] you're in a team with a bunch of snakes, [108:09] not all teams are like that, [108:12] you know, find your way out. [108:15] Another thing, [108:17] if there is a chance, rather than [108:20] counterattacking the person [108:23] uh who's undermining you, [108:26] that puts you down in their gutter. [108:28] instead figure out a way to catch them [108:31] out or set a trap or otherwise expose [108:34] them as a talker. Um maybe you know [108:38] your team probably has a bunch of [108:39] neutral people who just don't care. [108:42] Um wait until that person who's got that [108:45] behavior probably shoots at other people [108:47] too. Go find those people and say, "Hey, [108:51] I heard Ethan say that you didn't [108:53] contribute that much. I just want to let [108:55] you know I thought I thought you [108:57] contribute a lot. I'm not sure where [108:59] that came from. You do that with a few [109:01] people and that's just forms the like [109:05] right and you're not you never said like [109:08] I see he's running you down. Say I'm not [109:10] sure why he said that. I thought you did [109:11] a lot. It's that subtle just like hey I [109:15] see you. And you do that with a few [109:17] people and suddenly they're all like oh [109:19] you know that other person's always with [109:21] a little bit of help. People are very [109:23] good at seeing through others. Once your [109:27] eyes are open to like this person's [109:29] behavior has double meaning, it's much [109:32] easier to see. So, you just have to like [109:34] help people open their eyes a little. [109:36] You can even just be really curious and [109:38] say like, [109:39] you know, I noticed today Ethan was [109:42] saying bad things about Fred's work. [109:44] You're talking to a third person. [109:46] Why? Why do you think that was? Like, [109:48] what what caused him bring that up? It's [109:50] so strange. You're not even saying like [109:53] I disagree with it. Just that was a [109:55] little weird. [109:57] You just leave it. Their mind will go [109:59] like what was weird about that? Huh? [110:01] Maybe like seeds of doubt. Seeds. [110:04] Planting seeds and being patient. Great [110:06] relationship tool both in terms of [110:08] planting seeds of I'll help you and [110:10] planting seeds of doubt where you need [110:11] to. That's that doubt like where I've [110:13] said my career is very important to me [110:15] and I need to move it forward. I'm just [110:16] planting that little seed of doubt of [110:17] like either you take care of me or I [110:19] take care of myself. I just let that [110:22] grow, plant those seeds. When I think of [110:25] politics, it feels like this adversarial [110:28] game. If everyone was playing this game [110:31] optimally or using all these tactics [110:33] that you were saying, does that change [110:35] what is the best thing to do? [110:38] >> So, I will answer your direct question [110:40] in a second of like does that change [110:41] what's optimal? [110:44] Politics, the way you're describing it [110:46] in all these sort of dark scenarios, [110:48] they're never ideal. this dark scenario [110:52] in a real like where do we start about [110:54] getting credit? In the best world, [110:56] managers have a pretty good idea of [110:58] credit, but all the team members are [111:00] sharing honestly what they've done and [111:01] we're all trying to grow together. And [111:04] like I said, with this company I'm [111:05] working with, we're trying to get all [111:06] the boats to rise. The company gets [111:08] higher performance, which means it does [111:11] better in the marketplace, which means [111:12] everybody's shares goes up and we can [111:14] give more out and like everyone wins at [111:16] some level. So, there are positive ways [111:18] to do this. It does not have to be zero [111:20] sum or prisoners dilemma but those [111:23] situations do arise [111:25] and if everyone we know where the [111:28] prisoners dilemma to site a problem [111:30] hopefully if somebody's watching they [111:31] don't know it Google it but I'm assuming [111:33] they all do [111:35] in the prisoners dilemma we know how it [111:37] ends which is everyone stabs each other [111:39] all the time and it ends up nobody makes [111:42] progress but nobody loses progress so in [111:44] this highly political everybody doing [111:46] this what you would have is you'd have a [111:49] set where because everyone is [111:50] maneuvering in this politically optimal [111:53] way, you're right back where you [111:54] started. No one's getting an advantage. [111:57] So you're back to neutral. [112:00] What I would say to do is if you [112:02] recognize that case like, oh, everyone [112:04] here is very politically astute. I would [112:06] be like, ah, so my problem is I'm [112:11] playing poker at a team of excellent [112:14] poker players. I can hold my own, but a [112:17] much better thing is go to that table of [112:19] suckers and clean them out. Like go [112:21] somewhere else that's a different game [112:24] or a different level of play where I'm [112:27] the star. I often share it this way. [112:30] When I chose to do what I do today, [112:32] which is coach and teach online, I [112:33] realized I have three talents. I'm a [112:37] pretty good public speaker. [112:39] I know a lot about careers. [112:43] And I know a fair amount about social [112:45] media from having worked at Twitch and [112:47] been a Twitch streamer. I am certainly [112:49] not and by no means was anywhere near [112:52] the best Twitch streamer. I'm probably [112:54] nowhere near the best public speaker. [112:57] And while I'm a career expert at some [112:59] level, I may not even know the most [113:01] about careers, but when you intersect [113:03] those three things, I'm very near the [113:06] best. So I went and found the one poker [113:08] table where like no, I have very little [113:10] competition. So, what I would say to do [113:13] in that case is go find the place that [113:15] like fits you. Um, [113:19] because if you're that good and everyone [113:20] else is that good, go somewhere where [113:22] the competition is softer. Now, some [113:24] people are like, "Oo, I don't want to do [113:26] that. I want to win or I want to be at [113:27] the toughest place." Well, that's fine, [113:29] too. It's a lot of effort to stay, you [113:32] know, let's use sports as an analogy. [113:35] you want to play on the top team, [113:38] whether it's World Cup or whatever, [113:41] getting the benchwarmer spot on the top [113:44] team, is a lot harder than getting the [113:47] star spot on like the sixth team. And [113:51] that is a choice. The star on the sixth [113:54] team though probably makes more than the [113:55] benchwmer on the top team. So, it is [113:59] what do you want? If you want to say, "I [114:01] was part of the team that won the [114:02] championship," you might have to take [114:04] the benchwarmer spot. And if you want [114:07] the big paycheck, you might want to go [114:09] somewhere else. And those are both valid [114:10] choices. They're just choices. In the [114:13] hypothetical, I guess you are at the [114:16] poker table and everyone's playing [114:18] optimally. Does the way the people play [114:20] the game change? [114:23] >> It does in that [snorts] Well, it [114:26] changes. It changes in that nobody tries [114:30] simple moves anymore. Meaning the way [114:34] you might [114:36] bait someone or bluff someone who's [114:41] greener isn't going to work once you [114:43] recognize it's all stars. [114:46] It makes you more conservative in that [114:50] no [114:52] makes you more conservative in that [114:54] there aren't going to be any easy [114:56] shortcuts and any mistakes are going to [114:58] be caught and punished. So I think it [115:01] makes you play a lot more cautiously [115:04] because a mistake is at that table. If [115:09] you make a mistake you're done. [115:11] >> Darker hypothetical [115:13] >> darker. Here we go. Well, so we talked [115:16] about empire building before. It's [115:18] incentivized if you want to grow as as a [115:21] manager and you know my question to you [115:25] because you had so much success as a VP. [115:28] Did you do empire building? [115:30] >> Yeah. So I mentioned earlier the human [115:33] mind is great at rationalizing. I think [115:35] in hindsight I for sure did some empire [115:37] building but at the time you probably [115:40] don't tell yourself you're empire [115:41] building. What you tell yourself is with [115:43] all these people I could do so much [115:44] more. Right? You frame it as, man, I [115:47] have all these great ideas. We've got a [115:49] big backlog. If only I had 375 more [115:51] people. Imagine what we could do and [115:54] it's not your budget, so why not ask for [115:56] it? So, I got totally burned on this. [115:59] Um, when we were growing Amazon's app [116:01] store, we had launched the store and we [116:03] had our annual meeting with Bezos and we [116:05] said like, we've launched the store and [116:06] we took him this huge ask for all these [116:09] people. And I remember like what stands [116:13] out to me most is I think we had nobody [116:17] in marketing. We had no dedicated [116:19] marketers because we had started this [116:21] lean team. It was something absurd like [116:23] we need 25 marketing people and it was [116:28] going to be like this is not exactly [116:30] right but it's like we need five PR [116:32] people and we had these idea like oh [116:35] we're operating in five countries we [116:37] need one PR person per country. So, we [116:39] had some justification in our own minds, [116:42] but we were just asking for everything [116:44] under the sun. Like, well, if we had all [116:47] this, I'm sure we could do a lot and [116:49] wouldn't it be great? Well, Jeff tore [116:51] into us. He asked a couple questions [116:53] like, "What are these people going to [116:54] do?" And what are these people going to [116:55] do? What? No, what are they actually [116:56] going to do? And our answers fell apart [116:59] because we were just sort of like, "Wow, [117:01] they're going to do marketing. That's [117:02] why they're called marketing people. We [117:04] need, you know, we need more marketing [117:05] and 25 is a good number." And he he I [117:09] remember very distinctly he asked one [117:11] question, we gave a crappy answer and he [117:14] was like you could tell he's like [117:17] so then a second later he asked another [117:19] question and we gave another crappy [117:21] answer. And he's like okay I don't [117:25] believe any of your numbers for here on [117:26] I've asked you two questions. They were [117:28] both nonsense. I'm not gonna go through [117:31] everything else. I don't believe any of [117:32] it. Here's what you're gonna do. go back [117:35] and bring me a sheet where the maximum [117:39] size of any bucket of anything you're [117:41] asking for is two or three people and it [117:44] says exactly what they're going to do [117:46] and I will go through that line by line [117:49] and tell you what you can have and [117:52] that's what he did. We went away and [117:53] came back with this line by line and he [117:56] went through it and like two people for [117:58] PR. [118:00] I can believe you need some PR. No one. [118:03] And he just like literally with a red [118:06] pen with all of his direct leaders [118:09] watching. No, you know, three, none, [118:12] two, okay, both for that, but I want [118:15] this, this, and just took us over the [118:17] coals. He wasn't wrong. He was actually [118:21] right. I was relatively newer. One of my [118:24] managers was newer. We had gotten big [118:27] eyes because we'd launched the project [118:28] and thought like, well, let's see what [118:30] we can do with this. Like, it's a good [118:32] project. Let's see what they want to do. [118:33] And what we found out was not very much. [118:35] They want us to be lean. That was for [118:38] sure empire building. But I would say in [118:40] that case, it was driven out of laziness [118:43] as much as like this idea of I'll have a [118:45] huge team. Not that a huge team wasn't [118:47] also appealing, but we were just [118:49] daydreaming rather than thinking. [118:52] When people set out to really empire [118:54] build, they're either asking for people [118:57] and resources they don't really have any [118:59] use for or they're asking for stuff they [119:03] do need and what they're not doing is [119:05] worrying about what they're taking it [119:06] away from because the company only has [119:08] so many resources. So my job is to [119:11] advocate. The way I was successful [119:13] empire building later, if you want to [119:15] call it that, was coming up with new [119:18] ideas that the company wanted to invest [119:21] in. We're going to do this. Look at the [119:23] money. We're going to do this. Look at [119:24] the customers. We're going to do this. [119:27] Well, that's a lot of growth, Ethan. [119:28] Like another challenge. You can't hire [119:30] all those people. And I'd be like, okay, [119:32] here's what let's do. You hold a hundred [119:35] heads for me and release them in groups [119:37] of 20. And if I don't fill the first 20, [119:40] I don't get the second 20. I got really [119:42] good at filling heads and with good [119:44] people, by the way, not just filling [119:46] them. But I found ways to turn my heads [119:50] into performance, but then I was very [119:52] aggressive asking for more. Like, I've [119:55] done this much. I've built leaders who [119:56] can do it. I want this, I want that. [119:58] That was me being the I want guy. The [120:00] the here's my proposal. Here's my new [120:02] idea. Um, a story of empire building [120:06] sort of. [120:08] I ran the Amazon App Store team. We sold [120:11] apps. Our job was to build an app store [120:13] for the Kindle and for phones. [120:17] We had this idea. We were supposed to [120:18] compete with Google and Apple who own [120:20] their platforms. It was a very hard job. [120:23] And we were trying to figure out uh how [120:26] can we compete with Google and Apple? [120:28] What can we offer? They can't. And we [120:29] had this somewhat hairrained idea of [120:33] well, they can't ship physical goods. [120:35] We'll go to all the game makers and [120:36] offer to be their swag department. like [120:38] we'll make their t-shirts and their [120:40] coffee cups and whatever and we'll be [120:42] we'll tell them you should work with us [120:43] because we can help you with your merch. [120:46] So, we built this group called Merch by [120:48] Amazon and we started with printing [120:50] t-shirts. [120:52] Well, my leadership came to me and said, [120:55] "Why are you working on a t-shirt [120:56] printing project and you have people on [120:58] a t-shirt project from within the app [121:00] store?" I said, "Well, we have these [121:02] reasons." Well, the bottom line is [121:05] t-shirt printing didn't change the app [121:07] business, but Amazon now prints more [121:09] than a billion dollars of t-shirts a [121:11] year and we built a t-shirt business. [121:14] It was a matter of me fighting for it [121:16] and saying, "I have a theory and we have [121:18] the ability to do it and there's a [121:20] business model behind it." And then when [121:22] it turned out the business model, this [121:24] is the key. When it didn't work for what [121:26] I planned for, it was working to sell [121:29] like clever slogans and people's party [121:32] t-shirts and people's political [121:34] t-shirts. That was selling great. So, I [121:37] just pivoted right away and said, you [121:38] know, this isn't really about apps [121:39] anymore. It's about look at how many [121:41] t-shirts we can sell and how much money [121:43] we're making. And I just [121:46] and that became a new empire. Now, we [121:48] spun that off and it went elsewhere in [121:50] the company. [121:52] Part of empire building [121:55] in a good way is being good at turning [121:57] things into money and being willing to [121:59] be flexible. My theory of why to make [122:02] print t-shirts was a total failure. It's [122:05] going to make game makers prioritize [122:08] putting their apps on Amazon's app [122:09] store. They didn't care. They like merch [122:12] was such a small thing to them. wasn't. [122:14] But we found other money and so we just [122:17] used it for other money and we kept it. [122:20] Another thing I've done before is I've [122:22] gotten heads for a project, that project [122:23] has tanked. I don't go and say, "Oh, [122:26] that project tanked. You should take the [122:27] heads back." I'm like, "That project [122:28] tanked, but you know what? Great news. [122:31] I've put those heads on this thing [122:33] that's working and now it's going twice [122:34] as fast." So, you've got to always know [122:36] like where do you shift the resources [122:40] to where they're making money or [122:42] delivering results. And if you're doing [122:44] several things, if one thing fails, you [122:47] just immediately put them on the other [122:48] thing and do it twice as well. And they [122:51] don't take them away. I think it's [122:53] undeniable and this this doesn't look [122:56] good to me to say I was an empire [122:57] builder in ways. I the only defense I [123:00] have is I made it pay off for the [123:01] company to the goals the company wanted [123:04] andor in hard cold cash sometimes those [123:06] weren't the same. You know I've talked [123:08] about rationalization. I've rationalized [123:10] it to myself where I feel like I [123:12] delivered value. Some other people [123:14] looking at listening to this some of my [123:15] old peers will be like Ethan [123:17] you were just really slippery. [123:20] I hate that idea that they might think [123:21] that. I would say well I did deliver a [123:23] lot of value right? At least I made a [123:25] lot of money and you can't deny that. So [123:28] if you were empire building, is there [123:30] ever a case where they clawed back [123:32] headcount because maybe you didn't need [123:35] all of those headcount? And if so, how [123:37] do you defend against your headcount [123:40] getting, you know, clawed back? Amazon [123:43] didn't shrink much during the times I [123:45] was there. [123:46] So pure clawbacks, [123:50] I don't think I faced too many, but as I [123:52] described, [123:54] that's because I was playing offense [123:57] when something wasn't working, I was [123:59] upfront about it not working. And before [124:01] they could say, well, we could use those [124:03] elsewhere. I was talking about what I [124:05] had already done with them because they [124:06] were on my team. So I already had them [124:08] assigned to something else, something [124:09] more valuable. So they would have to [124:11] come and say like, no, no, you can't [124:14] move them to that. we have to take them [124:16] back off of that. I'm like, well, isn't [124:17] that important? Look at So, [124:20] I sort of prevented that by staying [124:23] ahead of it. I never left headcount open [124:26] at the end of the year because that was [124:27] their favorite thing to take back. [124:30] Amazon often did this thing where at the [124:34] beginning of the year, whatever, we'll [124:36] pick a random number that's too small, [124:38] but to illustrate, they would say, [124:41] "Okay, we have budget for a thousand [124:43] heads this year across the company. [124:46] We're going to let people open 1,500 and [124:49] we'll see who fills them, and we'll cut [124:51] it off when we get there." Well, I put a [124:54] lot of effort on hiring, so I I played [124:56] offense. My heads were all full before [124:59] the gate came down. And I did that year [125:01] after year. And other teams, [125:04] they would be like, "Oh, we were too [125:06] busy working and now it's November and [125:08] we haven't hired yet. What do you mean [125:09] we can't?" Sorry. What you're talking [125:12] about is any kind of resource [125:14] competition. You've got to think about [125:16] how do I seize those resources and make [125:18] my use of them something no one will [125:20] argue with or that it's too late to [125:22] argue with it. You know, there are some [125:25] things that like once the ship has left [125:27] the dock, it's gone. [125:29] I was very good at getting my ship out [125:32] to the ocean and by the time they're [125:34] like, "Hey, we uh we needed that ship." [125:37] You're like, "Well, I'll give it to you [125:38] when I get back." Like, it was too late. [125:41] And that that part of empire building, [125:43] like if you want to say for a place, I [125:45] was very maliciously empire building. I [125:48] knew that how headcount worked and I was [125:51] always the first to hire and fill my [125:54] team. So much that I taught a class on [125:56] how to hire quickly. [125:58] Um because I knew others wouldn't do it [126:02] and that was my way to get people. That [126:04] was in fact another argument I made was [126:08] they'd say, "Oh, we don't have any [126:09] headcount left to give this year." And [126:11] I'd say, "Well, isn't there a bunch of [126:12] other teams not filling their [126:13] headcount?" Tell you what, they're [126:15] probably not going to get to it. like [126:17] let me hire a little head and we you [126:19] know they're not going to get to it. And [126:21] I that was another story I told of like [126:23] hey across your whole org like all these [126:25] other teams are behind you have [126:27] headcount you can loan me that they're [126:29] not going to get to and that was just [126:31] literally me like taking other people's [126:33] heads but knowing I could get away with [126:35] it. [126:37] Now I put them to good use. Remember I [126:40] talked earlier about you have to be a [126:41] good performer. My teams were always at [126:43] least delivering their stuff. And so it [126:47] wasn't like they were going to look at [126:48] me like, "Why would we let you do [126:49] anything? Your shit's all broken." I [126:52] never had that accusation. I've shared [126:54] before though, I was very willing to [126:55] hack to get things out. And I probably [126:57] shipped some stuff that was too raw. [127:00] That was though, keep the speed moving, [127:03] keep in front, like don't get bogged [127:06] down in the perfect project. like get it [127:08] out there and show progress and then [127:10] iterate is better than oh but it's not [127:14] quite ready yet. I can't let it out yet. [127:15] That because if I can't see it, it's not [127:18] real. People could see my stuff and [127:19] they're like it's got warts and I'm like [127:21] yeah but it's there. It's different. As [127:24] opposed to your thing that you know if I [127:26] ever pulled to like shoot at somebody [127:27] else they'd be like yeah maybe their [127:29] project's perfect. You know they've been [127:30] telling us that for two years. Where is [127:32] it? [127:33] >> With all these changes with AI. I think [127:36] you could make a case that it's a boom [127:39] in some places, a bust in many places [127:42] and I know you have a lot of experience [127:43] across different companies and periods [127:46] in the tech industry. So, uh when you [127:49] look at today's landscape of tech [127:52] careers, what advice would you give [127:55] people in the uncertainty of potential [127:57] scenarios with all this AI stuff that's [128:00] happening? [128:01] I wish I had a perfect crystal ball with [128:03] AI because I'd make a fortune on Wall [128:05] Street. But I do think there are going [128:06] to be winners and losers and I do think [128:08] some types of jobs are going to get [128:10] eliminated. I think other types are [128:11] going to change. I think some will also [128:13] get created that we don't understand [128:15] yet. Um so what do you do to position [128:19] yourself for that? Well, I think breadth [128:21] of learning is more valuable than depth, [128:24] flexibility. And so, of course, I am a [128:27] fan, as we talked about, of develop your [128:29] soft skills because that's not a target [128:31] of AI at the moment. AI's strongest [128:35] target [128:36] is things that have rule sets, coding [128:40] languages, law, math, things that have [128:43] firm rules, it can be optimized around a [128:46] lot easier. You've said how many times [128:48] today regarding soft skills, well, it's [128:51] a gray area. That's where AI is going to [128:54] struggle because how to act like a human [128:57] at that level and how to convince people [129:00] and it doesn't have a body or a face and [129:02] it can't hug anyone or shake hands. It's [129:04] got a lot of limitations that in this [129:06] pure does the code run or not? Is this [129:08] contract viable or not? [129:11] So I think leaning into some of those [129:13] skills that require human presence [129:16] is a big tool, a big tactic. Um at the [129:22] same time you can't be AI ignorant or [129:24] resistant. You have to be aware of the [129:26] tools able to use them. [129:29] I think the people who are spending [129:32] absolutely every moment trying to stay [129:34] on top of AI only [129:38] may be I've called it like winning the [129:42] race off the cliff. [129:45] You're you will be the best person at [129:48] using the tools, but as those tools chip [129:51] away at what you do or obsolete what you [129:54] do, you'll be the last one kept around [129:56] to operate them until they don't need [129:58] you either. It's a kind of a pirick [130:00] victory. Now [130:03] again, there's at least two analogies [130:05] that get bandied around. You mentioned [130:08] engineers and coding in our opening. [130:13] We know that spreadsheets didn't [130:15] eliminate bankers or financial analysts. [130:17] They increased the demand. Financial [130:20] tools have increased the interest in [130:21] doing all kinds of weird financial [130:23] instruments and analysis. And so there [130:25] are more bankers, not less. Similarly, [130:28] it was thought like ATMs are going to [130:30] automatic teller machines are going to [130:32] eliminate bank tellers. Didn't happen. [130:36] There is an argument that these tools [130:40] are only going to increase the demand [130:42] for things. In other words, more people [130:44] have seen what code can do for them. [130:46] There's more people uh playing around [130:49] with vibe coding and they're going to [130:51] reach a point where they realize I [130:52] actually need a software engineer to [130:54] help me with this. So, it's going to [130:56] increase demand. I don't actually know [130:58] which of those wins. I'm sure that [131:00] sitting and pounding a keyboard the way [131:02] I grew up doing it is not going to be [131:05] the same. So, the jobs are going to [131:07] change. What do I advise having the best [131:10] eye you can on where is the value going? [131:14] What are people valuing? [131:16] What I think they're valuing more and [131:18] more now is [131:21] more people can produce more code or [131:23] more legal documents or whatever. Who's [131:25] deciding? Who's explaining those? who's [131:28] deciding what's needed, who's deciding [131:30] what to prioritize for release, who's [131:33] deciding what to tell customers. Uh, [131:35] let's say the engineers on Gmail can now [131:38] write 10 times as many features. [131:41] Well, we don't need 10 times as many [131:42] features. We we actually might need [131:44] less, fewer, that are better or [131:47] different. Who's deciding? That's that [131:50] whole taste or judgment. I think that's [131:53] going to be very highly prized. [131:56] And [131:57] I'd rather be in the judgment seat than [131:59] in the running the tools seat. [132:02] >> In the last few years, there's this [132:05] trend of flattening orgs or getting rid [132:08] of the the layers. And I wanted to ask [132:13] you in your experience, is that in the [132:16] tech industry, is that just something [132:18] that es and flows with the booms and the [132:21] bus or do you think that's a new [132:24] permanent way of of operating? The [132:26] delayering is a is a cyclical [132:30] um it's a cyclical pressure and it's a [132:33] cyclical pressure when companies are [132:35] very focused on headcount on keeping [132:38] headcount flat. Companies go through [132:40] periods of expansion and contraction or [132:43] or rationalizing. [132:46] And when they're trying to rationalize, [132:48] they're always trying to flatten because [132:50] there's this belief managers in the [132:52] middle don't do anything. And so, how do [132:54] we get rid of them? But I want to talk a [132:57] little bit about history. There was an [132:59] early dynasty in China that in 600 BC [133:04] implemented the first testing for civil [133:06] servants. And by 200 BC, this had [133:09] actually become like a formal process [133:10] with a written exam. So if you think of [133:13] administrators as basically the same as [133:15] managers, [133:17] we've been we've had manager layers [133:20] since like 600 BC to the point that they [133:23] were selecting them with tests. [133:26] I believe AI changes a lot of things. I [133:28] don't believe it changes human nature to [133:31] where there's no longer going to be this [133:34] idea that you need one person to [133:36] organize other people's work or to speak [133:38] for it or to centralize it. And so [133:42] I think it's cyclical. [133:45] I don't think it permanently changes. It [133:48] might be that AI tools [133:51] increase what is considered a team, like [133:54] how many people can be on a team because [133:56] the manager has automation helping them. [133:59] But I can just as easily argue that [134:02] because each individual on the team is [134:04] producing more and more decisions are [134:06] needed and more judgment is needed, more [134:08] communication about what's been done is [134:11] needed, that it increases the need for [134:15] people acting as managers. [134:18] Right now, this flattening idea, it's [134:21] got a couple of poster children like [134:22] Jensen Wong, who's got 60 direct [134:25] reports. [134:28] Is everyone Jensen? They're not. And by [134:31] the way, those 60 people, I coached some [134:33] people in his organization. They are [134:35] extremely senior. So, can one brilliant [134:39] guy lead 60 other brilliant people? [134:43] Yeah, maybe. Can I do it? Can you do it? [134:46] Can Can the average first level manager [134:48] scale from 10 engineers to a hundred and [134:50] still do a good job? [134:53] I doubt it. Right. I really doubt it. [134:55] So, I think it's cyclical. Predicting [134:57] that human nature is going to be [134:59] different is a really bad prediction [135:01] because it's been the same for so long. [135:05] And the idea that a tool is magically [135:08] going to make humans different, I'm [135:10] skeptical. [135:12] In the doomer AI case where there's less [135:16] technical roles, I think people might [135:18] worry about layoffs and those kinds of [135:21] things. what are the top ways that you [135:24] know to protect against against layoff [135:26] and also I'm curious to know how do you [135:30] avoid the negative optics? Yeah. So let [135:32] me address your second question first [135:33] which is the optics. I think right now [135:36] AIdriven layoffs or downsizing from big [135:39] companies is so common. You tell that [135:41] story. Exactly. You say look my my org [135:43] was eliminated. My whole org was [135:45] eliminated. That's a simple way of [135:47] saying it's nothing to do with me. And [135:50] that's so common now that [135:54] a recruiter isn't going to be like, "Oh, [135:57] you were at Google, but now you're" or [135:59] again, fill in the blank. Meta's done a [136:01] lot of layoffs. Amazon's done them. Uh, [136:03] all the big companies have [136:06] saying that you were laid off from one [136:07] of these big companies when your org was [136:09] closed down or significantly reduced no [136:12] longer has the tarnish it did. But the [136:15] rest of how you prevent that from [136:16] tarnishing you is you make it a quick [136:18] fact and you pivot. And so you say, [136:21] "Yeah, unfortunately my organization at [136:23] Meadow is eliminated." But the good news [136:26] is [136:27] fill in your story. That gives me a [136:30] chance to do something new. That [136:33] actually gives me a chance to bring the [136:34] meta philosophy or the meta insights on, [136:37] you know, whatever fill in the blank [136:39] again to to other companies. that gives [136:41] me a chance to bring Amazon's experience [136:43] with scale to to you. And so I'm [136:46] actually excited. You know, it sucks I [136:48] got laid off. I admit I wasn't looking [136:50] for that, but it's opened my eyes that [136:53] there's a chance to bring that to [136:54] someone else. And you change the topic [136:56] quickly to the future. So truth about [137:00] the past quick move on. Um now, how do [137:05] you avoid a layoff? First, sometimes you [137:07] can't. You know, if they whack a whole [137:08] org, you may be done. But even in most [137:12] layoffs, [137:14] I know [137:16] top managers or executives, they try to [137:18] place their key people in other orgs. [137:22] So I know a leader at Amazon was [137:26] shutting down a whole big org and she [137:29] had a list of like her top performers [137:31] and she was calling other leaders and [137:33] saying like make a space. You want to [137:35] make a space for this person? How do you [137:37] get on that list? The layoff key is the [137:40] decision is often not made by your [137:41] manager, it's made by your skip or a [137:43] couple levels up. So, you need some [137:45] visibility as a top performer. Top [137:48] ratings is one key. They'll look by [137:51] rating, but being known for an [137:53] accomplishment, something like that Matt [137:54] Round tool that I talked about earlier [137:57] or something, a tool with your name on [137:59] it, having a unique skill. We talked [138:01] about the keragin engineer that's the [138:03] only one who knows something. If you're [138:05] on, if you're the only one who knows [138:07] something that's still needed, I can cut [138:10] half of your org, but I have to keep you [138:12] because you're the only one who knows [138:13] this thing. Those are the different [138:15] techniques. And again, I'm mixing [138:18] technical knowledge, building tools, or [138:20] having unique [138:22] expertise with social engineering, being [138:25] known to the skip, skip, and whatever. [138:27] It's always every answer I give should [138:31] be a combination of [138:33] what I said be good and be likable. Both [138:36] are additive, maybe even multiplicative. [138:39] Yeah, we we talked a lot about the the [138:42] social engineering and kind of the the [138:44] negative and the the politics. I do want [138:46] to talk a little bit about the the [138:48] positive side of soft skills as well. [138:51] What is executive presence and how do [138:54] you develop it? Yeah. So, executive [138:57] presence is very hard to define because [139:00] it's something others decide about you. [139:01] They look at you and they either decide [139:03] you have it or you don't. And they're [139:05] combining a few things. So, what is [139:07] executive presence? Uh, I have two [139:09] definitions. One of them is from a book [139:11] and it's academic. And it says it's 60% [139:13] gravitas, which is like the weight of [139:15] your accomplishments, what you've done. [139:17] It's 30% communication skills, 10% [139:20] appearance. This is from a researcher [139:22] who has done all this work to figure it [139:23] out. I think it's a fine framework. The [139:26] other way I look at executive presence [139:28] is are people coming to you for your [139:31] opinion particularly on things that um [139:35] you may not directly be involved in like [139:38] are they coming and saying hey Ryan we'd [139:40] love to get your take on this because [139:42] you have really good insights or we'd [139:43] love to get your support on this because [139:45] we know people look up to you. That's [139:47] the other sign of presence is you're [139:49] being sought after even when it's not [139:51] directly your work. You're being valued. [139:55] Um [139:57] it's those two ways of looking at it [140:01] define executive presence. If you want [140:03] me to really boil it down to a phrase, [140:06] it is do you command respect in a room? [140:10] Do people like listen to you? Do they [140:13] look to you? Are they busy? This is a [140:16] little overly political, but are they [140:17] busy like uh reading your gestures? So, [140:22] if like you're talking and I pick up the [140:24] phone, are they like, "Oh, well, we can [140:26] ignore Ryan because Ethan is." That's [140:29] the sign of a lot of presence. when you [140:32] framed executive presence as people want [140:34] to know your opinion. I've seen that [140:36] where there may be someone who's a quiet [140:40] engineer, but they've been there a long [140:42] time and they know everything and [140:45] a lot of people go to them for their [140:47] opinion. [140:48] >> So, I I could see that being one path to [140:52] executive presence. I could also see a [140:54] case where it's not grounded in their [140:58] being objectively correct all the time. [141:00] something about the way they stand, the [141:03] way they speak, what they accept, what [141:07] they don't accept. And [141:09] >> it's that's a little harder to define. [141:11] >> I will tell you a story which is I speak [141:15] with tremendous confidence. And [141:18] sometimes [141:20] I can sound like the voice of God. Like [141:23] I can sound like I am declaring truth [141:26] from on the mountain. I have the [141:28] tablets. [141:29] And my wife who knows me very well, she [141:32] once told me, she said, "You know, [141:34] Ethan, I've learned that you sound like [141:38] you know." And so sometimes when I think [141:40] something different, I don't say [141:42] anything because you sound so sure. And [141:46] then it turns out you're wrong. And I'm [141:47] like, "Why didn't I say anything? I knew [141:49] we needed to turn right at the last [141:51] corner, but you said, "No, it's [141:53] straight." And you sounded like you knew [141:54] and I bought it. That's [141:58] my executive presence going too far, [142:01] right? Because I think it's straight, [142:02] but I don't know. But I'm saying, "Oh, [142:03] I'm sure it's straight." And she's [142:05] hearing, "I'm sure it's straight." [142:09] What are those traits? Well, some of [142:11] them are very superficial. The number [142:13] one and two are confidence and [142:15] decisiveness. Um, if you undermine [142:17] yourself and say, "Well, I think maybe [142:19] it's straight, people are definitely [142:20] going to challenge you." Whereas, if you [142:22] say, "It's straight. The next we don't [142:25] turn. It's it's two two lights then a [142:27] right. Very specific. Everybody's going [142:30] to buy it. One thing I do in my [142:32] executive presence class, I teach a [142:34] class on it, is I share the fact that [142:38] stats with numbers are 62% more [142:40] believable than stats without them. Now, [142:43] the truth is I just made that up. I've [142:45] never looked it up. But 62% sounds so [142:48] specific and I delivered it like, "Oh, [142:51] yeah. This is true." Maybe you bought [142:53] it. Probably you bought it. But a lot of [142:55] people listening were like really 62%. I [142:57] was just lying through my teeth or at [142:59] least embellishing, right? Um [143:04] specificity delivered with confidence, [143:07] speaking up quickly. The list of traits [143:10] are being tall and white. You don't have [143:13] to like it, but it's true. They're both [143:15] like if you look at presidential height, [143:17] if you look at how many white men we've [143:18] had as president, not just here. Go [143:20] around the world, go through history. [143:22] These are these are things, okay? Um, [143:25] doesn't mean they're good. It means [143:26] they're true. Deep voice. We respond [143:29] better to people with deep voices. Uh, [143:32] which is why when I do the voice of God, [143:33] I go even lower. Um, and so did all the [143:36] actors who've ever done God. So [143:38] apparently God's a baritone. Like you [143:40] never see a squeaky God. Another trick [143:43] is speaking slowly. [143:46] Usually pausing for emphasis makes you [143:50] seem confident [143:52] and gestures, body language when you [143:55] said all the things that aren't just [143:57] being a great engineer who knows all the [143:59] facts. [144:01] It's this feeling like your trustworthy [144:03] uncle. Like that's the picture, right? [144:06] The uncle who's like your dad's older [144:09] brother and runs a business. He's fun, [144:12] but he's really smart and he owns two [144:14] cars and has a beautiful wife and three [144:16] lovely children. It's exuding that [144:20] successful, [144:21] comfortable in every situation. Another [144:23] big factor is never getting flustered. [144:26] They're never out of control. They may [144:29] show anger, but it's always like this. [144:33] It's not this wild like screaming rage [144:36] and spit, you know, blowing spittle. [144:39] It's this lean in like how dare you [144:43] little one. And and so it's emotion [144:46] under control. It's, you know, if you [144:48] don't like it, I guess, or if you do [144:50] like it, it's all these ape dominance [144:51] tricks. Like what makes the top ape in [144:54] the tribe who gets the bananas? It's [144:56] just the human version of those brought [144:58] into a room. [145:00] This reminds me, there was that one CEO, [145:03] Elizabeth Holmes, and she was, I guess, [145:08] famous for her deepened voice when she [145:11] was speaking, [145:12] >> and there's there's recordings of her [145:15] not doing the CEO voice and it's [145:18] >> different. [145:18] >> Different. Yeah, it's different. So, I [145:20] guess she picked up on that and she's [145:23] trying to exude executive presence. [145:26] >> And she's not the only one. Um, Margaret [145:28] Thatcher, the historic, you know, the [145:30] prime minister in the UK back in the [145:32] 80s, I think she was the first female [145:34] prime minister. I may have that wrong, [145:36] but I think so. She early in her career [145:38] was accused in the media of screeching, [145:41] of being high pitch. She said that'll [145:43] never happen again. She systematically [145:45] trained herself to speak low and slow, [145:48] basically. And this again will bother [145:51] lots of people, took on a man's voice to [145:54] compete in a man's world. Now, this goes [145:57] down into that whole should thing again. [145:58] Should she have to do that? No. Did she [146:01] do that? Yes. Did it work for her and [146:03] Elizabeth Holmes? Yes. So, until our [146:08] world changes, [146:10] that's different. And and so, yeah, that [146:12] is one of the signs. The good news is [146:15] you can be successful and have high [146:17] executive presence without any one of [146:20] these given traits, but you're going to [146:21] have to have some of the others. So, [146:23] you're either going to have to be really [146:24] good at what you do. That's the [146:27] engineering viewpoint. The example I [146:29] always point to there is Warren Buffett. [146:32] Warren Buffett, no one that I know of [146:34] has ever said, "What a dramatic speaker. [146:38] What a showman." And yet, he commands [146:41] tremendous respect, tremendous executive [146:43] presence. That's your case of the [146:45] engineer who's the expert. It's because [146:48] he's Warren Buffett and his investment [146:50] track record. It's not any of these [146:52] other factors. We look at somebody else, [146:55] Steve Jobs or Elon Musk. They are both [146:59] showmen. They were very good. They may [147:01] have had great ideas, but they are icons [147:04] in our industry because they were also [147:07] very good at all the speaking [147:10] and presence. They controlled their [147:13] stage presence. [147:15] They did things in a very exacting way. [147:18] Well, it's interesting you mentioned the [147:20] Elon Musk one as an example of [147:23] showmanship because when I see a public [147:25] speech of Steve Jobs, it's very [147:30] >> polished. But yeah, when Elon speaks, it [147:32] it doesn't seem so much as showmanship. [147:36] What are those traits in him that you're [147:38] seeing that are [147:39] >> I think the showmanship in him uh that [147:42] works for him is he can deliver [147:44] relatively outrageous claims very 100% [147:49] conviction. He can make you believe that [147:53] at least he believes. So like if we look [147:55] at the recent SpaceX IPO, he's talking [147:58] about how he's going to build factories [147:59] in space. [148:02] Maybe like if you start really thinking [148:06] through all the things that would have [148:07] to be true to make it possible to like [148:09] build things at space and make it [148:11] useful, it's a very long list of [148:13] problems. But he says it with this total [148:17] conviction and like his [148:21] whether he says these words or not, he's [148:22] like, "Nobody thought we could do [148:24] electric cars. Check did that. Nobody [148:27] thought I could build a private rocket [148:29] company. Check did that." And I'm [148:31] telling you next is space factories. And [148:34] he just says it in a way that like it's [148:36] it's inevitable like the sun will come [148:38] up tomorrow, water is wet, and Elon Musk [148:41] will build factories in space. It's I [148:45] think his showmanship whether it's an [148:47] act or not is conveying utter conviction [148:52] of ideas that [148:54] are somewhere between incredibly cutting [148:57] edge and total fantasy [149:03] who what you think there depends on what [149:05] you think of Elon like is it [149:08] one or the other but he's able to like [149:11] get out in that space and make it [149:12] plausible because he's done stuff that [149:16] people didn't believe was possible. So [149:18] his essential pitch is you didn't [149:20] believe me before and you were wrong. [149:22] Are you going to dare to doubt me again? [149:26] >> Obviously, it's it's an asset if you're [149:27] liked and you should build relationships [149:30] at work. How do you actually go about [149:34] that? [149:35] >> I think networking there's a recipe to [149:37] do it. is very authentic, very [149:38] effective, and that's figure out some [149:42] stuff you love, stuff you're passionate [149:43] about, stuff you would like to share [149:45] with people, you're proud of, you're [149:46] interested in. Do those things or work [149:49] on those things and figure out just put [149:51] in a little extra effort to figure out [149:54] how can I give this to other people? How [149:56] can I make it available? How can I [149:57] package it as a tool? How can I give [150:00] away my advice, give a class, give a [150:02] talk? The key is to give. take what you [150:05] like doing and give it away because [150:08] there are other people who [150:11] don't like that thing or don't know [150:13] about it or want to know more and they [150:16] want your help with it. So, it does [150:18] require that you have some sort of [150:19] expertise, but it doesn't have to be [150:22] wild. It just has to be solid because [150:24] there's other people who aren't good at [150:26] that thing and if you can figure out how [150:28] to give away some value. So my first way [150:31] of doing this at Amazon was I mentioned [150:34] how I was really good at hiring. So I [150:37] started teaching a class to other [150:38] managers on how to hire really fast and [150:41] well. Then I started teaching some other [150:44] stuff and that led to my teaching. I and [150:47] I found other ways to give stuff away. [150:49] So, I started streaming on Twitch, [150:50] giving away advice, and I built an [150:52] audience. That's all network, but it was [150:55] all based on what could I give away. And [150:58] why was I willing to give away with it? [151:00] Give it away. I loved it and I was good [151:03] at it. It was fun for me. It wasn't [151:05] work. So, I often share a story. There [151:09] was a guy at Amazon [151:11] who liked to ski and he was an engineer, [151:15] I think, but he went to the local ski [151:17] slopes and he got their um bulk ski [151:20] tickets and he had a deal with him where [151:23] they would ship him tickets and he would [151:24] resell them internally so that people [151:27] could get a ski ticket for those hills [151:29] at the discount bulk price. Well, he [151:32] just basically did it because he liked [151:34] skiing, he liked helping people, and he [151:35] liked to get cheap tickets himself. So, [151:37] it was a way for him to get bulk [151:39] pricing. But through doing this, he made [151:42] hundreds of connections with people who [151:44] got discounts through him. It meant if [151:47] he ever needed anything, he had all [151:49] these people he knew or if he called up [151:50] a random person, there was a good chance [151:52] like, "Oh, you're the ski ticket guy. [151:54] Yeah, I'll help you out." Why do I give [151:56] this example? He wasn't sharing anything [151:58] technical. He wasn't doing anything he [152:00] didn't want to do or even that he didn't [152:02] benefit from, but it built a network. [152:06] And everyone can find some way to do [152:08] that, to share something they're [152:10] interested in or love or don't mind [152:11] doing that they're really good at. It's [152:15] easy and fun for them or at least not [152:16] too hard and other people appreciate it. [152:19] What most people think of when they [152:20] think of networking is we're all [152:22] standing in some room for some random [152:24] purpose and I have a cocktail and I have [152:26] to go talk to people I don't know and be [152:29] like, "Hi, I'm Ethan. Why are you here? [152:32] Let's find something in common so you [152:34] give a shit." And that that's an [152:37] introvert's nightmare. And I get it. And [152:41] it's hard to build a relationship where [152:43] there's no [152:45] uh shared interest. What works about the [152:49] skiing example or anything else is the [152:51] one guy liked to ski? Well, the people [152:52] who were getting the tickets also liked [152:54] to skis. They immediately had something [152:55] in common. Oh, are you going this [152:57] weekend? How was the snow? Conversation [152:59] is easy. And then once you like have [153:01] talked a little bit, it's easy to go [153:03] deeper. Um, [153:06] that's how you build a network [153:09] naturally, organically. [153:11] Every engineer has some piece of [153:14] technology that they know more about [153:17] than the average engineer and that [153:19] they're excited to talk about. [153:22] Talk about it. You can talk about it in [153:24] recordings. You can talk about it in [153:25] forums, on Reddit, it doesn't matter [153:27] where. Share value. [153:30] >> I like this version of networking, but [153:32] of course I got to ask the dark version. [153:34] [laughter] [153:34] >> Of course you do. which is I stumbled [153:38] upon this post and it is the the basic [153:41] principles of politics and it was saying [153:45] step one be aware of who's powerful and [153:48] who's not. Step two, help the powerful [153:51] people as best you can. Yeah. Step [153:54] three, make sure they know that you're [153:56] helping them. So, this is a little bit [153:58] of a darker, more mchavelian [154:01] framing of networking. [154:04] A lot of people, let's say they're going [154:06] for a promo, they want to think, okay, [154:07] how do I make that VP that's making that [154:10] decision like me? Is there a way to do [154:13] it organically that you would recommend? [154:17] There are ways. Uh, let me give you a [154:20] few. First, let's take this VP. You can [154:23] take a couple shots like, hey, I've [154:25] built this thing where I get bulk ski [154:27] tickets. I don't know if you go skiing, [154:29] but if you do, I went like 375 people [154:32] around the company are using it. Is it [154:34] something you'd want to use? That's one [154:37] way. It like talks about something [154:38] you've done and maybe you'll get lucky [154:40] and they're like, "Oh yeah, I ski. How [154:42] do I get some tickets?" That's one way. [154:44] Same thing with if you've built a tool [154:47] or you're sharing your expertise, you [154:49] can be like, "Hey, I built this [154:51] interview tool or fill in the blank what [154:52] you did. I don't know if it's of use to [154:55] you, but a lot of people in your org are [154:57] using it, so I thought you'd want to [154:58] know it existed. And that's just a way [155:00] of like dropping in like you may or may [155:03] not directly value what I do, but I've [155:05] got a line on a bunch of your people. [155:07] And the really like in your dark world, [155:10] powerful people always want to know like [155:13] who's influencing my people. They like, [155:16] oh, you've attracted attention from a [155:18] third of my people. I better like know [155:20] you and keep an eye on you. And that [155:22] keep an eye can be like I got to watch [155:25] you, but it can also be like maybe [155:27] there's a way to use you. And so that's [155:29] a door in. But the other door is if you [155:32] built a network, someone in your network [155:35] knows that person. And so what you do is [155:38] you go to one of their direct reports or [155:40] whatever and say, "Hey, I really would [155:42] like to get to know our VP. I haven't [155:44] figured out. We don't have any, you [155:46] know, common interest I can figure out. [155:48] You know them. would you be willing to [155:50] put in a good word for me or suggest [155:53] that they do a skip level with me or you [155:56] know like can you help me get in front [155:58] of them? And because you've built a [156:00] relationship with the person in your [156:01] network and you've helped them out with [156:03] ski tickets or whatever, they're like, [156:05] "Yeah, I can help you out. Let me think [156:06] about that." So, I'll give you the [156:08] dumbest example that blows my mind. I do [156:11] charity work for Ukrainian refugees that [156:14] were driven out of Ukraine by the war [156:16] and they're in Poland. And early in the [156:19] war, I wanted to get a bunch of [156:20] suitcases of medical supplies and other [156:22] gear shipped from the US to Poland free [156:28] on a United Airlines flight. So, I went [156:31] out to my network. It's a very [156:33] empathetic story, so I had that to my [156:36] advantage. I said, "Oh, I want to get [156:37] medical supplies to Ukraine, and I need [156:40] somebody who knows people in United [156:42] Airlines that can help me get 10 [156:44] suitcases sent for free on this flight." [156:47] I was thinking, who knows what'll [156:49] happen. I get an email back from someone [156:51] in my network who says,"I know the [156:54] chairman of the board for United. I'm [156:57] going to connect you to him in email." [156:59] Now, this is using a sledgehammer to [157:01] kill an ant. But I get this email a [157:04] little bit later. I get put on email [157:06] with this guy, chairman of the board for [157:09] United, who's like, "Hey, I hear you [157:10] want to, you know, you're trying to help [157:12] some people displaced by the war. What [157:14] do you need?" And I wrote him an honest [157:16] note being an executive. I'm like, [157:17] "Dude, this is such a waste of your [157:19] time. Just delegate me to someone. [157:21] Here's what I need." And he was like, [157:23] "It's cool. I like to help people." [157:27] Well, all the bags went on the airplane [157:29] for free, but when the guy who was [157:31] flying with them got went to drop them [157:32] off, like the whole team from United met [157:35] him with like a gift basket, which is [157:38] just stupid overkill. The point I'm [157:42] making though is I had built a network [157:44] and then I needed something random [157:48] and I didn't even ask a specific person. [157:50] I just put out there into the world. I [157:53] need help reaching someone in power at [157:55] United. And I ended up with the chairman [157:57] of their board. [157:59] I could tell three more stories that are [158:02] almost the same level of like I reached [158:04] out for help and I got this like [158:07] overkill god help. You go through an [158:10] intermediary who wants to help you. [158:12] Here's the key. I'll give everyone a [158:14] key. Helping people makes you feel good. [158:18] So, when someone in your network asks [158:20] for a favor, if it's a favor you can [158:23] grant easily, [158:25] you get to feel so good and it didn't [158:28] cost you anything. So, like let's jump [158:30] to the situation of the guy who [158:32] introduced me to the chairman. For him, [158:35] he gets this note. He sees it on [158:36] LinkedIn. He's like, "Oh, I like he [158:39] needs help. He's doing something good. [158:42] He's helping refugees." Wow, that's [158:45] really good. If I help him do that, that [158:47] means I'm really good and I know the [158:50] chairman and he's going to go along with [158:53] it. Wow. All I got to do is send an [158:56] email and I look like a the tooth fairy. [158:59] Now, if my friend is listening to this, [159:01] I'm not saying your motivations were [159:03] that base [159:05] because it's legit to be like, "Oh, [159:06] refugees, I want to help them and I [159:08] can." So, it wasn't like he was like, [159:09] "Oh, I get to feel good." But believe [159:11] me, I'm sure he did feel good. [159:15] And that's a great feeling. So, the [159:17] reason networking works is you're [159:19] finding someone and giving them a way to [159:21] feel really good and magnanimous. And we [159:24] all love to be able to pat ourselves on [159:26] the back about what great friends we [159:28] are. [159:29] I'm just opening the door if you'd have [159:31] a chance to do that. [159:33] >> When you were a VP at Amazon, did you [159:35] have people coming up to you and clearly [159:39] there was an ulterior motive and they [159:41] were trying to I guess you quotequote [159:43] network? What' you what' you feel in [159:45] those cases? What' you do in [laughter] [159:46] those cases? [159:48] >> So, I've already shown you I'm very [159:50] blunt. I had like engineers three levels [159:53] below me or four levels, you know, I had [159:55] big organizations. So way down the org, [159:57] they'd come to me and be like, "Hey, can [159:58] you mentor me or can I have a one a [160:01] monthly one-on-one with you?" And I'd be [160:03] like, [160:04] "So, I have absolutely no time for this. [160:07] I have no time to put you on my [160:08] calendar, but here's the deal. I'm going [160:10] to give you one meeting. You're going to [160:12] bring me something really interesting I [160:13] don't know, and you're going to bring me [160:15] value in that meeting. And if you do, [160:17] we'll have another one. That's your [160:18] shot. Go do it." That's And if they [160:21] wanted something, I would just tell them [160:23] like, "What's the price?" Like I've said [160:26] bring value okay [160:29] I will do what you want surprisingly I [160:31] will say yes but what are you going to [160:33] show me like make it interesting and [160:37] that was actually my challenge to them [160:38] often which is my job's kind of boring [160:41] it's a lot of meetings it's a lot of [160:42] pushing paper around bring me something [160:45] interesting if you can keep my interest [160:47] we'll keep meeting as soon as you become [160:48] boring well it was more of a chance than [160:51] sorry I'm too busy [160:54] Right. So, uh, and a lot of some some [160:57] people were good at and some of them [160:58] never came back and I'm okay with that. [161:01] >> Most people I feel like are not as [161:03] direct with their incentives. And so, in [161:06] those cases, how do you find the things [161:09] that people want or what their goals [161:11] are, how you can help them in a way [161:13] that, you know, can make some win-win [161:15] interpersonal dynamics? So I think you [161:18] want to build a trusting relationship so [161:20] you can have more of that talk even if [161:22] you can't use his blendal language. But [161:25] before you do that or as you do that I [161:28] think there are four ways to kind of [161:30] figure out what people want. One is to [161:33] directly ask them. We've kind of talked [161:34] about that. The second is listen to what [161:37] they're saying. What are they talking [161:38] about in their all hands? What are they [161:40] talking about in the staff meeting? [161:42] Whatever. What are they saying? Are the [161:44] problems? What are they saying are the [161:45] goals? because those are they're talking [161:47] about the things they want and don't [161:49] want. The third way is [161:53] ask their direct reports. Ask ask others [161:57] in the organization who know them or [161:59] have a relationship with them. This is [162:01] called triangulation. Rather than ask [162:03] them directly, you go out and you c you [162:05] know you cross over and you see what [162:06] this person says they think they want [162:08] this person, this person and you figure [162:10] out okay, what are they um what are they [162:14] telling others? even if it's only little [162:16] bits or what are others inferring so you [162:18] triangulate. The last way is observing [162:20] them. Actions speak louder than words. [162:22] Where are they putting their money? [162:23] Where are they putting their time? Where [162:25] are they hiring? Where where are they [162:27] spending their time in meetings? Their [162:29] actions are going to show what matters [162:31] to them. So four ways, ask [162:35] um what? Ask, listen, triangulate, [162:38] observe. Those are the four ways to [162:41] figure out what they want. And then more [162:44] or less those are the same paths to [162:46] start going at them and and adding [162:49] value. you start moving towards the [162:52] things they value and then finding ways [162:57] to come to their attention or or whether [162:59] you send it up through friends or you [163:01] send it up through a status report or [163:04] you know when you bump into the hallway, [163:07] you find different ways to showcase that [163:09] you're working on the things they value [163:11] and asking how you can help. And [163:15] again, [163:17] this is less direct than the [163:20] Ethan, let's make a deal kind of way. [163:24] And some people are even bothered by [163:25] that idea. They say, "Let's make a [163:27] deal." That door was open to everyone. [163:29] Make a deal with me where you deliver [163:31] more value and I will find a way to help [163:32] you move you up. Like that's a fair [163:34] deal. It is the corporate deal. The more [163:36] valuable you are, the more I can pay [163:37] you. So bring more value, I'll give more [163:40] value. Fair deal. [163:43] And therefore, I don't think deal making [163:44] is bad. It's just explicit. [163:47] But for the people who aren't so [163:51] transparent or transactional, they do [163:54] still have all the same goals and [163:55] motives at some level, which is [163:56] progress, [163:58] you just have to find a way to do it in [164:00] their style. And their style is less [164:04] explicit, more implicit. You're going to [164:06] have to tolerate more ambiguity because [164:09] if you'd like to have that clear [164:10] statement of you do these three things [164:11] and I will do my best to get you [164:13] promoted next cycle, you're not going to [164:15] get that from them. You're going to have [164:16] to be like, "Well, I can see who they're [164:18] promoting and what they're valuing. I'm [164:19] going to do those things and trust." [164:21] You're going to have to weather more [164:23] ambiguity. I have found that if you [164:26] build a relationship with people, [164:29] most people, [164:32] they may never be willing to be [164:33] transactional or explicit with everyone, [164:37] but they will do it with you inside the [164:39] confines of that built personal [164:42] relationship. When I was working at [164:44] Meta, when someone's underperforming and [164:47] then they get managed out, it's it's [164:49] more clear even if no one says anything. [164:51] But there were cases where someone came [164:54] to work on Friday and then on Monday [164:56] they were gone and there was no clear [165:00] evidence of why they would disappear. So [165:02] in those cases, it felt like there was [165:05] some secret HR thing that had happened. [165:09] And at the time I was just a software [165:11] engineer and I just thought okay I don't [165:14] know what just happened to that person [165:15] but they're gone and it was not [165:17] performance because I had worked with [165:18] them and as a VP I imagine you you knew [165:22] a lot of the things that happened and so [165:24] in those cases where people just [165:26] disappear suddenly what what is it that [165:29] goes on behind the scenes at the HR [165:32] team? Well, I mean, a lot of those [165:35] so-called disappearances, [165:38] they're the case where someone did [165:40] something, frankly, that put the company [165:42] at some kind of risk. So, they're [165:45] usually the bad things. [165:48] Racism, theft, embezzlement, sexual [165:50] harassment. I will tell a story. I know [165:53] someone. They had a strong political [165:55] opinion on a topic and the company was [165:58] doing something they saw as inconsistent [166:00] with that and they leaked an internal [166:02] memo to a reporter and then they got [166:05] caught. uh they didn't think enough [166:07] about how the company's IT systems [166:10] worked and they left a paper trail and [166:12] after the news report came out that [166:13] obviously the reporter had had access to [166:17] information [166:19] um you know the company tracked it back [166:21] down to them and they were gone. I [166:27] actually now that I think about it I saw [166:29] several people fired for leaks. [166:32] So, a case that you might not think of [166:35] that gets people broomed that isn't like [166:39] interpersonally gross, like a sexual [166:41] harassment thing, is stuff like that. [166:44] Leaks, sharing competitive information. [166:47] Sometimes they're just dumb. Another [166:49] story I tell, we didn't end up firing [166:51] this guy, but we very easily could have, [166:53] and no one would have blinked. At one [166:55] point, I ran a video game team, and that [166:57] team made violent shooter games. One of [167:00] our artists one day brought in his [167:02] actual real firearm collection, spread [167:05] it all over his desk and like when other [167:07] people walked in, his desk was covered [167:09] with guns. He was totally innocent. He [167:12] was making up new weapons and he wanted [167:14] his guns as models and inspiration and [167:16] it never clicked with him like how [167:18] having a desk full of guns in a [167:20] California office might like wig some [167:23] people out. Now, if we'd have just been [167:26] like, "Guns in the office, done," nobody [167:30] would have said a thing. We figured out [167:32] like, "Okay, there's a difference [167:34] between thoughtless and actually [167:36] planning on murdering your teammates." [167:38] So, we're just going to send you home [167:41] with all your stuff and tell you, [167:42] "Please never do that again." [167:45] But that could have been like gone. So, [167:47] people make the dumbest [167:50] the stuff that happens. [167:53] You would never believe. [167:55] One time I had uh I came back to my [167:58] office from a business trip to visit [168:00] another office. My female executive [168:03] assistant and one of my female employees [168:05] greeted me at the office door and said, [168:08] "We got to tell you what happened while [168:09] you were gone." And like every alarm [168:12] bell for a manager at this point is [168:14] going off. It's we're, you know, it's [168:17] Amazon, so it's mostly male. I have a [168:19] female leader in my EA who are both [168:21] women saying, "They have to tell me what [168:23] happened. I know it's going to be bad." [168:26] Well, what had actually happened was so [168:28] unbelievable. [168:30] What had happened was my employee came [168:33] in, the the leader, and found a pile. We [168:37] had dogs in our office. We had pet [168:39] policy, right? You could have dogs. She [168:40] found a pile of poo under her desk, and [168:42] she's like, "Oo, gross." So she calls, [168:45] you know, the building maintenance like, [168:46] "Uh, dog had an accident." The woman [168:48] gets there to clean it up and says, [168:50] "This is not dog poo." So they call [168:53] security like, "There's human poop under [168:56] the desk." Oh [laughter] god. And so [168:58] security is pretty smart. They ask her [169:00] like, "Has anybody been showing unusual [169:03] attention in you?" You know, blah blah [169:05] blah. And she's like, "Well, you know, [169:08] now that you mention it, there's this [169:10] one janitor and he seems to hang out and [169:12] whatever." So, they go grab this janitor [169:15] and they quiz him like security does. [169:17] Well, he cops to it and this was his way [169:20] of like showing [169:23] obviously he was not normal the way we [169:26] was his way of showing interest was he [169:28] had [169:30] but when I say you wouldn't believe what [169:33] goes on of course he was fired and given [169:35] a restraining order to go with it like [169:37] you can't come near the building again [169:39] or her [169:41] but [169:43] when I say you wouldn't believe because [169:45] when I tell these stories people [169:46] bringing guns runs in like, "Oh yeah, [169:48] it'll be fine if I just spread them out [169:49] all over my cube or I'm going to like [169:53] show my affection or interest by." [169:57] You wonder what were they thinking? And [169:59] the answer is they weren't thinking in a [170:01] normal way. People both do things that [170:03] are unethical and they're very [170:05] intentional, but they also do some stuff [170:07] that later you're just like, "Wow." [170:10] So that's why those people disappear. [170:13] We've talked about gray areas all [170:15] throughout this conversation and you [170:18] mentioned this situ I think you said it [170:20] was like Joe Blow that gets the the F or [170:24] whatever and this other person gets the [170:26] the A. [170:28] >> There's this implicit framing of one [170:31] person's going to get ahead and one [170:32] person's going to get put behind. And so [170:35] in your career, you were there ever [170:38] cases where you had to burn someone to [170:41] get ahead? [170:43] >> I would love to say no to that. I'm [170:45] cautious to say no because of [170:47] rationalization. [170:49] Um [170:50] there are definitely places where I [170:52] competed with people. There were [170:53] definitely places where I was trying to [170:55] make sure I look better than others. I'd [170:58] like to say that was always me doing [171:00] superior work. Is there ever a case [171:03] where I like targeted someone to burn [171:07] them down? [171:09] I don't think so. I think there were [171:11] definitely places where I did everything [171:13] I could to make sure I came out ahead. I [171:17] think one of the cases I feel worst [171:18] about wasn't anything I explicitly [171:23] did to someone on purpose. [171:26] But when I first joined Amazon, [171:29] and when I mean first, I mean the first [171:31] week, [171:32] I had been hired without being told what [171:34] my job would be. It was a secret project [171:36] and all they would tell me was like the [171:38] general area, but I couldn't know what [171:39] the project was and I had to accept. So [171:41] I got there and I went to my boss and I [171:43] said, "Hey, I'm here now. What the hell [171:44] am I doing?" and he said, "Well, we have [171:47] two jobs open. One of them is building [171:50] our next video product, our first video [171:54] product, and the other one is building [171:56] the ingestion systems that will be used [171:59] to ingest the video and also will [172:02] support our music project and our books [172:05] project, what became Kindle. [172:08] Which one do you want?" Well, I'm an end [172:10] I'm an enduser guy, so I'm like, I want [172:13] to build the end user thing. I'm not an [172:14] infrastructure person. I want to build [172:16] the video product. He's like, great, [172:18] done. What? I had no idea. Another [172:21] manager started the next Monday and they [172:24] had apparently told him he could build [172:26] video and he got the infrastructure [172:29] project. He like he joined for the job I [172:33] had asked for. I had no idea, but I [172:35] absolutely the result of my action was [172:37] he got put in a job he didn't want. And [172:39] I think it sucked for him. That's the [172:42] closest I can think of to where [172:44] something I did really screwed someone [172:46] else in a in like that lasted you that [172:49] was like his job for the next two years. [172:51] Now the other thing if I had been told [172:56] well there's two people I would have [172:59] still fought for that job. I'd have [173:01] still said like can't I have it? I'm [173:04] good at that. I have history in that. [173:05] Like why didn't you pick me? [173:08] So I would have still fought for it. Um, [173:11] but it would have been because I wanted [173:13] that job, not to screw him, but it had [173:17] that side effect even though I didn't [173:18] know in that case. But I would have [173:20] pushed for it, sure, because I want to [173:22] do what I want to do, just like [173:23] everybody else. When we make these [173:26] videos, it's very polarizing because [173:27] there's a big group of people who say, [173:30] "Thank you for saying it as it is. This [173:32] is so helpful, and I'm going to be aware [173:35] of this and use some of these tips in [173:36] their career, and this is how the game [173:38] works." And then there's a group of [173:40] people that don't engage with the [173:41] content fully. They just hear something [173:43] that they don't like on a moral level [173:47] almost. They hear, "Oh, how could you [173:49] think that? How could you say that?" [173:51] >> And what would you say to those people [173:54] that say the premise of all of this [173:57] stuff, the premise of the game is [173:59] distasteful. It's not something they [174:01] even want to believe, for instance. [174:03] >> Yeah. So, I have a good friend who takes [174:05] exactly that viewpoint and we argue all [174:07] the time. Um, and the premise is this [174:13] game sucks and no one should have to [174:15] play it. And the fact you're talking [174:16] about how to play it means you've [174:18] already bought into the evil side. Um, [174:21] what I would say is this game is real [174:25] and I wish it wasn't real in some ways. [174:27] I wish we could all be judged on our [174:29] intentions and on our merit and we were [174:32] all seen, [174:34] you know, we all had unlimited [174:35] opportunity and we were all rewarded for [174:37] what we really did. [174:40] I wish those things were true, but I [174:42] don't know how to make them true. So, [174:44] what I say is I try to make them as true [174:47] as possible for people working with me [174:50] and around me. That's why I'm so [174:51] transparent, not only with you, I was [174:54] pretty transparent at Amazon. And I made [174:57] deals and I did everything I could to [174:59] keep them. [175:01] And I've been honest about I still [175:03] regret 20 years later this one guy I let [175:05] down. It still bothers me. But [175:10] humans human society is full of nasty [175:13] people and it's also full of limited [175:14] resources and competition. And I think [175:17] this is reality. And so I get that all [175:22] the time. I hear people are bothered by [175:24] the reality and they want me to make the [175:27] world just. [175:29] I don't know how to do that. I know how [175:31] to work towards it, but that's going to [175:33] take well beyond my life or your life. [175:36] And we see that because if we look at [175:38] all the nasty things that happened in [175:39] history like slavery or oppression or [175:42] you know uh uh limitations on women's [175:46] rights. [175:48] I dismiss none of those, but they've [175:50] been ongoing battles for a century or [175:52] more. They're not going to be solved [175:53] this year or next year. So I coach women [175:56] all the time how to get ahead in a [175:58] biased world. Does that mean I support [176:00] bias against women? Absolutely not. But [176:03] I can't fix that this year. And those [176:05] people have to try and move their career [176:07] ahead this year. So what I would say to [176:09] the people who dislike it is I am trying [176:11] to deal with what's going to happen this [176:14] year while also working on rights. I [176:18] think people can throw stones at me, but [176:20] when I talk about like I started a [176:23] charity in Poland to help refugees from [176:25] Ukraine, it's not like I don't believe [176:27] in causes and I'm not willing to tilt [176:29] against windmills and try and write [176:30] injustice. [176:32] That's my particular cause. You may wish [176:35] I worked on your particular cause. But [176:37] if you just objectively say, does this [176:39] guy try and do good? I do. But I also [176:43] have to deal with what is reality today [176:46] moral situation. [176:48] I I made a friend who's Ukrainian. Her [176:51] husband voluntarily joined the army in [176:54] Ukraine. He served two years. He wanted [176:57] to get out after two years of volunteer. [176:59] Ukrainians need soldiers. They wouldn't [177:02] let him out. He was going to be sent to [177:04] the front in a place where he would [177:05] likely die. [177:07] We knew [177:09] that he could be bribed out of the army [177:11] and it was relatively little money. It's [177:13] about $1,000. So, a friend of mine and I [177:16] gave his wife $1,000 and she went in and [177:18] bribed her husband out of the Ukrainian [177:20] army. Probably some other dude we don't [177:23] know died in his place. So, American [177:27] wealth because we knew this woman saved [177:29] this guy's life, killed this other guy. [177:32] It's very real and I am completely okay [177:34] with it because I know her and she's my [177:36] friend. I didn't want to kill the other [177:37] guy. Maybe I didn't. I get to have [177:39] plausible deniability. Maybe it's all [177:41] happy nobody died. But [177:46] I deal in that reality. She was [177:48] important to me and I could help her. He [177:51] had served some time. He had done some [177:52] duty for his country. I was okay letting [177:54] him out. [177:56] Right decision or not, I don't know. [177:58] Like me or don't, I'm okay with my [178:01] decision. [178:03] Same thing as all the corporate [178:04] politics. [178:06] I teach people how to deal with the [178:08] world that is. The world that is was [178:11] he'd serve some time and probably he was [178:14] going to die and this woman I cared [178:15] about was going to be hurt and it was [178:18] going to cost me relatively no money to [178:20] save his life. I was okay with that. [178:24] There are 50 ways you can say that was [178:26] an evil decision of mine. There are also [178:29] 50 ways you can say, "Wow, [178:32] you did something remarkable for that [178:34] woman and you're trying to help other [178:35] people there." [178:38] So, here's the thing I think about some [178:40] of the critics. They have an ideal in [178:43] mind. It's a great ideal. I support [178:46] their ideal, but [178:49] you got to understand, it's an ideal [178:50] that we're far from. And just because I [178:54] deal with reality today does not mean I [178:57] think your ideal is wrong. I'm just [178:59] trying to also live today and help other [179:02] people do that. [179:03] >> I pulled people on Instagram and one [179:06] common question people were asking is uh [179:09] do you have any book recommendations on [179:12] you know power dynamics or people or you [179:15] know these kinds of uh topics that we we [179:18] discuss that you'd recommend to people? [179:20] I have several. Um, so my all-time [179:23] favorite book on this has uh is called [179:26] Leadership and Self-Deception by the [179:27] Arbinger Institute. It's a book that [179:30] explains uh how we sometimes treat other [179:33] people as objects without meaning to. [179:35] But if we objectify people, which means [179:37] we treat them as a roadblock, like a we [179:39] treat them as an API, how do I press the [179:41] right buttons to get the response I [179:42] want? That doesn't usually get a good [179:44] reaction because they feel manipulated. [179:48] It's but if you treat them as a human [179:50] and like hey I know this is hard for [179:52] you. I know you're busy. You know, how [179:54] can we make this work? Here's what I [179:55] need. And with warmth, they're more [179:58] willing to help because people seen as [180:00] humans will treat you back as a human. [180:02] That's that book. Second book is Chris [180:04] Voss, Never Split the Difference. That's [180:07] all about negotiation [180:08] and about understanding [180:11] how human motivation works. All of this [180:14] is human psychology. So, all of these [180:16] things are human psychology. [180:18] Um, the third book, even though I hate [180:21] to recommend it for all your interest in [180:23] dark side, is that 48 laws of power, [180:26] it's a very thorough catalog of the dark [180:29] ways people think and manipulative [180:31] tricks. You can either become that [180:34] person who manipulates or you can at [180:36] least become aware of how psychology can [180:39] be pulled on and see some of it and it [180:42] will open your eyes for better or worse. [180:46] In video gaming, there's this premise of [180:48] speed running. And this is basically [180:51] trying to get through a game, okay? As [180:53] quickly as possible. [180:53] >> I worked at Twitch. I know speed [180:55] running, [180:56] >> right? [180:57] >> Okay. So, imagine you're playing the [180:59] game speed running, you know, any [181:02] percent. You're trying to just get to a [181:04] VP level and you start at the beginning [181:07] at Amazon. What would you do? What might [181:10] you change today? [181:11] >> Yeah. So first thing is I would not be [181:14] planning on getting a VP at Amazon. [181:15] That's not going to be a speedrun at [181:17] this point. And the reason is the [181:19] company's not growing the way it was. It [181:21] grew while I was there grew a hundfold. [181:24] That meant endless opportunity. It's not [181:27] true anymore because it's not got the [181:29] growth. So what I would do if I was at [181:31] Amazon today is I would say how can I [181:33] suck as much information and technique [181:35] out of this company in 18 to 24 months [181:38] to get more skilled and then I'm going [181:41] to have to go somewhere that's high [181:42] growth. And so I'm going to try to [181:44] become an expert in a skill that will [181:46] get me bought externally which probably [181:49] means AWS. It could mean a few other [181:51] things, but I'm going to try and become [181:54] enough of an AWS expert that someone who [181:57] needs AWS knowledge will hire me in at a [181:59] higher level in a high growth place. And [182:02] then I'm going to go find a high [182:03] [snorts] growth place that wants to use [182:05] cloud computing, hopefully the stuff [182:07] I've been working on, and I'm going to [182:08] pitch to them. Bring me in, and I'm [182:12] going to be your solution to adopting to [182:15] like adopting this fast, well, and [182:17] cheaply. Then I'm going to deliver on [182:20] that and talk to them about, okay, how [182:22] do I move? That's where I'm then going [182:23] to run this. How do I move up? I want to [182:25] grow in this way. I want to lead. Now, [182:28] the next thing you're going to need to [182:29] do is speedrun. You're going to need [182:30] some management skill if you want to be [182:32] a VP. You've got to be good at the job. [182:34] You're not trained in that. So, you're [182:36] going to have to start studying the [182:37] psychology, the organization, the risk [182:40] takingaking, the decision makingaking. [182:42] The next thing I will say is favor [182:45] gambling. favor taking risks. You'll [182:48] probably move up faster by shooting for [182:52] big wins and missing a few because you [182:55] can always unfortunately fortunately you [182:57] can always leave behind the smoking [182:59] ruins of your disaster at one company [183:01] and try again somewhere else and [183:02] eventually if you take enough big swings [183:05] um you will uh hit one. So I'm going to [183:10] use a baseball analogy from the book [183:12] Moneyball. You can either bat for like [183:15] on base percentage and I want to swing [183:17] to get a safe trip to first base and [183:20] that's actually easier than trying to [183:21] hit a home run, but if what you want is [183:24] the home run, you got to swing hard and [183:28] wild a little bit and you'll strike out [183:31] more, but you'll get a few home runs. [183:32] And that's actually what makes you [183:33] famous. Like nobody cares that you got [183:35] on base. They like to see the ball fly [183:36] over the wall. So, uh, that's [183:42] I would leave Amazon with my expertise, [183:46] with the Amazon name on my resume, go [183:48] somewhere high growth and start giving [183:50] them value, asking for advancement, and [183:52] taking risks. If I succeeded, I'd move [183:54] up. If I didn't, I'd hop again. [183:57] And that would be my way is when I found [184:00] a high growth place where I was [184:01] succeeding and moving up, I'd then ride [184:03] that. That would be the end of my [184:04] speedun. But that might be the third or [184:06] fourth company. Um there was a time I [184:10] know many people who went from entry [184:13] level at Amazon to VP. They're VPs [184:15] today, but I don't think that's [184:17] repeatable without 35. There is no [184:20] speedrun of that today. There's like a [184:22] slug run. I don't know what the opposite [184:23] of a speedrun is, but it's very slow and [184:26] that's what a playthrough it's, you [184:29] know, like what's the what's the [184:30] playthrough where you complete every [184:32] quest? It's that one. And it's like slow [184:35] as And that's what's left. And [184:37] it's because, well, it's because a [184:39] company that grew from 14,000 employees [184:42] when I joined to 1.4 million when I left [184:44] is now still more or less 1.4 million. [184:47] The opportunity is not there. And the [184:49] same as you were at Meta. Meta used to [184:52] grow like crazy. Now it's shrinking. [184:54] They like I'm sure many careers were [184:58] made at Meta, but I don't think they're [184:59] being made the same way now. like what [185:02] you did at meta because I know you had a [185:04] lot of success there. I don't even know. [185:07] Do you believe that's repeatable at meta [185:10] today this moment? [185:12] maybe through the early engineering [185:14] levels but not in the higher levels [185:16] where business case matters more I would [185:19] say [185:19] >> right so that's why to VP it's not [185:22] possible you totally could stay at [185:23] Amazon to go L4 which is the entry level [185:26] to L5 maybe L6 but from there it's out [185:31] get go out somewhere that's going to be [185:32] faster because other people are going to [185:35] value that expertise way higher than [185:37] Amazon does one thing I'd say about [185:39] Amazon that makes this interest answer [185:41] interesting [185:42] They have 50,000 L4s or whatever 30,000 [185:47] I don't know the number. They have [185:49] 50,000 L5s. [185:52] That means you're just a number. You can [185:55] go somewhere where you're the only AWS [185:58] native engineer. [186:01] That is turning being one of 50,000 L5s [186:04] into leverage in another company. It [186:07] actually drives Amazon nuts because they [186:10] can't afford to pay all 50,000 L5s what [186:13] each one is individually worth to [186:15] externals. So they're always getting [186:17] snapped out by companies are like having [186:20] that person in here is going to save us [186:22] a ton on our bill and our implementation [186:24] times. They're worth 300,000 to us, but [186:26] Amazon's only paying them two. Buy them [186:28] out. [186:31] Thank you so much for your time and your [186:33] transparency. And for people who want to [186:35] find more of what you're doing, where [186:38] can they find you? [186:39] >> Two places. Ethan evans.com is my [186:41] website. It links to everything else. Or [186:43] find me on LinkedIn. I'm Ethan Evans [186:46] there. You'll find me in a heartbeat. [186:48] >> Awesome. Well, thank you so much for [186:49] your time, Ethan. I really appreciate [186:50] it. [186:50] >> Thank you, Ryan. It's always a pleasure. [186:53] I know you have an endless list of [186:54] questions, so someday we'll continue. [186:57] Hey, thank you for watching this [186:58] podcast. If you liked it and you want to [186:59] see the show grow, please support with a [187:02] comment or a like. Also, if you have any [187:05] recommendations for people you want me [187:06] to bring on, please drop a comment. [187:09] Guests like Barbara Liskov, Mike [187:11] Stonereaker, Mark Brooker, these were [187:14] all people that I brought on because [187:16] someone left a comment. On another note, [187:18] aside from the podcast, I'm working on [187:20] building the ergonomic keyboard that I [187:22] wish existed. Here's a glance at the [187:24] prototype. It's a split keyboard, so [187:26] there's two sides. um this isn't the [187:28] case, but yeah, we launched on [187:30] Kickstarter and we hit our goal within [187:32] eight hours of launching. I really [187:33] appreciate it if you were one of the [187:35] people who grabbed one of the early [187:36] units. Um we're now working on the long [187:39] journey of building the tooling now and [187:41] so if you still want to pick one up, [187:42] I've left the late pledges open on [187:44] Kickstarter, so you can grab one there. [187:47] I'll put a link in the description. [187:49] Thank you again for watching the podcast [187:51] and I'll see you in the next