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
Radical Focus

Radical Focus

Achieving Your Most Important Goals with Objectives and Key Results
A tea startup is losing focus; can its founders turn ambitious goals into a working business?
by Christina Wodtke 2016 179 pages
3.96
4k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Protect the time needed to turn a promising idea into reality.

Ideas are the easy part. TeaBee’s founders, Hanna and Jack, wanted to connect excellent tea growers with restaurants. The business began to stall when restaurants hesitated to buy from a new company. Hanna noticed restaurant suppliers were willing to place much larger orders, reaching many restaurants at once. That shift could preserve TeaBee’s mission while giving it a viable business. Jack resisted because he feared losing control over quality and the brand. Their conflict was not simply about tea. It was about whether the founders would follow evidence or cling to their preferred version of the idea.

Distraction has a cost. The book compares tempting opportunities to obstacles that pull a runner away from the finish line. A conference invitation, a custom request, or an attractive side project can all consume the time a goal needs. A clear objective helps a team decide which opportunities to decline.

Analysis

The story’s useful tension is that focus does not mean stubbornly preserving the first plan. Hanna’s pivot is disciplined because it changes the route while retaining the purpose. This resembles adaptive strategy: hold the problem steady, but let evidence revise the solution. The counterpoint is that customer demand alone cannot settle every question. A profitable channel might erode quality or mission over time. The founders therefore need explicit boundaries, not just a revenue signal, so adaptation does not quietly become a different company.

Measure the change customers experience, not the projects teams ship.

Outputs are not outcomes. An Objective states a meaningful destination, while Key Results are measurable signs that the destination has been reached. For TeaBee, building an online ordering feature would be an output. Seeing a rising share of supplier orders placed independently, alongside stronger customer satisfaction, would indicate an outcome. A team can complete a help center, a redesign, and training without improving the customer’s ability to solve a problem. The book recommends asking what should change if a proposed project works, and which numbers would reveal that change.

Choose measures carefully. Three Key Results can offer different views of progress, such as revenue, repeat use, and customer satisfaction. Pairing measures helps expose trade-offs. A revenue increase alongside worsening retention may signal that short-term sales are masking a weak customer experience.

Analysis

This distinction is a practical defense against mistaking activity for value. It also reflects a measurement problem across science and management: observable indicators are proxies, not the thing itself. A well-chosen proxy makes a goal discussable; a poor one invites teams to optimize the number while neglecting the underlying purpose. Multiple measures reduce that risk, though they do not eliminate it. Teams should ask not only whether a metric moved, but whether the movement plausibly represents a better experience for the people the product serves.

Give the whole company one priority people can actually remember.

Focus has a memory limit. TeaBee’s first attempt at OKRs gave the company several objectives, spanning supplier value, the ordering platform, sales, and customer service. By quarter’s end, Hanna and Jack could barely recall all of them, and the team had pursued plenty of work that did not support the agreed goals. The revised approach centered the company on one shared objective, with a small set of measurable results. Teams then connected their own work to that priority instead of receiving a separate agenda for every department.

Simplicity is a management choice. A small company may need just one company objective. A large organization can align autonomous product teams to the company strategy, while teams with unrelated business models may need separate objectives. The point is not to force every group into one metric. It is to make the organization’s priorities clear enough to guide everyday choices.

Analysis

A memorable priority functions like a shared decision rule: it helps people resolve small conflicts without waiting for a manager. That is especially valuable in complex organizations, where local teams see information leaders cannot. The strongest version of focus therefore combines a clear center with room for local judgment. Too many goals fragment attention, but one universal target can flatten genuinely different businesses. The book’s emphasis on one objective is best understood as a default for coherence, not a reason to pretend every unit has the same job.

Make execution a weekly rhythm, not a quarterly announcement.

Goals need repetition. OKRs means Objectives and Key Results, a method for setting a time-bound goal and tracking measurable outcomes. The book argues that the method’s real force comes from its cadence, not from writing a polished goal once and leaving it on a wall. TeaBee’s founders initially set OKRs but did not regularly revisit them. The team drifted back to familiar work, including tastings and design polish, while urgent order problems went unresolved.

Build the week around progress. At the start of the week, people identify a few priorities, discuss confidence in the results, flag blockers, and share what is approaching. At week’s end, teams show work and recognize concrete wins. TeaBee’s Friday demonstrations made engineering, design, sales, and customer service work visible to one another. The rituals supported both accountability and morale, without requiring a lengthy report of every task.

Analysis

The cadence turns goals into a feedback loop. In control theory, a system cannot correct its course if it receives no information about its current state. Weekly conversations provide that information and create opportunities to adjust effort before a quarter is lost. Celebration has a functional role too: it makes progress socially visible, not merely emotionally pleasant. Still, rituals can become theater if meetings reward confident reporting over honest diagnosis. Their value depends on whether people can surface bad news and ask for help without being punished.

Set goals that stretch judgment without making failure inevitable.

Aim beyond the comfortable. The book recommends setting ambitious Key Results that a team believes it has roughly a one-in-two chance of achieving. A confidence rating of five out of ten is a starting estimate, not a promise. If every goal is easy, the team may be sandbagging. If success seems impossible, the target can demoralize people or encourage them to hide problems. In TeaBee’s revised process, the team discussed confidence as the quarter unfolded, changing its estimate when evidence or obstacles changed.

Use the forecast to learn. A falling confidence rating should prompt questions: What changed? Is the plan failing? Can another team help? The number is useful because it opens a conversation, not because it predicts the future precisely. Hard goals create useful tension only when leaders treat misses as information rather than automatic evidence of poor performance.

Analysis

The middle ground between easy goals and impossible demands is psychologically important. Challenge can direct attention and effort, but threat can redirect effort toward self-protection. Confidence ratings make uncertainty visible while avoiding the fiction that early forecasts are exact. Their weakness is subjectivity: two teams may use the same rating differently. A group benefits from discussing what evidence would raise or lower confidence, so the scale becomes a shared language rather than a mood report.

Watch the business you could damage while chasing the business you want.

Protect what already works. Health Metrics track essential conditions the organization should maintain while pursuing change. Examples include customer satisfaction, code stability, team well-being, and repeat business. TeaBee’s push to gain suppliers could have harmed existing customers if orders became inaccurate or support deteriorated. A health signal gives the team a reason to notice such damage before it becomes a larger crisis. If a vital measure turns red, the company may need to pause its growth effort and address the immediate risk.

Do not weaponize targets. The book warns that impossible top-down demands tied to jobs or compensation can provoke cheating. It points to scandals at Wells Fargo and Volkswagen, where pressure to meet aggressive targets contributed to deceptive practices. OKRs should guide learning and prioritization, not serve as a complete performance scorecard. Individual contributions still require ongoing managerial judgment and conversation.

Analysis

This is a governance insight as much as a measurement technique. Every target creates incentives, including incentives its designers did not intend. Goodhart’s law captures the danger: once a measure becomes a high-stakes target, it can stop representing the quality it was meant to track. Health signals and independent measures of customer experience act as partial safeguards. Yet red, yellow, and green labels are blunt instruments. They work best as prompts for investigation, not as substitutes for evidence or dialogue.

Use OKRs to empower capable teams, never to micromanage them.

Autonomy is a prerequisite. OKRs specify what outcome matters, while leaving the team room to decide how to achieve it. In TeaBee’s first cycle, Jack repeatedly returned to tasks he preferred, and Hanna delayed hard conversations about his responsibilities. Meanwhile, an engineer undermined the company’s code to protect his own position. The founders needed to clarify roles, address harmful behavior, and give the team a voice in setting its goals. They also needed to trust people to choose tactics once the desired outcomes were clear.

Safety makes candor possible. The book recommends building relationships and team agreements so people can question plans, admit uncertainty, and discuss conflict. It advises against individual OKRs as a routine management tool, because they can become a mechanism for micromanagement. Team goals should coordinate work, not turn each person into a quota-bearing unit.

Analysis

The distinction between direction and control is central. A team cannot be accountable for outcomes while being denied meaningful authority over its methods. Psychological safety, the shared sense that speaking up is socially acceptable, supports the information flow such accountability requires. It does not mean avoiding standards or difficult personnel decisions. TeaBee’s response to deliberate code obfuscation shows that empowerment also needs boundaries. Trust is not permissiveness; it is a working relationship in which expectations are clear and people can raise problems early.

Keep solutions flexible when evidence is still arriving.

Treat plans as hypotheses. OKRs should describe the result to pursue, not freeze a project plan into a commitment. The book recommends keeping a pipeline of possible projects and comparing their potential impact, effort, and supporting evidence. If one tactic fails to move a Key Result, a team can try another. A fixed roadmap can make an early guess feel permanent, even after customers show it is wrong.

Match the goal to uncertainty. Exploratory OKRs help teams investigate an unfamiliar market. Hypothesis OKRs test whether a proposed value proposition attracts real demand. Milestone OKRs define meaningful evidence for long projects, such as whether a prototype improves users’ experience. The Half-Built Strategy keeps the next quarter specific while leaving later objectives provisional, because distant forecasts are less reliable than near-term ones.

Analysis

This approach combines strategic intent with experimental flexibility. It resembles the scientific method: state what would count as evidence, run a test, and revise the explanation when results disagree. The distinction between a pipeline and a fixed roadmap protects teams from escalating commitment to a weak idea. But flexibility needs a stable question. Without a clear mission or strategy, repeated experimentation can become random motion. The useful balance is a durable direction with revisable tactics and a willingness to stop when evidence remains poor.

Treat missed goals as data, then improve the next cycle.

A first miss can diagnose the system. TeaBee’s first quarter ended with none of its Key Results achieved. The problem was not simply that OKRs had failed. The team had set too many objectives, lacked weekly follow-through, and kept doing familiar work that did not move the chosen measures. After recognizing those patterns, the founders simplified the company goal, involved employees, and began checking progress regularly. Later results improved, although the team still sometimes missed targets.

Start small and review honestly. The book recommends piloting OKRs with a capable team, or beginning with one company-level objective, rather than imposing a full hierarchy of goals at once. Teams can score results numerically, but the score is only a starting point for discussing what happened, what was learned, and what should change. OKR performance should inform the work conversation, not mechanically determine an employee’s pay or worth.

Analysis

The narrative makes failure useful by distinguishing a failed goal from a failed method. That distinction supports organizational learning: teams can change the process without abandoning the underlying aim. A pilot also limits the cost of adopting a new management practice before its assumptions are tested. The caution is that iteration can become an excuse to normalize chronic overload or endlessly reset targets. Learning requires naming the cause of a miss and changing something specific, not merely promising to try harder next quarter.

Analysis

Radical Focus is both an introduction to OKRs and an argument about the kind of organization in which they can work. Its central contribution is to shift attention away from goal-writing as a standalone exercise and toward a repeating cycle: choose a priority, define evidence of impact, coordinate action, inspect progress, and learn. The TeaBee story gives that cycle human stakes. Hanna and Jack do not fail because they lack ambition. They fail because their ambitions compete, their roles are unclear, and the company’s attention keeps returning to familiar work. The narrative makes execution a problem of alignment and behavior, not merely planning.

The framework is strongest when it separates outcomes from deliverables and when it treats weekly check-ins as opportunities to revise action. This makes OKRs compatible with experimentation rather than rigid project control. The insistence on a small number of memorable goals also respects a basic constraint: people cannot use priorities they cannot recall. Health metrics extend the method by making visible what growth efforts might damage, while the emphasis on empowered teams explains why top-down adoption often produces empty compliance.

The same strengths create limits. Measurable outcomes are proxies, and some valuable work has delayed or ambiguous effects. A team can also be held responsible for results affected by market conditions or other departments, even when it has little control over them. Confidence ratings help surface uncertainty but do not remove it. The book’s answer is not to abandon measurement, but to pair it with context, autonomy, and candid review. That answer depends on management behavior: leaders must accept uncomfortable results, distinguish learning from negligence, and avoid tying ambitious goals mechanically to compensation.

The practical lesson is that OKRs are not a software feature or a reporting template. They are a compact operating rhythm for organizations willing to focus, communicate repeatedly, and change course based on evidence. Without trust and honest discussion, the same metrics can become another instrument of command and control. With those conditions, they can help a team protect its purpose while adapting its plans.

Summary in 30 Seconds
TeaBee founders Hanna and Jack set out to connect tea growers with restaurants, but hesitant buyers slow the business. A supplier offers a route to larger orders, though Jack worries that growth will weaken the brand. Their first goal-setting effort sprawls across too many priorities, and the team ends its quarter without meeting its key results. Weak follow-through, unclear responsibilities, and harmful behavior among employees compound the problem. Hanna and Jack narrow the company’s focus, involve the team, and establish regular check-ins and demonstrations. They track customer impact alongside business health, give teams freedom over methods, and adjust plans as evidence changes. Later results improve, though some targets remain unmet. The experience shows how focused goals, candid reviews, and team autonomy can help a company learn and adapt.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.96 out of 5
Average of 4k+ ratings from Goodreads and Amazon.

Radical Focus receives mixed reviews, with an average rating of 3.97 out of 5. Many readers appreciate the OKR framework presented but criticize the book's structure. Some find the storytelling approach engaging, while others consider it unnecessary. Positive reviews highlight the practical advice and actionable insights, particularly in the latter part of the book. Criticisms include redundant information, grammatical errors, and a lack of depth. Several reviewers suggest the content could be condensed into a shorter format. Overall, it's considered a good introduction to OKRs, especially for beginners.

Your rating:
4.47
437 ratings
Want to read the full book?

Glossary

OKRs

Goals with measurable outcomes

Objectives and Key Results, a goal-setting and execution method. An Objective describes an important, time-bound destination in qualitative terms. Key Results provide measurable evidence of whether the destination has been reached. In this book, OKRs also include regular progress conversations and end-of-cycle reflection, not just the written goals.

Objective

A motivating near-term goal

The qualitative part of an OKR. An Objective describes what a team wants to accomplish over a defined period, often a quarter. It should be meaningful, clear, ambitious but possible, and within the team’s ability to influence. Unlike a numeric target, it gives the measurable results a shared purpose.

Key Results

Measures of achieved outcomes

The measurable indicators paired with an Objective. Key Results show whether the intended change occurred, using measures such as revenue, repeat use, satisfaction, or performance. They should describe results rather than a list of projects. A team can change its tactics when the measures reveal that its current approach is not working.

Health Metrics

Signals of operational wellbeing

Measures monitored to ensure that pursuing an ambitious objective does not damage essential parts of the organization. Examples include customer satisfaction, team health, code stability, and existing business performance. A deteriorating health metric can prompt a team to investigate, intervene, or temporarily redirect effort from its growth objective.

Exploratory OKRs

Goals for investigating unknown markets

An OKR variant for teams that do not yet know which market, customer, or use case will respond to an idea. It provides a provisional destination and measurable signals, such as preorders or beta use, while the team runs small experiments. The purpose is to learn where opportunity exists, not to pretend the answer is already known.

Hypothesis OKRs

Tests of a value proposition

An OKR variant used after a promising direction has emerged. The Objective states a hypothesis about how a particular market will value a product or service. Key Results measure market response, such as purchases, conversions, or repeat use. Results help the team decide whether to pursue, revise, or abandon the hypothesis.

Milestone OKRs

Outcome checks for long efforts

An OKR variant for work that takes longer than a single quarter, including research and development or complex launches. Instead of measuring task completion alone, the Key Results define evidence that a project is moving toward a worthwhile outcome. These checkpoints let teams learn and change direction before committing to the entire long-term effort.

Pipeline

A flexible set of possible projects

A collection of candidate projects that might help achieve an Objective or Key Result. Teams compare ideas using factors such as potential impact, effort, and evidence, then choose what to test. Unlike a fixed plan, a Pipeline preserves options so teams can replace tactics that fail to produce the desired outcome.

Half-Built Strategy

A near-term plan with future drafts

A planning approach that makes the next quarter’s Objective and Key Results specific while sketching only tentative Objectives for later quarters. It provides direction without pretending that distant conditions can be predicted precisely. As the team learns from each cycle, it can revise future priorities and define their measures when they become more relevant.

Four Square

A weekly progress overview

A compact status format used to structure weekly team conversations. It brings together the week’s most important priorities, upcoming work, confidence in Key Results, and selected health signals. The format is meant to support discussion and coordination, not to make people read a report aloud or list every task they completed.

FAQ

What's "Radical Focus" about?

  • Core Concept: "Radical Focus" by Christina Wodtke is about achieving significant goals using the Objectives and Key Results (OKRs) framework.
  • Narrative Approach: The book uses a business fable to illustrate how a struggling startup can use OKRs to turn their business around.
  • Practical Guidance: It provides practical advice on setting and achieving goals, focusing on outcomes rather than tasks.
  • Empowerment and Culture: The book emphasizes the importance of a culture of empowerment and how OKRs can help foster this within teams.

Why should I read "Radical Focus"?

  • Goal Achievement: It offers a proven framework for setting and achieving ambitious goals, which can be applied in both personal and professional contexts.
  • Real-World Application: The book addresses common challenges and mistakes in implementing OKRs, providing solutions based on real-world experiences.
  • Engaging Format: The use of a narrative makes complex concepts more relatable and easier to understand.
  • Expert Insights: Christina Wodtke is a recognized thought leader in the field, bringing valuable insights from her experience with companies like LinkedIn and Zynga.

What are the key takeaways of "Radical Focus"?

  • Focus on Outcomes: The book stresses the importance of focusing on outcomes rather than outputs or tasks.
  • Iterative Learning: It highlights the need for continuous learning and iteration to improve goal-setting and achievement processes.
  • Cultural Shift: Successful implementation of OKRs requires a shift towards a culture of empowerment and trust within teams.
  • Cadence and Commitment: Regular check-ins and celebrations are crucial for maintaining focus and motivation towards achieving OKRs.

How does Christina Wodtke define OKRs in "Radical Focus"?

  • Objective: A qualitative, inspirational goal that motivates the team and is time-bound.
  • Key Results: Quantitative measures that indicate whether the objective has been achieved, typically three per objective.
  • Outcome-Oriented: OKRs focus on the desired outcomes rather than the tasks or projects to achieve them.
  • Iterative Process: OKRs are set, tracked, and graded regularly, allowing for adjustments and learning.

What is the "Executioner's Tale" in "Radical Focus"?

  • Business Fable: The "Executioner's Tale" is a fictional story used to illustrate the practical application of OKRs in a startup setting.
  • Character Journey: It follows Hanna and Jack, founders of a struggling tea startup, as they learn to implement OKRs to achieve their business goals.
  • Challenges and Solutions: The story addresses common challenges in goal setting and execution, providing solutions through the characters' experiences.
  • Engagement and Learning: The narrative format makes the concepts more engaging and memorable for readers.

How does "Radical Focus" suggest implementing OKRs for the first time?

  • Start Small: Begin with a pilot team or a single OKR for the entire company to reduce complexity and risk.
  • Focus on Learning: Use the initial cycles to learn and adjust the approach, rather than expecting immediate success.
  • Simplify the Process: Avoid overcomplicating the process with too many OKRs or unnecessary software initially.
  • Iterative Improvement: Continuously refine the OKR process based on feedback and results from each cycle.

What are the common mistakes in using OKRs according to "Radical Focus"?

  • Task Focus: Mistaking tasks or projects for key results, which should be outcome-based.
  • Lack of Iteration: Failing to iterate and learn from each OKR cycle, leading to repeated mistakes.
  • Cultural Misalignment: Implementing OKRs without fostering a culture of empowerment and trust.
  • Overcomplication: Setting too many OKRs or making the process too complex, which can overwhelm teams.

How does "Radical Focus" address the role of culture in OKR success?

  • Empowerment Culture: OKRs thrive in a culture where teams are empowered to make decisions and take ownership of outcomes.
  • Trust and Safety: Psychological safety and trust are essential for teams to experiment and learn from failures.
  • Communication: Regular communication and reiteration of goals are crucial for maintaining focus and alignment.
  • Leadership Role: Leaders must model and support the cultural shift towards empowerment and focus on outcomes.

What are the best quotes from "Radical Focus" and what do they mean?

  • "Solve the problems you have, not the ones you imagine." This emphasizes focusing on real, present challenges rather than hypothetical or future issues.
  • "When you are tired of saying it, people are starting to hear it." Highlights the importance of consistent communication and reinforcement of goals.
  • "OKRs are all about mapping the actions we take now to the outcomes we want later." Stresses the connection between current efforts and future results.
  • "Life is too short to start work on your dreams 'tomorrow,' for tomorrow never comes." Encourages immediate action towards achieving goals.

How does "Radical Focus" suggest balancing OKRs with other business operations?

  • Health Metrics: Use health metrics to monitor ongoing operations and ensure they remain stable while pursuing OKRs.
  • Prioritization: Clearly prioritize OKRs over routine tasks to ensure focus on strategic goals.
  • Flexibility: Allow for adjustments in operations to support the achievement of OKRs without compromising essential business functions.
  • Integration: Integrate OKRs into existing processes to align them with overall business objectives.

What is the role of the "cadence" in OKRs according to "Radical Focus"?

  • Regular Check-Ins: Weekly check-ins help track progress and adjust efforts towards achieving OKRs.
  • Commitment Meetings: Monday meetings set intentions and priorities for the week, aligning team efforts with OKRs.
  • Celebration Rituals: Friday celebrations recognize achievements and maintain motivation and morale.
  • Continuous Feedback: The cadence provides continuous feedback, enabling teams to learn and adapt quickly.

How does "Radical Focus" recommend using OKRs for product teams?

  • Team-Level Focus: Product teams should focus their OKRs on business-related objectives that align with company goals.
  • Cross-Functional Alignment: Ensure alignment across different functional areas within the product team to avoid conflicting priorities.
  • Outcome-Based Objectives: Set objectives that drive meaningful business outcomes rather than departmental tasks.
  • Iterative Learning: Use OKRs to foster a culture of continuous learning and improvement within product teams.

About the Author

Christina R Wodtke is a prominent figure in Silicon Valley, known for her expertise in product design and team management. She has worked with major tech companies like LinkedIn, MySpace, and Yahoo!, and has founded three startups. Wodtke is a Lecturer at Stanford University in the HCI group and teaches globally on innovation and high-performing teams. She is the author of several books, including the bestselling "Radical Focus," which uses storytelling to explain the OKR framework. Wodtke's work focuses on combining human innovation with effective team performance, and she is recognized for her engaging and insightful approach to teaching and writing.

Download PDF

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

Download EPUB

To read this Radical Focus 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.43 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...