Visual summary of operating lessons from Bill Carr.

Lessons from Bill Carr

As Vice President of Digital Media at Amazon, Bill Carr managed the development of Amazon Music, Prime Video, and Amazon Studios. He co-authored Working Backwards to document the management practices used to scale the company. This collection organizes his explanations of those mechanisms into practical rules for hiring, product design, and organizational structure.

Part 1: The PR/FAQ Process

  1. On starting at the end: "You write the press release as if the product has already launched, which forces you to clearly articulate the customer benefit before a single line of code is written." — Source: [Working Backwards]
  2. On filtering ideas: "If the mock press release doesn't sound compelling to the team, we don't build the product. It saves millions of dollars in wasted engineering time." — Source: [Lenny's Podcast]
  3. On the FAQ section: "The frequently asked questions section is where you have to answer the hardest questions from both the customer's perspective and the internal business perspective." — Source: [a16z Podcast]
  4. On customer-centric design: "The PR/FAQ is a tool that physically forces the team to obsess over the customer experience rather than their own technical capabilities." — Source: [Product Mastery Now]
  5. On iterating the vision: "You don't just write a PR/FAQ once. You share it, get brutal feedback, and rewrite it. Sometimes it takes twenty drafts to get it right." — Source: [Working Backwards]
  6. On avoiding marketing spin: "The press release must be written in simple, jargon-free language. If it reads like marketing fluff, you haven't identified the true value." — Source: [Seeking Wisdom Podcast]
  7. On resource allocation: "We wouldn't allocate budget or headcount until the PR/FAQ was approved by leadership. It was the gatekeeper for new initiatives." — Source: [Working Backwards]
  8. On price and cost: "You have to specify the price in the PR/FAQ. This forces the team to figure out how to build it at a cost that makes that price profitable." — Source: [a16z Podcast]
  9. On clarity of thought: "Writing a good PR/FAQ is incredibly hard because clear writing requires clear thinking. You can't hide behind a bulleted list." — Source: [Lenny's Podcast]
  10. On long-term vision: "The PR/FAQ isn't about what we can build next quarter; it's about what the customer will want in three years." — Source: [Working Backwards]

Part 2: Single-Threaded Leadership

  1. On focus: "The best way to fail at inventing something is by making it somebody's part-time job." — Source: [Working Backwards]
  2. On accountability: "A single-threaded leader wakes up every day thinking about only one thing. If the project fails, they can't blame it on competing priorities." — Source: [Lenny's Podcast]
  3. On resource independence: "Single-threaded teams need to be separable. They should have their own engineers, product managers, and budget so they don't have to wait on other teams." — Source: [Working Backwards]
  4. On organizational drag: "Coordination is a tax. Single-threaded teams reduce the coordination tax by keeping dependencies within a small, autonomous group." — Source: [a16z Podcast]
  5. On identifying leaders: "You don't need a massive team to start. You just need one capable, single-threaded leader who is fully empowered to figure it out." — Source: [Seeking Wisdom Podcast]
  6. On team size: "We started with two-pizza teams, but realized the size of the team mattered less than having a single leader whose sole focus was the project's success." — Source: [Working Backwards]
  7. On shifting priorities: "When we realized a project was moving too slow, the first question we asked was, 'Who is the single-threaded leader for this?' Often, there wasn't one." — Source: [GeekWire Podcast]
  8. On empowerment: "We give these leaders the authority to make decisions without constantly seeking approval from a committee." — Source: [Product Mastery Now]
  9. On mitigating risk: "Having a single-threaded leader actually lowers risk, because someone is watching the details of the project full-time." — Source: [Working Backwards]
  10. On scaling: "You can't scale a company if the CEO has to make every decision. Single-threaded leadership is how you scale decision-making." — Source: [a16z Podcast]

Part 3: The Bar Raiser Hiring Model

  1. On hiring standards: "Every new hire should raise the average level of performance for their specific role. If they don't, you are slowly diluting your talent pool." — Source: [Working Backwards]
  2. On the Bar Raiser role: "The Bar Raiser is an interviewer outside the hiring manager's chain of command, ensuring an objective evaluation of the candidate." — Source: [Lenny's Podcast]
  3. On hiring manager bias: "Hiring managers are often desperate to fill a seat. The Bar Raiser provides a necessary check against the urgency to hire a mediocre candidate." — Source: [Working Backwards]
  4. On veto power: "A Bar Raiser can veto any hire, and their decision cannot be overruled by the hiring manager. This structural power is what makes the mechanism work." — Source: [Seeking Wisdom Podcast]
  5. On evidence-based hiring: "We don't use gut feel. Interviewers must provide specific data points and examples from the candidate's past behavior." — Source: [Working Backwards]
  6. On written feedback: "Before discussing a candidate, every interviewer must write down their feedback and vote to hire or not hire. This prevents groupthink." — Source: [a16z Podcast]
  7. On the debrief meeting: "The Bar Raiser leads a Socratic discussion during the debrief, pushing interviewers to defend their assessments with facts." — Source: [Working Backwards]
  8. On behavioral interviewing: "Past behavior is the best predictor of future behavior. We drill down into specific examples rather than hypothetical scenarios." — Source: [Product Mastery Now]
  9. On training Bar Raisers: "Becoming a Bar Raiser is a rigorous process. You have to shadow dozens of interviews and prove you deeply understand the leadership principles." — Source: [Working Backwards]
  10. On long-term impact: "The Bar Raiser program is arguably the most important process at Amazon, because the quality of your people dictates the quality of your products." — Source: [GeekWire Podcast]

Part 4: Six-Page Narratives and Meetings

  1. On banning PowerPoint: "PowerPoint is great for the presenter but terrible for the audience. It hides a lack of deep thinking." — Source: [Working Backwards]
  2. On the six-page memo: "We replaced slide decks with six-page narrative memos. It forces the author to connect their ideas logically and defend their assumptions." — Source: [a16z Podcast]
  3. On reading in meetings: "The first twenty minutes of a meeting are spent reading the memo in total silence. This ensures everyone is actually prepared." — Source: [Lenny's Podcast]
  4. On leveling the playing field: "Written narratives equalize the room. A great idea from a quiet engineer can win over a bad idea from a charismatic executive." — Source: [Working Backwards]
  5. On the structure of narratives: "The memo must have a clear context, a proposed solution, and an honest discussion of the risks and alternatives." — Source: [Product Mastery Now]
  6. On iterative writing: "A good six-pager is never written in a day. It is drafted, reviewed by peers, and refined over weeks before it goes to a leadership team." — Source: [Working Backwards]
  7. On information density: "A six-page memo contains exponentially more information than a one-hour slide presentation. It allows leaders to make faster, better decisions." — Source: [Seeking Wisdom Podcast]
  8. On appendices: "The main narrative is strictly limited to six pages, but you can attach as much data as you want in the appendix for those who want to dig deeper." — Source: [Working Backwards]
  9. On active consumption: "Reading a document forces the executive to actively engage with the material, rather than passively listening to a pitch." — Source: [a16z Podcast]

Part 5: Managing Inputs and the WBR

  1. On the Weekly Business Review (WBR): "The WBR is a tactical, data-driven meeting meant to identify anomalies in the business, not to solve them in the room." — Source: [Working Backwards]
  2. On input vs. output metrics: "You can't manage outputs like revenue or stock price. You can only manage the inputs—the specific activities that drive the results." — Source: [Lenny's Podcast]
  3. On leading indicators: "We spent massive amounts of time identifying the right controllable input metrics, like delivery speed or inventory selection." — Source: [Working Backwards]
  4. On avoiding vanity metrics: "We don't care about metrics that always go up and to the right. We want metrics that tell us if the customer experience is actually improving." — Source: [a16z Podcast]
  5. On standardized reporting: "The WBR deck is highly standardized. Once you learn how to read it, you can digest the health of a massive business in an hour." — Source: [Working Backwards]
  6. On exceptions over status updates: "In the WBR, leaders only speak to exceptions—metrics that are out of bounds. We don't do status updates for things working as expected." — Source: [Seeking Wisdom Podcast]
  7. On auditing the data: "You have to constantly audit your metrics. Just because a dashboard says an order was delivered on time doesn't mean the customer actually received it." — Source: [Working Backwards]
  8. On the root cause: "When a metric is off, we use the Five Whys to drill down past the superficial explanation and find the structural defect." — Source: [Product Mastery Now]
  9. On anecdote vs. data: "When the data and the anecdotes disagree, the anecdotes are usually right. It means your data is measuring the wrong thing." — Source: [Working Backwards]

Part 6: Digital Media and Amazon Studios

  1. On transitioning to digital: "We knew the physical media business was going away. The challenge was cannibalizing our own DVD and CD sales before someone else did." — Source: [Working Backwards]
  2. On launching video: "Our first attempt at digital video was clunky and not customer-centric. We had to learn from that failure to eventually build Prime Video." — Source: [a16z Podcast]
  3. On bundling with Prime: "Adding video to Amazon Prime wasn't obvious at first, but it became the ultimate retention tool for the subscription." — Source: [Working Backwards]
  4. On the origin of Amazon Studios: "We realized that simply licensing content wouldn't differentiate us. We had to create our own original programming to own the customer relationship." — Source: [Lenny's Podcast]
  5. On applying data to Hollywood: "We tried to apply Amazon's data-driven pilot process to script development. It worked in some ways, but we learned that creative intuition still matters." — Source: [GeekWire Podcast]
  6. On negotiating with studios: "The established media companies viewed us as a threat. We had to convince them that a digital partnership was their only path to survival." — Source: [Working Backwards]
  7. On hardware ecosystems: "Digital media requires an ecosystem. You can't just sell the file; you have to build the device and the software that makes consumption seamless." — Source: [a16z Podcast]
  8. On global expansion: "Scaling a digital rights business globally requires intense localized effort. Copyright law doesn't scale easily across borders." — Source: [Working Backwards]
  9. On patience with new businesses: "Amazon Music and Video took years of massive investment before they became core pillars of the company. You have to be willing to be misunderstood for long periods of time." — Source: [Seeking Wisdom Podcast]

Part 7: Customer Obsession and Invention

  1. On true customer obsession: "It’s not just listening to customers; it’s inventing on their behalf. Customers didn’t ask for Prime, but it was exactly what they wanted." — Source: [Working Backwards]
  2. On systemic innovation: "Invention shouldn't rely on a lone genius. It should be a systemic, repeatable process embedded in the company's daily operations." — Source: [Lenny's Podcast]
  3. On the cost of failure: "If you are going to invent, you have to be willing to fail. If you know it’s going to work in advance, it’s not an experiment." — Source: [GeekWire Podcast]
  4. On wandering: "There is a difference between efficient execution and wandering. You need both. Wandering is where the big breakthroughs happen." — Source: [Working Backwards]
  5. On competitor focus: "If you focus on competitors, you have to wait until there is a competitor doing something. Being customer-focused allows you to go out ahead." — Source: [a16z Podcast]
  6. On raising expectations: "Customer expectations are never static. As soon as you deliver a great experience, that becomes the new baseline. You must constantly improve." — Source: [Product Mastery Now]
  7. On solving hard problems: "The best products solve problems that customers have accepted as a necessary evil. Find those pain points and engineer them away." — Source: [Working Backwards]
  8. On removing friction: "Any friction in the customer journey is a defect. Our job was to relentlessly identify and remove that friction." — Source: [Seeking Wisdom Podcast]
  9. On long-term trust: "You build trust by doing the hard things well over a long period of time. There are no shortcuts to customer loyalty." — Source: [Working Backwards]

Part 8: Culture and Scaling Organizations

  1. On mechanisms over intentions: "Good intentions don't work. When there is a problem, you don't ask people to try harder; you build a mechanism to fix the root cause." — Source: [Working Backwards]
  2. On leadership principles: "Leadership principles aren't inspirational posters. They are practical tools used daily to make hard business decisions." — Source: [Lenny's Podcast]
  3. On disagree and commit: "You can argue fiercely about an idea, but once a decision is made, you must fully commit to its success, even if you disagreed." — Source: [a16z Podcast]
  4. On organizational debt: "As companies grow, they accumulate processes that slow them down. You have to actively prune the bureaucracy." — Source: [Working Backwards]
  5. On truth-seeking: "Our culture values truth over harmony. We want the data and the narrative to expose the unvarnished reality of the business." — Source: [Seeking Wisdom Podcast]
  6. On bias for action: "Speed matters in business. Many decisions are reversible two-way doors. Make them quickly and adjust if you are wrong." — Source: [Product Mastery Now]
  7. On frugality: "Constraints breed resourcefulness. By not throwing money at problems, you force teams to invent more elegant solutions." — Source: [Working Backwards]
  8. On diving deep: "Leaders operate at all levels. They stay connected to the details and don't assume that a high-level summary tells the whole story." — Source: [GeekWire Podcast]
  9. On operational excellence: "Scaling a business requires a relentless commitment to operational rigor. You have to inspect what you expect." — Source: [Working Backwards]