A Life Engineered · Published 2026-08-03

Ex-Amazon VP on What Actually Gets You Promoted | Ethan Evans

Open on YouTube ↗

Summary

Overview

  • Speaker: Ethan Evans and Steve Huynh
  • Channel: A Life Engineered
  • Main topic: Corporate politics, career advancement, and managing up in software engineering and technology organizations
  • Purpose: Provide software engineers and tech professionals with actionable frameworks and strategies for career advancement and navigating workplace dynamics. Ethan Evans, former Amazon VP, shares insights on why hard work alone does not lead to promotions, how to navigate corporate politics ethically, and how to build productive relationships with managers and peers.

Topic Map

The Myth of 'My Work Will Speak for Itself'

  • Explanation: Many employees believe that working hard is enough to get noticed and promoted, but Evans argues that hard work alone often makes someone average in a competitive environment.
  • Key claims:
    • Most people approach work by working hard and hoping to be noticed.
    • Hard work on its own does not lead to promotions.
    • Ripping out the idea that work speaks for itself is crucial for career growth.
  • Examples:
    • Engineers expecting their code quality to automatically result in career progression without advocacy or visibility.
  • Terminology:
    • work hard and hope to be noticed
    • average worker
  • Why it matters: Relies on passive strategies that disadvantage ambitious employees in large organizations.

The Three Rules of Corporate Politics

  • Explanation: Evans outlines three fundamental rules for approaching workplace politics: accepting it is real, being reasonable, and recognizing that politics are learnable skills.
  • Key claims:
    • First rule: Accept that politics are real.
    • Second rule: Be reasonable in your interactions and avoid being intransigent.
    • Third rule: Politics are learnable skills, similar to technical skills.
  • Examples:
    • Viewing politics as human interaction, relationship building, and resource negotiation rather than malicious manipulation.
  • Terminology:
    • corporate politics
    • reasonable
    • learnable set of skills
  • Why it matters: Reframes politics from a negative concept to an essential tool for human interaction and career navigation.

Influence vs. Manipulation

  • Explanation: Distinguishing between influencing others for mutual benefit versus manipulating them for personal gain.
  • Key claims:
    • Influence is trying to persuade someone of something for mutual or their good.
    • Manipulation is trying to convince someone of something primarily for your own good.
    • High influence allows you to stand up to manipulators and help people.
  • Examples:
    • Negotiating a tradeoff where you cancel vacation to deliver a project in exchange for manager support on career progression.
  • Terminology:
    • influence
    • manipulation
    • mutually beneficial deal
  • Why it matters: Helps professionals navigate workplace negotiations while maintaining ethical standards.

Managing Up and the Manager-Employee Relationship

  • Explanation: The relationship with your manager is the single most important one at work, requiring empathy, clear communication, and understanding their pressures.
  • Key claims:
    • The relationship with your manager is the most important one at work.
    • Managers have their own worry lists, goals, and pressures.
    • Managing up involves making your manager's job easier and aligning your work with their priorities.
  • Examples:
    • Bringing solutions and status updates rather than unloading problems onto a manager's desk.
  • Terminology:
    • managing up
    • manager's worry list
    • collaboration
  • Why it matters: Directly impacts career progression, promotion velocity, and daily job satisfaction.

Asking for Raises and Negotiation

  • Explanation: Only 30% of people ask for raises, but 70% of those who ask get something. Approach negotiations based on business value rather than personal need.
  • Key claims:
    • Only 30% of people ask for raises; 70% of those who ask get something.
    • Do not open negotiations with personal reasons ('I want a raise').
    • Frame requests around business value, market rate, and high performance.
  • Examples:
    • Connecting salary requests to exceptional deliverables and increased responsibility.
  • Terminology:
    • ask for raises
    • business value framing
    • high performance
  • Why it matters: Empowers employees to capture appropriate compensation for their contributions.

Key Points

Hard work is not enough

  • Explanation: Working hard makes you average if everyone else is also working hard; visibility and advocacy are required.
  • Evidence: Most organizations have high-performing employees who are overlooked for promotions because they lack advocacy.
  • Practical implication: Proactively communicate your achievements and align with leadership priorities.

Politics are human relationships

  • Explanation: Politics is simply how businesses and people within businesses reconcile different goals and limited resources.
  • Evidence: Dependency and scheduling conflicts require negotiation and relationship building across teams.
  • Practical implication: Develop emotional intelligence and treat relationship-building as a core professional skill.

Trust is earned through sacrifice

  • Explanation: Trust is established when people are willing to experience inconvenience or make sacrifices for each other.
  • Evidence: Manager-employee relationships thrive when both parties make mutual concessions to achieve goals.
  • Practical implication: Demonstrate commitment by supporting key initiatives even when inconvenient.

Frameworks, Models & Processes

The Three Rules of Corporate Politics

  • How it works: A structured mindset shift for tech professionals to embrace and master workplace dynamics.
  • Components:
    • Accept politics are real
    • Be reasonable
    • Politics are learnable
  • When to use: Whenever navigating team dependencies, promotions, or organizational changes.

Influence vs. Manipulation Framework

  • How it works: Evaluates interactions based on intent and outcome to ensure ethical workplace navigation.
  • Components:
    • Check intent (mutual good vs. personal gain)
    • Evaluate transparency of decisions
    • Assess long-term relationship impact
  • When to use: During negotiations, cross-functional planning, and career discussions.

Examples & Case Studies

An Amazon VP was asked about his personal goals for the year and replied that he only manages and does no individual work.

  • Illustrates: The mismatch in expectations between individual contributors and leadership regarding hands-on work.
  • Lesson: Leaders at higher levels focus on organizational delivery rather than individual code contributions.

An engineer asked a manager for an improvement on an internal tool, taking half a day, versus going directly to make the change.

  • Illustrates: The difference between seeking permission and showing initiative.
  • Lesson: Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.

Actionable Takeaways

  • Immediate:
    • Stop relying solely on hard work to get noticed.
    • Reframe corporate politics as relationship management and negotiation.
    • Make your manager's job easier by bringing solutions rather than problems.
  • Strategic:
    • Invest in emotional intelligence and learn political navigation as a core career skill.
    • Build trust through strategic sacrifices and mutual support with leadership.
    • Evaluate your manager relationship regularly to determine if a pivot is necessary.
  • Questions to investigate:
    • Am I actively advocating for my work, or am I just hoping to be noticed?
    • Is my manager relationship a virtuous or vicious cycle?
    • Am I framing my compensation requests around business value or personal need?

Claims Worth Verifying

  • Only 30% of people ask for raises, and 70% of those who ask get something. (Statistical claim)

Notable Quotes

"There are cases where every manager and every employee lies." (at 0:00) "Yes, I lie. I hate it. I hate it when I do it, and I don't think it's avoidable." (at 0:05) "Why working hard never gets people promoted on its own?" (at 0:25) "Most people in fact, their basic approach to work is work hard and hope to be noticed." (at 0:26) "Accept politics are real" (at 7:15) "Be reasonable" (at 7:19) "Politics are learnable" (at 10:18) "If you want something done, give it to a busy person." (at 85:31) "Always insist on working on your manager's most difficult problem." (at 94:57)

Compressed Summary

  • Hard work alone does not drive promotions; visibility and advocacy are required.
  • Corporate politics is simply relationship management, negotiation, and resource allocation.
  • Influence focuses on mutual benefit, while manipulation serves self-interest.
  • Managing up requires understanding your manager's pressures and making their job easier.
  • Trust is earned through sacrifice and delivering results under pressure.
  • Keywords: promotions, politics, management, career, influence
  • Core insight: Career advancement requires moving beyond passive hard work to master ethical influence, corporate politics, and strategic alignment with leadership.

Core insights

7
Mental Modelmedium noveltymoderate evidence

Influence and manipulation are distinguished purely by intent (mutual/other-benefit vs. self-benefit), not by the observable action. Two identical request sequences — the vacation-cancel-for-sponsorship trade — are classified differently depending on whose utility they optimize.

Why it matters

If the same action trace can be labeled cooperative or adversarial only by inspecting the objective function behind it, then action logs, tool-call transcripts, and outcome metrics are insufficient audit artifacts for agent safety. Auditing requires declared or recoverable intent (which principal's utility is being maximized, what was disclosed to the counterparty), not just behavior replay.

Generalization

Applies to any multi-agent or human-agent setting where one party negotiates with another: an agent that optimizes its operator's utility while representing a shared decision to a third party is behaviorally indistinguishable from an aligned collaborator unless intent is separately attested. Suggests intent/objective provenance as a first-class log field.

Influence is trying to persuade someone of something for mutual or their good.
Open source video
Manipulation is trying to convince someone of something primarily for your own good.
Open source video
Mechanismmedium noveltymoderate evidence

Working hard is explicitly framed as the path to being average when everyone else works hard; outcome depends on an advocacy/visibility layer that translates output into the evaluator's priorities, not on the output itself.

Why it matters

This separates the producer from the reporter as distinct functions. A system that generates correct artifacts but has no component whose job is to surface those artifacts in the decision-maker's frame will be systematically under-credited — a silent, structural failure rather than a capability failure.

Generalization

Generalizes to agent pipelines: an agent whose work product is never summarized, ranked, or routed into the consuming decision process is functionally invisible regardless of quality. Implies a reporting/prioritization layer as a separate component with its own eval criteria (does the principal notice at the right time?), not an afterthought of the worker.

Working hard makes you average if everyone else is also working hard; visibility and advocacy are required.
Open source video
Hard work on its own does not lead to promotions.
Open source video
Mental Modelmedium noveltymoderate evidence

Politics is defined operationally as the mechanism by which an organization reconciles different goals under limited resources — dependency and scheduling conflicts requiring negotiation across teams.

Why it matters

Multi-agent systems are structurally political: agents have divergent objectives and contend for shared finite resources (context window, tool quotas, compute, API rate limits, human review time). Treating that contention as an implicit byproduct of scheduling rather than an explicit negotiation surface is where cross-agent deadlock and priority inversion come from.

Generalization

Any system with >1 optimizing agent over a shared budget needs an explicit mechanism for reconciling goals and allocating the scarce resource, not just a queue. The coordination protocol is a design artifact, not an emergent property.

Politics is simply how businesses and people within businesses reconcile different goals and limited resources.
Open source video
Dependency and scheduling conflicts require negotiation and relationship building across teams.
Open source video
Tradeoffmedium noveltyweak evidence

A half-day internal-tool change was contrasted between asking a manager for permission and simply making the change; proactive execution is claimed to build more value and trust than bureaucratic check-ins.

Why it matters

This is the autonomy-vs-authorization boundary stated in cost terms: permission-seeking has a real cost, and for cheap, bounded, low-blast-radius actions the coordination overhead exceeds the action. The implicit gating variable is reversibility and blast radius, not capability.

Generalization

Directly transferable to agent autonomy gating: derive an action's required authorization level from cost-to-reverse and blast radius, not from a blanket policy. Agents that ask before every low-risk write pay a latency and coordination tax; agents that never ask before irreversible writes trade that latency for unrecoverable error.

Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.
Open source video
The difference between seeking permission and showing initiative.
Open source video
Empirical Resultmedium noveltymoderate evidence

Only 30% of people ask for raises, but 70% of those who ask get something; the failure mode is not being refused but never issuing the request, and the productive framing is business value rather than personal need.

Why it matters

Quantifies the cost of non-escalation and shows that the request itself changes the outcome distribution. For agents, the analogous failure is terminating at a limit silently instead of surfacing a structured request — a silent-stop failure that is invisible in success-rate metrics because nothing errored.

Generalization

Escalation should be a designed, measured path with its own success rate. Two metrics matter: escalation rate (are agents asking when they should?) and grant rate conditional on asking (is the ask well-framed in the principal's terms?). A ask framed on the principal's objectives is more likely to succeed than one framed on the agent's own constraint.

Only 30% of people ask for raises; 70% of those who ask get something.
Open source video
Do not open negotiations with personal reasons ('I want a raise').
Open source video
Frame requests around business value, market rate, and high performance.
Open source video
Mechanismmedium noveltyweak evidence

Trust is defined as established when parties are willing to experience inconvenience or make sacrifices for each other, i.e. via costly, mutually observable concessions rather than cheap assurances.

Why it matters

Implies trust signal must be costly to be credible — which means trust calibration in a system requires memory of past cost-bearing events and the capacity to bear cost deliberately. Cheap commitments (promises, stated confidence, style) carry no calibration value.

Generalization

Applies to human-agent and agent-agent trust: an agent earns expanded permissions by demonstrably absorbing cost under constraints (degraded mode, budget sacrifice, delay) on prior tasks. Suggests a commitment ledger of kept costly commitments as the substrate for increasing autonomy, the way Amazon-style bar-raising documents function for promotion cases.

Trust is established when people are willing to experience inconvenience or make sacrifices for each other.
Open source video
Manager-employee relationships thrive when both parties make mutual concessions to achieve goals.
Open source video
Mental Modelmedium noveltyweak evidence

At higher organizational levels the unit of accountability shifts: an Amazon VP reportedly described his yearly goal as managing only, doing no individual work, and leaders at that level focus on organizational delivery rather than personal code contributions.

Why it matters

Level is defined by the granularity of the outcome being judged, not by seniority or model capacity. Applying individual-contributor success criteria to a coordinating role (or vice versa) produces a persistent eval mismatch: the agent looks like it is doing nothing important because the rubric scores the wrong unit of work.

Generalization

Maps to hierarchical agent architectures: an orchestrator agent scored on token-level or artifact-level correctness will be misjudged; it needs rubric at the delivery level (did the goal complete, at what cost, with what coordination failures), while worker agents are scored on artifact quality. Rubric must match role.

The mismatch in expectations between individual contributors and leadership regarding hands-on work.
Open source video
Leaders at higher levels focus on organizational delivery rather than individual code contributions.
Open source video

Deep dives

5

Intent provenance as a first-class audit field

Research question

Can declared objective provenance at decision time improve detection of adversarial versus cooperative agent action over behavior-only auditing?

Why

If the same action trace can be cooperative or adversarial depending only on whose utility is optimized, action logs and tool-call transcripts are insufficient audit artifacts for agent safety.

Influence is trying to persuade someone of something for mutual or their good.
Open source video
Manipulation is trying to convince someone of something primarily for your own good.
Open source video
Source video

Agent escalation instrumentation and ask framing

Research question

What are agent escalation rates and conditional grant rates, and does framing an ask around the principal's objective change the grant rate versus framing it around the agent's own constraint?

Why

Silent stops are invisible in error-based monitoring, so escalation must be a designed, measured path with its own success metrics.

Only 30% of people ask for raises; 70% of those who ask get something.
Open source video
Do not open negotiations with personal reasons ('I want a raise').
Open source video
Source video

Autonomy gating by reversibility and blast radius

Research question

How should an agent decide between acting directly and asking for authorization when gating is parameterized by cost-to-reverse, blast radius, and expected coordination latency?

Why

A blanket permission policy either pays an unnecessary coordination tax on cheap reversible actions or allows unrecoverable errors on irreversible ones.

Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.
Open source video
Source video

Trust ledger for permission expansion

Research question

Can a per-agent ledger of kept costly commitments predict appropriate permission expansion better than static, configuration-based permission policies?

Why

If trust is signaled through observed cost-bearing rather than stated confidence, then autonomy should be earned against durable memory of constrained execution, budget sacrifice, and correct refusal.

Trust is established when people are willing to experience inconvenience or make sacrifices for each other.
Open source video
Manager-employee relationships thrive when both parties make mutual concessions to achieve goals.
Open source video
Source video

Reporting layer as a separate evaluated component

Research question

Does a summarizing and prioritization layer improve principal decision quality and time-to-notice, or does it mainly add noise and consume attention budget?

Why

Producing work and getting credited for work are separate functions, so a system with no reporting layer can fail silently by being under-noticed regardless of output quality.

Hard work on its own does not lead to promotions.
Open source video
Most people approach work by working hard and hoping to be noticed.
Open source video
Source video

Article ideas

4

Your Agent's Action Log Cannot Tell You Whether It Was Manipulating

Because influence and manipulation differ only by intent, agent platforms need objective provenance and disclosure metadata as first-class telemetry rather than relying on behavior replay alone.

Angle

Agent safety and observability: behavior-only auditing is structurally blind to the cooperative/adversarial distinction.

Source video

The 30/70 Rule for Agents: Silent Stops Are the Real Failure Mode

Agent reliability metrics miss non-escalation; platforms should instrument escalation rate and conditional grant rate, and asks should be framed in the principal's objectives rather than the agent's constraints.

Angle

Reliability engineering: a confident silent stop looks like success in error-based monitoring.

Source video

The Reporting Layer Is Not Overhead: Why Multi-Agent Systems Need Advocacy

Production and credit are separate functions, so a multi-agent pipeline without a reporting or prioritization component will systematically under-credit its own work regardless of artifact quality.

Angle

Architecture: treat reporting as a component with its own precision, recall, and attention-budget metrics.

Source video

Role-Specific Rubrics for Hierarchical Agents

Applying artifact-correctness rubrics to orchestrator agents mis-scores the unit of work; hierarchical systems need delivery-level rubrics for coordinators and artifact-level rubrics for workers.

Angle

Evaluation design: level is defined by the unit of accountability, not by seniority or model capacity.

Source video

Project ideas

4

Intent Provenance Logger

gatehouse

Recording declared objective provenance per action improves human detection of adversarial agent behavior over behavior-only logs without increasing false positives on cooperative runs.

Proof of concept

Build a wrapper that requires agents to emit principal, beneficiary, and expected-utility fields alongside each tool call, then replay red-team scenarios with and without provenance in a review UI.

Measurement

Adversarial-behavior detection accuracy, time-to-detection, false-positive rate on cooperative traces, and reviewer confidence.

Source video

Escalation Instrumentation Harness

beyond-evals

Silent stops cluster around specific limit types, and asks framed on principal objectives have a higher conditional grant rate than asks framed on agent constraints.

Proof of concept

Instrument agent runs to log limit events, escalation attempts, ask framing, and outcomes; classify non-escalations by limit type and compute rates.

Measurement

Escalation rate, conditional grant rate, silent-stop count, and grant-rate difference by ask framing.

Source video

Reversibility-Gated Autonomy Controller

gatehouse

A gating policy based on cost-to-reverse, blast radius, and coordination latency reduces total task latency without increasing unrecoverable errors compared with always-ask and never-ask baselines.

Proof of concept

Simulate file, config, and resource operations across reversibility and blast-radius levels; sweep gating thresholds and compare against baselines.

Measurement

Total task latency, unrecoverable-error rate, unauthorized irreversible-action count, and ask frequency.

Source video

Trust Ledger for Autonomy Expansion

new

Permissions expanded from a ledger of kept costly commitments outperform static permission policies on task success and incident rate.

Proof of concept

Maintain a per-agent ledger of constrained executions, budget sacrifices, and correct refusals; grant autonomy after thresholds and compare with static permissions.

Measurement

Task success rate, incident rate, permission-expansion latency, and attempted ledger-spoofing events.

Source video

Architectural implications

5

Intent, not behavior, is the discriminator between cooperative and adversarial action, yet systems log only behavior.

Before

Audit artifacts consist of action traces, tool calls, and final outcomes; reviewers infer purpose from what the agent did.

After

Objective provenance — which principal's utility is being optimized, what was disclosed to the counterparty — is recorded alongside each action as a first-class field.

Consequence

Emergent adversarial behavior becomes detectable without needing to distinguish it from behavior alone; but the system must now carry and, where relevant, reveal intent metadata, which is itself a privacy and leakage surface.

Source video

Producing work and getting credited for work are separate functions.

Before

The worker component emits an artifact and assumes downstream consumers will rank and prioritize it correctly.

After

A distinct reporting layer whose job is to translate artifacts into the principal's priority frame, with its own eval (was it noticed at the right time?).

Consequence

Attention becomes an explicit, budgeted resource in the architecture; the reporting layer can itself become the bottleneck or a source of noise, so its precision/recall must be measured.

Source video

Agents that hit limits and stop silently are invisible in error-based monitoring.

Before

Failure detection is based on exceptions, timeouts, and error codes; a confident silent stop looks like success.

After

Escalation is a designed path with an instrumented request channel, plus metrics for escalation rate and grant rate conditional on escalation.

Consequence

Adds a coordination cost and a false-escalation failure mode (asking when action was warranted), so the gating policy must be tuned on reversibility and blast radius rather than applied uniformly.

Source video

Trust expansion is driven by observed cost-bearing, not by stated confidence.

Before

Permission levels are static or set from model-identity/configuration, independent of track record.

After

Permissions expand against a ledger of kept costly commitments (constrained execution, budget sacrifice, correct refusal) recorded per agent or per task class.

Consequence

Requires durable memory of commitment outcomes and a policy for revocation; also creates an incentive to manufacture visible cost, which is a gaming vector.

Source video

Role level determines the unit of accountability.

Before

One rubric (artifact correctness) is applied across worker and orchestrator agents.

After

Role-specific rubrics: orchestrators scored on delivery, coordination failures, and cost; workers scored on artifact quality.

Consequence

Evaluation becomes comparable only within role, so cross-role comparisons require an explicit conversion — otherwise well-functioning orchestrators read as low-output.

Source video

Tradeoffs and failure modes

5

Autonomy vs. authorization overhead

Benefit

Acting directly instead of seeking permission captured a half-day improvement and built trust in the cited example.

Cost or risk

Skipping the check-in removes the coordination point where blast radius, reversibility, and cross-team side effects would have been caught.

Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.
Open source video
Source video

Intent ambiguity in auditing

Benefit

A single influence mechanism (persuasion toward mutual benefit) can also be used to help others stand up to manipulators.

Cost or risk

The same mechanism is indistinguishable from manipulation when judged by behavior alone; ethics hinge entirely on non-observable intent.

High influence allows you to stand up to manipulators and help people.
Open source video
Source video

Trust through costly signaling

Benefit

Mutual concessions let the manager-employee relationship produce goals neither could reach alone.

Cost or risk

Building trust requires actually bearing inconvenience — a real, exploitable cost, and one that can be performed visibly without being real.

Trust is established when people are willing to experience inconvenience or make sacrifices for each other.
Open source video
Source video

Advocacy overhead vs. pure production time

Benefit

Visibility and advocacy are what convert output into promotion; relying on work alone yields average outcomes.

Cost or risk

Time spent on visibility and reporting is time not spent producing, and the reporting layer adds signal-to-noise risk for the consumer.

visibility and advocacy are required
Open source video
Source video

Framing a request as business value vs. personal need

Benefit

Framing requests around business value, market rate, and high performance aligns the ask with the principal's objectives and is claimed to succeed 70% of the time when made.

Cost or risk

This delegates the framing burden to the requester and rewards those who can translate their constraint into the principal's terms — capability that is unevenly distributed.

Frame requests around business value, market rate, and high performance.
Open source video
Source video

Open questions

5

Can intent (mutual benefit vs. self-benefit) be recovered from action traces, or must it be declared at decision time?

Why unresolved

The summary defines the distinction only by internal intent, never claiming any behavioral tell, and offers no mechanism for inspection.

Research direction

Build an intent-provenance schema for agent actions and test whether declared objectives at decision time improve adversarial-behavior detection over behavior-only auditing.

Source video

What is the agent equivalent of the 30% ask / 70% grant base rate, and how should escalation be instrumented?

Why unresolved

The summary gives a human survey-style figure with no source, and offers no analogous measurement for systems.

Research direction

Instrument agent runs to record escalation rate and conditional grant rate; check whether non-escalation clusters around specific limit types and whether the ask framing (agent constraint vs. principal objective) changes grant rate.

Source video

What variables should gate an agent between acting and asking?

Why unresolved

The summary asserts that proactive execution is better than check-ins but gives no threshold, and the counterexample (a half-day tool change) is cheap and reversible — the boundary is never stated.

Research direction

Sweep a gating policy parameterized by cost-to-reverse, blast radius, and expected coordination latency; measure error rate and total latency against always-ask and never-ask baselines.

Source video

Does an advocacy/reporting layer improve principal decisions, or just add noise?

Why unresolved

The summary asserts visibility is required for promotion but never addresses the cost to the decision-maker of consuming additional reports.

Research direction

Measure principal decision quality and time-to-notice with and without a summarizing layer, varying report frequency and ranking quality.

Source video

Can trust be modeled as a function of observed cost-bearing events, and does that model predict permission expansion?

Why unresolved

The claim is stated as a general assertion about people with no measurement, and no mechanism is offered for tracking or revoking earned trust.

Research direction

Maintain a per-agent ledger of kept costly commitments and test whether autonomy policies driven by it outperform static policies on task success and incident rate.

Source video

Key claims

9
causalVerification needed

Hard work on its own does not lead to promotions; visibility and advocacy are also required.

Evidence

Hard work on its own does not lead to promotions.

Question

Is there any outcome data showing that visibility/advocacy variables predict promotion independently of measured performance?

Source video
factualVerification needed

Only 30% of people ask for raises, but 70% of those who ask get something.

Evidence

Only 30% of people ask for raises; 70% of those who ask get something.

Question

What is the source, population, and time frame of these figures, and does the 70% include non-monetary concessions?

Source video
opinionVerification not requested

Influence and manipulation are distinguished by intent: mutual/other benefit vs. primarily one's own benefit.

Evidence

Manipulation is trying to convince someone of something primarily for your own good.

Source video
causalVerification needed

Trust is established when people experience inconvenience or make sacrifices for each other.

Evidence

Trust is established when people are willing to experience inconvenience or make sacrifices for each other.

Question

Is costly sacrifice necessary for trust formation, or is it one of several sufficient paths, and does performed cost without real cost have the same effect?

Source video
comparativeVerification needed

The relationship with one's manager is the single most important relationship at work.

Evidence

The relationship with your manager is the most important one at work.

Question

Compared against which other relationships (peers, cross-functional partners, reports), and measured against which outcomes?

Source video
opinionVerification not requested

Politics is how businesses and people reconcile different goals and limited resources, and it is a learnable skill set.

Evidence

Politics is simply how businesses and people within businesses reconcile different goals and limited resources.

Source video
comparativeVerification needed

Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.

Evidence

Proactive execution builds more value and trust than unnecessary bureaucratic check-ins.

Question

At what reversibility and blast-radius threshold does acting without checking in stop paying off?

Source video
causalVerification needed

Leaders at higher levels focus on organizational delivery rather than individual code contributions.

Evidence

Leaders at higher levels focus on organizational delivery rather than individual code contributions.

Question

Is the shift driven by level itself or by span of responsibility and number of dependents, and does the same shift hold in smaller organizations?

Source video
causalVerification needed

Requests framed around business value succeed more often than requests framed around personal need.

Evidence

Do not open negotiations with personal reasons ('I want a raise').

Question

Is the framing effect directionally supported by negotiation data, or is it an untested heuristic?

Source video

Connections

5