Book summary “Working Backwards”: summary

Introduction

You face a difficult challenge when your business grows past the startup phase. You watch agility fade, communication break down, and meetings turn into unproductive theater. You struggle to maintain high standards while hiring rapidly and launching new products.

Amazon’s phenomenal growth and success stem not from genius intuition, but from codifying scalable operational mechanisms around customer obsession, hiring, communication, and metrics.

Colin Bryar and Bill Carr spent a combined twenty-seven years as executives at Amazon. They witnessed firsthand the creation of Prime, Kindle, and Amazon Web Services. They show you how the company replaced good intentions with reliable mechanisms that run the business day after day.

You will learn how the company operates through six core areas:

• How do you build operational mechanisms that outlast your personal oversight?
• How do you protect your hiring standards as your workforce scales rapidly?
• How do you structure teams to eliminate gridlock and accelerate innovation?
• How do you replace slide decks with written narratives to force deep critical thinking?
• How do you work backwards from the customer before building any product?
• How do you manage controllable input metrics instead of chasing output results?

1. Building Blocks and Mechanisms

Good intentions cannot solve recurring problems or enforce cultural standards; companies must implement concrete mechanisms to translate principles into action.

Amazon's 14 Leadership Principles evolved from an initial codification project to serve as the living, breathing constitution of the company.

As the company grew rapidly, human resources set out to capture the implicit ethos of effective leaders through interviews. This effort resulted in a structured set of actionable guidelines used in every hiring decision and performance review.

Robin Andrulevich spent nine months interviewing leaders across Amazon to codify the original set of principles. Jeff Bezos formally announced them in early 2005.

Mechanisms Over Intentions

Amazon relies on systemic mechanisms like annual planning, S-Team goals, and long-term equity compensation to structurally align employee actions with customer and shareholder interests. You replace vague hopes for improvement with structured operational cadences like OP1, OP2, and regular reviews of input metrics.

Structuring executive compensation around long-term equity rather than short-term cash bonuses eliminates perverse incentives that sacrifice future value for quarterly targets. Amazon limits maximum base salaries and weights senior leadership compensation heavily toward multi-year equity. This prevents executives from playing games with revenue timing, overspending marketing budgets, or cutting maintenance to hit temporary milestones.

While the authors were at Amazon, the maximum base salary for any employee was capped at $160,000.

Annual Planning and Compensation

The annual planning process combines bottom-up operating proposals with top-down executive goals through two distinct phases known as OP1 and OP2. OP1 runs through the fall. Every product and business team engages in four to eight weeks of intensive planning during the summer to align their bottom-up proposals with company-wide expectations.

During this planning phase, you follow specific steps:

• Assess past performance including achieved goals, missed goals, and lessons learned
• Outline key initiatives for the following year
• Prepare a detailed income statement
• Submit requests and justifications for resources such as new hires, marketing spend, and fixed assets

OP2 adjusts these plans in January based on final fourth-quarter results to set the final plan of record. S-Team goals focus heavily on controllable input metrics and are aggressive enough that management only expects about three-quarters of them to be fully achieved.

Senior executives select hundreds of specific, measurable, attainable, relevant, and timely goals from team operating plans. These goals receive rigorous quarterly tracking using status indicators to ensure execution details are managed closely. The S-Team might select 6 goals out of 23 submitted by the Amazon Music team to prioritize resource allocation throughout the year.

2. Hiring and the Bar Raiser Process

Rapid growth requires a rigorous hiring model to select missionaries who embody corporate leadership principles rather than mercenaries seeking a quick financial gain. Conventional hiring often suffers from urgency bias, unstructured interviews, and confirmation bias. Amazon developed the Bar Raiser process to avoid these pitfalls and ensure every hire raises the talent bar.

Personal bias causes managers to hire people who resemble them in background and experience, which damages diversity and limits workforce performance.

Managers often pick candidates from résumés who feel familiar, using superficial similarities that have nothing to do with actual job performance, leading to un-diverse teams with a narrower field of vision. A middle-aged manager from the University of Michigan who worked at McKinsey and plays golf tends to be drawn to candidates with similar attributes.

Hiring urgency creates desperation that leads to shortcuts, poor processes, and permanent, haphazard shifts in corporate culture. Fast-growing companies understaffed and working on tight deadlines often bypass formal hiring frameworks, letting urgency and convenience drive choices instead of data, which changes the corporate culture for better or worse. Sequoia Capital noted that the average Silicon Valley startup spends 990 hours to hire 12 software engineers, averaging more than 80 hours per hire.

The Bar Raiser Solution

Amazon created the Bar Raiser program as a mechanism to maintain consistent hiring standards and prevent falling talent levels during rapid employee growth. When early leaders noticed that new managers were hiring subpar talent, they codified a scalable interview process instead of relying on good intentions, naming twenty original Bar Raisers with veto power over hiring managers. In the early days, Amazon grew from roughly 600 employees in 1997 to 9,000 in 2000, and then to 100,000 by 2013.

The Bar Raiser hiring process relies on a strict, repeatable eight-step framework designed to eliminate bias and evaluate candidate substance. The formal sequence includes job descriptions, résumé reviews, phone screens, in-house interviews, written feedback, debrief meetings, reference checks, and offer through onboarding, with the Bar Raiser maintaining program integrity and holding veto power.

• Job Description
• Résumé Review
• Phone Screen
• In-House Interview
• Written Feedback
• Debrief/Hiring Meeting
• Reference Check
• Offer Through Onboarding

Behavioral interviewing uses specific past performance and the STAR method to evaluate how well a candidate aligns with company leadership principles. Instead of open-ended career walks, interviewers assign specific leadership principles and ask probing questions to extract what the candidate personally contributed versus what the overall team accomplished.

• What was the situation?
• What were you tasked with?
• What actions did you take?
• What was the result?

Mandatory written feedback and collaborative debrief meetings allow interviewers to make hiring decisions based on aggregated data rather than isolated impressions. Interviewers must submit detailed notes and a strict vote without seeing others' feedback first, and a Bar Raiser then leads a debrief where all transcripts are read and votes can be revised using additional data.

• strongly inclined to hire
• inclined to hire
• not inclined to hire
• strongly not inclined to hire

3. Organizing for Innovation and Speed

As your company expands, tightly coupled software and organizational structures create dependencies that exponentially increase coordination costs. You experience these bottlenecks when teams spend excessive time seeking approvals through layers of management or shared code blocks.

Eliminating human communication overhead through two-pizza teams, APIs, and single-threaded leaders prevents organizational gridlock.

Colin experienced technical bottlenecks working on the Amazon Associates Program due to monolithic website code named Obidos and a database change review board known as the DB Cabal. Revenue growth surged from $148 million to over $3.1 billion between 1997 and 2001, which severely strained these shared systems. Better cross-team coordination proved to be the wrong answer to this growth challenge.

The Cost of Dependencies

Early company attempts to manage dependencies relied on global prioritization mechanisms like New Project Initiatives, which created heavy administrative burdens, high error margins, and drained team morale. NPI was designed to rank projects globally across the company once every quarter. Teams submitted proposals requiring resources from outside their own groups, which generated long meetings and frequent situations where you had to staff other projects while maintaining your own workloads.

Getting NPI'd meant your team had to fully staff other approved projects before your own internal projects. 30 or 40 attendees were on hand to review a full list of projects during NPI scoping meetings. Projected feature estimates typically carried a wide cost and return range of 4 million to 20 million dollars.

Two-Pizza Teams and APIs

Better coordination was the wrong answer because organizations must instead eliminate human communication overhead through loosely coupled interactions via APIs. Werner Vogels recalled the serious introspection period that led Amazon to adopt a service-oriented architecture long before it became an industry buzzword. Isolating software components through a microservices-based architecture eliminates cross-team dependencies and accelerates development by requiring requests exclusively through published APIs.

CIO Rick Dalzell defined the two-pizza team model where groups were small enough to be fed by two large pizzas, completely autonomous, self-funding, and responsible for their own design, technology, and business results. You must design teams to meet specific operating rules:

• be small, with no more than ten people;
• be autonomous, having no need to coordinate with other teams to get work done;
• be evaluated by a well-defined fitness function;
• be monitored in real time;
• be the business owner;
• be led by a multidisciplined top-flight leader;
• be self-funding;
• be approved in advance by the S-Team.

The Inventory Planning team met with leadership to establish boundaries and metric weightings like in-stock product pages displayed versus holding cost. Their fitness function used a 50 percent weighting for new distinct items added, a 30 percent weighting for units of new distinct items sold, and a 20 percent weighting for page views those distinct items received. Software systems under this model maintained 24 hours a day, 7 days a week operation monitoring requirements.

Single-Threaded Leaders

Making an initiative someone's part-time job frequently leads to failure due to competing priorities. You achieve successful launches of complex company initiatives by assigning single-threaded leaders with dedicated teams to replace part-time project assignments.

Fulfillment by Amazon struggled for over a year as a part-time initiative until Tom Taylor was freed from other responsibilities to lead it full-time in 2005. This focus enabled the successful September 2006 launch date for Fulfillment by Amazon, an operation managed by executives overseeing 26 total initiatives before delegating parts to managers.

4. Communicating Without PowerPoint

PowerPoint presentations strip discussions of important nuance and rely heavily on the presenter's salesmanship. Written narratives provide higher information density and allow decision-makers to absorb complex, interconnected arguments quickly.

Banning PowerPoint in favor of dense written narratives forces deeper thinking and improves executive decision-making.

On June 9, 2004, Colin Bryار sent an email mandated by Jeff Bezos announcing that PowerPoint presentations were banned at weekly S-Team meetings. Weekly S-Team meetings typically had a 4 hours runtime. A typical Word document contained 3,000 to 4,000 characters per page. Analyzed PowerPoint slide presentations averaged 440 characters per page. Standard narrative documents had a 6 pages maximum length. You can estimate reading speed for complex information at 3 minutes per page.

You must follow these steps to manage written communications:

• Stop using presentation software like PowerPoint.
• Use Microsoft Word for written narratives.
• Distribute narratives at the start of the meeting for silent reading.
• Dedicate the first 20 minutes of a 60-minute meeting to reading the document.
• Begin discussion only after everyone has finished reading.

The Six-Pager and Tenets

Effective six-pagers utilize structured components like tenets and FAQs to address counterarguments and establish baseline principles. Including foundational tenets gives readers an anchor point to evaluate proposals, while a frequently asked questions section proactively addresses potential misunderstandings and opposing views.

Quarterly business reviews at Amazon are structured with specific sections covering accomplishments, misses, headcount, P&L, and appendices.

You should build your documents using these practices:

• Include an introduction to state the proposal.
• Define key tenets that the proposal relies upon.
• Detail accomplishments and misses for operational reviews.
• Provide proposals for the next period, headcount, and P&L.
• Add an FAQ to anticipate counterarguments and points of contention.
• Attach appendices with supporting data, spreadsheets, and mock-ups.

Feedback as Collaboration

Reviewers must treat narrative feedback as an active collaboration, adopting a critical mindset that challenges underlying assumptions. Deep critical reading involves treating every sentence as potentially incorrect until proven otherwise, helping to uncover hidden flaws and improve the overall product or policy.

Challenging the assumption that a 60-day return window was inherently customer-friendly led Amazon to create the friction-free refund policy, compared to the 30 days offered by competitors.

You should apply these behaviors during reviews:

• Assume each sentence in a narrative is wrong until proven otherwise.
• Challenge the content of the writing rather than the motives of the writer.
• Question implicit assumptions regarding customer benefit.
• Take comprehensive notes during the discussion stage on behalf of the entire audience.

5. Working Backwards: The PR/FAQ

Rather than building technology first and finding a use for it, product development starts with the desired customer experience. You work backward iteratively until the team achieves absolute clarity. Colin Bryar and Bill experienced this process across early digital media product developments and S-Team reviews.

Product development must start with the desired customer experience by drafting a press release and an FAQ before any engineering or hiring begins.

Jeff Amazon challenged digital media teams who presented traditional MBA-style PowerPoint slides and Excel models by asking for visual mock-ups. He ultimately demanded a narrative press release and FAQ. This working forward alternative prevents half-baked thinking and aligns everyone on customer value before committing resources.

When Bill and his digital media team proposed digital music and e-books using spreadsheets and PowerPoint, Jeff repeatedly asked for mock-ups and details. That pressure led to the invention of narrative documents and the Kindle press release.

Crafting the Press Release

A standard PR/FAQ consists of a concise press release under one page and an FAQ under five pages. You cover customer needs, economics, dependencies, and feasibility. Limiting the length acts as a forcing function that cultivates better thinkers and communicators.

You must follow specific steps when you draft the announcement:

• Write the press release heading using a name target customers will understand.
• Add a one-sentence subheading describing the target customer and their benefits.
• Write a summary paragraph starting with the city, media outlet, and proposed launch date.
• Describe the customer problem from the customer's point of view in the problem paragraph.
• Write solution paragraphs detailing how the product simply and easily solves the customer's problem.
• Add a quote from a spokesperson and a second quote from a hypothetical customer describing benefits, plus a link for more information.

Building the Internal FAQ

The press release highlights the customer experience. The internal FAQ addresses external customer questions and internal operational, technical, financial, and legal risks.

The book illustrates a fictitious product called Melinda, a smart mailbox costing $299 that securely receives and chills grocery and e-commerce deliveries. It is accompanied by a detailed internal FAQ addressing its bill of materials and third-party dependencies. The estimated bill of materials to manufacture Melinda is $250, requiring a team of 77 people with an annualized cost of $15 million.

You must build out the internal document with rigorous detail:

• Address Consumer Needs and Total Addressable Market by filtering out customers lacking space, power, or budget.
• Include per-unit economics, gross profit, contribution profit, and a mini P&L in the FAQ.
• Analyze third-party dependencies and detail how external partners or couriers will interact with the product.
• Outline technical, UI, and legal feasibility challenges and financial risk management for the up-front investment.

Reviewing PR/FAQs requires stakeholders to read the document in silence before engaging in rigorous line-by-line debate. Senior leaders always speak last. Teams write multiple drafts and hold meetings where participants read copies silently, ask hard questions, and request extensive revisions before presenting to executive leaders.

6. Metrics: Manage Inputs, Not Outputs

Sustainable growth requires monitoring controllable input metrics and reviewing performance through rigorous operational mechanisms.

Companies often focus on lagging output metrics like revenue or share price. Leaders cannot control outputs directly. You must track specific activities that directly drive those results over time. Mistaking one for the other leads to poor operational focus.

A Fortune 500 CEO celebrated a 30-cent rise in share price as if he had caused it directly. In the year 2000, Amazon recognized $2.76 billion in annual revenue. During that same holiday season, net sales increased by 44 percent in Q4 compared to the previous year.

The Flywheel and Input Metrics

The Amazon flywheel is a closed-loop model showing how controllable input metrics drive customer experience, traffic, sellers, selection, and lower cost structures to generate growth. Energy injected into any element accelerates the entire cycle. In 2001, Jeff Bezos drew this virtuous cycle on a napkin, inspired by Jim Collins's book Good to Great.

Choosing the wrong input metric misdirects team behavior. Amazon retail teams initially rushed to create thousands of new detail pages. This only increased inventory holding costs rather than sales. Refining the metric to view counts, in-stock status, and finally Fast Track In Stock corrected team focus toward high-impact products, setting the standard at 95 percent for each category.

Organizations must eliminate internal bias in data collection and use the Five Whys method to uncover true root causes behind operational anomalies. Charlie Bell noted that the probability of identifying an actual root cause within the first 24 hours of a problem is close to zero without deep investigation.

• Define the specific metrics you want to measure to deliver clear guidance.
• Measure data using unbiased collection tools and audit them regularly.
• Analyze data to separate signals from noise and uncover root causes of variation.
• Improve processes based on robust metrics and verified root-cause understanding.
• Control processes to ensure normal operation and automate repeatable tasks.

The Weekly Business Review

The Weekly Business Review deck maintains a consistent, end-to-end view of the business using charts, graphs, and multi-timeline comparisons. It plots results against comparable prior periods and includes two or more timelines, such as trailing 6-week and trailing 12-month views side by side. Amazon measures page views with a chart showing 6 data points for trailing 6 weeks on the left graph and 12 data points for the trailing year month by month on the right.

Numerical data should be combined with real-life customer anecdotes and exception reports to uncover hidden defects. A customer service story revealed that an edge-case bug was barraging credit cards with $1.00 pre-authorizations, causing a card to be declined when buying medicine for a child.

• Review top-ten contribution profit negative products to investigate automated purchasing system data errors, manual order entry mistakes, faulty cost allocation, shipping fee discrepancies, or low-price high-shipping-cost items.

10 Key Ideas

1. Amazon achieves sustainable growth by codifying scalable operational mechanisms around customer obsession, hiring, communication, and metrics instead of relying on good intentions or genius intuition.
2. Personal bias in traditional hiring is neutralized through the Bar Raiser program, which employs a strict eight-step framework and behavioral interviewing to protect corporate culture and talent standards.
3. Organizations eliminate human communication overhead and accelerate innovation by structuring autonomous, self-funding two-pizza teams that interact exclusively through published APIs.
4. Assigning single-threaded leaders with dedicated teams to high-priority initiatives prevents the failures commonly caused by competing priorities and part-time project assignments.
5. Banning PowerPoint presentations in favor of dense six-page written narratives forces deep critical thinking and significantly improves executive decision-making.
6. Reviewers treat narrative feedback as active collaboration by reading documents in silence, challenging underlying assumptions, and assuming each sentence is wrong until proven otherwise.
7. Product development begins with the desired customer experience by drafting a press release and an FAQ before any engineering or hiring begins.
8. Sustainable business growth requires tracking and managing controllable input metrics rather than chasing lagging output results like revenue or share price.
9. Choosing the right input metrics—such as Fast Track In Stock percentages—directs team behavior toward high-impact customer value instead of wasteful activities.
10. The Weekly Business Review maintains a consistent, end-to-end view of operations by combining multi-timeline data graphs with real-life customer anecdotes and exception reports to uncover hidden defects.