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
Managing the Unexpected

Managing the Unexpected

Resilient Performance in an Age of Uncertainty
Build an organization that catches small failures before they become disasters.
by Karl E. Weick 2001 208 pages
3.78
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat weak signals as system warnings, not harmless exceptions

The warning arrived early. In May 2000, a planned burn at New Mexico’s Cerro Grande escaped its boundaries. The crew had struggled to control the fireline, exhausted workers were sent away, and requests for fresh help stalled amid unclear rules and budget concerns. Then strong winds pushed the blaze toward Los Alamos. It burned 48,000 acres, destroyed 235 homes and 39 laboratory buildings, and caused about $1 billion in damage.

Small failures connected. A firefighter described the escape as beginning with a tiny strip of flame crossing the line. The disaster was not simply one person’s mistake. Underestimated complexity, thin staffing, delayed support, and changing conditions combined. The authors use high reliability organizations, or HROs, as a contrast: these are groups operating in hazardous conditions that work to catch trouble early and keep errors from disabling the system.

Analysis

The case makes organizational failure easier to understand as a chain than as a single bad decision. Each weak point looked manageable in isolation, but their interaction narrowed the crew’s options. This resembles the way small faults can compound in tightly connected technical systems. The practical implication is to examine how problems travel between teams, rules, and resources, not only whether each unit followed its procedure. Still, a system explanation should not erase individual accountability. It makes accountability more useful by asking what conditions made the action likely, and how those conditions can be changed.

Question what your expectations are making you overlook

Expectations guide attention. They help people coordinate, but they also encourage them to notice confirming evidence and explain away contradictions. The authors call mindfulness a rich awareness of relevant detail: noticing context, revising assumptions, and recognizing when events do not fit the expected pattern.

Surprise has three forms. Something expected may fail to happen, something unexpected may happen, or an event nobody imagined may appear. On aircraft carriers, a loose bolt once caused an engine failure. Crews responded by walking the flight deck repeatedly to find objects that could be sucked into engines. The walkdowns turn a general expectation of safety into active searching for evidence that it may be wrong. The key moment for learning is often just after surprise, before people explain it away as normal.

Analysis

Expectations are not the enemy; unexamined expectations are. A team without shared assumptions cannot coordinate, but a team that treats its assumptions as settled facts loses sensitivity to change. The carrier example shows how a useful routine can test the very belief that makes routine possible. This is a demanding balance: constantly questioning everything can drain attention and slow action. A stronger approach is selective doubt, aimed at assumptions with serious consequences if they prove false, and at moments when new evidence conflicts with the working picture.

Reward early error reports before silence turns anomalies into normality

Small defects can reveal system health. At Ohio’s Davis-Besse nuclear plant, rust repeatedly clogged air filters. Workers replaced them every two days, though the usual interval was about a month. The rust was an early clue to severe corrosion in a reactor containment structure, which had thinned to about the width of a pencil eraser in one area.

Make reporting safe. HROs treat near misses and small failures as useful information, not automatic proof of individual incompetence. In one example, a worker who reported possibly causing a missile malfunction helped investigators identify the actual cause and avoid unnecessary redesign. Research described in the book also found that nursing teams reporting more errors could be performing better because staff were more willing to discuss mistakes and learn from them. Reporting rates need interpretation, not reflexive punishment.

Analysis

The distinction between error frequency and error visibility is essential. A workplace that hears about more mistakes may be safer than one with a cleaner-looking record, because its people can surface problems while they are still manageable. This shifts the managerial question from how to suppress error to how to make error legible. Yet openness alone is not enough: reporting without follow-up teaches employees that candor is pointless. Leaders need to show what was learned, what changed, and where the limits of acceptable conduct remain.

Keep categories provisional when familiar labels hide important differences

Labels simplify the world. They help people coordinate, but they can also hide details that signal danger. At Cerro Grande, the burn’s complexity was assessed with the wrong rating scale, making the same conditions appear less demanding and supporting a smaller resource plan. In another example, calling an oxygen generator empty obscured the fact that it could still contain volatile material.

Preserve the inconvenient detail. HROs do not reject categories; they use them cautiously and revise them when evidence changes. They seek different perspectives because people with different roles may notice different features of the same event. A familiar label should prompt a check: does this situation truly resemble the cases behind the label, or does the resemblance conceal a consequential difference?

Analysis

Categories are necessary for action, but they are also compressed theories about what matters. The danger is not only that a label is inaccurate. It can shape what people search for next, making the label self-confirming. Diverse teams help by keeping more than one interpretation in play, provided disagreement can be expressed without becoming a status contest. There is a cost: too many competing descriptions can delay decisions. The goal is not endless analysis, but enough interpretive variety to catch distinctions that change the risk.

Manage the work as it unfolds, not as the plan describes it

Plans describe intentions. Sensitivity to operations means staying close to what people are actually doing, what conditions they face, and how the system is changing. At Cerro Grande, the on-scene burn boss sought a fresh crew before the fire was formally declared escaped. Dispatch hesitated because its interpretation of the rules did not match the crew’s urgent operational need. While they argued over status and resources, the fire continued to grow.

Frontline detail matters. Carrier crews continually adjust to changing wind, sea, deck, and aircraft conditions. Nuclear plant teams use frequent briefings and cross-department conversations to build a current picture of interdependent work. The authors’ point is that strategy and procedure cannot fully specify action in a changing environment. Managers need contact with operations and channels for frontline staff to speak up.

Analysis

This principle challenges the idea that managers can understand a system primarily through plans, dashboards, and reports. Those tools summarize work, but summaries can miss timing, friction, and improvised coordination. Direct contact supplies context that formal data often cannot. However, staying close to operations should not become managerial micromanagement. The value lies in listening, noticing variation, and removing obstacles, while leaving decisions with people who understand the immediate task. Operational awareness is a shared capability, not a leader’s claim to know everything.

Build recovery capacity for failures no plan can predict

Resilience means continuing or recovering. It is a system’s ability to preserve its function through disruption, or to regain stability without collapsing completely. The authors argue that errors cannot all be prevented, so organizations need broad skills, experience, resources, and the ability to improvise and learn while responding.

Slack can protect service. Each evening, FedEx’s domestic network sent roughly 20 to 25 aircraft toward Memphis only 60 percent full. The unused space gave controllers room to divert aircraft and recover unexpected cargo. They still protected a hard arrival deadline rather than stretching the whole system to save one shipment. This reserve capacity costs something when nothing goes wrong, but it gives the operation room to absorb surprises when something does.

Analysis

Resilience changes the definition of efficiency. A system optimized to use every person, minute, and asset may perform brilliantly in ordinary conditions and fail abruptly when conditions shift. Reserve capacity is not waste if it preserves options. The harder question is where to place that capacity, since unlimited slack is neither affordable nor necessary. The book’s examples point toward targeted reserves: knowledge, trained people, flexible relationships, and time near critical bottlenecks. Recovery should also leave the organization more capable, rather than merely restoring the conditions that produced the failure.

Let decisions move toward the people closest to the problem

Rank and knowledge differ. Deference to expertise means that authority can shift toward whoever has the relevant knowledge, regardless of title. Decisions may move downward to someone who sees a problem first, or upward when broader experience and coordination are needed. Expertise is often distributed across several people rather than held by one celebrated specialist.

Columbia shows the cost of hierarchy. After debris struck the space shuttle during launch, several groups asked for clearer images. Managers focused partly on who was asking rather than on the technical basis for the request. The damage was treated as a relatively familiar tile issue, while expertise about another vulnerable area was not adequately brought into the discussion. The authors also warn against excessive deference to a famous expert: others may stop sharing observations that the expert has not noticed.

Analysis

Flexible authority is not the same as abandoning accountability. The useful shift is to let the problem determine whose knowledge matters, while keeping the decision visible and coordinated. This is especially important when expertise is narrow: a specialist may know one component deeply without understanding the whole system. Teams therefore need ways to combine technical knowledge, local observation, and organizational authority. A culture that celebrates experts but discourages challenge can recreate the hierarchy it claims to bypass.

Turn mindful behavior into norms, not a slogan on the wall

Culture shapes what gets noticed. An informed culture is one where people managing and operating a system have current knowledge of the human, technical, organizational, and environmental conditions affecting safety. The book describes four supporting habits: people report problems, blame is handled fairly, roles can adapt under pressure, and lessons lead to changed practice.

Bristol lacked these conditions. In five of seven years from 1988 to 1994, mortality for babies undergoing open-heart surgery at the Bristol Royal Infirmary was roughly twice that of other English centers. More than a hundred concerns were raised, yet a closed, largely oral culture and a powerful inner circle limited scrutiny. Poor outcomes were often explained away rather than treated as evidence that the service might need to stop or change. Culture is built through repeated actions, what leaders reward, and what colleagues accept.

Analysis

The Bristol case shows how a group can convert warning signs into stories that protect its existing identity. This is not necessarily conscious deception; it can emerge from loyalty, professional pride, and pressure to keep a service running. A fair reporting environment must therefore do more than invite feedback. It must make dissent consequential, establish how accountability works, and connect evidence to decisions. Culture change cannot be reduced to leadership messaging, since local groups interpret messages differently. The proof of a value is the behavior that receives support when it becomes inconvenient.

Make change tangible through small experiments that teach the system

Small wins create evidence. A small win is a concrete, completed change of moderate importance that shows improvement is possible and helps reveal where resistance or opportunity lies. Rather than wait for an organization-wide transformation, managers can change a meeting habit, improve information sharing, or test a safer handoff.

Review events for learning. Wildland firefighters use after-action reviews to compare what they intended, what occurred, why it happened, and what should change. Staff rides go further by placing participants at the site of a past incident and asking them to reason through the decisions made there. Audits can also reveal differences between how departments see one another and how they see themselves. Those disagreements are useful clues, not noise to be averaged away.

Analysis

Small experiments make abstract principles observable. They allow a group to test whether a new practice actually improves reporting, coordination, or recovery before scaling it. This resembles disciplined learning: define a change, observe its effects, and revise the explanation. But incrementalism has a limit. When a practice is causing serious harm, a modest adjustment can become a way to postpone decisive action. Small wins work best when they are tied to clear measures, honest review, and a willingness to stop an experiment that is not improving the system.

Analysis

The book’s central contribution is a shift in what reliability means. Reliability is not the calm repetition of a perfect procedure. It is the continuing work of detecting variation, interpreting it accurately, and adapting without losing control. That makes the organization less like a machine running a fixed program and more like a group maintaining a shared, revisable picture of a changing situation.

The five principles form a practical sequence. Attention to failure, resistance to premature simplification, and contact with operations help identify trouble before it spreads. Resilience and deference to expertise help contain trouble once prevention has failed. Their value lies in their combination. Failure data without psychological safety stays hidden. Diverse interpretations without respectful coordination become argument. Local expertise without authority becomes advice that can be ignored. Flexibility without shared purpose becomes fragmentation.

The cases also make clear that organizational learning is political. Information competes with status, budgets, professional identity, and the desire to preserve a successful story. A concern can be present in the system yet have no influence if the person raising it lacks credibility or access. For that reason, mindfulness is not merely an individual virtue. It depends on structures that give observations a route to decision makers and make it safe to revise a settled view.

The argument has a real tension: broad vigilance is valuable, but attention and resources are finite. A team cannot treat every discrepancy as an emergency or debate every assumption indefinitely. The book’s strongest implied answer is context: intensify scrutiny where work is tightly connected, fast-moving, consequential, or difficult to reverse. For less hazardous work, routine and standardization may be efficient. The challenge is recognizing when the environment has changed enough that routine has become a blindfold. Preparedness is not predicting every surprise. It is keeping enough interpretive range, expertise, and capacity to respond when prediction fails.

Summary in 30 Seconds
Serious failures often grow from minor warning signs, delayed help, and assumptions that hide changing conditions. Make it safe to report mistakes, stay informed about frontline work, and let decisions follow relevant expertise rather than rank. Reliability also requires spare capacity: FedEx sent evening aircraft toward Memphis about 60 percent full, leaving room to absorb disruptions. Review incidents and test small changes to improve future responses.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.78 out of 5
Average of 500+ ratings from Goodreads and Amazon.

Managing the Unexpected receives mixed reviews, with an average rating of 3.82/5. Readers appreciate its insights on high reliability organizations and organizational resilience. Many find the concepts valuable for improving business practices, particularly in unpredictable environments. The book is praised for its real-world examples and counter-intuitive ideas. However, some criticize it for being repetitive, dry, and academic in tone. Several readers note that while the content is valuable, the writing style can be challenging to engage with.

Your rating:
4.35
312 ratings
Want to read the full book?

Glossary

High reliability organizations (HROs)

organizations built for dependable operation

Organizations that operate in hazardous, complex, or rapidly changing conditions while experiencing fewer serious failures than might be expected. They are not error-free. Their distinguishing feature is a continuing effort to detect small problems, learn from near misses, adapt decisions to expertise, and prevent errors from disabling the whole system.

Mindfulness

detailed, revisable awareness

A way of attending that notices context and meaningful differences, questions existing expectations, and updates interpretations as events unfold. In organizations, mindfulness helps people detect early signs of trouble, avoid forcing unfamiliar events into familiar categories, and identify actions that can prevent a problem from spreading or help contain it.

Principles of mindfulness

five practices for reliability

The book’s framework for mindful organizing consists of preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise. The first three support anticipation by improving detection and interpretation. The last two support containment by strengthening recovery and moving decisions toward relevant knowledge.

Mindful infrastructure

routines that sustain alertness

The organizational practices that make mindfulness part of everyday work. These include detecting small failures, preserving differences in interpretation, staying informed about frontline operations, developing recovery capabilities, and allowing authority to shift toward expertise. The infrastructure matters because individual attentiveness alone cannot overcome routines, incentives, or communication systems that hide problems.

Resilience

capacity to continue or recover

The ability of a system to maintain or regain its functioning when internal or external conditions change. Resilience includes absorbing strain, recovering from disruption, and learning in ways that expand future response options. It depends on technical knowledge, varied experience, timely feedback, flexible resources, and the ability to recombine familiar actions in new ways.

Deference to expertise

authority follows relevant knowledge

A decision practice in which authority shifts toward the people or group with the most relevant knowledge for the problem, rather than automatically following rank. Decisions may move toward frontline observers for rapid action or toward senior roles when broader coordination is needed. Expertise is treated as distributed and dependent on interaction, not simply as an individual’s title.

Informed culture

shared knowledge of safety conditions

A culture in which people operating and managing a system possess current knowledge about the human, technical, organizational, and environmental factors affecting its safety. The book describes four supporting subcultures: reporting, just treatment of error, flexibility under pressure, and learning that turns experience into changed assumptions and practices.

Small wins

completed changes that enable learning

Concrete, implemented improvements of moderate importance that show change is possible and reveal practical opportunities or resistance. Small wins need not form a tidy sequence toward a predetermined goal. They can attract support, generate useful evidence, and make larger changes more imaginable, while remaining limited enough to test and revise.

Requisite variety

response range matching problem range

A systems principle stating that an organization needs a sufficiently varied set of responses to cope with the variety of conditions it faces. If the environment produces more variation than the organization can detect or handle, the system becomes vulnerable. Diverse expertise, flexible resources, and multiple interpretations help increase that response range.

Mindfulness Organizing Scale (MOS)

behavior-based mindfulness assessment

A concise assessment described in the book for measuring whether a work unit engages in behaviors associated with mindful organizing. It provides a practical alternative to longer organizational audits. The cited hospital research found that higher scores were associated with fewer reported medication errors and patient falls, making the scale a way to examine practice rather than rely only on stated values.

FAQ

What’s "Managing the Unexpected" by Karl E. Weick and Kathleen M. Sutcliffe about?

  • Focus on High Reliability Organizations (HROs): The book examines how organizations operating in high-risk, complex environments (like nuclear power plants, aircraft carriers, and wildland firefighting) achieve reliable, resilient performance despite constant threats of failure.
  • Unexpected Events and Mindfulness: It explores how organizations can better manage unexpected events by fostering a culture of mindfulness—an ongoing, collective awareness of operations, failures, and expertise.
  • Five Principles of Mindful Organizing: The authors introduce five key principles—preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise—as the foundation for reliable performance.
  • Practical Guidance: Through real-world case studies and practical audits, the book provides actionable strategies for leaders and organizations to assess and improve their capacity to manage the unexpected.

Why should I read "Managing the Unexpected" by Weick and Sutcliffe?

  • Relevance to All Organizations: The book’s lessons apply not only to high-risk industries but to any organization facing uncertainty, complexity, or rapid change.
  • Improved Crisis Management: It offers concrete methods to anticipate, contain, and recover from unexpected disruptions, which is crucial for organizational survival and reputation.
  • Cultivating Resilience and Learning: Readers learn how to build resilient systems that can adapt, learn, and bounce back stronger from setbacks.
  • Benchmarking Against the Best: The book provides insights from organizations that have mastered reliability, offering a blueprint for others to follow.

What are the key takeaways from "Managing the Unexpected"?

  • Mindfulness is Essential: Reliable performance in uncertain environments depends on collective mindfulness—being alert to small failures, operational details, and shifting expertise.
  • Five Principles Drive Reliability: The five principles (preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, deference to expertise) are practical guides for managing the unexpected.
  • Culture Shapes Outcomes: Organizational culture, especially one that values reporting, learning, flexibility, and justice, is critical for sustaining mindful practices.
  • Small Wins Matter: Incremental, visible changes (“small wins”) can cumulatively transform organizational practices and culture toward greater reliability.

How do Weick and Sutcliffe define "mindfulness" in organizations?

  • Rich Awareness of Detail: Mindfulness is defined as a “rich awareness of discriminatory detail,” meaning people notice subtle differences, deviations, and context-specific cues.
  • Continuous Updating: It involves ongoing scrutiny and refinement of expectations, as well as the willingness to invent new interpretations for unprecedented events.
  • Focused Attention: Mindful organizations maintain attention on the present moment, minimizing distractions and resisting the urge to normalize anomalies.
  • Collective Practice: Mindfulness is not just an individual trait but a collective organizational process, embedded in routines, culture, and communication.

What are the five principles of mindful organizing in "Managing the Unexpected"?

  • Preoccupation with Failure: Constantly seeking out and learning from small errors or near misses to prevent larger failures.
  • Reluctance to Simplify: Avoiding oversimplified explanations and embracing complexity, diversity of perspectives, and nuanced understanding.
  • Sensitivity to Operations: Maintaining real-time awareness of frontline operations and the actual work being done, not just plans or reports.
  • Commitment to Resilience: Developing the capacity to absorb shocks, improvise, and recover quickly from setbacks or surprises.
  • Deference to Expertise: Allowing decision-making authority to migrate to those with the most relevant knowledge, regardless of rank or hierarchy.

How do "high reliability organizations" (HROs) differ from typical organizations, according to Weick and Sutcliffe?

  • Operate in High-Risk Environments: HROs function in settings where errors can have catastrophic consequences, so reliability is non-negotiable.
  • Embrace Mindful Practices: They institutionalize the five principles of mindfulness, making them part of daily routines and culture.
  • Learn from Failure, Not Just Success: HROs treat every failure, however small, as a learning opportunity and are wary of complacency from success.
  • Flexible Decision Structures: Authority and decision-making shift dynamically to those with the most expertise as situations evolve.

What practical tools or audits do Weick and Sutcliffe recommend for assessing organizational mindfulness?

  • Mindfulness Audits: The book provides a series of audits (questionnaires) to assess tendencies toward mindfulness or mindlessness in individuals and organizations.
  • Five-Principle Assessments: Specific audits help organizations evaluate their preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise.
  • Mindfulness Organizing Scale (MOS): A concise behavioral measure to quickly gauge the presence of mindful organizing practices.
  • Actionable Debriefs: The authors recommend using audit results to spark discussion, identify areas for improvement, and develop targeted action plans.

How does organizational culture influence the ability to manage the unexpected, according to "Managing the Unexpected"?

  • Culture as an Invisible Hand: Culture shapes what people notice, how they interpret events, and how they respond to surprises.
  • Informed Culture: A culture that values reporting, justice, flexibility, and learning is more likely to detect and respond to unexpected events effectively.
  • Norms and Expectations: Shared values and norms (e.g., openness, support for speaking up, valuing expertise) reinforce mindful practices.
  • Change Through Small Wins: Culture change is gradual and often starts with small, symbolic actions or changes in behavior that accumulate over time.

What are some real-world examples or case studies used in "Managing the Unexpected" to illustrate key concepts?

  • Cerro Grande Wildland Fire: Analyzes how small failures and miscommunications escalated into a major disaster, highlighting the need for mindfulness.
  • Aircraft Carrier Operations: Demonstrates how HROs maintain reliability through wariness, continuous learning, and deference to expertise.
  • Nuclear Power Plants: Explores how complex, high-risk environments require constant coordination, reporting, and sensitivity to operations.
  • Bristol Royal Infirmary: Examines how a lack of informed culture and mindfulness led to preventable fatalities in pediatric cardiac surgery.

How can leaders and managers implement the principles from "Managing the Unexpected" in their organizations?

  • Model Mindful Behavior: Leaders should demonstrate openness to feedback, willingness to learn from errors, and respect for frontline expertise.
  • Encourage Reporting and Learning: Create a just culture where people feel safe to report mistakes and near misses without fear of blame.
  • Foster Diversity and Dialogue: Promote diverse perspectives, adversarial reviews, and open discussion to avoid oversimplification.
  • Invest in Training and Networks: Build resilience through cross-training, scenario simulations, and informal networks for rapid problem-solving.

What are the best quotes from "Managing the Unexpected" and what do they mean?

  • “Unexpected events often audit our resilience.” This means that surprises test how well an organization can stretch without breaking and recover from setbacks.
  • “The hallmark of an HRO is not that it is error-free but that errors don’t disable it.” Reliability is about the ability to contain and recover from errors, not the absence of errors.
  • “Mindfulness is about the quality of attention.” Sustained, focused attention on details and anomalies is crucial for early detection of problems.
  • “Culture is an invisible hand, but it is also a heavy hand.” Organizational culture subtly but powerfully shapes behavior, expectations, and the ability to manage the unexpected.

What are the limitations or challenges of applying the "Managing the Unexpected" approach in typical organizations?

  • Cultural Resistance: Shifting to a mindful, learning-oriented culture can be slow and may face resistance from entrenched norms or hierarchies.
  • Balancing Efficiency and Resilience: Practices that build resilience (like redundancy or slack) may seem inefficient in the short term, conflicting with lean management ideals.
  • Sustaining Mindfulness: Mindful practices require ongoing effort and vigilance; complacency can quickly erode reliability.
  • Translating HRO Lessons: Not all organizations face the same level of risk as HROs, so adapting these principles requires thoughtful customization to context.

About the Author

Karl E. Weick is a renowned American organizational theorist who has made significant contributions to the field of organizational studies. He introduced key concepts such as "loose coupling," "mindfulness," and "sensemaking," which have had a profound impact on understanding organizational behavior and dynamics. Weick currently holds the distinguished position of Rensis Likert Distinguished University Professor at the University of Michigan's Ross School of Business. His work has been influential in shaping modern perspectives on how organizations function, adapt, and manage complexity in rapidly changing environments.

Download PDF

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

Download EPUB

To read this Managing the Unexpected 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: 28
Want to read the full book?
Follow
Listen1 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 25,
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...