Office Politics, Decoded

Viewers often ask Mike whether being good with people or being good at the work matters more. He says that question belongs to a Chinese workplace, where his own experience is a two-and-a-half-month college internship, and that forcing it onto an English-speaking workplace is awkward. His alternative is to productize yourself. An iPhone needs both a strong product and strong marketing: excellent features without marketing do not sell, and great marketing cannot save an obsolete product.

A clear goal removes noise

Mike treats total time as skill time plus marketing time plus time spent handling noise. Noise returns nothing, so the first move is to shrink it, and only a clear goal lets you see what noise is. Before 2017 he had no clear goal and followed rules his parents gave him about getting along with everyone. In 2017 he set a goal of reaching senior manager within 24 to 36 months. Showing his expertise in meetings and claiming the credit he had earned became the priority; whether colleagues thought he was bragging became noise he could decide to ignore.

Inherited rules inflate the noise

He argues that much internal friction comes from goals handed to us by parents, teachers, and society. The same voices tell us to tend every relationship along the way and warn us not to self-promote, with sayings such as good wine needs no bush and gold will always shine. In his reading, that advice sets three of the four variables against you: a goal that is not yours, a larger share of noise, and a smaller share of marketing. Systems everywhere are designed to run at the lowest cost, he says, and your success is not part of their formula.

The right ratio depends on level

There is no golden ratio of skill to marketing; it depends on level and job. A new hire should spend most time on skill but can stand out with only a little marketing, because most people do none. Mike cites a figure he describes as real data: 97 to 99 percent of LinkedIn users never post. More important, though, is self-promotion inside the company, in meetings in front of your manager and skip-level manager. For directors and vice presidents, selling the vision repeatedly is part of the job, and in customer-facing roles marketing yourself, your team, and your product becomes a large share of the work.

When a manager finishes speaking, many of us repeat our understanding back to confirm it. Mike says that can please a teacher, but at work it adds to the manager's cognitive load and slowly moves you away from their trust.

Recap versus synthesis

Mike anticipates an objection: he has elsewhere told viewers to summarize in meetings. The difference is purpose. Around 2017, on a small launch, he worked with someone he calls Xiao T, who recapped every statement to confirm his own understanding, and someone he calls Xiao S, who synthesized. After a long, scattered discussion Xiao S would pause the group: so far we have identified three root causes, these are the priorities, the goal is a quick fix for the most visible symptom, so can we go deeper on option one and test its viability? Xiao T centered his own understanding; Xiao S centered the project and steered everyone toward a direction.

He acknowledges the good intent behind recapping: we want to be sure we match what the boss wants and avoid execution mistakes, we need to run the request through our own problem-solving frameworks before it becomes an action, and we were raised to show the speaker we are listening. The intention is fine; the way it sounds is the problem.

Why exam thinking stalls you

Mike watched a video of a middle-school teacher solving a shaded-area geometry problem by drawing an auxiliary line, rotating and moving shapes until the answer appeared. He could not solve it himself, but it made him notice something: an exam gives exactly the conditions you need, has one correct answer, and has an examiner. A meeting has none of those. Ten equally smart people are present, conditions are never exactly sufficient, and everyone is both solving and setting problems. Running exam-style simulations in that setting overloads us, and we wait for the moment our answer is fully confirmed. That moment never comes, so we fall a step behind and stay behind.

He contrasts our predict-and-simulate mode with the feedback mode he sees in many Western colleagues: say it, watch the reaction, adjust if someone objects, and treat silence as agreement. Around 2015 his boss told him he was very quiet in meetings and needed to be more engaged. Mike felt wronged because his mind was fully engaged. Later the boss explained what he saw: silence reads as no interest or no leadership, and once a line like he does not seem to have an opinion reaches your boss, it can damage your review and promotion.

The fix his boss pointed to was Amazon's bias-for-action principle: speed matters, and many decisions are reversible and do not need extensive analysis. Mike says he often fell into analysis paralysis. If a decision can be reversed, roughly 60 percent of the data is enough; waiting for 100 percent means the moment has passed. He recommends the book Working Backwards, written by two former Amazon senior executives, for its decision-making mental models, while noting that bureaucracy can distort these principles in a large company and that bias for action can carry other meanings in office politics that he leaves for another time.

Phrases that keep you safe

For gaining visibility, Mike suggests wrapping an idea in a question rather than a statement: have we thought about this aspect of the business, or this risk? If the answer is yes, a quick just wanted to double-check closes it; if no, you can offer maybe we could do this. He calls this a fake question and says that in leadership training they do not recommend it for leading a team, but for an individual trying to be seen it is useful. When a statement goes wrong, back-paddle without treating it as an admission: let me revise that, I will take that back and say what I actually meant, or, as he sometimes says to VPs, I misspoke on that, let me elaborate. It is simply thinking out loud.

Mike's test: count how often you say I am sorry in a day. More than twice is probably overuse. Early in his career he apologized in almost every other sentence when asking a question, and after a mistake he would add I will try as hard as I can. He calls these goodwill actions, and in a senior leader's ears a goodwill action means no action: I will try as hard as I can sounds like you will not really try. The intent is respect and de-escalation, avoiding conflict and blame.

Did you actually miss it?

He starts with mindset. First ask whether you really missed something, or whether other factors only make it look like your fault. If it is not your fault, apologizing is another form of arrogance: saying something for surface harmony. Second, there may be a bigger game behind the curtain. Admitting fault in a meeting can force your boss to do cleanup work you cannot see, so ask whether your boss needs you to hold the line.

Early in his career, after a miss he would feel ashamed, replay how he could have missed it, and mentally check out of the rest of the meeting, even though he might have had useful input on the real business problem. The leaders he saw earn trust from VPs and senior VPs talked about the business even when their own team had made the mistake.

This transcript repeats the lesson in Stop over-apologizing and making goodwill promises almost word for word: the twice-a-day test, goodwill actions read as no action, the four perceptions, the mindset questions, and committing to an action with an estimated completion date. Read that section for the full treatment.

Mike's rule of thumb: using more than five words to tell someone how great they are counts as over-praising. I have heard so many great things about you, followed by more, is too much; I like your shirt is fine. The urge is strongest with someone senior or someone new, and Mike says he still catches himself doing it. The intent is respect and quick rapport in a foreign language and culture, but it backfires. It raises doubts about competence, which creates a power imbalance and costs respect. And, as in our own culture, excessive compliments make the listener wonder what you want from them, which grows into skepticism and distrust if it becomes a pattern.

Decoding vague feedback

He adds an aside about vague feedback such as you need to be more assertive, more confident, or improve your communication. Bosses often give it because they were never trained to give feedback. Leading, managing, and coaching are separate skills; many bosses master one, and coaching is the hardest. You hear what you are not, but not how to change.

The fix starts with the idea that trust requires two people on level ground with mutual respect. People sense friendliness without extra words; humans are wired to read friend or foe quickly. They also sense, just as quickly, that you need something from them. So reverse-engineer it: go into the conversation with the mindset that you need nothing from this person. You will feel less needy, and the rest follows. Less is more, with the same caveat as before: you do not need to become cold, unsmiling, or aggressive, just rebalance the urge to be friendly.

The third politeness trap Mike describes is giving too much context before making the point or asking the question. The intent is thoroughness, respect, and a worry about being misunderstood. As he moved up, he found himself doubting such people. Does this person know what matters? A pile of words also triggers suspicion; he cites the saying that VPs and directors can smell nonsense from five miles away and admits he would wonder what was being hidden or whether someone was dodging a mistake. Finally, there is cognitive overload: senior leaders run back-to-back meetings, sometimes double or triple booked. His reaction was to protect himself and ask whether someone else could present next time, which is how people lose their seat in decision-making meetings.

What to do instead

The mindset fix is that you have nothing to prove in this meeting. Mike recalls believing he had to impress a VP as if one meeting would earn a promotion; in reality reputation and artifacts build over time, and the pressure only made him lose his rhythm. The practical fix is brevity, more so as the room gets more senior, and speaking in terms senior leaders universally understand: time, money (revenue, cost, profit), customer happiness, which Amazon called customer delight, and opportunity. His working definition of a company is that it trades existing resources, money and time, to delight customers so it can gain more resources and future opportunity. Tie what you say to one or more of those.

The clip retells the early-1960s experiments led by psychologist Stanley Milgram at Yale, inspired by the question of how ordinary people took part in atrocities under Nazi authority. Participants were assigned the role of teacher and told to give increasing electric shocks to a learner in another room, an actor who protested, begged, and eventually fell silent. When teachers hesitated, an experimenter in a lab coat used a fixed series of firm prompts, and the experiment ended only if all four were refused. The clip states that 65 percent of participants went to the maximum of 450 volts and that every participant reached at least 300 volts, many while visibly distressed.

The clip also notes the heavy ethical criticism: deception, intense stress, an unclear right to withdraw, incomplete consent, and delayed debriefing. It adds that later replications under more ethical conditions and cross-cultural studies still found high obedience, and concludes that situational factors such as legitimacy, setting, peer pressure, and procedure powerfully shape choices.

Many of us have heard you need to be more vocal in meetings or you need to speak up. Then in the meeting the heart races, you wonder what to say and which words to use, a topic you know finally comes up, and by the time you decide when to jump in it has passed. On the way home you replay the feedback and worry. Mike received similar feedback between roughly 2017 and 2019, while moving from middle manager to senior manager.

The overloaded processor

His explanation, offered with the caveat that he is no neuroscientist, starts with the prefrontal cortex, which handles reasoning and decisions but burns a great deal of energy. Speaking requires three jobs at once: what to say, how to say it, and when to say it. For native speakers much of this is muscle memory handled by language areas he names as Broca's area, Wernicke's area, and the motor cortex, so they can think on their feet. Non-native speakers also have to retrieve grammar, pronunciation, and word choice deliberately, which maxes out the processor. He calls this cognitive overload.

The alarm that makes you freeze

The worse part, he says, is the amygdala, which he compares to the grumpy old gatekeeper of a building complex who treats every child as a threat. It scans what we see, hear, and imagine, and when it senses danger it triggers stress hormones for fight, flight, or freeze. Humans are social, and for our ancestors being pushed out of the group could mean death. Not having a voice in the tribe's discussion still reads as that danger. So the gatekeeper keeps sounding the alarm, energy drains, and finally you freeze. That is why you can be exhausted after a meeting in which you said nothing, while your boss simply sees no contribution and no presence and repeats the label you need to speak up.

Mike describes himself as introverted. He made speaking first into a rule and practiced it until he no longer had to think about it. He connects this to Daniel Kahneman's Thinking, Fast and Slow, which he first read around 2017 or 2018: move habitual behavior into the fast system. Speaking first removes all three jobs at once, because what to say and how to say it are prepared and when to say it is decided. About six months later his boss told him he had really stepped up and that people spoke highly of his presence in different meetings. He frames the change as sending the gatekeeper home early rather than becoming a different person.

Mike opens with a pattern from what he estimates are more than ten thousand hours of meetings: people rarely get blamed because they actually ruined something. It happens in the first few seconds of explaining themselves when challenged. Long explanations aimed at being understood push you lower each time and signal that you lack political savvy, so the other side marks you as a beginner and future blame flows your way. Explaining, he argues, is something the party in the wrong usually starts. East Asian upbringing and culture make self-justification instinctive, and if the other person wants a scapegoat, every extra sentence welds the blame on more firmly.

Move 1: when you are volunteered in public

A colleague says in a cross-functional meeting: let's have Mike's team own this; you can get it done by Friday, right, Mike? As a senior manager and director, Mike often assigned work this way in front of a VP. It was rarely personal; he needed his leader to see that he had the problem covered and was showing leadership. What he watched was not whether you could do it but how you answered and how his VP's face reacted. If you say you have no bandwidth or hesitate, you become the scapegoat for unowned dirty work, and the assigner can lecture you about priorities, which shows off his leadership at your expense. Do not open with well, which reveals hesitation, disagreement, and low confidence in a single word. The question contains two questions: are you good with owning this, and can you finish by Friday? Answer in two parts: yep, totally on board with the direction; let me move things around and follow up with you offline on the timeline. Then stop. The pressure returns to the asker, and the timing moves to a conversation you control.

Move 2: present the plan, then ask for objections

Asking a senior person what feedback do you have on this plan invites criticism. Mike admits that as a newly promoted director he felt he had to show judgment, so he would toss out have you thought about this, are you sure, or can we double-check, and each casual line became a day or two of work for you. Questions such as are you good with this or can I do this push the senior person toward finding fault. In a one-on-one, say instead: here is what I am going to do; we will do A because of B, and it will get us C. Any objections? Silence means consent, and the easiest reply to a leading question like that is no, I am good.

Move 3: ask instead of asserting

In English-speaking workplaces, Mike says, the person with the right to ask questions is the leader of the meeting, and between peers everyone has that right without permission. Staying in the answering seat, even when right, invites attack: people find small holes in a flat statement and keep questioning until observers conclude you are the one in the wrong. When a cross-functional meeting turns into a fight, ask: hey guys, just want to take a step back. Are we solving the symptoms customers are seeing, or the root cause underneath? You give no answer, but you raise the level of the meeting and everyone follows your question. As a director he welcomed that person, because he could build on the question or give a ruling, and the boss concludes your thinking is at their level. His rule: if you are 60 to 70 percent sure of a view, the safest way to state it is as a question.

Move 4: counter an aggressive accusation calmly

When a colleague aggressively blames you in front of your boss, for example asking whether the front-end data was your responsibility and whether you reconciled it properly, remember who the audience is. As a director Mike saw such clashes two or three times a week and remembered almost none of the details. What stayed was who panicked, who stayed steady, and who rushed to defend and talked more and more. Someone who barely engaged and only asked calm questions made the aggressive party look like the problem. Step one: acknowledge the emotion without accepting the accusation, and do not reflexively say sorry; say I hear your frustration. Step two: the accusation usually mixes what you knew with what you did not. Seize a detail you never heard about: can you elaborate on that? Who did you talk to on my team about this? People bluffing often reply well, I am raising it because it is urgent, and as a director Mike's judgment tilted against them at that word. Then say: this is the first time I have heard about this; is there a miscommunication somewhere? Their accusation becomes their communication gap. Finally hand the action back: I am happy to help; what is the fastest way you can get me the information or requirements I need?

Some people play less skillfully, raise their voice, and say something like I just want to call out that your team is blocking everything. Stay calm, lower your pitch, and repeat the last phrase back: we are blocking everything? What specifically makes you say that? The calmer you are, the weaker their case looks, especially with the boss watching. The goal is never to win the argument or force an admission. It is for your boss to leave the meeting knowing the problem is not yours, and from then on the boss tends to side with you.

This clip contains the full voluntold lesson: why a director assigns work in front of a VP, why no bandwidth turns you into the scapegoat, why to drop the word well, and the two-part reply that agrees with the direction and takes the timeline offline. The wording matches Move 1 in Four moves to hold the room when blame is in the air.

This clip covers why asking a director for feedback invites extra work and ends with the any objections close. Part of the middle is missing in the transcript: it jumps from have you thought about that directly to the end of the plan formula, so the full version in Move 2 of Four moves to hold the room when blame is in the air is the better reference.

Mike states the principle that the questioner leads, explains why flat statements attract attack, and gives the step-back question about symptoms versus root cause. He closes with the rule that a view you are 60 to 70 percent sure of is safest when packaged as a question. Move 3 of Four moves to hold the room when blame is in the air covers the same lesson in the same words.

Mike walks through why the boss, not the accuser, is the real audience; acknowledging frustration without saying sorry; asking about a detail you never heard; naming a possible miscommunication; returning the action; and repeating a loud accusation back in a calm, lower voice. The content matches Move 4 of Four moves to hold the room when blame is in the air.

Mike's conclusion comes first: the same question can help or hurt depending on whom you ask and who else is present. His example is early 2019, when Amazon launched a new US service he says Prime members likely use weekly. On launch day nearly everything that could go wrong did. A group chat included a senior director, a junior director, senior managers, and many managers and individual contributors, who posted every question there. At the next morning's meeting the senior director was unhappy: there was too much back-and-forth to tell signal from noise. A chat with senior stakeholders should not be a forum for front-line questions, and every question effectively said look over here, my area is full of problems.

What Mike did

Mike offered that his team would own communication with the senior director: each data point would come with root cause and action items, in an accurate report every three hours, so the director no longer had to read the chat. He then created two new chats: one with everyone except the senior director, and one with everyone except both directors. The second became the working stream where individual contributors and middle managers could ask execution questions freely. He used the junior director to judge which stories the senior director and the VP would understand and which details were too technical to pass up.

The lesson is that a question shapes the listener's opinion, sometimes a prejudice, about you, your team, and even your boss, and you should know how many people are forming that view and from which teams. A simpler example: as a newcomer you ask a basic question of someone who happens to be very close to your skip-level boss. Their impression that you do not know things can reach that boss before you have spoken to them more than once. So create a safe environment to ask the questions you need to grow.

If that sounds exhausting, Mike argues it is a one-time investment. Trust and information channels between people rarely change without a major event. Observe once who tells whom what, map the network, and it will serve you for six months to a year, changing only at the edges. His team motto drew on the idea that a customer eating a sausage does not need to watch how it was made; watch a hot-dog factory video if you doubt it. Workplaces are the same.

A common scene: in a meeting, a boss or stakeholder asks you about something that is not your responsibility. You worry that saying so looks like shirking and you do not know how to get the real owner to explain, so you say I will follow up. Something that was never yours becomes yours, and you spend hours of overtime on work that does nothing for your promotion because it looks like cleaning up your own mess. Mike says the deeper issue is not face but not knowing how to dismantle the other person's logic without a confrontation.

Why the obvious answer fails

Take why is this project delayed again, asked of you when you own only part of it. The asker is not necessarily malicious; the question is simply too broad. Complaining that the manager cannot see who is responsible does not help, because you cannot control what is asked. A typical answer is that a partner team had attrition last month and you hit some technical obstacles, which you are solving and will follow up on. It sounds fine but collapses under follow-ups: how do we know attrition was the issue, did no one step in, why was this not escalated? The more you explain, the more it sounds like excuses. Why delayed sounds goal-oriented but has no operational handle.

The better answer

Move from the doer being held accountable to the leader helping everyone see the problem. If you own infrastructure development, say something like: happy to shed some light; let's take a quick step back and break down the components. First, infrastructure is about a week ahead of schedule and we are confident the trend is sustainable. Second, the pipeline build is on time. We did hit hiccups in UI and UX design and in the system algorithms, which created the bottleneck. Joe and David, I see you both on the call; can you fill us in on that side and our path to green?

Some colleagues pass blame through a tricky question. You end up saying I will follow up, work hours of overtime, and watch stakeholders credit the asker with leadership, sometimes even at promotion time. Mike's point is that the task is not to solve their problem or prove your technical ability, because starting to answer is the trap. Why do we keep delaying this feature request, we have talked about it numerous times, is not a request for a reason; it casts you as the person stalling the project. What actions are you going to take to solve this issue is not a request for your opinion; it casts you as the person who catches the problem. The real contest is over who defines the problem, because whoever defines it assigns roles and next steps.

Go upstream

School trains us to jump straight into solving the word problem. At work your next move should be upstream: pull out the assumptions and premises and ask whether they hold. What assumptions have to be true for this question to be valid? Answering accepts all of them, and one may be the hole you fall into. His joke example is the classic chickens-and-rabbits puzzle, in which you count heads and feet to find how many of each animal are in a cage. Before writing equations, ask the person who set it why they can count heads but cannot tell a chicken from a rabbit.

Why this happens more as companies grow

If your company is small or growing fast, you may rarely see this, because growing the cake matters more than dividing it. Once an organization passes a certain size and resources become limited, friction over allocation produces negotiation, debate, and conflict. You can absorb some friction with your own time and energy, but that does not end the debate over the cake or guarantee you a bigger piece. Instead, others learn that your personal time can be sacrificed and use it as a bargaining chip, and your workload grows.

Putting it into words

Replying I am tied up these few weeks, I will look into it, concedes the premise that you keep delaying, and your reputation erodes. Mike's alternative: I remember your request from our conversation earlier this week. Let's pause and let me clarify our intake process. A business unit submits a request through our ticketing system with clear requirements and impact, and every Monday our team reviews all new and existing requests to scope and prioritize them by impact and risk. When you say we have talked about it numerous times, was there a ticket your team submitted after our conversation? That is not an excuse; it puts three premises in front of everyone: why it has not been done, whether the request was formally submitted, and whether it is worth doing. The topic shifts from proving your innocence to whether their question deserves discussion, and over time people think twice before passing you blame.

Mike pictures your job as a pressure cooker and your workload as its pressure. Too little pressure and the meat never cooks, which at work can mean being laid off. More pressure cooks faster, but too much and the pot explodes, which is burnout. The cook is your manager, who wants the meat tender as fast as possible without an explosion, and would love a gauge. You are the gauge. Most people only speak up when they are about to blow or already have, which forces the manager to rescue the work and the pot at once and creates strong negative feelings; a cook may stop using a pot that exploded. So report your workload and pressure while it is still manageable.

A signal disguised as recognition

When his team was slammed and he feared more assignments, he would say in a group meeting: I want to take a moment to recognize the work my team is putting in. They are working twelve hours a day, weekdays and weekends. At this speed I am confident we will hit the deadline. When you see them in the hallway, give them a high five, so we keep morale high and finish strong. It sounds generous. The message to everyone listening is to think twice before adding work, because new work will delay this project.

Suppose your boss's tone drains you daily, but visa status or a thin network means you cannot leave soon. Mike starts by saying that judging a boss as toxic is subjective. Some of his own reports liked him and others disliked him; the difference was their culture, communication preferences, and tolerance for feedback. Sometimes a report decided he was toxic without his knowing what had offended them and then blew up, which naturally made him defensive, so the report's fears came true. That is why he disagrees with online advice to confront your boss or flip the table. His videos are about deflecting blame from peers and from people unrelated to your review, not fighting your boss, because a showdown has a cost. If you cannot leave soon, add time to the equation: buy time, build your network inside the company and on LinkedIn, and then move to the internal team or company you want.

Should you go to HR?

Mike says it depends on what toxicity means. HR is a filter between the business and legal risk, whose main job is reducing future legal and PR risk from employees. If you are describing your feelings, the future risk to the company is you, and HR may pass your complaint to your boss and ask them to pay closer attention to you. If you have real evidence that your boss crossed a red line, such as sexist or racist remarks, the scale tips your way because the boss has become the risk. He stresses respect for HR, noting that many of his friends and corporate clients work in HR, but HR is not your friend. A former director gave him a blunt test: if this went to court, would you have specific evidence and witnesses to win, or only your feelings? If only feelings, you would be wasting the legal fees.

A short-term tactic

For surviving the next few months with a boss who does not trust you, Mike's first step is to demystify the boss. School teaches that leaders sit far above us, but your boss is a future you, with a boss, performance pressure, and criticism of their own. Find where their pressure comes from, then create closed-loop expectations and feedback. If they ask how we make sure we stay in sync with other teams on this project, answer with something that appears to cover every possibility and has a timeline: that is a good perspective. I am setting up one-on-ones with representatives from the teams we work with, I will get their first pass and report results in our next sync, and then I plan to set up a weekly mechanism with all of them. I will spearhead this over the next few weeks until we are stable. Any objections? A vague I will ask other teams becomes a concrete plan; it also signals that this is your focus for two weeks so no one should add other work, and the outreach expands your network for your next move.

Mike introduces the compilation as four of the most common sources of toxic workplace pressure for people who cannot simply quit because of visa or money constraints: being held accountable, being blamed, accumulating work, and a toxic boss. The four segments then repeat, nearly word for word, the videos summarized above.

The most frustrating moment at work, Mike says, is cracking a hard technical problem only to hear from your manager that you are moving too slowly. The usual mistake is pouring all effort into the final presentation, document, or slide deck. From the manager's side, the larger their scope, the less they can hold its details, so every week without an interim update raises their insecurity. Mike says this is not only a Chinese habit; Americans do it too.

A cautionary story

In 2018, when Mike was a middle manager, an individual contributor a few years older than him, whom he calls Lao M, transferred in after failing to get promoted on his previous team. Lao M liked to save everything for a big reveal and rarely reported in between. Asked about a project, he would say he was still working on it and nothing more, and he told peers and other teams the same, so they all came to Mike. The eventual result was ordinary. Meanwhile Mike carried the communication cost, assessing risks himself and resolving cross-team friction, so much of the mental load of Lao M's job ended up on Mike. Asked how he stayed in sync with other teams, Lao M complained that they did not understand his area and that he had carried everything alone. After seven or eight months Mike's patience ran out; he found himself micromanaging because he got no usable information and was often caught unprepared in meetings with his own boss and peers. In Mike's account, Lao M was eventually managed out through a performance improvement plan.

What reporting is really for

Many people think good upward reporting means speaking clearly at the end, polishing the deck, or showing professionalism and effort. Mike calls that self-congratulation worth nothing. The essence of reporting up is giving your leadership certainty in exchange for the resources you need. Managers are often more insecure than their staff: they carry KPIs or OKRs from above, and resources are limited, so what goes to one peer cannot go to another.

Mike was a general manager and director in Amazon's global supply chain. Amanda Tobin worked with him at Amazon for five years across operations, program, and product management and is now a principal product manager at Everbridge. In 2021 Q3 her organization was reorganized under Mike, and she reported to him directly. She was later moved to a skip-level position, regained his trust, became his proxy in meetings, returned to direct report, and eventually led a global organization of more than 160 people with two senior managers under her. When Mike started his own business, she was one of the first people he asked for help. The session covers diagnosing friction, neutralizing distrust, rebuilding partnership, scaling, and when to walk away.

The clip opens on the phrase radical objectivity, separating what is said from how it is said, then plays Amanda's description of being reorganized under Mike, moved to skip level, unsettled by peers' comments, and learning what did not work, venting to coworkers, and what did, keeping her side of the street clean, showing competence, and watching her peers. Mike closes by saying the changes were subtle but not small. All of it is covered in the first two questions of the full conversation.

This excerpt contains Mike's description of Amanda surfacing issues early with options, Amanda's self-critical review of her own areas, and Mike's signal that she was ready for more scope: she informed him she was handling problems instead of asking for solutions. It adds a short remark from Amanda about staying one step ahead so her team could proactively share news and get credit instead of reacting. The full exchange is the scaling question in Turn around a relationship with a boss who does not trust you.

The opening captions are garbled repetition and are not summarized. The usable portion names a second and third step, aligning on goals while over-communicating and building your paper trail, then plays Mike's observation of more proactive communication from Amanda and her explanation of moving from distrust to neutral: over-communicating, representing the business well, showing consistency, and keeping a win log. See the second question of the full conversation.

Mike joined Amazon in 2015 as a warehouse front-line manager, launched a team with Sam as peers in 2017, moved across the country in a 2018 reorg, became a senior manager (L7) in 2020, became head of an organization called Central Operations after a 2021-22 reorg, was promoted to L8 director in 2023, and began working for himself in 2024-25. Sam spent just over a decade at Amazon, led an organization called Sub Same Day for about four years, grew it fourfold, and helped open more than 67 buildings; Mike notes that her organization included nested directors. A 2023 reorg expanded her scope to program and product teams, and in 2024 she left to lead an industrial-design AI company. The caption spelling of Sam's surname is uncertain, so this section uses her first name.

Why reorgs happen

Mike gives two kinds of causes. External: shareholder expectations swing from revenue growth to profit to cost to new pillars such as AI, customer demand keeps rising, and the economy shifts, so growth is never linear. Internal: companies must keep hiring and promoting regardless, current structures move too slowly for new goals, big tech became top-heavy after years of exponential growth, front-loaded growth created duplicate work, and when a senior leader leaves, their scope is divided among others in a cascade down to individual contributors. Sam adds an example: when pandemic orders surged in 2020, by 300 to 500 percent in her recollection, Amazon's operations leadership reorganized to launch more buildings. When the world reopened in 2022 a second reorg reduced unnecessary layers and focused on cost. She sees tech today in a similar position, with tools changing every few months and leaders racing competitors.

Before the announcement: assess yourself

Because reorgs now arrive without warning, roughly yearly in big tech, Mike says to prepare continuously with a self-assessment. Do you have your manager's or skip-level manager's trust? Does your skip level see your work? Do you have solid stakeholder relationships, credibility, and reputation? As an individual contributor your work may not change much in a reorg, and people will want you to stay. Next: do people know what you want and that you want to grow? Have you shown you can take on more without burning out, which he calls punching above your weight class? Then plan for the unhappy path, a new org that disappoints, with a strong internal and external network as a plan B. He reruns this check about every two months. Sam adds that she and Mike both kept regular one-on-ones with peers, every two weeks or monthly, which keep partnerships healthy and give early knowledge of leadership changes. She says Amazon reorgs went from roughly yearly to about every six months after 2020.

The first 30 days

Mike's three steps after an announcement. First, send stakeholders and internal customers a personal message: you probably saw the announcement; restate what it says; I wanted you to hear it from me because I value our partnership; I will keep our communication clear; for now it is business as usual, and I will personally make sure your priorities stay intact and nothing falls through the cracks. Partners who went through a reorg recently understand, and the shared vulnerability builds lasting alliances. Second, document your achievements and align with your current boss while you still have them; voice concerns and ask them to send your list of achievements to the new boss. If that is not possible, send the new boss your package yourself. Third, request the first one-on-one with the new manager proactively. Being the first to reach out and anchor the change during uncertainty means a lot to leadership.

Meeting the new manager

A new manager spends the days after an announcement wondering who is upset, who will quit, what will break, and who will lead peers through the change. Reaching out to calm them and signal that you can solve one or two of those problems earns goodwill. Mike's suggested lines: say you are excited to work for them, crisply; say you would like to understand their vision and goals for the new org and where you can add value, and that you do not want to dump information on them before knowing their vision. Then ask about their pain points as a conversation, not a one-sided pitch about why you deserve a promotion. Negotiate without threatening: I do not know if my previous boss sent a handoff about my achievements, but I am a candid person, so I want to raise my concern up front. I have been on a promotion track for the past twelve months, and these are the things I achieved. How will the new org affect my career progression? He calls that a fair question.

Sam on new bosses and success stories

When Sam took over Sub Same Day in 2020 she barely knew its leaders, so she toured every building in the US network to hear about problems and successes directly; she did not want to hear only that everything was great. With a new boss, highlight successes such as a strong partnership so it continues, and be candid about rocky relationships while saying what you are doing about them and asking for help where needed. If you list five problems and nothing is solved after 60 days, raise them again in business terms: is it delaying a launch or costing more? Sam calls this talking in terms of entitlement. Above all, you are your own best advocate; do not rely on your manager or skip level to have passed on your record. She blocked a red, recurring 30-minute weekly calendar slot titled success stories, rescheduled it at first, and learned to treat it like a meeting with her boss, writing wins in a cloud document so she could send her accomplishments to anyone at once, for example if a reorg landed just before a January promotion.

Mike closes the framework by saying reorgs are part of corporate life: repeat the preparation, since another one is likely within a year, and keep honing soft skills such as advocating for yourself, influencing stakeholders, leading meetings, and managing up, which amplify technical skills.

The first lines are caption fragments from a slide (VP, director, scope, manage up) plus one complete question: if this VP or director leaves, who on their team can step up and keep the lights on immediately? The rest repeats the introductions, the external and internal causes of reorgs, and Sam's pandemic example from A 90-day framework for surviving and using reorgs.

The opening teaser gives a stakeholder one-on-one sequence: open with a specific item, such as a quick check-in for feedback on your team's product or a sneak preview of something you are building; ask for feedback; act on it afterward; ask whether you may set up a follow-up; and later ask whether they have felt a difference in the past two weeks. In the example, the stakeholder says yes, they definitely felt the difference. Mike's summary: use a specific item to start the one-on-one, ask for feedback, act on it, and ask whether your actions made a difference.

The rest repeats the self-assessment from the full session: trust and visibility with your manager and skip level, stakeholder relationships, telling people you want to grow, punching above your weight class without burning out, a plan B network, rechecking every two months, and Sam's regular peer one-on-ones.

The opening teaser covers impressing a boss without wasting their time. Bosses do not need someone who wants to solve their problems but someone who is solving them, so keep your opener under ten words and get to the point. Pick the issue your boss talked about most in the last meeting, which is probably their top priority, and one you have the resources to solve. Then: I want to talk about the issue we debated in the last team sync; what is your take? It seems we do not have a mechanism, solution, or alignment on it. I am passionate about this. Are you opposed to me spearheading it and circling back with you next week? He also notes that after a reorg you should tell your boss you support the change.

The remainder repeats the three reasons a reorg can be an opportunity: the boss's uncertainty, vacant scope going to trusted people, and cracks in a new structure that reward early adopters.

Covers the inside-joke question, the sports and clique follow-up, and staying out of toxic pre-meeting chatter, in the same words as Fan Q&A, part 1: jokes, side conversations, slang, and empty talk.

Covers interjecting, disclosing a language barrier, nonverbal cues, the yes-or-no question that invites correction, and trying only once, as in the second question of Fan Q&A, part 1.

Covers the 80 percent comprehension point, muttered jokes as a warning sign, not fake-laughing, and acting as an upstander, as in the third question of Fan Q&A, part 1.

Covers note-taking, Mike's anticlimactic story, using a new word about five times, and sports analogies in American corporate speech, as in the fourth question of Fan Q&A, part 1.

Covers extending grace to a non-technical colleague, not over-promising, asking whether a mechanism or rollback criteria exist, and Mike's point that askers look like leaders, as in the fifth question of Fan Q&A, part 1.

Covers learning what you do not know, posturing, adding value while talking, and not becoming the person who talks for its own sake, as in the last question of Fan Q&A, part 1. This cut includes a joke Mike tells about middlemen in American companies, in which a struggling company with nine managers and one real worker fires the worker, as a way of saying such frustrations are a fact of life.

The third bucket

Most Western advice on being social says people instantly judge whether a newcomer is friend or foe, so smile more, compliment more, and look less intimidating. Mike says it leaves out a third bucket: someone they can manipulate, a tool. Many Asian professionals fear being seen as a foe and overcompensate, smiling too much, complimenting too much, and nodding along even when they disagree. It feels safe, but it signals that we are neither friend nor rival, but someone who can be used. This need not be malicious; it is a split-second mental shortcut. He gives two causes: East Asian upbringing teaches people-pleasing, and we feel we need something from the other person, recognition, approval, or acknowledgment, especially from Westerners we perceive as having more power or resources.

Sending signals

Mike believes actions shape the mind, so he turns the mindsets into greeting habits. He states that about 70 percent of what we communicate is nonverbal, and that body language can carry only a few signals before it confuses people, so prioritize. For people who look like him, the top priority is signaling that you are not easy to manipulate. He points to a clip of Singapore's Lee Kuan Yew with Ronald Reagan at a White House reception: Lee stood still, mostly serious, laughed at Reagan's joke, then quickly returned to a serious face. Mike reads that as a signal of backbone from the leader of a much smaller country, and calls it the hardest part, without which you are not on level ground.

Responding to signals

Balance it so you do not seem cold. Think of a good stand-up comedian, who rarely laughs at their own jokes but uses energy or wit to engage the audience. When asked how are you doing, I am good, how about you? signals either that you do not want to talk or that you lack confidence, which Mike calls a tool signal. Aim for a friend signal instead. Use energy, with phrases such as doing pretty awesome, beyond good, or living the dream, said with genuine energy rather than dread. Or use wit, with a beginner's formula: explain why you feel good with an absurdly related reason, such as feeling great because in two days you will not have to wake up early for the morning sync, or because your football team beat its rival in 2023. The gesture shows you are trying to make the moment fun, and the other person usually picks up the topic you chose.

Mike and Amanda, introduced as a born-and-raised Seattle resident, list the names worth knowing for small talk about Super Bowl 60 between the Seattle Seahawks and the New England Patriots. Mike jokes that, as a University of Michigan alumnus who owns a Tom Brady jersey, he might be a quarter of a Patriots fan.

For the halftime show they name Bad Bunny and Green Day as the announced headliners, noting more could be added. To sound more fluent, mention the two NFL conferences: the National Football Conference and the American Football Conference. The winners of each meet in the Super Bowl, and this year the Seahawks won the NFC and the Patriots the AFC. They suggest looking up any unfamiliar name with a search engine or AI tool before work.

Politics as a skill: motives, narratives, leverage and relationships (Ethan's view)

Ethan Evans, a former Amazon vice president, returns for a second conversation with Ryan and argues that corporate politics is a learnable skill set rather than an optional extra. In Ethan's account, reorgs, promotions, scope fights and firings are shaped by incentives, stories and relationships as much as by technical merit. His advice is to read other people's motives, prepare careful wording before a hard conversation, build leverage so that a request is hard to refuse, and treat the person across the table as a human being rather than an obstacle. The examples are Ethan's own experience at Amazon and with coaching clients. Figures, legal points and claims about other companies are his recollection or second-hand reports, not verified facts.

This source is not a video transcript. It is a set of dated meeting notes, January to March, from a reading group working through Camille Fournier's The Manager's Path chapter by chapter. It mixes the group's paraphrases of the book, a few quoted passages, and comments from members named Michael, Elle, Adam, and Lachlan. This section paraphrases the notes and does not reproduce the book.