Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Think Like Amazon

Think Like Amazon

50 1/2 Ideas to Become a Digital Leader
Build a company that adapts quickly without mistaking new technology for real transformation.
by ROSSMAN 2019 320 pages
4.08
440 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat digital as speed and agility built for the long term

Digital means competing differently. Rossman argues that digital is not a synonym for websites, mobile apps, or cloud software. It is the ability to serve customers faster and adapt quickly when their needs or markets shift. Speed comes from reliable, repeatable operations; agility comes from sensing change and responding. Both require technology, data, new business models, and habits that reach beyond the IT department.

Invest before the deadline. Amazon’s second headquarters search is presented as a response to a long-term growth constraint: recruiting and retaining technology talent in Seattle. The point is to spot a bottleneck early, before it becomes a crisis. Rossman also recalls that AWS grew out of an effort to make Amazon’s own computing infrastructure more reliable, then became a service for external developers. Digital capability can emerge from solving a real operating problem, not from launching a transformation campaign.

Analysis

The useful distinction is between adopting tools and changing the tempo of an organization. A company can buy cloud services and still make decisions at the pace of a paper ledger. The idea also fits the logic of dynamic capabilities: successful firms notice shifts, mobilize resources, and reconfigure operations rather than merely becoming efficient at yesterday’s model. Long horizons help fund that adaptation, but they do not excuse vague strategy. Leaders still need observable milestones so patience does not become a cover for indefinite spending.

Make customer obsession everyone's job, not a department's assignment

Start with the whole experience. Rossman rejects the idea that a customer officer can own customer focus on everyone else’s behalf. In his account, Amazon’s first leadership principle is customer obsession, and it must influence every team, including finance, technology, and operations. Managers are urged to see the experience directly, investigate specific failures, and use customer feedback to assign root-cause work rather than merely collect opinions.

Customers include your partners. When Rossman joined Amazon to launch Marketplace, the company needed sellers to build a business customers could trust. The team therefore treated sellers as customers too, developing tools and support that made selling easier. The broader lesson is to map the customer’s full journey and ask where effort, waiting, confusion, or uncertainty can be removed. For Amazon sellers, a perfect order measure tracked whether orders arrived without defects such as cancellations, late dispatches, or refunds.

Analysis

This approach pushes customer orientation beyond marketing language and into operating design. Service design research similarly emphasizes the entire journey, including the handoffs customers experience between departments. A complaint can reveal a broken internal interface, not merely a weak frontline employee. Still, customer obsession needs boundaries: customers can ask for incompatible things, and the loudest request is not always the most important need. Direct observation and behavioral data are valuable precisely because they can challenge both executives’ assumptions and customers’ stated preferences.

Expose bad news early before success hardens into Day 2

Spot institutional drift. Rossman uses Amazon’s distinction between Day 1 and Day 2 to describe a company that either keeps renewing itself or settles into inertia. Day 2 begins with stagnation, then risks irrelevance and decline. Warning signs include slowing growth, commoditized offerings, customer complaints, shrinking ambition, and more attention to internal comfort than external needs.

Make decline discussable. Leaders are urged to state what is failing, identify its causes, and make visible commitments to address it. Rossman recommends asking sharper questions, such as how a service could become self-service, and examining how a competitor might attack the existing business. This is not a call for theatrical pessimism. It is a way to stop polite optimism from hiding risk. Past success should not make a company too protective to change its strategy or confront a failing business.

Analysis

The strength of this model is its focus on organizational attention. Decline often becomes dangerous not when the facts are unavailable, but when people learn that reporting them brings blame or embarrassment. A norm of candid review can improve the quality of learning, much as incident analysis does in aviation and medicine. Yet candor is not the same as harshness. If leaders punish the people who surface problems, the ritual of admitting failure becomes another performance. Psychological safety and high standards have to reinforce each other.

Keep innovation separate from routine investments and give bets distinct rules

Manage unlike risks differently. Rossman argues that a predictable efficiency project deserves a conventional business case, while an uncertain new product or business needs a different investment logic. Treating both as if their costs, timelines, and returns were equally forecastable can suffocate experiments before they produce evidence. A portfolio approach spreads risk: small trials test assumptions, while only promising ideas receive larger commitments.

Protect the people building. Amazon’s Lab126 is offered as an example of a team insulated from the routines of the core business while remaining connected to senior leadership. Rossman also describes Two-Pizza Teams, small, multidisciplinary groups that own a capability from design through operation. A senior leader should be dedicated to a major bet, and the team should have clear customer and operating measures. Independence is not isolation. It gives builders room to work without requiring the legacy business to approve every unfamiliar move.

Analysis

The portfolio idea addresses a basic mismatch in corporate governance: mature operations are judged by predictable delivery, while innovation is valuable partly because its outcome is uncertain. Research on exploration and exploitation describes this same tension between improving current capabilities and searching for new ones. Separation can protect exploration, but it can also create a laboratory that never reaches customers. Senior sponsorship, shared interfaces, and explicit tests of adoption help connect protected experimentation to the actual business.

Think big, test small, and distinguish learning from careless failure

Test the risky assumption first. Rossman distinguishes a failed experiment, which teaches whether a hypothesis was wrong, from an execution failure, which reflects poor delivery. The Amazon Marketplace team initially expected customers to use seller-specific storefronts. After launch, behavior showed that customers preferred browsing across categories, so the team shifted its emphasis. Earlier efforts, including Auctions and zShops, had also failed to attract customers, but the accumulated learning informed Marketplace.

Scale only after evidence. Low-fidelity prototypes and minimum viable products help teams test a narrow part of a larger vision without building the whole thing. Amazon’s Fire Phone generated a reported $170 million inventory write-off; the Echo, by contrast, began as a limited release for Prime customers. Rossman’s point is not that every setback is valuable. Leaders should define what a test is meant to reveal, review results, and avoid using the language of experimentation to excuse poor judgment or sloppy execution.

Analysis

The distinction between hypothesis failure and delivery failure is crucial because organizations can otherwise turn experimentation into a slogan that protects weak work. A good test has a stated uncertainty, a method for observing evidence, and a decision that follows from the result. Small experiments can also mislead when they use unrepresentative customers or omit the costs of operating at scale. The goal is not simply to fail cheaply. It is to make uncertainty visible while keeping the consequences proportionate.

Instrument the work before you automate it

Make the process visible. Rossman treats metrics as a management practice, not a reporting exercise. Teams should define measures for customer experience, quality, cost, and throughput, then collect fine-grained data quickly enough to identify problems while they can still be corrected. At Amazon, regular metrics reviews assign owners to trends and root causes. A measure matters only when it leads to investigation and action.

Write down the operating logic. Rossman describes an appliance repair business that estimated each technician’s effective daily capacity from work time, travel time, and the share of repairs completed on the first visit. Tracking those inputs revealed causes such as missing parts or poor scheduling. In Amazon fulfillment, scans through the ship, label, and manifest process helped identify misrouted packages. Clear process definitions, formulas, and reliable data create the groundwork for automation and machine learning.

Analysis

The central insight is that automation depends on making work legible. A process that cannot be described in terms of inputs, decisions, and outcomes is difficult to improve reliably, whether by software or management. This connects to process engineering and control theory, where feedback is essential for correcting variation. Measurement also carries a danger: teams can optimize what is counted while neglecting what matters. Balancing customer outcomes with efficiency measures, and revisiting measures when behavior changes, helps prevent the scorecard from becoming the real objective.

Decentralize building, but retain control of your strategic decision engine

Put technology near the work. Rossman argues that as products become more technology-dependent, technical talent should often sit close to customers and business teams rather than wait in a centralized queue. Central IT still has important jobs, including infrastructure, security standards, and shared systems. Clear interfaces and APIs allow independent teams to build and operate services without directly altering one another’s systems.

Scale through other people’s work. Other People’s Work, or OPW, means designing tools and systems that let customers, sellers, partners, or contractors perform repeatable tasks. Customer reviews and Marketplace sellers illustrate how participation can expand a business beyond its own staffing. But Rossman warns against outsourcing the strategic logic that allocates resources or makes critical decisions. Partners can execute tasks; the company should understand and retain the rules, data, and operating logic that create its advantage.

Analysis

Decentralization can improve responsiveness because the people closest to a problem often have the best context. Shared standards and stable interfaces make that local autonomy compatible with an integrated enterprise. The harder question is governance: a platform can create value for participants while also concentrating control over access, data, and rules. OPW therefore requires more than efficient task design. The company remains accountable for quality, fair treatment, privacy, and the incentives experienced by the people doing the work.

Make hard plans legible before asking teams to execute them

Turn ambition into a shared object. Rossman describes forcing functions as constraints or commitments that guide a team toward a desired outcome without prescribing every action. A future press release imagines the successful customer-facing result; FAQs anticipate what users and stakeholders will need to know. Writing these documents before building exposes vague assumptions and helps teams see what success requires.

Own the handoffs. Leaders are accountable for dependencies, not just the work inside their own team. Rossman recommends taking control of a dependency when possible, setting explicit commitments when it is not, and preparing a fallback. Amazon’s Operating Plan 1 brings performance reviews, priorities, investment requests, and cross-team commitments into an annual planning process. For everyday decisions, teams should distinguish reversible choices from costly, hard-to-reverse ones, moving quickly on the former and deliberating more carefully on the latter.

Analysis

Written plans can improve thinking because they force claims to become specific enough to question. This resembles the use of pre-mortems and design specifications: teams make assumptions visible before implementation makes them expensive to change. The documents are useful only if they invite revision rather than function as contracts that punish new evidence. Likewise, fast decisions are not automatically good decisions. Reversibility is a helpful guide, but a seemingly reversible choice can still create reputational damage, customer harm, or costly downstream dependencies.

Hire for adaptability and reward enterprise value over local wins

Resist the urgent hire. Amazon’s Bar Raiser is an interviewer independent of the hiring team who can veto a candidate. The role exists partly to counter pressure to fill a vacancy quickly, and to assess whether a person can grow beyond one job. Rossman describes a demanding process with structured interviews, written evidence, and a clear yes-or-no decision. The principle is to build a workforce for future needs, not only the immediate opening.

Align incentives with the whole. Rossman argues that team or individual bonuses can encourage people to improve their own score at the company’s expense. Amazon’s emphasis on ownership and long-term stock value is one alternative, though not a universal formula. Frugality also serves as a constraint: the door desk symbolizes designing within limits rather than treating spending as the default solution. Compensation, hiring, and resource allocation should reward durable enterprise performance.

Analysis

Independent review can counteract urgency bias, a real risk when a vacancy creates immediate operational pressure. Yet rigorous processes can become exclusionary if they mistake familiarity with a company’s interview style for ability, or if they reward endurance over contribution. Incentive design has a similar double edge. Individual bonuses can fragment effort, but shared rewards may obscure accountability or expose workers to factors beyond their control. Strong systems combine clear responsibility with rewards that reflect both team outcomes and the employee’s actual influence.

Treat customer trust as an operating promise, including security

Make the promise measurable. For Amazon, trust means more than a reassuring brand message. Customers expect the right item, in the right condition, delivered as promised. Marketplace applied this expectation to outside sellers too, tracking performance and extending a customer guarantee across orders. Rossman’s broader lesson is that companies should define what their brand promises and build ways to detect when that promise is at risk.

Build security into ownership. Security is not a task that can be handed off entirely to a specialist team. Business teams own the systems and data they operate, while security experts provide standards, advice, and risk assessment. The book describes this as security by design: anticipate threats during system design, identify valuable assets, and treat vulnerabilities as defects to correct. Rossman connects this discipline to trust, arguing that customer confidence can be damaged by neglected controls and evasive responses.

Analysis

Trust is an asset produced by repeated behavior, not a sentiment that advertising can manufacture. Reliability, clear recourse, and honest communication all contribute to it. Treating security as shared ownership is especially important because risks often arise at the boundary between teams, vendors, and systems. At the same time, distributed responsibility needs a strong coordinating function; otherwise, every team can assume another team has covered the risk. Trust therefore requires both local ownership and enterprise-wide oversight.

Analysis

Rossman’s central argument is that Amazon’s advantage is not a single technology or trick. It is a reinforcing operating system: long horizons support investment; customer attention reveals friction; small teams and experiments turn insight into services; metrics expose whether those services work; and clear ownership helps them scale. The book is most persuasive when it connects seemingly separate management choices to that cycle. Customer focus shapes the measures, measures discipline autonomy, and autonomy depends on shared technical standards and explicit commitments.

The framework also explains why importing isolated rituals can disappoint. A company can adopt six-page memos, small teams, or innovation awards without adopting the conditions that make them useful: leaders who engage with the details, tolerate informed disagreement, and accept that some experiments will not pay off. Practices are not portable independently of culture and incentives. Rossman’s recurring emphasis on personal change is therefore more than motivational framing. Executives must alter how they allocate attention, make decisions, and respond to unwelcome evidence.

There is a tension between the book’s admiration for high standards and its descriptions of intense pressure, blunt criticism, and high turnover. Those conditions may produce urgency, but they can also suppress dissent, exhaust employees, and narrow the range of people who thrive. A durable version of the model needs candor without humiliation, accountability without scapegoating, and innovation that considers workers and partners as stakeholders, not just inputs. Customer obsession should not become permission to externalize costs onto employees or communities.

The most practical reading is not to copy Amazon’s scale or personality. It is to identify a real customer promise, map the work required to keep it, make the work observable, and give a capable team authority to improve it. Long-term thinking becomes credible when translated into near-term evidence, explicit trade-offs, and a willingness to revise assumptions. That combination, more than any slogan, is what makes the book’s idea of digital leadership useful beyond Amazon.

Summary in 30 Seconds
Digital leadership means adapting quickly while investing for long-term needs. Start with a clear customer promise, map the work required to fulfill it, and measure quality, cost, and speed closely enough to catch failures early. Test uncertain ideas on a small scale, then expand only when evidence supports them. Give teams authority to improve their work, with clear ownership, shared standards, and incentives that favor company-wide results.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.08 out of 5
Average of 440 ratings from Goodreads and Amazon.

Think Like Amazon receives mostly positive reviews, with an average rating of 4.09/5. Readers appreciate its actionable ideas, insights into Amazon's leadership principles, and concise chapters. Many find it useful for business leaders and innovators. Some criticize the author's bias and outdated perspective, while others feel certain sections lack depth. The book's format of 50 ideas is generally well-received, though some find it repetitive or difficult to remember. Overall, it's considered a valuable resource for understanding Amazon's success and applying its strategies.

Your rating:
4.55
150 ratings
Want to read the full book?

Glossary

Day 1 and Day 2

Renewal versus organizational drift

Rossman uses Day 1 for a company that stays alert to customers, adopts relevant changes, and makes decisions with urgency. Day 2 describes stagnation that can progress into irrelevance and decline. The contrast is not about a company’s age. It is a way to assess whether its culture keeps challenging the status quo or protects established routines.

Two-Pizza Team

Small, autonomous capability team

A Two-Pizza Team is a small group, generally no larger than about eight to ten people, responsible for a defined service or capability. The team is expected to design, build, operate, and improve its work, with clear customers, measures, and interfaces to other teams. The name refers to a practical limit on team size, but autonomy and accountability are the central ideas.

flywheel

Self-reinforcing business cycle

A flywheel is a model of factors that strengthen one another as they operate. In Amazon retail, better selection and customer experience attract shoppers, more shoppers attract sellers, and greater scale can support lower prices and further improvements. The model helps leaders explain how investments contribute to sustained momentum, and where intervention may make the system stronger.

forcing function

Constraint that guides outcomes

A forcing function is a requirement, constraint, or commitment designed to make a desired outcome more likely without dictating every step. A defined customer experience, a measurable service target, or a limited headcount budget can shape choices and expose design problems early. It works best when established before execution and understood by the people expected to meet it.

Other People’s Work

Scalable work by participants

Other People’s Work, abbreviated OPW, is a strategy for enabling customers, sellers, partners, or contractors to perform repeatable tasks through well-designed tools and processes. Product reviews and marketplace selling are examples. The organization can extend its capacity without doing every task itself, but it remains responsible for quality, customer outcomes, and the systems that govern participation.

Operating Plan 1 (OP1)

Annual planning and investment review

Operating Plan 1 is Amazon’s annual planning process for reviewing business performance, setting goals, evaluating proposed investments, and aligning resources across teams. Plans are developed from the bottom up, then examined by senior leaders and affected partners. The process is intentionally detailed and deliberative, with the aim of producing clear priorities, commitments, and decisions about what to fund.

regret minimization framework

Long-horizon decision test

The regret minimization framework asks a decision-maker to imagine looking back on a choice much later in life and consider which outcome would be most regrettable. Bezos used this perspective when weighing whether to leave a secure job and start Amazon. It shifts attention from temporary discomfort, such as giving up a bonus, toward the lasting cost of never attempting a meaningful opportunity.

future press release

Written picture of success

A future press release describes a project as if it has already succeeded and customers are experiencing its benefits. It begins with the customer value and states measurable results and important design principles. Writing one before development helps teams clarify the intended outcome, surface difficult requirements, and coordinate work across organizational boundaries.

fitness function

Long-term capability scorecard

A fitness function is a set of long-term measures used to assess the impact and effectiveness of a team, service, or capability. It can track qualities such as customer value, adoption, cost, and reliability. The measures help determine whether a capability remains useful over time, rather than merely whether a project was completed or a short-term target was met.

instrumentation

Fine-grained operational data collection

Instrumentation is the deliberate design of data collection so a process or system can be monitored in sufficient detail and with minimal delay. Rossman emphasizes capturing granular, timely information because summarized or delayed data may hide the causes of errors. Good instrumentation supports operational response, root-cause analysis, and the development of automation.

security by design

Security built into system design

Security by design means considering threats, data protection, and failure scenarios from the beginning of a system’s design and throughout its operation. Security is treated as a core requirement rather than a final audit or checklist. Business and technical teams own the risks in their systems, with security specialists supplying expertise, standards, and support.

FAQ

What's Think Like Amazon about?

  • Digital Leadership Focus: Think Like Amazon by John Rossman provides insights into adopting Amazon's principles to excel in the digital age, emphasizing customer obsession, innovation, and operational excellence.
  • 50½ Actionable Ideas: The book offers 50½ practical ideas covering culture, strategy, business, and technology, forming a comprehensive framework for leaders.
  • Real-World Applications: Rossman uses his Amazon experience to show how these principles apply across industries, making it relevant for both startups and established companies.

Why should I read Think Like Amazon?

  • Learn from an Insider: Gain insights from John Rossman, a former Amazon executive, who shares unique perspectives on Amazon's strategies and culture.
  • Practical Advice: The book provides actionable strategies that can be immediately applied to help businesses navigate digital transformation challenges.
  • Stay Competitive: Understanding Amazon's approach can help organizations remain competitive and innovative in a rapidly changing business landscape.

What are the key takeaways of Think Like Amazon?

  • Customer Obsession: Prioritizing customer needs is central, with leaders starting with the customer and working backward in decision-making.
  • Long-Term Thinking: Emphasizes planning and investment for sustainable growth, encouraging leaders to think beyond immediate results.
  • Embrace Innovation and Failure: Advocates for a culture of experimentation, viewing failures as learning opportunities essential for driving innovation.

What are the best quotes from Think Like Amazon and what do they mean?

  • “The best offense is more offense.”: Highlights the importance of proactive strategies, suggesting continuous innovation over reactive competition.
  • “In God we trust. All others must bring data.”: Emphasizes data-driven decision-making, advocating for metrics and accountability in business.
  • “You are the Chief Product Officer.”: Stresses that leaders should take ownership of product development and customer experience, being deeply involved in the details.

What is the concept of "Customer Obsession" in Think Like Amazon?

  • Foundational Principle: Customer obsession is Amazon's first leadership principle, driving all decisions and strategies by prioritizing customer needs.
  • Empathy and Understanding: Encourages businesses to deeply understand customer pain points and desires, fostering a culture focused on enhancing customer experience.
  • Continuous Improvement: Suggests organizations should constantly seek feedback and iterate on offerings to meet evolving customer expectations.

How does Think Like Amazon define "Ownership"?

  • Empowerment Across Levels: Ownership means every employee is responsible for their work outcomes, promoting accountability and initiative.
  • Long-Term Value Focus: Leaders prioritize sustainable growth over short-term gains, ensuring decisions benefit the entire organization.
  • No Excuses Culture: Leaders take responsibility for failures, working collaboratively to find solutions without blaming others.

What is the "Two-Pizza Team" concept in Think Like Amazon?

  • Small, Autonomous Teams: Refers to small, cross-functional teams that can be fed with two pizzas, promoting agility and innovation.
  • Focus on Accountability: Each team is responsible for its projects, fostering ownership and accountability that drives performance.
  • Encourages Innovation: Minimizes bureaucracy, allowing teams to quickly iterate on ideas and respond to customer needs effectively.

How does Think Like Amazon suggest handling failure?

  • Embrace Failure as Learning: Advocates for a culture viewing failure as essential to innovation, learning from failures for better future outcomes.
  • Test and Iterate: Encourages small experiments to fail fast and learn quickly without significant risk, refining ideas and strategies.
  • Focus on the Right Failures: Distinguishes between failures providing valuable insights and those from poor execution, emphasizing learning from the former.

What is the significance of "Forcing Functions" in Think Like Amazon?

  • Guidelines for Success: Forcing functions are constraints guiding teams toward desired outcomes without micromanagement, maintaining focus and accountability.
  • Encourages Autonomy: Clear expectations allow teams to operate independently while aligning with organizational goals, fostering innovation.
  • Examples in Practice: Amazon uses forcing functions like specific metrics and goals to drive performance and achieve results.

What is the Launch-and-Learn strategy mentioned in Think Like Amazon?

  • Iterative Approach: Encourages launching products quickly, learning from customer feedback, and iterating based on that feedback.
  • Minimize Risk: Testing ideas in small increments minimizes risk and avoids large-scale failures, allowing agile market responses.
  • Foster Innovation: Promotes a culture of experimentation, enabling teams to explore new ideas without fear of immediate failure.

How does Think Like Amazon address the concept of bureaucracy?

  • Avoiding Bureaucracy: Warns against bureaucracy's dangers, which can stifle innovation and slow decision-making processes.
  • Empowerment: Advocates for empowering employees to make decisions aligning with customer needs, reducing unnecessary approval layers.
  • Streamlined Processes: Encourages creating simple, efficient processes to minimize bureaucratic hurdles and enhance operational agility.

What is the Future Press Release technique in Think Like Amazon?

  • Vision Clarity: Involves writing a press release for a product before development, clarifying the vision and goals for the initiative.
  • Customer Focus: Emphasizes starting with the customer, detailing how the product will benefit them and solve problems.
  • Accountability: Serves as a forcing function, holding teams accountable to commitments made in the press release, guiding successful execution.

About the Author

John Rossman is a former Amazon executive who worked as the Director of Merchant Integration from 2002 to 2005. He played a key role in creating Amazon's third-party platform, which now accounts for over half of the company's physical gross merchandise sales. After leaving Amazon, Rossman founded Rossman Partners, a business advisory firm serving clients like Microsoft, Walmart, and the Gates Foundation. He's authored several books, including "The Amazon Way," now in its third edition. Rossman is a sought-after speaker on innovation and corporate culture, known for his expertise in digital business models and operational excellence.

Download PDF

To save this Think Like Amazon summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.45 MB     Pages: 21

Download EPUB

To read this Think Like Amazon summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.44 MB     Pages: 28
Want to read the full book?
Follow
Listen8 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...