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
Lean UX

Lean UX

Applying Lean Principles to Improve User Experience
A $600,000 redesign won applause, and six months later the site hadn't changed. Here's the fix.
by Jeff Gothelf 2012 148 pages
3.99
6k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Replace design handoffs with experiments that improve a measurable user outcome.

Deliver outcomes, not artifacts. Lean UX treats design as a way to change what customers can do, not a factory for specifications. Its case against handoffs is illustrated by a pharmaceutical ecommerce redesign that cost $600,000 and aimed to raise revenue by 15 percent. The team delivered a detailed presentation, the client applauded, and six months later the site had not changed. The work had produced an impressive output, not a business outcome.

Keep the loop moving. Lean UX combines design thinking, Agile development, and Lean Startup experimentation. Teams form an idea, create a small test, observe what happens, and adjust. Documentation still has a place, but it should support shared learning and delivery rather than stand in for progress.

Analysis

The distinction between activity and effect is familiar in operations research, where a process can hit its production targets while missing the purpose those targets were meant to serve. Lean UX makes that mismatch visible in product work. A useful safeguard is to define an outcome that matters to both customers and the business, then watch for unintended effects. A single metric can distort priorities: increasing sign-ups, for instance, says little about whether new users find lasting value. Outcome focus works best when paired with qualitative evidence and a clear account of whose needs count.

Turn uncertain assumptions into ranked, falsifiable product hypotheses.

Make beliefs testable. A hypothesis statement connects a proposed change, a specific group of users, an intended outcome, and the evidence that would support or weaken the idea. Before writing one, the team surfaces business and user assumptions, then ranks them by risk and uncertainty. The riskiest unknowns deserve attention first, rather than the ideas that are easiest to build or most loudly advocated.

Start with a baseline. At TheLadders, the team believed better recruiter messaging could increase job-seeker replies and satisfaction. It could test that belief by tracking replies and recruiter-initiated messages against current levels. The book also recommends proto-personas: quick, team-created sketches of likely users that research can correct. A CSA app team assumed its likely cooks were women, then field research showed many were young men, prompting a revised user model.

Analysis

This approach borrows the discipline of scientific inquiry without pretending product teams can run laboratory-grade experiments. Naming a prediction in advance helps prevent teams from explaining away every result after the fact. Risk-ranking also has a practical logic: a mistaken assumption about who needs a product can invalidate a long list of downstream design choices. Still, evidence quality matters. A handful of interviews can expose a bad assumption, but should not be mistaken for a precise estimate of market-wide behavior. Hypotheses are useful when teams treat them as provisional claims, not verdicts.

Design with the whole team before polishing any interface.

Bring expertise together early. Lean UX asks designers, developers, product managers, QA, and other relevant colleagues to shape solutions together. The designer still contributes craft, but also facilitates the process. Low-fidelity sketches make ideas concrete while keeping them inexpensive to change. In a Design Studio, people first sketch options individually, present and critique them, revise promising ideas, then converge on a shared direction.

Make understanding visible. In one example, a designer and developer spent two hours sketching a crowded dashboard on a whiteboard. The developer could flag what fit the available sprint, while the designer could clarify the user experience. They left with a direction both understood, and the developer could begin infrastructure work as the design was refined. This shared understanding reduces the need for exhaustive handoff documents and lets work proceed in parallel.

Analysis

Cross-functional sketching is a practical way to combine different kinds of knowledge before a decision hardens. It resembles distributed cognition: a team uses people, drawings, and conversation together to reason through a problem that would exceed any one person's view. Low fidelity also lowers the social cost of disagreement because a rough sketch feels easier to challenge than a polished screen. But collaboration is not automatically equitable. Strong personalities can dominate a room, so facilitation, silent individual sketching, and structured critique help make participation more than a slogan.

Build the smallest MVP that can answer the riskiest question.

Test before investing heavily. A Minimum Viable Product, or MVP, is the smallest thing that can help determine whether a hypothesis deserves more effort. It may be a prototype, a working feature, or even a test that does not imitate the final product. Teams should first ask whether they are trying to learn about demand, value, or usability, because each requires different evidence.

Use cheap signals carefully. A company considering a monthly newsletter built only a sign-up form, spending half a day on it before deciding whether to produce the newsletter. CityPockets tested its online coupon wallet by having founder Cheryl Yeoh manually enter customers' forwarded coupons rather than first building costly backend systems. Both experiments reduced commitment before the idea was proven. A click, sign-up, or interview response is a signal, not proof that a full product will succeed.

Analysis

The MVP idea is powerful because it reframes product development as buying information with limited time and money. It also guards against a common error: treating a prototype as inherently useful simply because it looks like the eventual product. The right test depends on the uncertainty being investigated. A sign-up page can indicate curiosity, but not repeat use or willingness to pay. Experiments that collect customer intent should be designed honestly, especially when a promised feature is not available yet. The smaller the test, the more carefully its limitations need to be stated.

Put customers in the loop every week, with the whole team watching.

Make discovery routine. Lean UX treats research as continuous and collaborative, not a specialized event performed only at a project's beginning or end. One suggested cadence, called 3-12-1, means meeting three users by noon once a week. Teams can test sketches, wireframes, clickable mockups, or live code, as long as they match the question being asked. A sketch can reveal whether a concept resonates, but not whether its controls are usable.

Learn together. The book's PayPal example sent mixed pairs of developers and nondevelopers to nearby shopping malls with a prototype. They interviewed people, compared notes, revised the design, and returned to test again. Meetup scaled its in-house practice to about 600 sessions a year, at a reported cost of roughly $30,000 excluding staff. Shared observation helps teams see user difficulty firsthand and discuss patterns while evidence is fresh.

Analysis

Regular contact helps correct the distance between a team's internal story about users and the behavior of actual people. It also makes research less ceremonial: a small, recurring session is easier to connect to a specific product decision than a large study delivered months later. Yet frequency alone does not guarantee sound conclusions. Small samples are better at revealing friction and generating questions than establishing population-level preferences. Teams should distinguish repeated qualitative patterns from statistical evidence, and combine interviews with behavioral data when the decision requires both explanation and scale.

Keep UX and engineering inside one shared sprint rhythm.

Avoid mini-waterfalls. A staggered-sprint model puts design one sprint ahead of development. It can help teams moving from traditional methods or working where frequent releases are impossible, but it can preserve the old handoff problem: designers and engineers may work on different questions and rely on documents to bridge the gap. Lean UX aims for closer collaboration, with the whole team shaping work and customer feedback informing each cycle.

Use the team's real cadence. In Scrum, designers should participate in planning, stand-ups, and retrospectives so design effort and engineering constraints are visible when work is prioritized. A team that changed a customer-facing workflow without alerting customer service learned that product changes also affect colleagues outside the development group. Proactive updates about what was learned, what is changing, and which teams depend on the change help preserve coordination without requiring a rigid long-term feature plan.

Analysis

The book's argument is not that meetings or plans are inherently wasteful, but that they should connect disciplines to the same decisions. This aligns with research on team coordination: interdependent work requires shared expectations and timely information, not simply individual efficiency. A common sprint rhythm can expose mismatched assumptions early. The caveat is that constant collaboration can fragment focused work, especially for designers handling complex interaction problems. Teams need protected making time alongside joint sessions, and release constraints in regulated or embedded environments may require more deliberate sequencing than the idealized rapid loop.

Use living pattern libraries to make good design reusable.

Turn repeated choices into shared tools. A style guide, or pattern library, collects interface, visual, and writing conventions so teams can reuse working components instead of reinventing them. It should be easy to find, regularly updated, and actionable, with usable assets and code rather than examples that sit untouched in a document.

Let consistency increase speed. General Electric's Industrial Internet Design System served a company with about 8,000 software engineers and roughly 500 developers for every designer. It gave teams reusable templates, code, guidelines, and example applications, allowing them to create clickable prototypes in days rather than months. The book reports project lifecycles shortened by as much as six months and estimated annual resource savings in the millions. A style guide needs an owner and maintenance process; otherwise, its patterns can become stale or obstruct a genuinely new interaction.

Analysis

Reusable design systems function like organizational memory: they preserve decisions that teams should not need to renegotiate on every project. This can free scarce design capacity for novel problems and improve consistency across products. The important qualifier is that reuse should reduce repetition, not become an excuse to force every problem into an existing component. A pattern library can encode assumptions just as easily as it encodes good practice. Its governance should make it possible to propose changes, retire outdated patterns, and document when a team has a sound reason to depart from the standard.

Reward learning, not heroic polish or feature count.

Change what teams are praised for. Lean UX favors small, dedicated, cross-functional teams assigned a problem and an outcome, rather than a feature list. Designers become facilitators as well as makers, and colleagues contribute beyond narrow job titles when they have relevant skills. The aim is a team that can test ideas without waiting for a celebrated individual to deliver a finished vision.

Make experimentation safe. The book recounts a ceramics class split between students graded on one carefully made pot and students graded on the total weight of pots produced. The quantity group made the strongest work, because repeated attempts gave them practice and feedback. The lesson is not to prize volume for its own sake, but to let teams learn from imperfect attempts. Small teams, often capped at ten core members, can test and discuss ideas with less coordination overhead.

Analysis

A team culture that tolerates failed experiments can improve learning, but the ceramics story should not be read as proof that speed or volume always produces quality. Practice helps when people receive useful feedback and have time to reflect; repetition without either can simply repeat mistakes. Similarly, removing individual heroes is not a case for flattening expertise. Teams need specialists, but expertise becomes more valuable when it informs shared decisions rather than operating as a private oracle. Managers shape this culture through what they fund, celebrate, and permit teams to stop doing.

Treat rough experiences as debt, and keep paying them down.

Keep quality on the backlog. UX debt is the gap between the experience users have now and the experience the team believes it should provide. Like technical debt, it can accumulate when teams ship quickly and never return to improve the product. The book recommends recording those gaps as backlog stories so they can be made visible and prioritized rather than dismissed as optional polish.

Adapt the method to reality. Some organizations must keep formal documentation for regulation, coordination, or future teams. Lean UX can still begin with conversation, sketches, and experiments, then document decisions as evidence strengthens. Agencies and external development vendors may need flexible time-and-materials arrangements to accommodate learning and changed plans. Teams should also tell customer service, marketing, and other affected groups what is changing. Agility means responding to new information, not surprising everyone who must support the product.

Analysis

Calling usability problems debt gives them a place in the same economic conversation as engineering maintenance, which can help prevent visible new features from crowding out basic experience quality. The metaphor also has limits: UX debt is not always a neatly quantifiable liability, and some gaps reflect deliberate trade-offs rather than neglected work. Teams can make the concept more actionable by identifying who is harmed, how often the problem occurs, and what improvement would look like. Documentation and stakeholder communication are not opposites of experimentation; they are part of making learning usable across an organization.

Analysis

Lean UX is a practical response to a structural mismatch: software can be changed quickly, while many organizations still make product decisions through slow, sequential handoffs. Its central intervention is to move uncertainty into the open. Teams state what they believe, identify which belief could cause the greatest damage if false, create a small test, and use customer response to decide what to do next. That sequence links design craft to business accountability without reducing design to decoration or a dashboard.

The method's deepest mechanism is shared understanding. A sketch, interview, or prototype is not merely an artifact; it is a common object around which people with different expertise can reason. That helps explain why the book treats collaboration, small teams, customer contact, and low-fidelity work as mutually reinforcing practices. Fewer handoffs mean less knowledge is lost, while repeated customer exposure gives the team a reality check that internal debate cannot supply.

The approach is strongest where products can be tested safely and changed often. Its prescriptions become harder in regulated, high-risk, or infrastructure-heavy environments, where a flawed experiment may impose real harm or where deployment is expensive. There, the same logic still applies, but the test may need simulation, staged access, or stronger review. Speed is not the primary virtue; reducing the cost and duration of consequential uncertainty is.

A further tension lies in measurement. Outcomes keep teams from confusing shipped features with value, but metrics can narrow attention to what is easy to count. Reply rates or clicks need interpretation: who acted, what they understood, and whether the behavior creates durable value? Lean UX is most persuasive when quantitative signals, direct observation, and ethical judgment inform one another. In that form, it is not a recipe for building faster at any cost. It is a disciplined way to make fewer unsupported bets, learn in public with a team, and preserve responsibility for the experience after launch.

Summary in 30 Seconds
Design should be judged by changed customer behavior, not by deliverables. Write beliefs as testable hypotheses, rank them by risk, and test the riskiest first with the cheapest possible experiment. Design together with developers and product people using rough sketches, and meet a few real users every week with the whole team watching. Keep designers inside the shared sprint rhythm, maintain reusable pattern libraries, and log rough experiences as backlog debt.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.99 out of 5
Average of 6k+ ratings from Goodreads and Amazon.

Lean UX receives mixed reviews, with an average rating of 3.99 out of 5. Many readers appreciate its practical advice on integrating UX design with agile methodologies, finding it valuable for beginners and experienced professionals alike. The book is praised for its concise presentation and real-world examples. However, some critics argue that the content is outdated or oversimplified, and a few suggest alternative books for more in-depth information. Overall, readers find it a useful guide for implementing lean UX principles in product development, despite some limitations.

Your rating:
4.42
436 ratings
Want to read the full book?

Glossary

Lean UX

Collaborative, experiment-led design

A product-design practice that combines design thinking, Agile development, and Lean Startup learning. Cross-functional teams make small, testable versions of ideas, seek customer feedback frequently, and focus on outcomes rather than treating documents or features as proof of progress. Its aim is to build shared understanding while reducing wasted design and handoff work.

hypothesis statement

Testable product belief

A clear statement linking a belief about a product or user problem to the market evidence that would support or weaken it. A product-level hypothesis typically identifies the change being considered, the people it is intended to help, the outcome expected, and the feedback or metric that will indicate whether the idea is working.

Minimum Viable Product (MVP)

Smallest useful learning test

The smallest product, prototype, or other test that can provide meaningful evidence about a hypothesis. An MVP may be designed primarily to learn whether people want an idea, or to deliver an early version of value while learning from real use. It need not contain code or resemble the complete product.

proto-persona

Researchable user assumption

A quick, team-created sketch of a likely user, based on current assumptions about that person's needs, context, and behavior. Unlike a persona built from extensive prior research, a proto-persona is explicitly provisional. Teams use ongoing customer research to correct or replace it, rather than treating the initial sketch as established fact.

Design Studio

Collaborative sketching exercise

A structured activity in which a cross-functional team explores solutions to a defined design problem. Participants first sketch ideas individually, then present and critique them, refine promising directions, and work toward a shared concept. The process makes diverse perspectives visible and creates low-fidelity material for prototyping and testing.

3-12-1

Weekly user-testing cadence

A suggested rhythm for continuous customer research: meet with three users by noon once a week. The team selects what to test, prepares a prototype or other artifact, observes sessions, and reviews findings promptly. The cadence is intended to keep product decisions close to customer feedback, not to guarantee statistically conclusive results.

GOOB

Get outside the office

An acronym for getting out of the building to meet potential customers and test assumptions in the marketplace. It emphasizes that internal discussion cannot conclusively establish what users need or whether an idea has value. Teams should expose ideas to relevant customers while they are still inexpensive to change.

UX debt

Unresolved experience problems

The accumulated gap between the current user experience and the experience a team believes it should provide. UX debt can result when teams ship quickly but fail to revisit confusing, incomplete, or inconsistent interactions. The book recommends recording these issues as backlog work so they remain visible and can be prioritized.

Concierge MVP

Manual service test

A way to test a product idea by manually delivering the underlying service before investing in automated systems. In the CityPockets example, the founder entered customers' forwarded coupon information herself instead of first building a backend. This let the team learn whether customers valued the service while limiting early development costs.

FAQ

What's "Lean UX: Applying Lean Principles to Improve User Experience" about?

  • Core Concept: "Lean UX" by Jeff Gothelf, edited by Josh Seiden, focuses on integrating Lean Startup principles with user experience design to create more efficient and effective product development processes.
  • Methodology: It emphasizes collaboration, rapid iteration, and continuous learning to improve user experience and product outcomes.
  • Target Audience: The book is aimed at UX designers, product managers, developers, and managers who want to enhance their team's design and development processes.
  • Practical Approach: It provides actionable advice, case studies, and techniques to implement Lean UX in various organizational settings.

Why should I read "Lean UX: Applying Lean Principles to Improve User Experience"?

  • Modern Relevance: The book addresses the challenges of integrating UX design with Agile and Lean methodologies, which are prevalent in today's fast-paced development environments.
  • Improved Collaboration: It offers strategies to break down silos and foster cross-functional teamwork, leading to better product outcomes.
  • Efficiency and Innovation: By focusing on outcomes rather than outputs, the book helps teams innovate more effectively and reduce waste.
  • Real-World Examples: It includes case studies and examples from companies like GE and Meetup, providing practical insights into successful Lean UX implementation.

What are the key takeaways of "Lean UX: Applying Lean Principles to Improve User Experience"?

  • Cross-Functional Teams: Emphasizes the importance of diverse teams working together from the start to create better products.
  • Outcome Focus: Encourages measuring success by outcomes rather than deliverables, aligning team efforts with business goals.
  • Continuous Learning: Advocates for regular user feedback and iterative design to quickly validate assumptions and improve products.
  • Collaboration Over Documentation: Suggests reducing reliance on heavy documentation in favor of building shared understanding through collaboration.

How does "Lean UX" integrate with Agile methodologies?

  • Scrum Integration: The book provides guidance on fitting Lean UX into Scrum processes, using meetings and sprints to enhance collaboration.
  • Staggered Sprints: Initially suggests staggered sprints for design and development but ultimately advocates for concurrent work to maximize team cohesion.
  • Participation: Stresses the importance of full team participation in Agile rituals to ensure shared understanding and effective prioritization.
  • Iterative Process: Aligns with Agile's iterative nature, using rapid prototyping and testing to refine products continuously.

What is the role of hypothesis statements in "Lean UX"?

  • Foundation for Testing: Hypothesis statements are used to express assumptions in a testable format, guiding the design and development process.
  • Structure: They typically include a belief about the product, the target audience, and the expected outcome, along with criteria for validation.
  • Focus on Learning: By framing work as hypotheses, teams can focus on learning from market feedback rather than just delivering features.
  • Iterative Refinement: Hypotheses are refined through continuous testing and feedback, allowing teams to pivot or persevere based on evidence.

How does "Lean UX" address the challenge of documentation?

  • Conversation Over Documentation: The book advocates for using conversation as the primary means of communication, reducing the need for extensive documentation.
  • Shared Understanding: Emphasizes building a shared understanding among team members to minimize reliance on detailed specs and handoffs.
  • Lightweight Artifacts: Encourages creating only the necessary design artifacts to move the team's learning forward, avoiding waste.
  • Documentation as a Tool: Suggests using documentation to capture decision history and inform future work, rather than as a primary deliverable.

What are some practical techniques from "Lean UX" for collaborative design?

  • Design Studio: A collaborative sketching exercise that involves the entire team in generating and refining design ideas.
  • Style Guides: Living repositories of design patterns and components that facilitate consistency and efficiency in design and development.
  • Prototyping: Using low-fidelity and high-fidelity prototypes to quickly test and iterate on design concepts with users and stakeholders.
  • Remote Collaboration: Techniques for working with geographically distributed teams, including using digital tools and setting up virtual design sessions.

How does "Lean UX" suggest handling user feedback and research?

  • Continuous Discovery: Incorporates regular user feedback into every iteration, allowing teams to validate hypotheses and adjust designs quickly.
  • Collaborative Research: Involves the entire team in research activities to build a shared understanding and reduce the need for handoffs.
  • Lightweight Methods: Uses small, informal qualitative research studies to gather insights without disrupting the development process.
  • A/B Testing: Employs A/B testing to evaluate different design options and determine which best meets user needs and business goals.

What organizational shifts does "Lean UX" recommend?

  • Outcome-Driven Culture: Shifts focus from outputs to outcomes, empowering teams to design solutions that achieve business goals.
  • Cross-Functional Collaboration: Encourages breaking down silos and fostering collaboration across disciplines to enhance product development.
  • Embracing New Skills: Suggests that designers develop facilitation skills and take on leadership roles in collaborative design processes.
  • Small, Agile Teams: Advocates for small, co-located teams that can work efficiently and adapt quickly to new information.

What are some of the best quotes from "Lean UX" and what do they mean?

  • "Speed first, aesthetics second": Emphasizes the importance of rapid iteration and learning over perfecting design details early in the process.
  • "Get out of the deliverables business": Encourages teams to focus on creating value and achieving outcomes rather than producing extensive documentation.
  • "Permission to fail": Highlights the need for a culture that supports experimentation and learning from failure to drive innovation.
  • "Shared understanding is the currency of Lean UX": Stresses the importance of building a common understanding among team members to facilitate collaboration and reduce waste.

How does "Lean UX" address the role of designers in a team?

  • Facilitators of Collaboration: Designers are encouraged to lead collaborative design sessions and involve the entire team in the creative process.
  • Beyond Deliverables: The book suggests that designers focus on solving problems and creating value rather than producing polished artifacts.
  • Embracing Iteration: Designers are urged to embrace rapid prototyping and testing to refine ideas based on user feedback.
  • Leadership Role: Designers are positioned as leaders who guide the team in building a shared understanding and achieving design goals.

How can "Lean UX" be applied in an agency setting?

  • Outcome-Based Contracts: Agencies can experiment with moving away from fixed-scope contracts to focus on achieving client outcomes.
  • Increased Collaboration: Encourages breaking down barriers between clients and agencies to foster collaboration and improve project outcomes.
  • Flexible Processes: Agencies can adopt Lean UX principles to iterate quickly and respond to client feedback more effectively.
  • Client Involvement: Suggests involving clients early and often in the design process to ensure alignment and reduce the risk of rework.

About the Author

Jeff Gothelf is a prominent figure in the field of user experience design and product development. He is best known for his work on Lean UX methodologies, which combine principles from lean startup, design thinking, and agile development. Gothelf has extensive experience working with both startups and large organizations, helping them improve their product design processes. He is a sought-after speaker, workshop facilitator, and author, having written multiple books on UX design and lean methodologies. Gothelf's approach emphasizes cross-functional collaboration, rapid experimentation, and continuous learning to create better products and services.

Download PDF

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

Download EPUB

To read this Lean UX 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.34 MB     Pages: 26
Want to read the full book?
Follow
Listen9 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...