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
Understanding A3 Thinking

Understanding A3 Thinking

A Critical Component of Toyota's PDCA Management System
Help teams solve workplace problems with evidence, tested changes, and lasting process improvements.
by Durward K. Sobek II 2008 165 pages
4.04
283 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat the A3 as a way to think, not a page to fill

The page is a trace. An A3 report is a concise visual account of a problem, a proposed change, or project results. It traditionally fits on one side of an 11-by-17-inch sheet, but the paper size is not the point. A3 thinking is the disciplined investigation and collaboration that produce the report. A polished page cannot rescue weak reasoning.

Improvement comes from people. Toyota's advantage, the authors argue, comes less from copying tools such as just-in-time production than from engaging people in continual improvement. The report makes their reasoning visible, helps others question it, and preserves what was learned. A3s can be used across manufacturing, engineering, sales, and health care, but only when they support real work rather than become a paperwork ritual.

Analysis

The report's most useful function is to make reasoning inspectable. That connects to a broad principle in organizational learning: knowledge becomes easier to challenge, share, and improve when it is made explicit rather than kept in one person's head. The compact page also creates a shared object for discussion across teams. Brevity, however, can hide uncertainty or essential context. A sound A3 should make the central logic easy to grasp while leaving supporting evidence accessible, not imply that every complex issue can be reduced to a single sheet.

Spend more effort proving the problem than selling your fix

Plan before action. Plan-Do-Check-Act, or PDCA, is a cycle for learning through deliberate change. In Plan, investigate the situation, identify likely causes, set a measurable target, predict results, and decide how to implement and evaluate a change. Do puts the plan into practice. Check compares actual outcomes with the prediction. Act standardizes a successful change or starts another cycle when results fall short.

Resist the quick fix. The authors contrast the common urge to implement first and tidy up afterward with Toyota's emphasis on thorough preparation. Their comparison of spending eleven months planning and one month implementing is explicitly an exaggeration, but it captures the point: careful planning makes it possible to distinguish a mistaken diagnosis from a poorly executed change.

Analysis

A prediction turns a change into a test of understanding, not merely a task completed. This is the same logic that makes a scientific experiment informative: expectations are stated before results arrive, so surprises have something specific to challenge. The approach can also protect teams from expensive, premature commitments. Yet planning is not automatically productive. When investigation becomes a way to avoid action, small, reversible tests can be more informative than extended analysis. The practical balance is to plan enough to make the test interpretable, then learn from what happens.

Go to the work, measure what happens, and replace blame with evidence

See the process firsthand. Toyota's term genba means the actual place where work happens. Going there lets a problem-solver observe the process as performed, speak with the people involved, and test assumptions against conditions on the ground. A written report or a description of how work is supposed to happen may miss the detail that explains the failure.

Let facts redirect the debate. In one plant, production blamed maintenance for equipment downtime, while maintenance blamed production. Investigation found that seven of 120 machines caused most of the downtime. Five were waiting for spare parts delayed by incorrect vendor information in purchasing. The data shifted attention from departmental accusations to a specific process failure that could be addressed.

Analysis

Firsthand observation is valuable because it can expose the gap between formal procedures and actual practice, a familiar challenge in fields from medicine to software operations. Quantification also helps teams see whether a vivid incident is typical or exceptional. Still, observation is not neutral by itself: people may change their behavior when watched, and a narrow sample can mislead. Combining direct observation with records, interviews, and repeated measurement makes the resulting account more robust than relying on any one source.

A fix is not proven until results match a prediction

Test cause and effect. A countermeasure is a change intended to address a cause and prevent a problem from returning. The team should predict what the change will achieve, specify who will implement it, and plan how to measure the result. Without a prediction and a follow-up measure, a problem that disappears may still leave the team unsure what actually helped.

Learn from the mismatch. A trainee investigating defects on a precision grinder tested possible causes one at a time and discovered that contaminated coolant was contributing to the problem. Replacing it reduced defects from 2.3 percent to below 0.2 percent. His supervisors then asked how contamination had occurred and what checks could prevent it. The immediate improvement mattered, but so did understanding whether the process could sustain it.

Analysis

The prediction and follow-up discipline helps distinguish learning from luck. It also makes a failed intervention useful: a result that differs from expectations points toward a faulty hypothesis, weak implementation, or an incomplete measure. Before-and-after numbers alone do not prove that a change caused an improvement, since other conditions may have shifted at the same time. Tracking implementation and choosing measures carefully strengthen the inference. The approach works best when teams treat disappointing results as information, not as a reason to conceal or punish failure.

Trace causes until the process, not a person, can be changed

Look beneath the symptom. The 5 Why's technique repeatedly asks why a problem occurred, turning each answer into the next question until investigation reaches a cause that can be addressed. The number five is a guide, not a rule. A fishbone diagram can organize several possible causes, and experiments may be needed when observation alone cannot establish which cause matters.

Prevent a repeat. A machine that repeatedly stopped after an overload alarm was initially repaired by resetting the relay, then by replacing a damaged shaft. Deeper investigation traced the failure to metal shavings entering the lubrication system; a strainer at the inlet addressed that pathway. A repair restores function now. A durable countermeasure changes the conditions that produce the failure.

Analysis

The shift from blame to process is both practical and humane. It asks what features of the work system made an error or breakdown likely, rather than assuming an individual's bad judgment explains everything. That is especially useful in complex environments where failures often have several contributing causes. The five-question routine can be abused, though: a neat chain of answers is not proof of causality, and some problems do not have one root. Teams should treat each proposed cause as a hypothesis to verify, not a satisfying endpoint.

Make the one-page story align teams around shared facts and action

Show the whole chain. A strong A3 connects the reason a problem matters to the observed current state, the target, the analysis, the proposed changes, and the follow-up. Diagrams, charts, and concise labels can make the logic visible, helping readers challenge a specific part of the account instead of arguing from separate assumptions. The report should also explain how the work serves broader organizational goals.

Make coordination concrete. In a hospital example, 17 charts were reported as awaiting transcripts, although seven transcripts were already in the department. The team simplified the workflow by receiving transcripts in the Emergency Department and matching them to charts there. After implementation, over 98 percent of 371 charts arrived with transcripts, and average bill-drop time reached 6.55 days, below the seven-day target.

Analysis

A visual account can act as a common reference point for people with different expertise and priorities. The hospital example shows that a clear process picture can reveal a coordination failure that is hard to see in isolated departmental reports. It also illustrates an important systems question: a change may simplify work in one unit by shifting it to another. The reported speed and completeness gains are encouraging, but checking coding accuracy and the added workload in the Emergency Department remains essential. Alignment is strongest when affected teams can see both benefits and costs.

Use problem-solving, proposal, and status A3s at different PDCA moments

Match the document to the work. A problem-solving A3 investigates a current issue and records the reasoning, actions, and results. A proposal A3 is written before a significant change, so decision-makers can compare options, assess risks, and consider a pilot. A status A3 reports what implementation has achieved and what still needs attention. Each follows PDCA logic, but each emphasizes a different point in the cycle.

Report mixed results honestly. In a corporate purchasing-card pilot, costs and processing time improved as expected, but reconciliation discrepancies increased. That unexpected result belonged in the status review because it affected the overall assessment and pointed to more work. The authors stress that the formats are adaptable guides, not mandatory templates. The essential requirement is a coherent account suited to the decision at hand.

Analysis

Separating these uses helps prevent a common category error: asking a proposal to prove results before it has been tested, or treating a status update as if it were a full diagnosis. It also clarifies what decision a reader is being asked to make. Reporting unfavorable side effects alongside benefits is particularly important because organizations often optimize the visible metric and overlook the work displaced elsewhere. The three forms are useful distinctions, but real projects blur their boundaries; the format should follow the question, not force the work into a label.

Use review to develop the problem-solver, not just approve the page

Make reasoning coachable. Managers and peers review an A3 by asking whether the problem is well framed, the evidence is sufficient, the causes are plausible, and the actions and checks fit the analysis. Approval is not merely permission to proceed. It can be a mentoring conversation in which an experienced manager tests the author's thinking and helps build investigative and communication skills.

Prepare people before decisions. For a proposal, Toyota's practice of nemawashi means discussing the idea with affected parties before the formal approval meeting. Their concerns can shape the proposal, and unresolved disagreements can be addressed directly. The process does not require universal agreement, but it does require that concerns are heard and that decisions are explained.

Analysis

Review works as a learning mechanism when questions improve the work rather than merely enforce hierarchy. Making assumptions visible gives a manager something concrete to coach, while early conversations reduce the likelihood that stakeholders encounter a major change as a surprise. These benefits depend on candor. If approval becomes a test of loyalty or a source of delay, authors may hide uncertainty and produce polished but less truthful reports. Clear authority, timely feedback, and permission to revise a mistaken hypothesis make the review process more than ceremonial control.

Begin with a two-to-four-week problem you can actually influence

Build skill through a complete cycle. For a first A3, the authors recommend a meaningful but contained problem within the learner's control, ideally one that can be addressed in two to four weeks. A smaller scope lets the learner practice observation, analysis, implementation, and follow-up without getting overwhelmed by cross-departmental politics or long delays.

Sketch before polishing. Hand-drawing the process can prompt closer observation and faster feedback from coworkers. A computer can make editing and sharing easier, but beginners may spend more energy arranging a report than understanding the work. Templates should provide a starting point, not a cage. A3s are not required for every issue, and a report is useful only if it supports improvement rather than replacing it.

Analysis

This advice recognizes that a method is learned by practice, not by memorizing its vocabulary. A short, bounded project gives a learner a chance to see the consequences of each step while the experience remains fresh. Sketching also lowers the cost of revising an early understanding in conversation. The limitation is that many consequential problems exceed one person's control or a few weeks. Those issues still need structured investigation, but beginners benefit from gaining fluency on manageable work before they take on wider organizational questions.

Analysis

The book's central argument is that Toyota's A3 is not primarily a reporting format. It is a management practice that joins investigation, experimentation, communication, and employee development. That framing explains why copying the one-page layout or a collection of lean tools is unlikely to reproduce the underlying capability. The system depends on repeated habits: observe actual work, make claims testable, involve affected people, assign actions, and inspect results against expectations.

Its most compelling contribution is the insistence that problem-solving quality includes both outcomes and the route to them. A quick improvement that cannot be explained or sustained may be organizationally fragile. A disciplined test can produce value even when its hypothesis fails, provided the result changes understanding. The A3's visual compression serves this learning process by exposing gaps in logic and giving teams a shared object for discussion. The book also makes managerial review part of the method, turning approval into an opportunity to coach rather than merely authorize.

The approach is not a universal recipe. Root causes in real organizations are often multiple, shifting, and difficult to isolate. Measures can be incomplete, and local improvements can transfer cost or workload elsewhere. A one-page account may also create an appearance of certainty that the underlying evidence does not warrant. These risks do not undermine A3 thinking; they clarify what its discipline must include: transparent assumptions, suitable measures, attention to side effects, and supporting evidence beyond the summary when needed.

The deepest lesson is therefore institutional, not graphic. Organizations improve when they make inquiry a normal part of work and give people time, authority, and coaching to complete the learning cycle. A3 is a compact scaffold for that behavior. If the scaffold becomes the objective, its value disappears. If it helps people see a process more accurately, test changes responsibly, and share what they learn, the page earns its place.

Summary in 30 Seconds
Reliable improvement starts with observing work directly, defining a measurable problem, and investigating its causes before choosing a change. Predict what a change should accomplish, then compare results with that prediction; one equipment intervention reduced defects from 2.3 percent to below 0.2 percent. Trace failures to conditions the process can address, involve affected colleagues, and use reviews to strengthen problem-solving skills. Keep early projects small enough to complete and evaluate.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.04 out of 5
Average of 283 ratings from Goodreads and Amazon.

Understanding A3 Thinking receives mostly positive reviews, with readers praising its insights into Toyota's problem-solving approach. Many find it valuable for Lean practitioners and project managers. The book is lauded for its explanation of A3 reports, PDCA cycle, and data-driven decision-making. Some readers note its focus on manufacturing and suggest prior knowledge of Lean concepts is helpful. A few criticisms mention repetition and dryness, but overall, readers appreciate the book's practical advice and its emphasis on systematic problem-solving and organizational alignment.

Your rating:
4.51
178 ratings
Want to read the full book?

Glossary

A3 report

Visual improvement summary

A concise document that records the reasoning and key information behind problem solving, a proposal, or a project-status review. It traditionally fits on one side of A3 paper, roughly 11 by 17 inches. Its value lies not in the size or template alone, but in how it supports investigation, communication, review, and follow-up.

A3 thinking

Collaborative problem-solving discipline

The style of reasoning encouraged by Toyota's A3 process. It combines logical analysis, objective evidence, attention to both results and process, concise visual communication, stakeholder alignment, coherence, and a view of effects across the larger system. The aim is to solve problems while developing people's ability to investigate and improve work.

Plan-Do-Check-Act (PDCA)

Cycle for tested improvement

A continuous-improvement cycle. Plan means studying a problem, identifying likely causes, setting a target, predicting results, and preparing an implementation and measurement plan. Do means carrying out the change. Check compares actual outcomes with predictions. Act means standardizing a successful change or responding to results that show more work is needed.

genba

The actual work location

A Japanese term for the real place where work happens. In A3 problem solving, going to the genba means observing the process in context and speaking with people who perform or encounter the work. The practice helps test assumptions about how a process operates and can reveal details that reports or general descriptions miss.

5 Why's

Repeated cause investigation

A technique for exploring a problem by repeatedly asking why it occurred. Each answer becomes the subject of another question, creating a cause-and-effect chain that may lead beyond the immediate symptom. The name does not require exactly five questions. When causes are uncertain or multiple, diagrams and structured experiments may be more appropriate.

countermeasure

Change aimed at preventing recurrence

A specific change intended to address an identified cause of a problem. The term emphasizes that an intervention is a response to a particular condition and may be improved or replaced as learning continues. A countermeasure should be linked to the evidence and analysis, assigned for implementation, and checked to see whether it had the predicted effect.

nemawashi

Early stakeholder dialogue

A Japanese business practice of discussing a proposed change with affected parties before a formal decision meeting. In A3 work, these conversations allow people to understand the rationale, surface concerns, and influence the proposal while it is being formed. They reduce avoidable surprise and help build practical alignment without requiring that every participant agree on every detail.

yoko-narabi-tenkai

Lateral sharing of findings

Toyota's term for extending useful findings to related groups beyond the team that made an improvement. Once a countermeasure has been checked, the organization considers whether similar equipment, processes, or departments could benefit. This prevents learning from remaining local and can help spread effective changes or lessons about what did not work.

FAQ

What is "Understanding A3 Thinking" by Durward K. Sobek II about?

  • Comprehensive guide to A3 thinking: The book explains the A3 report as a core tool in Toyota’s PDCA (Plan-Do-Check-Act) management system, emphasizing its role in structured problem-solving and continuous improvement.
  • Focus on thinking, not just tools: It stresses that A3 is more than a reporting format; it’s a disciplined way of thinking and communicating that underpins Toyota’s success.
  • Practical application: The book provides step-by-step guidance, examples, and exercises for writing and reviewing A3 reports in various organizational contexts.
  • Transferable methodology: While rooted in Toyota’s practices, the concepts are presented as broadly applicable to any organization seeking to improve problem-solving and management effectiveness.

Why should I read "Understanding A3 Thinking" by Durward K. Sobek II?

  • Learn Toyota’s secret sauce: The book demystifies the thinking and processes behind Toyota’s sustained excellence, which many companies try but fail to replicate.
  • Develop problem-solving skills: It offers actionable methods to improve both individual and organizational problem-solving capabilities.
  • Enhance communication and alignment: Readers gain tools to foster clearer, more objective, and more collaborative communication within teams.
  • Applicable across industries: The A3 approach is shown to work in manufacturing, healthcare, services, and more, making it valuable for a wide audience.

What are the key takeaways from "Understanding A3 Thinking"?

  • A3 is a thinking process: The value lies in the disciplined, logical, and collaborative approach to problem-solving, not just the report format.
  • PDCA is foundational: The Plan-Do-Check-Act cycle is the backbone of continuous improvement and is deeply embedded in Toyota’s culture.
  • Seven elements of A3 thinking: Logical thinking, objectivity, focus on results and process, synthesis and visualization, alignment, coherence, and a systems viewpoint are essential.
  • Mentoring and learning: The A3 process is as much about developing people as it is about solving problems, with mentoring and review being central.

How does "Understanding A3 Thinking" define the A3 report and its purpose?

  • One-page structured report: An A3 report is a concise, visual, and structured document (typically one side of an 11x17” sheet) that summarizes a problem, analysis, countermeasures, and action plans.
  • Tool for PDCA management: It operationalizes the PDCA cycle, making thinking and decision-making visible and reviewable.
  • Facilitates alignment and learning: The A3 report is a focal point for discussion, feedback, and consensus-building across functions and levels.
  • Not just documentation: The process of creating and discussing the A3 is more important than the document itself.

What are the seven elements of A3 thinking described by Durward K. Sobek II?

  • Logical thinking process: Emphasizes disciplined, step-by-step reasoning and clear cause-effect relationships.
  • Objectivity: Encourages fact-based analysis, minimizing bias and subjective opinions.
  • Results and process: Stresses the importance of achieving results through robust, repeatable processes.
  • Synthesis, distillation, and visualization: Requires condensing complex information into clear, visual, and actionable insights.
  • Alignment: Focuses on building consensus and shared understanding across stakeholders.
  • Coherency within and consistency across: Ensures logical flow within the report and consistency with organizational goals and other reports.
  • Systems viewpoint: Promotes understanding the broader context and avoiding sub-optimization.

How does the PDCA (Plan-Do-Check-Act) cycle underpin A3 thinking in the book?

  • Framework for improvement: PDCA provides a structured approach to problem-solving and continuous learning.
  • Emphasis on planning: Toyota invests heavily in the Plan phase to deeply understand problems before acting.
  • Check and Act are critical: The book highlights the importance of verifying results and institutionalizing successful changes.
  • Iterative learning: PDCA is a repeating cycle, fostering ongoing improvement rather than one-off fixes.

What are the main types of A3 reports explained in "Understanding A3 Thinking"?

  • Problem-solving A3: Used to analyze and resolve specific issues, following the PDCA cycle closely.
  • Proposal A3: Developed during the planning phase to recommend significant changes, policies, or investments, often before implementation.
  • Status (or project review) A3: Summarizes progress, results, and next steps after implementation, focusing on the Check and Act phases.
  • Flexible templates: While each type has a typical structure, the book emphasizes adapting the format to fit the situation and audience.

What is the practical process for problem-solving using A3 thinking, according to the book?

  • Grasp the current situation: Go to the actual place (genba), observe, and collect data to understand the problem context.
  • Identify root causes: Use techniques like the 5 Whys and fishbone diagrams to dig beyond symptoms.
  • Devise and visualize countermeasures: Brainstorm and select actions that address root causes, and depict the future state.
  • Create and execute implementation and follow-up plans: Assign responsibilities, set timelines, and plan how to check effectiveness.
  • Engage stakeholders: Discuss with affected parties, obtain approval, and ensure alignment throughout the process.

How does "Understanding A3 Thinking" advise on writing effective A3 reports?

  • Be concise and visual: Fit all key information on one page, using diagrams, charts, and tables where possible.
  • Use clear structure and flow: Organize sections logically (background, current condition, analysis, countermeasures, etc.).
  • Write for the audience: Tailor content and language to the needs and knowledge of the intended readers.
  • Prioritize clarity and brevity: Avoid jargon, repetition, and unnecessary detail; highlight key points for quick understanding.

What role do mentoring and review play in the A3 process, as described by Durward K. Sobek II?

  • Mentoring opportunity: Managers use A3 reviews to coach and develop problem-solving skills in their teams.
  • Socratic questioning: Reviews often involve probing questions to test the author’s understanding and reasoning.
  • Ensures rigor and alignment: The review process checks for thoroughness, objectivity, and consensus among stakeholders.
  • Promotes organizational learning: Sharing and critiquing A3s helps disseminate best practices and lessons learned.

What are common pitfalls or misconceptions about A3 thinking and how does the book address them?

  • Form over substance: Mistaking the A3 report as just a documentation tool, rather than a thinking and learning process.
  • Template rigidity: Over-standardizing the format at the expense of flexibility and context-appropriate communication.
  • Skipping steps: Neglecting the Plan or Check phases, or failing to engage stakeholders and mentors.
  • Superficial analysis: Stopping at symptoms rather than digging for root causes, or implementing solutions without verification.

What are some of the best quotes from "Understanding A3 Thinking" and what do they mean?

  • “A3 is more of a way of thinking than a report-writing methodology.” – Emphasizes that the mindset and process are more important than the document itself.
  • “The A3 provides a disciplined way of reporting on problems that encourages a disciplined way of solving problems.” – Highlights the link between structured communication and effective problem resolution.
  • “The process of creating and discussing the A3 is more important than the document itself.” – Reminds readers that collaboration, feedback, and learning are central to the A3 approach.
  • “Do not become slave to a format, but use the format as a standard for starting your A3 reports.” – Encourages flexibility and adaptation rather than rigid adherence to templates.
  • “Improvement efforts in companies become ineffective when the emphasis becomes adhering to a standard tool and enforcing a certain way of doing things.” – Warns against prioritizing tools over genuine improvement and learning.

About the Author

Durward K. Sobek II is an expert in lean manufacturing and organizational improvement. He has extensively studied Toyota's management practices and is known for his work on A3 thinking. Sobek is a professor of Industrial and Management Systems Engineering at Montana State University. His research focuses on product development, lean manufacturing, and healthcare delivery systems. He has authored several books and articles on these topics, with "Understanding A3 Thinking" being one of his most recognized works. Sobek's expertise in translating Toyota's problem-solving methods for broader application has made him a respected figure in the field of continuous improvement and lean management.

Download PDF

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

Download EPUB

To read this Understanding A3 Thinking 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.39 MB     Pages: 25
Want to read the full book?
Follow
Listen
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...