Bill Carr on Working Backwards, Single-Threaded Leadership, and Amazon's Management Operating System

Bill Carr on Working Backwards, Single-Threaded Leadership, and Amazon's Management Operating System

transcriptlennys-podcastamazonworking-backwardspr-faqsingle-threaded-leadershipinput-metricshiringmanagementprocess-innovation

Bill Carr on Working Backwards, Single-Threaded Leadership, and Amazon’s Management Operating System

Source: Lenny’s Podcast Speaker: Bill Carr Date: ~2023 Link: https://www.lennysnewsletter.com/p/unpacking-amazons-unique-ways-of

Key ideas

  • Working Backwards PR/FAQ process. New product or feature development begins with a fictional press release: three money paragraphs defining the customer, the specific problem, and the proposed solution — written before any engineering begins. Serves as a forcing function for clarity. Iterated in concentric circles from single author → small group → wider group → CEO, but not every PR/FAQ survives to the next ring. The goal is a product funnel not a tunnel: write many, kill most, build only the best. Separates the “deciding what to build” process from the “how to ship it” process. Fire Phone is the cautionary counter-example: technology-first (3D effects) in search of a problem, not customer problem first.
  • Input vs output metrics. Inspired by Good to Great: identify the input metrics that causally drive customer value (selection breadth, price levels, page load time, shipping speed) and manage those rigorously. Output metrics (revenue, free cash flow, customer growth) follow as an “article of faith.” Amazon’s S-Team goals list of ~500 items contained only 10 financial metrics — the rest were inputs. Compound metrics (Amazon called early experiments “fitness functions”) obscure causality and should be abandoned in favour of individually tracked metrics. Input metrics must be: customer-touching, controllable by the team, and causally linked to outputs.
  • Single-threaded leadership. Shift from project orientation (cross-functional teams swarm a project, then disperse) to program orientation (a permanent team with a single leader owns a product area and all its dedicated resources). Benefit: clear ownership, speed, agility — management referees team resource allocation once or twice a year rather than refereeing every roadmap item. Cost: functional excellence risk when generalist leaders manage specialists outside their domain. Countermeasures: C-level functional leaders maintain company-wide standards (promotion criteria, code review standards, interview methodology); senior ICs hold cross-company functional roles in addition to their day job.
  • Disagree and commit. The least understood of Amazon’s leadership principles. The disagree obligation: when you have a new data point, new angle, or new concern, you are obligated to voice it — all the way up the chain if necessary. The commit trigger: once the decision-maker demonstrates they have genuinely heard and considered your argument (even if they decide differently), you commit fully and find the kernel of the other person’s reasoning to champion. Grudging compliance is not commitment. Fire drill context: data rarely makes decisions — judgment and interpretation do, which is why “leaders are right a lot” (through experience, not omniscience) matters.
  • Bar Raiser hiring process. On every interview loop, one person who is neither the hiring manager nor their report acts as Bar Raiser: runs the debrief, nominally holds veto power (rarely invoked), and enforces objective criteria (leadership principles + behavioural interviewing) rather than letting urgency bias or prior-company standards dominate. Hiring manager retains final decision. Purpose: prevent “new people hiring new people” degradation during hypergrowth. Strong development vehicle for earlier-career leaders given added responsibility. Originally borrowed from Microsoft’s “As Appropriate” process.

Overview

Bill Carr — co-author of Working Backwards (with Colin Bryar); joined Amazon in 1999, spent 15 years, ultimately VP Digital Media (launched Amazon Music, Prime Video, Amazon Studios) — unpacks the management operating system Amazon developed in the 2003–07 window of complexity: the PR/FAQ process for product development, single-threaded leadership as an org structure, input vs output metrics, disagree-and-commit, and the Bar Raiser hiring programme. Highly practical: covers origin stories, failure modes (Fire Phone, fitness functions), countermeasures, and implementation advice for other companies. Closes with Lightning Round and consulting services (Working Backwards LLC).